Frequently Asked Questions

Keys simplified. That's it.

A self-custodial MPC wallet where two independent key shares are created together — one in your browser, one on the server. No single private key ever exists. Neither party holds the full key.

Multi-Party Computation — a cryptographic technique where multiple parties compute a function together without revealing their individual inputs. In kexify, two key shares sign a transaction without ever combining into a full private key.

Yes. Built on Coinbase's cb-mpc library (our fork). Frontend: kexify-web.

Yes — free forever, no subscription, no ads. kexify was built by its creator for personal use. There's no business model because it's not a business. It's a tool that needed to exist.

By design. A wallet should do one thing well — hold and sign. Swaps, lending, and bridges are already solved by dApps like 1inch, Aave, and MyEtherWallet. Connect to any of them via WalletConnect. Fewer features means fewer bugs and a smaller attack surface.

Three principles: keep it simple, stay focused on being a wallet, and optimize only for UX and security. Every feature decision is filtered through these. If it doesn't make the wallet easier to use or more secure, it doesn't ship.

No. kexify is a personal project provided as-is, with no warranty. You are responsible for your own keys and funds. That said, the code is open source — you can verify everything yourself.

Anyone who wants MPC security without the complexity. Built by an engineer, for engineers — but designed so anyone can use it.

Nobody holds the full key. One share is in your browser (encrypted with passkey or passphrase), the other on the server (encrypted with AES-256-GCM). Both must cooperate to sign.

Use Recovery Mode. Export your server key share beforehand, then sign locally in your browser with both shares. The frontend is open source, and there's also a CLI tool to combine both shares into a full key. No server needed.

No. The server only has one share — it cannot sign alone. The 2-of-2 MPC protocol prevents unilateral signing by design. The frontend is open source — you can audit the code and even self-host it.

Browser: AES-GCM encrypted with WebAuthn passkey PRF or passphrase (PBKDF2). Server: AES-256-GCM with per-user HKDF-derived key. All in transit: TLS 1.3.

Before signing, kexify automatically checks the recipient address and token contract against GoPlus Security's database for known scams, phishing addresses, and malicious contracts. If a risk is detected, you'll see a warning before confirming. Enabled by default — no setup needed.

Both use MPC, but kexify is open source and fully self-custodial — you can export both key shares and sign offline anytime. ZenGo controls the recovery share and requires their servers. kexify also adds a Policy Engine (spending limits, address whitelists) that ZenGo doesn't have. And kexify is free — no swap fees, no premium tiers.

Think of it like a safe that needs two keys. You hold one key, the server holds the other. Neither can open the safe alone. But the server also acts as a guard — before turning its key, it checks your rules: Is this amount within the spending limit? Is this address on the approved list? Is the account frozen? If any rule is violated, the server refuses to co-sign and the transaction simply can't happen.

The server only enforces rules you set yourself. And if you ever disagree with the server, you have an exit: export both key shares and sign transactions completely on your own in Recovery Mode. The server can never hold your funds hostage.

EVM chains (Ethereum, Base, Avalanche, Polygon, Arbitrum, BSC...), Bitcoin, Solana, XRP, TRON, TON, Algorand, Cardano, Stellar, Litecoin, and Bitcoin Cash — plus their testnets and tokens.

Initiate from the app or connect via WalletConnect. Both key shares participate in multiple MPC rounds (~6 seconds) to produce a valid signature.

A self-imposed security layer that lets you set rules the server enforces before co-signing. Even if someone gains access to your browser, policies limit what they can do.

Spending limits — cap the USD value per transaction. Address whitelists — only allow transfers to pre-approved addresses. Both are enforced server-side before the server agrees to co-sign.

To prevent an attacker from changing your policies and immediately exploiting them. When you create or modify a policy, it takes 24 hours to activate. If you didn't make the change, you have time to freeze your account.

Yes. Freeze via email link. All signing is blocked for a mandatory 24 hours. This gives you time to secure your account if you suspect unauthorized access.

A set of advanced controls for power users: UTXO selection, Replace-By-Fee (RBF), custom nonce, sign-only mode (sign without broadcasting), separate broadcast, raw message signing, custom RPC endpoints per chain, and full key share backup. Hidden by default — toggle it on in settings when you need granular control.

Yes. Anonymous login lets you create a wallet without any email or personal information. Your key shares are stored locally in the browser, secured with a passphrase. This mode is designed for technical users who understand blockchain key management — there's no account recovery if you lose your passphrase and key shares.

kexify runs entirely on free infrastructure. Each account stores encrypted key shares on the server, so a cap of 3 accounts per user keeps storage and compute costs sustainable without charging anyone.

Each MPC signature requires multiple rounds of computation between your browser and the server. On UTXO chains (Bitcoin, Litecoin, etc.), every input needs a separate signature. Capping at 10 keeps signing time reasonable and prevents free-tier server resources from being overwhelmed. For most transactions, 10 inputs is more than enough.

kexify uses free public RPC endpoints by default. These can be rate-limited, congested, or occasionally down. For better reliability and speed, go to Settings and replace the default RPC with your own endpoint (from Alchemy, Infura, QuickNode, etc.) — most offer generous free tiers with an API key.

Yes. Magic link emails, API requests, and signing operations are all rate-limited to prevent abuse of the free infrastructure. If you hit a limit, wait a short while and try again. These limits are generous enough for normal use — they only kick in under unusual activity patterns.

Turnstile is a privacy-friendly CAPTCHA alternative that runs invisibly in the background. It protects the free infrastructure from bots and automated abuse — without annoying puzzles or tracking. You should rarely notice it.

ECDSA (secp256k1) for EVM/Bitcoin chains, EdDSA (Ed25519) for Solana/Stellar. Powered by Coinbase's cb-mpc WASM library running directly in your browser.

Coinbase's threshold cryptography library. We use a fork compiled to WebAssembly for in-browser execution.