Blockchain wallet development is mainly a key management and security project with a user interface on top. This guide covers the five decisions that set cost, risk and legal exposure: who holds the keys, which chains to support, which form factor to ship, how users see what they sign, and how to secure the build.
What is a blockchain wallet?
A blockchain wallet is software or hardware that stores the private keys for blockchain addresses and uses those keys to sign transactions. It does not hold coins: the assets stay on the chain, and the wallet proves that the user may move them. Whoever controls the keys controls the funds.
Wallets are grouped in two ways:
- Custodial or non-custodial. In a custodial wallet, a company holds the keys, while in a non-custodial wallet the user holds them, usually backed up as a seed phrase.
- Hot or cold. A hot wallet runs on a device connected to the internet, while a cold wallet keeps keys offline, for example on a hardware device.
Most build decisions below follow from these two choices.
Decision 1: who controls the keys
| Model | How it works | Typical users | Main risk |
|---|---|---|---|
| Custodial | The operator holds keys on its servers, usually in hardware security modules (HSMs) or an MPC system. Users log in with a password. | Exchanges, fintech apps, users new to crypto | The operator becomes a large target for attackers. In many countries, the operator also becomes a regulated custodian. |
| Non-custodial seed phrase | The device creates keys from a BIP-39 mnemonic and derives addresses with BIP-32 and BIP-44. | Experienced crypto users and self-custody products | Users lose or leak the phrase, or malware on the device steals it. |
| MPC (threshold signatures) | Key shares sit on the device, a server and a backup. The full key never exists in one place. | Consumer apps that want self-custody without seed phrases, and institutions | Complex cryptography, dependence on one vendor, and a hard recovery design |
| Smart account | A contract account under ERC-4337, or a normal account that delegates to contract code under EIP-7702. Signers, limits and recovery are programmable. | EVM apps that want passkeys, sponsored gas and session keys | Contract bugs, support on some chains only, and reliance on bundlers and paymasters |
Teams often combine these models. A common design in 2026 uses an MPC or passkey signer to control a smart account, so users sign up without a seed phrase and can recover the account on-chain. Since EIP-7702 went live on Ethereum mainnet with the Pectra upgrade on May 7, 2025, an existing Ethereum account can use smart account features without moving to a new address.
Legal exposure depends on custody
A wallet operator that holds user funds, or can move them alone, likely falls under custody and money transmission rules. In the EU, custody of crypto assets is a licensed service under MiCA. In the US, FinCEN guidance from 2019 treats providers of unhosted, non-custodial wallet software differently from custodial money transmitters. Features such as built-in swaps, fiat on-ramps or a power to freeze funds can change the legal analysis, so get legal advice before you finalize the design.
Decision 2: which chains to support
Each chain family has its own cryptography, address format and transaction model:
- EVM chains share secp256k1 keys and one address across networks, so adding another EVM chain is mostly configuration.
- Bitcoin adds UTXO selection, several address types and partially signed transactions (PSBTs).
- Solana uses ed25519 keys and its own transaction format.
- Polkadot uses sr25519 keys and SS58 addresses. See Polkadot wallet development.
Every new chain family adds a signing library, a node or RPC provider, a fee estimator, an indexer and a test suite, so start with the chains where your users already hold assets.
Decision 3: form factor
| Form factor | Strength | How it connects to apps |
|---|---|---|
| Mobile app | Secure enclave storage and biometric login | WalletConnect and an in-app browser |
| Browser extension | Most dApps look for a wallet here | An injected provider (EIP-1193), with EIP-6963 so several extensions can coexist |
| Embedded wallet | Lives inside one app, and users may not notice it | The provider's SDK |
| Desktop or hardware integration | Serves users with large balances | USB or Bluetooth, through the hardware vendor's libraries |
The Web3 wallet guide covers dApp connections in more depth.
Decision 4: how users see what they sign
Most wallet losses come from users who sign a malicious request, not from broken cryptography. A safe signing screen does five things:
- It decodes each transaction into plain language.
- It shows EIP-712 typed data in readable form.
- It warns about unlimited token approvals and
setApprovalForAllrequests. - It simulates the transaction and shows the balance changes.
- It flags addresses known to belong to drainer kits.
The signing screen often takes more engineering work than sending tokens.
Security essentials
- Create keys with a vetted cryptographic library and the platform's secure random source, and do not write your own cryptography.
- Store secrets in the iOS Secure Enclave, Android Keystore or StrongBox, or encrypt them with a key derived from the user's authentication.
- Keep keys out of logs, crash reports, analytics and the clipboard history.
- Pin dependencies and review every update. In December 2023, attackers published malicious versions of Ledger's Connect Kit library to npm, and dApps that loaded it showed drainer prompts to users.
- Order an independent security assessment of the app. For smart accounts, also order an audit of the contracts (see smart contract audits).
Build sequence
- Choose the custody model, chains and form factor, and write down the threat model.
- Implement key generation, storage, backup and recovery, and test recovery on real devices.
- Add chain clients, balance and history indexing, and fee estimation.
- Build the send, receive, swap or staking flows, with transaction decoding and simulation.
- Add dApp connections, then run a security assessment and a staged rollout.
Blockchain wallet development cost and effort
As a rough guide, three to four engineers can build a basic wallet, meaning a non-custodial, EVM-only mobile app with send, receive and WalletConnect, in three to four months. Another chain family, MPC, smart accounts with paymasters, fiat on-ramps, swaps and hardware wallet support each add weeks or months.
Running costs continue after launch, including RPC and indexing infrastructure, monitoring, chain upgrades and app store updates. White-label wallet SDKs and embedded wallet providers shorten the first build, but they charge per-user fees and tie the product to one vendor.
How to evaluate a blockchain wallet development company
A blockchain wallet development company usually delivers the apps, the key management layer, chain integrations, a backend for balances and notifications, and launch support. Ask each firm these questions:
- Which key management models has the firm shipped to production: seed phrase, MPC or smart accounts?
- Which cryptographic libraries does it use, and who audited them?
- How does the recovery flow work, and has it been tested on real devices?
- Who performed the last independent security assessment of a wallet the firm built, and can you read the report?
- Who owns the code and the signing infrastructure after delivery?
- Which recurring costs remain, such as MPC vendor fees, RPC providers and indexers?
For a consumer cryptocurrency wallet, the cryptocurrency wallet guide covers features and app store rules in more detail.
Frequently asked questions
Is a non-custodial wallet free of regulation?
Not automatically. Rules are often lighter for non-custodial software, but built-in swaps, fiat ramps or a power to freeze funds can bring a wallet into scope.
Should a wallet use MPC or smart accounts?
MPC works on any chain, because it produces ordinary signatures. Smart accounts offer on-chain logic such as spending limits and recovery, but only on chains that support them. Many products use both.
Can I build on an open-source wallet?
Yes, and many teams do. Check the license and the code quality, and plan to apply each upstream security fix.
How long does blockchain wallet development take?
A non-custodial, EVM-only mobile wallet with basic features takes a small team about three to four months. Extra chain families, MPC, smart accounts and swaps extend that time.