A finance team I keep hearing about runs month-end close on a spreadsheet that used to be one tab. Now it’s forty. Not because the business grew forty times — someone kept saying yes to new assets, and every asset meant a new wallet, a new balance to fetch, and another key to manage.
Nobody designed it that way on purpose. Wallet-per-asset is the architecture you fall into when the first integration works and the second looks almost identical. It’s only around asset thirty that finance starts asking why reconciliation takes four days instead of four hours.
What Forty Wallets Actually Cost
The visible cost is obvious: more infrastructure, more keys, more places to fail. The cost nobody budgets for shows up somewhere else — in finance, support, and operations.
A user asks where another balance went because it sits behind a different wallet. Finance runs forty reconciliation processes where one could have done the job, and each can fail differently. A fix to one flow doesn’t necessarily improve the other thirty-nine. At a small scale, that’s annoying. At forty assets, it becomes a second job.
The One-Wallet Fix and What It Actually Changes
Collapsing that architecture into one balanced view sounds like a UI decision. It isn’t. Underneath the interface, it’s an infrastructure and custody decision.
Instead of treating every asset as its own operational lane, the product gives users and finance one place to see balances and one process to reconcile them. The report becomes simpler because the architecture underneath it becomes simpler first.
The second-order effects are more interesting. Support gets fewer questions about missing balances. New-asset launches can move faster because the team no longer has to recreate the same custody setup every time. Finance gets one reporting process instead of dozens — and eventually starts trusting the numbers again.
The Part That Doesn’t Disappear
Consolidating custody doesn’t remove risk; it relocates it. Forty small operational risks become one larger relationship that has to be governed properly, which is often a cleaner model but still comes with its own responsibilities.
Someone still has to own provider oversight, permissions, security policies, access controls, and the consequences if the underlying infrastructure fails. The difference is that the risk is now concentrated enough to be visible, documented, and managed instead of being scattered across dozens of separate wallet setups.
Three Answers to Who Actually Holds the Key
Once a team decides that one wallet is better than forty, the next question is harder: where should that unified infrastructure actually live? The three models below solve the same operational problem differently, mainly in how much infrastructure and control the business chooses to hand off.
1 | Coinbase | Managed Wallet Infrastructure
Coinbase CDP Wallets take the managed-platform route. The stack includes TEE-backed key infrastructure, KYT screening, and APIs covering embedded and server wallets.
For a product team, the attraction is consolidation: wallet creation, security infrastructure, and compliance tooling sit behind one development layer rather than being assembled asset by asset.
The trade-off is equally clear. More infrastructure is delegated to an established provider, so the team has less of the underlying wallet stack to build and operate itself. Governance therefore shifts toward managing the provider relationship, permissions, policies, and integration rather than managing every key system independently.
2 | WhiteBIT | Unified Multi-Asset Custody
WhiteBIT’s Wallet-as-a-Service approaches the same problem from a multi-asset custody angle. It supports 340+ assets across 80+ networks within a single wallet, with address generation and AML checks built into the infrastructure.
For businesses managing many assets, the practical gain is fewer parallel systems. The same environment can support multiple networks and assets instead of requiring a new custody workflow every time the product expands its asset list.
Here too, simplification comes with concentration. Custody and a larger part of the operational layer sit with one provider, which reduces internal complexity but makes provider governance, security standards, access controls, and operational resilience more important.
3 | Openfort | More Control Over the Key Layer
Openfort takes a different route. Its Wallet-as-a-Service stack is built around non-custodial infrastructure, with self-hostable key management through OpenSigner and a policy layer for controlling how wallets operate.
The practical difference is configurability. Teams can define transaction rules, session permissions, contract allowlists, spending limits, and gas sponsorship without rebuilding the wallet stack around each use case. That makes Openfort especially relevant for products that need wallet behavior to vary across users, applications, or workflows.
That flexibility also keeps more operational responsibility with the product team. Key policies, security rules, and wallet behavior need to be actively governed, which can suit teams that want a more programmable infrastructure layer rather than simply outsourcing most of the wallet logic to a provider.
The Design Principle Underneath the Reconciliation Win
The clean balance view is real, and finance may feel the benefit first. But the honest way to judge wallet infrastructure isn’t by how clean the demo looks. It’s by what happens three years later, after asset coverage, transaction volume, and headcount have all moved in directions nobody predicted.
A system that turns forty reconciliation problems into one can remove a surprising amount of operational noise, but that simplification only works if the remaining relationship is governed properly. Forty risks becoming one is valuable only when somebody is clearly responsible for the one.
That responsibility isn’t a footnote to the architecture decision. It sits at the center of it, because the goal was never simply to make the balance screen cleaner — it was to make the underlying system easier to understand, operate, and trust.
Disclaimer: This is not financial or investment advice. Do your own research before making any decisions. Use at your own risk.
The Trade Nobody Puts in the Wallet Infrastructure Pitch Deck was originally published in Coinmonks on Medium, where people are continuing the conversation by highlighting and responding to this story.