Security

​

What “Zero-Trust” Means

Your signing keys never exist in complete form. They’re generated using distributed key generation (DKG) across the Ika network:

1. Your share - Encrypted with your passcode, stored in the Ika network
2. Network share - Held by Ika validators

To sign anything, both shares must participate through secure multi-party computation. But they never combine into a complete key. The signature is produced cryptographically without either party learning the other’s share.

​

What Umi Never Has

• Your complete private key (it never exists in complete form)
• Your passcode (only you know it)
• The ability to sign without your approval
• Access to move your funds unilaterally

​

What Umi Does Have

• Your encrypted key share (but can’t decrypt it without your passcode)
• Your public addresses (these are public by design)
• Your transaction history (for display in the app)

​

What the Ika Network Never Has

• Your complete private key
• Your passcode
• Your encrypted key share’s decryption key
• The ability to sign without your participation

​

The Security Model

For someone to steal your funds, they would need:

1. Your passcode (to decrypt your key share)
2. Access to the Ika network’s share (held by distributed validators)
3. To bypass your Umi Signer policies
4. To compromise all of these at the same time

This is dramatically more secure than:

• Centralized exchanges - One company holds everything
• Traditional wallets - One seed phrase controls everything
• Hardware wallets - One device holds everything

​

Multi-Layer Security

​

Layer 1: Distributed Key Generation

Your keys are generated using DKG across the Ika network. No single party ever has the complete key.

​

Layer 2: Umi Signer Policies

Before any signature is produced, your on-chain Umi Signer enforces:

• Spending limits (per transaction, daily, monthly)
• Address whitelists and blocklists
• Timelock delays between signatures
• Quota-based rate limiting
• Two-factor authentication requirements

​

Layer 3: TEE Validation

For spending-related transactions, a Trusted Execution Environment:

• Parses the actual transaction bytes
• Extracts recipient and USD value
• Validates against your configured limits
• Signs an attestation that the on-chain contract verifies

​

Layer 4: Agent Isolation

If you use AI agents:

• Agents have their own keypairs (separate from your dWallet)
• Agents must be whitelisted in your Umi Signer
• All agent transactions go through policy enforcement
• Agents cannot modify their own permissions

​

Gas Accounts and Treasury

Umi maintains gas accounts to abstract away the complexity of holding native tokens on each chain.

​

How Gas Accounts Work

1. Auto-generated keypairs: Umi generates secure keypairs for each supported chain
2. Encrypted storage: Private keys are encrypted with AES-256-GCM
3. Balance monitoring: Continuous monitoring of gas account balances
4. Auto-refill: When balances drop below thresholds, accounts are refilled from a USDC treasury

​

Treasury Security

• USDC treasury held on Solana
• Separate encrypted keypair
• Cross-chain refills via RocketX bridge
• Auditable refill history

​

Your Gas Credits

When you deposit to your gas credit balance:

• Your deposit is converted to USD-denominated credits
• When you transact, Umi pays gas from its chain-specific accounts
• Your credit balance is debited the USD equivalent
• You never need to hold gas tokens yourself

​

Protecting Your Account

​

Use a Strong Passcode

Your passcode encrypts your key share. Make it at least 12 characters with a mix of letters, numbers, and symbols.

​

Protect Your Login

Your Google/Apple/Facebook account is how you access Umi. Use strong passwords and 2FA on those accounts.

​

Configure Policies

Set up spending limits and timelocks in your Umi Signer. Even if something goes wrong, the damage is limited.

​

Monitor Activity

Review your transaction history and agent activity regularly. Set up notifications for large transactions.

​

Verify Transactions

Always check transaction details before confirming. Make sure the destination and amount are correct.

​

Be Careful with DApp Connections

Only connect to DApps you trust. Review what permissions they’re requesting.

​

If Something Goes Wrong

​

Lost Your Passcode?

Your passcode encrypts your key share. Without it, you can’t sign transactions. Umi cannot recover your passcode. This is a security feature - if we could recover it, so could an attacker. If you have a beneficiary configured, they can access the wallet after your inactivity period.

​

Lost Access to Your Login?

Recover your Google/Apple/Facebook account through their normal recovery process. Your Umi account is linked to that identity.

​

Suspicious Activity?

1. Pause any active agents immediately
2. Review recent transactions
3. Check your Umi Signer policies
4. Contact support for investigation

Note: We cannot access or move your funds, but we can help investigate.

​

Zero-Trust Wallet Mode

For maximum security, you can enable zero-trust wallet mode:

• Requires passcode for every sensitive operation
• Additional encryption layer on signing requests
• Recommended for large balances

​

TEE Technical Details

Umi uses AWS Nitro Enclaves for Trusted Execution Environment validation:

​

Platform Configuration Registers (PCRs)

The TEE’s code is verified through PCRs:

• PCR0: Enclave image hash
• PCR1: Linux kernel hash
• PCR2: Application hash

Any code modification changes these values, making tampering detectable.

​

Attestation Flow

1. TEE receives raw transaction bytes
2. Parses transaction (supports EVM, Solana, Sui, Bitcoin, etc.)
3. Extracts recipient address and amount
4. Fetches USD value from price oracles
5. Validates against user’s policy configuration
6. Signs attestation with TEE’s Ed25519 key
7. On-chain contract verifies signature against registered enclave

​

Security Properties

• Attestations expire after 5 minutes (no replay attacks)
• TEE code is publicly verifiable
• Enclave key never leaves the secure environment
• Real transaction values, not user-provided claims

​

Audits and Transparency

​

Smart Contracts

Umi’s smart contracts on Sui are:

• Open source and verifiable on-chain
• Built on Ika’s audited cryptographic protocols

​

Security Reviews

The core signing technology has been reviewed by security researchers. We’re committed to regular security assessments.

​

Bug Bounty

If you discover a security vulnerability, please report it responsibly. Contact security@umi.app.

​

Summary

Umi’s security comes from multiple independent layers:

1. No complete keys - Keys are split and never combined
2. Policy enforcement - Rules execute on-chain, trustlessly
3. TEE validation - Real transaction values verified in secure hardware
4. User control - You set the rules, you control the caps

Neither Umi, the Ika network, nor any third party can unilaterally access your funds. That’s what zero-trust means.