This guide is for product owners, CTOs and founders who are adding tokens, on-chain payouts or digital collectibles to a business app. It sits in our emerging technology guides, next to blockchain development, and compares the custody models by risk, not by vendor.
In this guide
- Who should hold the keys in a business Web3 app?
- Do you need a wallet at all?
- Five custody models compared
- Key-management checklist before launch
- What breaks when custody is chosen late?
- When is a custodial model the wrong choice?
- Where AI fits
- What delivery record exists, and what does not?
- Alternatives: who builds and runs the custody layer, and how to choose
- Limits of this guide
- Frequently asked questions
- Next step
Who should hold the keys in a business Web3 app?
On public networks such as Ethereum, whoever holds the private key controls the account. The Ethereum account documentation describes an externally owned account as one controlled by anyone with its private keys. Custody is therefore not a feature of the wallet screen; it is the decision about who can sign, who can stop a signature and who answers when a key is lost.
Three questions settle most cases. First, must the user be able to move the asset without the business, for example to another app or exchange? Second, if a key is lost, is the business expected to restore access? Third, does the business hold value on behalf of users, which in many jurisdictions is a regulated activity that needs legal advice before design?
If the answers are "no, yes, no", most products do not need an on-chain wallet in the user's hands at all. A database ledger with an account login, or a custodial set-up run by a licensed partner, gives users recovery and support without exposing them to key management.
Do you need a wallet at all?
A wallet is only needed when a user or the business must sign transactions on a public or permissioned network. Points, credits and vouchers that never leave your app are simpler, cheaper to support and easier to reverse on an ordinary ledger. Our guide to tokenized loyalty and rewards works through that screen for loyalty programs.
Keep the wallet out of the first release when no partner outside your company reads the ledger, when every transfer may need to be reversed by support, or when users would have to buy a network fee token before they can use the product.
Five custody models compared
| Model | Who holds the key | Main risk | Choose it when |
|---|---|---|---|
| No on-chain wallet (accounts and a database ledger) | Nobody; the business runs the ledger | Users cannot take assets elsewhere | Value stays inside your app and support must reverse mistakes |
| User self-custody (browser or mobile wallet the user brings) | The user alone | Lost keys are lost assets; support cannot help | Users are crypto-native and expect to move assets freely |
| Embedded or smart-account wallet (created inside your app) | The user, with recovery rules in a contract or shared key shares | Recovery and sponsor contracts become your code to secure | Mainstream users need easy onboarding but should keep control |
| Business-held keys under MPC or multisig | The business, split across people or devices | Insider misuse, weak approval policy, regulatory exposure | The business signs for itself: treasury, payouts, contract admin |
| Regulated third-party custodian | A licensed custodian under contract | Counterparty and integration dependency | You hold value for users and need a licensed party to do so |
Embedded and smart-account wallets. Account abstraction lets a wallet be a smart contract with its own rules. ERC-4337 defines account abstraction through user operations and an entry point contract, without a change to the consensus layer, and allows a paymaster to sponsor fees. That makes social recovery, spending limits and gas sponsorship possible, and it adds contracts that need the same testing and audit as any other.
MPC and multisig for the business. Multisig enforces "two of three people must approve" on chain; multi-party computation splits the signing key so no single device ever holds it. Both remove the single point of failure. Neither replaces an approval policy: the rules about who may sign what, up to which amount and with which second check still have to be written and tested.
Hybrid set-ups are common. Many products start users on an embedded wallet, let advanced users connect their own wallet later, and keep the business treasury under multisig. The matrix applies per asset and per role, not once per product.
Key-management checklist before launch
-
Write the custody map
List every key the system uses (user wallets, treasury, contract admin, fee sponsor, hot payout wallet) with its owner, purpose and maximum value.
-
Set approval policies
For every business key, define the signers, the quorum, the limits and the second check, and test that a single person cannot bypass them.
-
Separate hot and cold
Keep only the working balance in keys that sign automatically; move the rest behind manual approval.
-
Plan recovery and rotation
Document how a lost device, a departed signer or a leaked key is handled, and rehearse it on a test network. NIST SP 800-57 is a useful reference for key lifecycle states, rotation and compromise recovery.
-
Lock down admin roles
Contract owner and upgrade keys belong under multisig with a time delay, never in a single developer's wallet.
-
Log and monitor
Record every signature request, approval and rejection, and alert on unusual amounts, new destinations and failed attempts.
-
Review legal scope
Confirm with counsel whether holding or moving user assets needs a licence where you operate before you pick a model.
What breaks when custody is chosen late?
Custody chosen after the user interface is designed usually breaks three things. Onboarding has to be rebuilt when a self-custody flow turns out to lose most new users at the seed phrase screen. Support processes fail when agents discover they cannot reverse a transfer. And the treasury ends up in one engineer's wallet because nobody owned the approval policy.
The fix is to decide custody in discovery, alongside the data model and the integration with payment, CRM and accounting systems, so the wallet flows, back end and approval screens are built once.
When is a custodial model the wrong choice?
A custodial model is the wrong choice when users expect to move assets to other apps without asking you, when the business has no licence or licensed partner to hold value for others, or when the team cannot staff key operations around the clock. In those cases self-custody, an embedded wallet with user-controlled recovery, or no on-chain asset at all carries less risk.
Where AI fits
AI helps around the wallet rather than inside the signing path. A model can draft the custody map from the codebase, flag transactions that break the usual pattern for a human to review, summarise support tickets about lost access and suggest test cases for approval policies. Engineers and signers still own every key decision and every signature, because a model must never hold or use a signing key. Netbase works with the major commercial and open-source AI tools and models, chosen per project.
- Available capability
AI-assisted monitoring and engineering under human review
AI-assisted changes and alerts go through the same secure code review, version control and scanning as any other change; not yet tied to a published wallet or custody case.
What delivery record exists, and what does not?
Netbase designs, builds, integrates and runs software in every technology that large software market players offer, and blockchain applications, wallet connection and transaction signing are part of that scope. This page describes the capability and the approach; it is not backed by a published blockchain or custody client project.
Netbase's published security practices are secure code review and version control, TLS in transit and AES at rest, role-based access control, MFA for admin dashboards, vulnerability scanning and penetration testing, and disaster recovery. Security by design is part of how Netbase delivers, alongside API-first integration and IoT work.
Delivery follows a six-step lifecycle from discovery to ongoing support, with weekly reviews and a named project manager, which is where the custody map, the approval policies and the recovery rehearsal are scheduled. The same lifecycle runs on long-running products such as the multi-tenant cloud ERP for a US client.
Most Netbase projects are delivered on fixed-price contracts. No Netbase record publishes wallet counts, assets under custody, incident figures or launch outcomes, and none is offered here as evidence.
Alternatives: who builds and runs the custody layer, and how to choose
The custody model is one decision; who builds and operates it is another.
- A wallet-as-a-service or custody provider. Best when you need a licensed custodian or a tested MPC service quickly. Check where key shares live, what happens to users if the contract ends and how the provider's approval rules map to yours.
- Your in-house team. Best when signing is core to the product and you can staff key operations. Check that approval policies, monitoring and recovery have named owners.
- A development partner. Best when the wallet flows must connect to existing web, mobile and business systems. Ask for the custody map and the checklist above in writing, and for smart contract audit preparation of any recovery or sponsor contracts.
Choose by who can sign, who can stop a wrong signature fastest, and who keeps working if one vendor leaves.
Limits of this guide
- It covers custody models for business apps on public and permissioned networks, not trading, exchange operations or token economics.
- It is not legal, financial or compliance advice; licensing rules for holding assets differ by country.
Plan the next step with a Netbase consultant
Frequently asked questions
No. A non-custodial wallet removes the business as a holder of user assets, but it moves all key risk to the user. For mainstream users who lose phones and forget phrases, an embedded wallet with tested recovery or an ordinary account ledger is often the safer product.
Multisig is a smart contract or script that needs several separate signatures before a transaction runs, and the rule is visible on chain. MPC splits one signing key into shares held by different parties, which jointly produce a single signature without the full key ever existing in one place.
Yes, but it is a migration. Users must move assets to new addresses or accounts, contracts may need new admin roles and support processes change, so plan the model in discovery and design the first release so a second model can be added.
Next step
If you are choosing a custody model for a business app and want the custody map, approval policies and wallet flows designed with the systems you already run, book a solution review.
Related services and solutions
IoT development with AI analytics that connects devices to the business Netbase provides IoT development for manufacturers, logistics operators and product companies to connect devices and sensor data to the business platforms that act on them, with AI that spots anomalies and forecasts what needs attention. We design the device-to-cloud data path, build the back end, dashboards and integrations, and treat security, data ownership and AI as design decisions.
Learn More
Blockchain development: smart contracts, wallets and tokenisation built to last Netbase designs and builds blockchain applications: smart contracts, wallet integrations, tokens and permissioned ledgers, connected to the web, mobile and business systems you already run. We start by checking whether a blockchain is the right tool at all, test every contract against known attack patterns and plan an independent audit before anything holds real value.
Learn More
Digital wallet and payments with AI: balances, transfers, merchant payments and payouts on one ledger A digital wallet from Netbase is web and mobile software where customers hold a balance, top up, pay merchants, send money to each other and receive payouts, while operations and finance teams reconcile every movement on one ledger. We design and build it custom on licensed payment partners, and add AI that flags fraud while analysts decide.
Learn More
Work with Netbase remotely
Every Netbase engagement is delivered remotely, so clients in any country and any industry can work with us; Netbase has worked with clients in 80 countries. Contracts and invoices are issued by Netbase JSC, and payment is made by bank transfer to Netbase JSC's company account or PayPal Business. Talk to the CEO, Huy Nguyen (David), on WhatsApp or by email.
Discuss a project
Netbase JSC helps organizations design, build, modernize, and operate digital products and AI-enabled business systems.project@netbasejsc.com
+84 937 869 689
91 Nguyen Chi Thanh, Dong Da, Hanoi, Vietnam
Get in touch
Tell us what you want to build, modernize, or operate.