Wallet software users can trust with their keys.
BitAzure designs and builds wallets across custody models and platforms: MPC and multisig key management, multi-chain transaction handling, token and NFT support, in-app swaps and staking, and the backend indexing that keeps balances and history accurate.
- Custodial, non-custodial and hybrid architectures
- MPC, multisig and hardware wallet integration
- Multi-chain tokens, NFTs, swaps and staking
- iOS, Android, web and browser extension clients
What is crypto wallet development?
Crypto wallet development is the engineering of software that generates and protects private keys, constructs and signs blockchain transactions, and presents balances, tokens, NFTs and activity across one or more networks. The wallet is the primary security boundary between a user and their assets.
The custody model decides most of the architecture. Non-custodial wallets keep key material on the user device or split it with MPC so no single party can sign alone; custodial wallets hold keys in HSM-backed or MPC infrastructure operated by the business and expose accounts through policy-controlled APIs. BitAzure builds both, and the hybrid variants in between.
Beyond signing, a production wallet depends on backend services: chain indexers that reconcile balances and history under reorgs, price and token metadata feeds, swap and staking routing, push notifications and abuse detection. We deliver these services together with the client apps so the product behaves consistently on every chain it supports.
Crypto wallet development services
Wallet features are delivered as modules on a shared core, so custody model, platforms and chains can be combined without rewriting the signing path.
Custody Models
- Non-custodial wallets with device-held keys and encrypted backups
- Custodial wallets with HSM-backed signing and policy controls
- MPC wallet architecture with threshold signing across device and server shares
- Multi-signature wallets with configurable quorums and approval workflows
- Hybrid custody with user-held shares and business-held recovery shares
Platforms
- Mobile wallets for iOS and Android with biometric unlock
- Web wallets with passkey and WebAuthn authentication
- Browser extension wallets with dApp injection and permission prompts
- Shared TypeScript core across mobile, web and extension
- Hardware wallet integration over USB, Bluetooth and QR signing
Multi-Chain Support
- Multi-chain accounts for EVM networks, Solana, Bitcoin and Cosmos
- Token support: ERC-20, SPL, BEP-20 and custom token lists
- NFT support with metadata, media rendering and transfers
- Address management: HD derivation, labels, address book and name-service resolution
- Fee estimation, gas abstraction and transaction simulation
In-App Financial Features
- Swap with aggregator routing and slippage protection
- Staking and liquid staking flows with reward tracking
- DeFi integration: lending, vaults and yield positions in the portfolio view
- Fiat on-ramp and off-ramp provider integration
- Recurring payments and scheduled transfers
Connectivity & Data
- WalletConnect v2 sessions, request signing and permission scopes
- Transaction history with reorg-safe indexing and decoded contract calls
- Real-time balance and price updates over WebSocket
- Push notifications for incoming transfers and approvals
- Portfolio analytics and export for accounting
Security Architecture
- Secure enclave and keystore usage on every platform
- Encrypted cloud backup of shares with user-controlled recovery
- Transaction preview, simulation and contract risk warnings
- Spending policies, allowlists and cooling-off periods
- Root and jailbreak detection, certificate pinning and code obfuscation
Reference wallet architecture
A wallet platform keeps key material and policy enforcement separate from chain connectivity and data services, so a failure in an indexer or RPC provider can never lead to an unintended signature.
Hover or focus a component to see its role in the architecture.
- Mobile Wallet (iOS / Android): Biometric unlock, transaction preview and one MPC share stored in the secure enclave.
- Web & Extension Wallet (Passkeys · dApp injection): Browser clients sharing the TypeScript core, with WalletConnect and injected provider support.
- Secure Enclave (Device share): Hardware-backed storage for the device key share; never exported in plaintext.
- MPC Signing Service (Server shares): Threshold signing that combines partial signatures without reconstructing a full private key.
- Policy Engine (Limits · allowlists): Evaluates spending limits, destination allowlists and approval quorums before signing proceeds.
- Chain Adapters (EVM · Solana · Bitcoin): Per-chain transaction building, fee estimation, serialization and broadcast.
- Indexing Backend (Balances · history): Reorg-aware ingestion of transfers and events with decoded activity per account.
- Swap & Staking Router (Aggregator quotes): Quotes from aggregators and staking providers, with slippage and route validation.
- RPC & Indexer Providers (Multi-provider failover): Health-checked RPC endpoints and third-party indexers with automatic fallback.
- Blockchains (EVM · Solana · Bitcoin · Cosmos): Networks supported through the adapter interface.
Client
- Mobile, web & extension
- Secure enclave / keystore
- Transaction preview
Key management
- MPC or multisig signing
- Policy engine
- Backup & recovery
Chain connectivity
- Chain adapters
- RPC failover
- Fee estimation
Data services
- Indexing backend
- Swap & staking routing
- Notifications
Wallet products we build
Consumer self-custody wallet
Mobile-first wallet with MPC recovery for users who should never have to handle a seed phrase.
Exchange or fintech custody
Custodial wallet infrastructure behind a policy engine for platforms that hold client funds.
Business treasury wallet
Multisig approvals, spending limits and role separation for company-held assets.
Embedded wallets
SDKs that give games, marketplaces and social apps invisible key management.
DeFi and NFT super-app
Swaps, staking, NFTs and dApp browsing in a single multi-chain interface.
Payments and remittance
Stablecoin wallets with address books, invoices and fiat off-ramps.
Why teams build wallets with BitAzure
Custody flexibility
Non-custodial, custodial or hybrid designs from the same codebase and backend.
Accurate balances
Reorg-aware indexing and reconciliation keep history and balances in step with the chain.
One core, every platform
Shared TypeScript logic across iOS, Android, web and browser extension.
Defensive UX
Simulation, decoded calldata and risk warnings before the user signs anything.
Chain coverage
EVM, Solana, Bitcoin and Cosmos adapters behind a consistent internal model.
Security reviewed
Threat modelling, mobile hardening and coordination of independent review as part of delivery.
Technologies we use for wallet development
React Native
MobileNative iOS and Android apps from one TypeScript codebase.
TypeScript
FrontendStrict typing across the entire stack, client to contracts tooling.
Node.js
BackendEvent-driven APIs, gateways and real-time WebSocket services.
Rust
BackendMemory-safe, low-latency engines, on-chain programs and tooling.
Go
BackendConcurrent network services, relayers and infrastructure daemons.
EVM
BlockchainEthereum, BNB Chain, Polygon, Arbitrum, Optimism, Base, Avalanche.
Solana
BlockchainRust programs with Anchor, SPL tokens and high-throughput dApps.
Bitcoin
BlockchainUTXO wallets, PSBT signing, Lightning integrations.
PostgreSQL
DatabaseTransactional ledgers, ledgers-of-record and analytical workloads.
Redis
DatabaseCaching, sessions, rate limiting, pub/sub and order-book snapshots.
AWS
InfrastructureEKS, RDS, KMS, CloudHSM and multi-region deployments.
Kubernetes
InfrastructureAutoscaling, rolling deployments and workload isolation.
How we deliver a wallet
Every engagement follows a documented, milestone-driven path from discovery to continuous development.
- 01
Custody & threat model
Key ownership, recovery paths, attacker scenarios and regulatory position are settled before any screen is designed.
- 02
Architecture & chain scope
Supported networks, token standards, signing flow and backend services are specified with sequence diagrams.
- 03
Core wallet engine
Key generation, MPC or multisig signing, derivation and chain adapters are built with automated tests against local nodes.
- 04
Apps & backend services
Mobile, web and extension clients, indexers, swap routing and notifications are delivered in sprints with usability testing.
- 05
Hardening & review
Mobile hardening, penetration testing and, where required, independent review of the signing path.
- 06
Release & iteration
Store submission, phased rollout, crash and abuse monitoring, then continuous feature delivery.
Security practices in wallet development
Key isolation
Private keys and MPC shares never leave the secure enclave or signing service in plaintext.
Recovery without seed phrases
Encrypted share backups and social or institutional recovery remove single points of failure.
Policy enforcement
Limits, allowlists and approval quorums are enforced server-side where the custody model demands it.
Transaction safety
Simulation, approval scoping and warnings on unlimited allowances and known malicious contracts.
Mobile hardening
Root detection, certificate pinning, screen-capture protection and obfuscated release builds.
Dependency hygiene
Pinned, reviewed dependencies with supply-chain checks running in CI.
We coordinate independent third-party audits on request and never claim an audit, certification or compliance status unless it has actually been obtained.
What to decide before building a wallet
Who controls recovery
Seed phrases, MPC backups and institutional recovery differ in liability and support burden; choose deliberately.
Regulatory classification
Custodial wallets can fall under money transmission or VASP rules; non-custodial designs shift obligations but do not remove them.
Chain breadth versus depth
Every additional chain multiplies testing and indexing cost; start with the networks your users actually need.
RPC and indexer dependencies
Third-party providers fail and rate-limit; plan failover and self-hosted fallbacks for critical paths.
App store policies
Wallet, NFT and in-app purchase rules from the app stores influence feature design and monetisation.
Upgrade and migration paths
Changing key schemes or derivation later is painful; version the wallet data format from the start.
Crypto Wallet Development questions
A multisig wallet is a smart contract or script that requires several independent signatures on-chain. An MPC wallet produces a single signature from key shares held by different parties, so it works on any chain and reveals nothing on-chain. MPC suits consumer recovery and custodial infrastructure; multisig suits transparent treasury governance.
Planning a wallet product or custody stack?
Describe your users and custody stance. We will propose a key-management architecture and a delivery roadmap.