Ika-Based Wallet Expands for AI Agents

human.tech has expanded the Ika network-based wallet protocol into a distributed signature infrastructure for AI agents and decentralized applications. The plan is to provide the wallet not as a service managed by a specific entity, but as a protocol that combines distributed signatures and authority control.

In a press release on the 24th, human.tech introduced Wallet-as-a-Protocol (WaaP) in connection with Ika's 'Squid Mode'. The WaaP official site explains that Squid accounts sign using a 2PC-MPC method in conjunction with the Ika network.

2PC-MPC divides the signing authority into two parts, preventing either side from independently approving transactions. In the WaaP structure, the signing keys are shared between the WaaP infrastructure and Ika's distributed validator network. This design ensures that no agent or single server holds the entire key.

The focus of this announcement is more on the authority management issues of AI agents rather than the competition among general wallet services. The official document from human.tech states that AI agents should be designed not to directly hold private keys or raw API keys. Agents transact through the WaaP wallet, and critical actions are processed with verified human approval within pre-set authority limits.

The human.tech document describes this structure as △Delegated Custody △Credential Separation △Human Approval △Scope-Limited Authority. The aim is to reduce the risk of fund movement that may occur when agents perform payments, API calls, or automation tasks. It emphasizes that restrictions are enforced at the protocol level rather than through policy documents.

The combination of Ika and human.tech is not a newly emerging one-time partnership. Both parties announced the initial unveiling of WaaP on October 22, 2025, stating their intention to move wallet signing and access control to a distributed network. At that time, Ika presented a 2PC-MPC signing layer, while human.tech proposed wallet infrastructure to replace the fees, lock-in, and fragmentation issues of the existing Wallet-as-a-Service (WaaS).

WaaS is typically a model where companies provide user wallet creation and management features as a service. In contrast, WaaP aims for a protocol-based infrastructure where multiple entities share the responsibilities of signing and access control rather than a single entity fully managing the wallet. As the cases of AI agents handling funds and authority increase, this control structure becomes more critical.

There are discrepancies in the figures. The official document from human.tech presented over 43 million credentials issued, more than 2 million verified humans, and over $500 million (approximately 6.925 billion KRW) in protected assets as of August 7. In contrast, the redistributed press release mentioned 51 million credentials, 2.1 million accounts, and $512 million (approximately 7.091 billion KRW) in protected assets.

The criteria for the increased figures and the timing of changes have not been confirmed in separate documents. At the article stage, it is necessary to distinguish between the figures from the official document and those from the redistributed press release. Even if the operational metrics are rapidly changing services, it is difficult to juxtapose them as the same figures if the reference date and calculation methods differ.

The support chain notation also differs slightly. The WaaP official site mentions EVM, Stellar, and SUI under the multi-chain support section. The redistributed press release listed EVM, SUI, and Solana.

Ika has a history of separately announcing a bridging-less asset control layer for Solana. However, the product page for the public wallet protocol and the wording in the press release are not entirely the same. Further announcements are needed to clarify how the Solana support range is implemented within the WaaP product.

For Korean readers, this matter can be seen as a branch of AI agent payment infrastructure. Our publication previously reported that the way agents handle payments and authority is emerging as a separate experimental axis in the crypto industry through Algorand's x402 settlement increase and Rain AI payment alliance launch.

This announcement is a case that places wallet authority and signing structure at the forefront of that trend. While x402 or the agent payment alliance focused on payment messages and settlement procedures, WaaP addresses how agents receive and limit access to funds. It is closer to a control mechanism before the execution of payments.

Public reactions have been confirmed mainly through project accounts and adjacent communities. The WaaP and human.tech accounts have repeatedly disseminated the 2PC-MPC structure and agent wallet messages. Independent media's in-depth verification or large-scale developer adoption metrics have not been revealed within this confirmation scope.

human.tech emphasizes that AI agents do not directly hold private keys and act within human approval and scope-limited authority as the core message. The key question moving forward is whether the expanded narrative of the press release translates into actual usage, security verification, and product implementation across supported chains.