Crypto wallet development is mostly a key management and security job, because a wallet does not store coins; it stores or controls the keys that authorize transactions. The first decision is who holds those keys, and that choice shapes the rest of the product.
This guide compares the custody models, lists what a non-custodial wallet must do, and gives the steps to create a crypto wallet app. It also covers the main security risks and an estimate of cost and time.
Three custody models
| Model | Who controls the keys | Strengths | Trade-offs |
|---|---|---|---|
| Custodial | The operator, on its own servers or through a custody provider | Password resets, simple app flows, easy links to bank payments | Regulated as custody in most countries. One breach exposes every user. |
| Non-custodial with a seed phrase | The user, through a BIP-39 recovery phrase | No operator risk, and the wallet works with every dApp | A lost phrase means lost funds. Phishing for recovery phrases is common. |
| MPC or smart account | Key shares split between the user's device, the operator or guardians, or rules in a contract | Recovery without one secret, spending rules, sponsored fees | More components, dependence on a vendor, uneven support across chains |
A custodial wallet works like a bank account, and a non-custodial crypto wallet works like cash. MPC (multi-party computation) splits a signing key into shares, so no single device or server ever holds the whole key.
Smart accounts on EVM chains move the wallet's logic into a contract, following the ERC-4337 standard. Ethereum's Pectra upgrade in May 2025 added EIP-7702, which lets a normal address use smart account code. That brings social recovery, session keys, batched transactions and fees paid in tokens. The Fusaka upgrade in December 2025 then added a built-in check for P-256 signatures (EIP-7951), the curve that passkeys and phone secure chips use, so a smart account can now accept a passkey as its signer at low cost.
What a non-custodial crypto wallet must do
Key generation and storage
The wallet takes randomness from the operating system's secure random generator and turns it into a BIP-39 recovery phrase, which produces a master seed. Accounts are derived from that seed along standard paths (BIP-32 and BIP-44), though Solana, Cosmos and some other chains use their own.
On mobile, the wallet encrypts the seed with a key held in the iOS Secure Enclave or the Android Keystore, and biometrics unlock that key. Desktop apps and browser extensions encrypt the seed with the user's password and a strong key derivation function.
Transaction building and signing
The wallet fetches the nonce and a fee estimate, builds the transaction, shows the user what it does, and signs it on the device. Showing what it does is the hard part. The wallet has to decode contract calls, simulate the result, and warn about unlimited token approvals and EIP-712 permit signatures that can let an attacker take funds. Many users have lost assets by signing messages they could not read.
Chain data
Balances, token lists, NFT metadata, history and prices come from RPC nodes and indexers. Most teams use provider APIs rather than run nodes for every chain, which costs less but makes the wallet depend on the provider for privacy and uptime.
dApp connections
Browser extensions inject an EIP-1193 provider into web pages and announce themselves through EIP-6963. Mobile wallets connect to dApps through WalletConnect. If dApp access is central to your product, the MetaMask alternatives guide covers extension architecture.
How to create a crypto wallet app: build steps
- Pick the custody model and confirm its legal consequences in each country where you operate.
- Pick chains with care. Each non-EVM chain, such as Bitcoin, Solana, Cosmos or TON, needs its own derivation, signing, fee and data logic.
- Use audited cryptography libraries. Never write elliptic-curve math yourself.
- Design the transaction review screen with call decoding, simulation, approval warnings and detection of poisoned addresses.
- Build backup and recovery flows and test them with real users who are not technical.
- Commission a security review of key storage, signing, update channels and any smart account contracts. Contracts also need a smart contract audit.
Security risks to design against
- Weak randomness. Some wallets created keys from poor randomness, and attackers emptied those wallets years later. The 2022 Wintermute loss of about $160 million came from a vanity address tool with weak key generation.
- Supply chain attacks. A compromised dependency or update channel can steal seeds. Pin dependency versions, sign builds and limit who can publish releases.
- Blind signing. A wallet that shows raw hex for a contract call leaves users open to theft. Simulate each call and explain the result in plain words.
- Address poisoning. Attackers send tiny amounts from look-alike addresses, so users copy the wrong address from their history.
- Server breaches. In custodial and MPC designs, attackers target the operator's infrastructure. Keep signing services isolated from other systems.
Crypto wallet app development cost and timeline
This is an estimate from stated assumptions, not a quote. A mobile non-custodial wallet for EVM chains that shows tokens and NFTs, offers swaps through an aggregator API and connects through WalletConnect needs about two mobile engineers, one backend engineer, a designer and part-time QA for four to six months.
- Each extra non-EVM chain adds several weeks.
- An MPC vendor SDK speeds up key management but adds a fee per user.
- A security review needs its own budget from the start of the project.
- Ongoing costs include RPC and indexer providers, app store releases and security fixes.
Related guides cover Web3 wallets for dApp users, blockchain wallet architecture and DeFi wallets.
Frequently asked questions
Is a custodial or a non-custodial wallet safer to build?
Neither is safer in every case. A custodial wallet puts the risk and the regulation on the operator; a non-custodial wallet puts the risk on users, who may lose their phrases. MPC and smart accounts try to balance the two.
How do I create a crypto wallet without writing one from scratch?
You can fork an open-source wallet if its license allows it, but check carefully, because some popular wallets restrict commercial forks. You also become responsible for keeping up with security fixes. Wallet SDKs and MPC vendors are another starting point.
Do I need my own blockchain nodes?
Not at first. Most wallets use hosted RPC and indexing providers. Run your own nodes later for reliability, privacy or chains with few providers.
What does account abstraction change for wallets?
It lets an account be a contract with its own rules, which allows recovery without seed phrases, spending limits, batched actions and sponsored gas. Contract bugs can also lock or lose funds, so smart accounts need audits.