Managed Wallet
Pronunciation: MA-nuhjd WOL-it
Definition
A managed wallet is a wallet whose infrastructure, security operations, policy, or custody is administered partly or entirely by a service provider. For Managed Wallet, operational teams should document who can authorize transactions, which assets and networks are supported, how recovery works, and which evidence confirms the final on-chain result. Reliable use of Managed Wallet depends on clear signing authority, network-aware transaction review, protected recovery data, and records that connect each wallet action to its resulting balance change.
Overview
The provider may host nodes, store or co-manage keys, operate signing services, apply transaction policy, manage backups, perform recovery, or maintain the user interface and APIs. Some managed wallets are fully custodial, while others preserve client-controlled approval or key shares.
Managed operation reduces internal workload but introduces service, legal, technical, and concentration dependencies. The provider may be able to change policy, suspend service, recover accounts, or migrate infrastructure. A user-visible approval does not establish exclusive control if an administrative path exists.
Customers should review the exact custody model, roles, supported assets, segregation, availability, recovery, data export, audit evidence, and exit process. Contracts should define liability and incident handling. Independent transaction and balance records remain necessary. Critical users should test provider outage and migration scenarios before relying on the service.
The Managed Wallet workflow operates through several distinct states: request creation, user or policy approval, signature generation, network submission, execution, confirmation, balance recognition, and accounting. For Managed Wallet, a wallet interface or provider response can report progress, but it cannot replace verified transaction and ledger evidence.
Material risks for Managed Wallet include credential compromise, malicious destinations, unsupported assets, wrong-network transfers, stale balances, compromised software, provider outage, privacy leakage, and inaccessible recovery material. For Managed Wallet, controls should reflect value, automation, reversibility, and whether the organization or a third party controls signing.
Production ownership for Managed Wallet should identify the user or legal entity, supported assets and networks, address model, custody boundary, signing authority, recovery method, and systems permitted to request or observe transactions. For Managed Wallet, these fields determine who can act and which evidence is authoritative.
Key Takeaway
A managed wallet shifts operational duties to a provider, so control rights, dependency, evidence, and exit capability must be explicit.
Sources
- Bitcoin.org Documentation: Wallets — Bitcoin.org (2026-07-30)
- NIST Documentation: Key Management — NIST (2026-07-30)