dWallet Types Overview

dWallets use 2PC-MPC (Two-Party Computation Multi-Party Computation) to split cryptographic keys into shares. There are three main types, each with different trust and control models.

Zero-Trust dWallets

A Zero-Trust dWallet has two shares:

• User share: Encrypted and controlled by you
• Network share: Held by the Ika network

Why both shares matter: Without your user share, the network cannot create any signatures. You maintain control because your share is always required for signing operations.

---

Shared dWallets

A Shared dWallet has a public user share stored on-chain. This means:

• User share: Public and accessible on the network
• Network share: Held by the Ika network

What this means: Since both shares are accessible to the network, it can create signatures without user interaction. This enables powerful automation use cases like DAO treasuries, smart contract-controlled wallets, and automated trading systems.

---

Imported Key dWallets

An Imported Key dWallet brings an existing private key into the dWallet system. You can import it as:

Zero-Trust Imported Key:

• Split into user share (encrypted, controlled by you) and network share
• Both shares required for signing
• Original private key remains a potential security concern

Shared Imported Key:

• User share is public, network can sign on your behalf
• Original private key remains a potential security concern

The security consideration: Your original private key still exists outside the dWallet system. If compromised, it bypasses the dWallet security model entirely.

---

Which One Should You Pick?

Go with Zero-Trust if:

• You need user-controlled wallets where users maintain full signing authority
• Building custody solutions or personal wallets
• Regulatory or compliance requirements mandate user participation in signing
• You want maximum security with the zero-trust 2PC model

Pick Shared if:

• Building DAOs that need automated treasury management
• Creating smart contract systems that sign programmatically
• Developing automated trading bots or autonomous systems
• You want to delegate signing authority to the network or smart contracts

Choose Imported Key if:

• You need to bring existing keys into the dWallet system
• You can configure it as Zero-Trust (user control) or Shared (network control)
• Be aware that your original private key remains a security consideration

Ready to Get Started?

1. Get your dev environment set up - Set up a local network for development
2. Set up encryption keys - Required for Zero-Trust and Zero-Trust Imported Key dWallets