Decide this first: who holds the keys
Before a line of code is written you must answer one question, because the answer changes the architecture, the cost and your legal exposure.
Non-custodial — the user holds the keys
Keys never leave the user device and you cannot access their funds. Your liability is low and it matches the principles of the space. The cost is that a lost recovery phrase means permanently lost funds, and you cannot help. Most wallets on the market work this way.
Custodial — you hold the keys
Far easier for mainstream users, since a forgotten password can be reset. In exchange you take on custody of other people money, which demands serious security infrastructure and, in many jurisdictions including Thailand, may require a digital asset business licence. We recommend legal advice before choosing this route.
Capabilities we build
- Wallet creation and recovery via BIP-39 12 or 24 word phrases
- Multiple networks in one app, switchable without creating a new wallet
- Balances and transaction history for both native coins and tokens
- Send and receive with QR scanning and an address book
- NFT display
- In-app swaps through DEX integration
- dApp connectivity over WalletConnect
- Biometric unlock on mobile
- Multi-signature approval for corporate wallets
The mistake we see most often
The most common serious error is letting the private key or recovery phrase leave the user device — through an unencrypted cloud backup, or accidentally in a log sent to a server. Our rule is that keys never leave the device in readable form, and any backup is encrypted with a passphrase only the user knows.
How we work
- Model and scopeCustody model, supported networks, and which features genuinely belong in version one.
- User experience designWallet creation, phrase backup and transfer flows that someone new to crypto can complete without help.
- Key management coreThe part that demands the most care: generation, encryption, storage and transaction signing.
- Network and service integrationRPC nodes, price feeds, transaction history and DEX connectivity for swaps.
- Security reviewEvery path where a key is touched, plus abnormal-condition testing.
- Release and maintenanceStore submission or web launch, with update and monitoring processes in place.
Frequently asked questions
Why build a wallet instead of integrating MetaMask?
If your users already know crypto, integrating MetaMask is far cheaper and offloads the security burden. A custom wallet earns its cost when you need full control of the experience, want business-specific features built in, or your users would never manage to install MetaMask themselves.
Can it be published on the App Store and Google Play?
Yes, though both stores have specific rules for crypto apps around in-app purchases and risk disclosure. We prepare the app and documentation to meet them.
What if a user loses their recovery phrase?
With a non-custodial wallet, nothing can be done — that is inherent to the model. What we can do is design the backup step clearly and prompt repeatedly until the user confirms they have recorded it.
How many networks can it support?
Any number of EVM-compatible chains, since they share the same structure — adding one is a configuration change. Non-EVM networks such as Solana or TRON require separate integration work.
What are the ongoing costs?
Mainly RPC node access, price and transaction data services, and maintenance to keep pace with store policy and network changes.
Can you build a wallet for business use?
Yes. Corporate wallets typically need multi-party approval before transfers, role-based permissions and full activity logging for audit — quite different from a consumer wallet. We design that to match your internal controls.
Talk to us before you commit
Tell us what you are trying to solve. Our solution architects reply within 24 hours with an initial scope and approach, at no cost. If we think what you are asking for is not worth building, we will say so.