Human Wallet 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. This makes Human Wallet a protocol, not a Wallet-as-a-Service. 

With key management decentralized through Human Key Infrastructure, decentralizing the signing layer advances our move to Wallet as a Protocol (WaaP). This makes Human Wallet the only wallet infrastructure to be decentralized and censorship resistant, with zero trust security.

In 2PC MPC, a private key is split into two independent signing shares. This removes unilateral control over funds and opens a design space for zero-trust security, with no single point of failure. The user holds one share. A decentralized network operates the second share, verifies intent against policy, and presents a human-readable summary before it co-signs.

What Changes in our Infrastructure

Today, Human Wallet uses 2PC: the user holds one key share, and a secure enclave holds the second. Every signature requires both.

We are moving that security share from an enclave to Ika’s decentralized 2PC MPC network. The share will be operated by a non-collusive set of nodes rather than a single component. Operationally, this replaces a single enclave dependency with a decentralized service while preserving the current user experience and intent format. Rollout will begin soon, with staged enablement.

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.

The flow remains the same; the underlying architecture becomes decentralized. Policy and access controls continue to apply at the signing, including 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.

Even with 8 nodes (labeled as highly decentralized), legacy MPC solutions struggle to get low latency or high throughput, capable of generating only single digit signatures per second. 2PC MPC distributes the co-signer across hundreds of nodes and can scale to 10,000 signatures per second. – David, co-founder, Ika

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.

Wallet as a Protocol (WaaP), not Wallet as a Service (WaaS)

Wallet as a Service is good for onboarding. It offers ready-to-use, wallet infrastructure so dApps can ship branded wallets with familiar logins. The tradeoffs: extreme security and long-term UX problems. Keys are custodied not only by the centralized social logins, but also by the insecure iframe. In most cases, while not publicized, the key is often available to the WaaS company; dApps can sign any transaction on behalf of the user, effectively owning the user’s wallets.

As a result, WaaS creates different wallets for each dApp, so that logging into malicious dApp A cannot drain the wallet from dApp B. But this means wallets are locked into particular dApps, and you cannot use the benefits of most crypto wallets like MetaMask: being able to use the same wallet on multiple dApps. Imagine creating a new PayPal account for any new website you pay on, and transferring funds between your 100+ PayPal accounts to the new website. You would never use PayPal. In fact, you would likely never use any traditional financial applications like Apple Pay, Google Pay, bank accounts, etc., if they worked this way, nor would you use wallets if they worked this way. But this is how WaaS must work due to their custody model.

Fragmented on-chain experience sustains rent-seeking models.

Per-app wallets don’t just contain risk. They also align with WaaS’s pay-per-wallet revenue model. The result is fragmented accounts, lost composability and reputation, and a recurring cost for developers, commonly about 3–8 cents per wallet per month.

Wallet as a Protocol replaces rentable services with accounts that users own. The user creates one universal account that works across dApps and can be cross-authenticated across devices. Developers don’t pay any per-wallet fees. Revenue comes from the underlying Human Network economics that support the human.tech stack.

Security is enforced by a decentralized cryptographic protocol. 2PC MPC helps protect even if a user device is compromised, a dApp is compromised, or a malicious frontend attempts to trick the user. These are common attack paths in WaaS and seed phrase based wallets.

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.

Built as a protocol, Human Wallet enables developers to integrate seamless wallet experiences into their applications. Human Wallet 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 Human Wallet (Waap) → WaaP Developer Docs

FAQ

1. What’s changing in Human Wallet?

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 Human Wallet 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