Do you need wallet infrastructure at all?
Wallet infrastructure gives you the keys and the signing engine. It does not give you a licence, a fiat on and off ramp or a payout API that pays someone in local currency. If you are a payment platform without a crypto licence, a custodial payout provider such as BVNK, Bridge or Circle is usually the faster start, and the provider holds the wallets. You need wallet infrastructure when you hold clients' funds under your own licence, when you run your own treasury on-chain, or when you give each user a wallet in your app. The custody models guide walks through that choice.
How do the providers protect keys?
The label "MPC wallet" covers several designs. What matters is where the key or its parts live, and who can produce a signature:
- Threshold MPC. The key is split into shares on separate machines or parties. A threshold of them computes the signature together, and the full key never exists in one place.
- Secure enclaves. The key exists in full, but only inside attested hardware enclaves. Code you can verify decides what gets signed.
- Multisig. Several independent keys and a rule the blockchain itself enforces. The rule is public, but it works differently on each chain.
None of the three is safe by itself. In most public incident reports the failure was in the policy around signing or in an operator's machine, not in the cryptography. In the February 2025 theft from the Bybit exchange, for example, attackers compromised the interface signers used to review transactions, and the signers approved a transfer they could not see.
Twelve questions that separate the providers
Ask every provider on your shortlist the same questions, in writing:
- Can you or anyone at your company produce a signature without us?
- Where does each key share, or the enclave holding the key, run? In which cloud and country?
- Can we export the key or the shares, in which format, and has a client done it?
- Which of our chains and tokens are supported today, and which are on a roadmap?
- How do signing policies work: amount limits, whitelists, approvals by role, time windows? Can we manage them as code?
- Where are policies enforced, and who can change them?
- What is the signing latency at our peak volume, and what are the rate limits?
- What happens to signing if your service is down? What if your company fails?
- Which audits and certifications cover the signing path (SOC 2 Type II, ISO 27001, penetration tests)?
- How do you support DORA requirements: contract clauses, incident notices, exit support?
- How do webhooks work, and can we replay missed events?
- What will we pay at our expected volume in year one and year three?
Where lock-in really comes from
Key export is the first question everyone asks, and it is necessary, but it is rarely what keeps a team on a provider. The bigger lock-in is in everything built on top:
- Addresses. Counterparties, exchanges and recipients whitelist your deposit and payout addresses. New provider, new addresses, unless the key moves with you.
- Workflow features. Approval flows, address books and automation rules configured in the provider's console are not portable. Keep payout logic in your own service and use the provider for signing.
- Network memberships. Transfers between members of a provider's network are convenient and fast, and your counterparties start to rely on them.
- Reconciliation. If your books are reconciled against the provider's reports instead of the chain, you will rebuild reconciliation when you leave.
The cheapest protection is architecture: one wallet interface in your code with the provider behind it, ledger entries reconciled against chain data, and policies kept in version control and mirrored into the provider.
How to run a two-week evaluation
| Days | What you do | What you learn |
|---|---|---|
| 1–2 | Write down chains, tokens, volumes, policies and the exit requirement; send the twelve questions | Which providers stay on the list |
| 3–6 | In each sandbox: create wallets, set a policy, send and receive on two chains, receive webhooks | API quality, documentation, latency |
| 7–8 | Break things: exceed a limit, retry a request, miss a webhook, revoke an approver | How the provider fails, and how you find out |
| 9–10 | Security and legal: audits, DORA clauses, key export procedure, service levels | What the contract really promises |
| 11–14 | Compare total cost at year one and year three; write a one-page decision | A choice you can defend to your board and your auditor |
Which provider for which case?
| Your situation | Usual shortlist |
|---|---|
| Licensed EMI or CASP, payouts on many chains, many counterparties | Fireblocks, Dfns |
| App giving each user a wallet, high signing volume | Turnkey, Dfns, or an embedded wallet SDK |
| Institution that needs qualified custody and insurance | BitGo, Copper |
| Team that signs many smart-contract transactions and needs to see their effect | Fordefi |
| Strict data residency or no third party in the signing path | Self-hosted MPC or HSM |
What have we built?
Our founders built Stablerail, a treasury workspace for stablecoins, bank accounts and cards with approvals and audit records on self-custodial MPC, and Transatron, non-custodial TRON infrastructure. We integrate wallet providers for clients and design the wallet layer so the provider can be replaced.
FAQ
Q01Which MPC wallet provider is the best?
There is no best one, only a best fit. Fireblocks is the broadest network and policy engine; Dfns and Turnkey are API-first and suit teams that build their own product on top; BitGo adds regulated custody; Fordefi is strong where transactions must be simulated and explained before signing. Your chains, licence, volume and exit plan decide.
Q02Can we switch providers later?
Yes, but it usually means new addresses, a period of running both, moving balances on-chain and updating every counterparty's whitelist. Ask about key or share export before you sign, and keep your own payout logic outside the provider's workflow features.
Q03Do we need a licence to use one?
Wallet infrastructure gives you the keys, so if you hold clients' funds with it you are usually providing custody yourself and need the licence. Without a licence, a custodial payout provider is usually the right start.
Q04How do providers price?
Usually an annual platform fee plus charges by wallet count, transaction volume or assets, and they change often. We do not publish their prices; ask each for a quote at your expected volume in year one and year three.
Q05Are you paid by any of these providers?
No. We integrate several of them and receive no fees from any. If that changes, we say so on this page.
Sources
Disclosure: Vareger integrates wallet providers, including some named here. We receive no fees from any of them; if that changes, we say so on this page.
