human.tech’s Wallet-as-a-Protocol (WaaP) is migrating its 2PC signing layer to Ika’s 2PC MPC network, decentralizing programmable security and access controls across a non-collusive network designed for real-world throughput.

Protocols are at the heart of WaaP. It’s what makes it secure, trustless, and highly resilient to downtime or exploits. The addition of Ika as a module within the WaaP framework allows us to move beyond centralized Wallet-as-a-Service providers and bring easy onboarding infrastructure on-chain. WaaP now includes two decentralized protocols under the hood: key generation and management with Human Network and transactions policies and signing with Ika.

What is 2PC MPC and how does this advance wallet technology?

In 2PC MPC, a private key is split into two independent signing shares. This removes single points of failure in the user’s device, the user themself, or any third party that interacts with the key. The “2” in “2PC” corresponds to the user and a network. The user holds one share of the key. This key can be requested from the Human Network at any time. A decentralized network, like Ika, operates the second share, verifies intent against policy, and presents a human-readable summary before it co-signs.

What Changes in our Infrastructure

WaaP was designed from the ground up as a 2PC system. The default WaaP setting elects a secure enclave to hold the signing key share. Now, dApps can choose to store that security share to Ika’s decentralized 2PC MPC network. The share will be operated by a non-collusive set of nodes rather than a single component. This gives devs that seek lower trust assumptions than an enclave dependency the option to use a decentralized service as the signing backend while preserving the current user experience and intent format.

Over the past year, we optimized the security layer for policy engines and transactional simulation. It is now ready to run on a non-collusive network. Rollout will be complete by end of Q4 2025 and progressive releases to unlock the full feature set of Ika’s programmable policies and cross-chain abstraction.

The developer and user experience will remain the same; the underlying architecture for signing is further decentralized. Transaction simulation policies, user security settings, and access controls will now execute on Ika  spending limits, time-locks, extra authorization for higher risk actions, and high-value transfers.

2PC vs Legacy MPC

Is less actually more?

MPC structures typically use a t/n threshold, where t nodes out of n can sign to execute a transaction (e.g., 3/5). This design excludes the user from the signing process; if the network is attacked, corrupted, or colluded, it can steal all the user’s funds. Additionally, all users rely on the same shared committee of nodes, creating a centralized trust point.

2PC-MPC changes what a wallet can be,” said David Lachmish, Co-Founder of Ika. “It removes unilateral control, scales to real-world throughput, and for the first time, makes decentralized, flexible and secure wallets practical at the infrastructure level.

2PC MPC, on the other hand, requires user authorization for every transaction and ensures the full private key is never exposed or reconstructed in one place. The Ika network can compute MPC, like two-party ECDSA signatures, across hundreds, or even thousands of nodes. This is a vast improvement over small scale MPC implementations and helps scale the decentralization of critical compute infrastructure.

Developer Experience

Integrate in minutes. The quick start gets a wallet working in about five minutes. WaaP is EIP-1193 compliant, so your dApp uses the standard provider interface common across Ethereum wallets; copy-paste quick start examples are available to get running fast.

WaaP enables developers to integrate seamless wallet experiences into their applications. WaaP supports mass onboarding while ensuring strong security. Additional à la carte modules for developers include a dev portal, cross-chain gas tank to sponsor gas fees, blind signing protection module, and MFA for high value transfers.

Start building with WaaP → WaaP Developer Docs

FAQ

1. What’s changing in WaaP?

We’re moving our 2PC signing layer to Ika’s decentralized 2PC MPC network, replacing a single enclave with a non-collusive node set. This decentralizes security while keeping the same user flow.

2. What is 2PC MPC?

It splits the private key into two shares: one held by the user, one by a decentralized network. Both are required to sign, and the full key is never reconstructed.

3. Why is this important?

It removes single points of failure, prevents unilateral control, and scales to real-world throughput, enabling true zero-trust security.

4. What’s “Wallet as a Protocol”?

It means WaaP runs as open infrastructure, not a custodial service. Users own their universal account; developers integrate without per-wallet fees or iframe custody.

5. How does it differ from WaaS?

WaaS relies on centralized custody and fragmented per-app wallets. WaaP is decentralized, censorship-resistant, and user-owned – built to function as protocol infrastructure.

About human.tech

human.tech is a suite of technologies designed to enhance personal freedom, privacy, and financial autonomy. human.tech provides innovative solutions for secure identity, data ownership, and private transactions, ensuring that technology remains a tool for human empowerment.

Telegram: t.me/humantechofficial