What is Crypto Custody?
Crypto custody refers to the secure storage and management of private keys that control access to digital assets on blockchain networks.
Unlike traditional financial assets, cryptocurrencies and digital tokens exist as entries on distributed ledgers. Ownership is determined not by a central registry, but by possession of cryptographic private keys. Whoever controls the private key controls the assets—making secure custody a fundamental requirement for any institutional participant.
Core Components of Custody
Key Generation
Creating cryptographic key pairs using secure random number generation in isolated environments
Key Storage
Protecting private keys from theft, loss, or unauthorized access through hardware and software controls
Access Control
Defining and enforcing policies for who can initiate transactions and under what conditions
Transaction Signing
Using private keys to authorize blockchain transactions while maintaining security controls
Traditional vs. Crypto Custody
In traditional finance, custody involves holding securities or cash on behalf of clients, typically through a regulated intermediary. The custodian maintains records and facilitates transfers but doesn't directly "possess" the assets in the way a crypto custodian controls private keys.
With digital assets, the custodian's control is more direct and consequential: access to the private key means full control over the assets. This creates both opportunities for streamlined operations and significant security responsibilities.
Why Custody Matters for Institutions
For institutional participants—asset managers, corporations, funds, and financial services firms—custody is not merely a technical concern but a foundational business and regulatory requirement.
Fiduciary Obligations
Investment advisers and fund managers are typically required to maintain client assets with a "qualified custodian." This regulatory framework, designed to protect investors, extends to digital assets and shapes how institutions must approach custody.
Operational Risk Management
The irreversible nature of blockchain transactions means that errors or security breaches can result in permanent loss. Institutions require robust operational controls, segregation of duties, and disaster recovery capabilities that exceed what individual custody solutions might provide.
Insurance and Liability
Professional custody arrangements typically include insurance coverage and clear liability frameworks. For institutions managing third-party assets, this protection is essential for both regulatory compliance and client confidence.
Regulatory Considerations
- SEC Custody Rule: Investment advisers must maintain client assets with qualified custodians
- Bank Charters: Some custodians operate under national or state bank charters, providing regulatory clarity
- SOC Compliance: Service Organization Control audits validate operational controls
- Geographic Requirements: Different jurisdictions have varying custody requirements
Business Continuity
Institutions require assurance that their assets remain accessible even if a custody provider faces operational or financial difficulties. This necessitates careful evaluation of provider stability, key recovery mechanisms, and legal protections.
Custody Models Explained
Custody solutions exist on a spectrum from full self-custody to complete delegation to third parties. Each model involves different trade-offs between control, security, convenience, and regulatory treatment.
Custody Model Taxonomy
Self-Custody
The institution generates and maintains full control over all private keys. This provides maximum control and eliminates counterparty risk but requires significant technical expertise and operational infrastructure.
Suitable for: Technically sophisticated organizations with dedicated security teams, those with specific regulatory or policy requirements for key control, or entities with lower transaction volumes that don't require integrated services.
Hybrid / Shared Custody
Control is distributed between the institution and service providers. Multi-party computation (MPC) technology allows cryptographic operations without any single party having access to the complete key. Multi-signature arrangements require multiple parties to authorize transactions.
Suitable for: Organizations seeking to balance control with operational convenience, those requiring segregation of duties, or entities wanting to reduce single points of failure while maintaining meaningful oversight.
Third-Party Custody
A qualified custodian holds and manages private keys on behalf of the client. This model provides regulatory clarity, insurance coverage, and professional operations but introduces counterparty dependency.
Suitable for: Regulated investment advisers requiring qualified custodians, organizations without specialized crypto operations teams, or those prioritizing insurance and regulatory compliance over direct control.
Custody Decision Framework
Selecting a custody approach involves weighing multiple factors specific to your organization. This framework helps structure the evaluation process.
Decision Framework Flow
Key Evaluation Criteria
Security Architecture
- Key generation methodology
- Storage infrastructure (HSM, MPC, cold storage)
- Physical security controls
- Penetration testing history
- Incident response procedures
Regulatory Status
- Jurisdiction and licensing
- Qualified custodian status
- Banking charter (if applicable)
- SOC 1/2 audit reports
- Regulatory examination history
Insurance Coverage
- Policy limits and scope
- Covered events (theft, errors, etc.)
- Carrier ratings
- Claims history
- Excess coverage options
Operational Capabilities
- Supported assets and networks
- Staking and DeFi access
- API and integration options
- Reporting and audit trails
- Transaction throughput
Governance Controls
- Policy engine flexibility
- Approval workflows
- Role-based access control
- Whitelisting capabilities
- Transaction limits
Business Terms
- Fee structure transparency
- Minimum asset requirements
- Contract terms and SLAs
- Provider financial stability
- Exit provisions
Provider Landscape
The custody provider landscape includes specialized custodians, exchange-affiliated services, infrastructure providers, and traditional financial institutions entering the space. This categorization reflects how providers actually operate, not marketing positioning.
Provider Category Map
Note: This landscape represents a point-in-time view of a rapidly evolving market. Provider capabilities, regulatory status, and service offerings change frequently. The categorization reflects primary operating models; many providers offer services across multiple categories.
Category Characteristics
Regulated entities operating under bank charters or trust company licenses. These providers can serve as "qualified custodians" for SEC-registered investment advisers, meeting specific regulatory requirements for client asset protection. Typically offer the most comprehensive regulatory coverage but may have higher minimums and more limited asset support.
Providers focused on custody technology and infrastructure rather than direct custodial services. Often power other custodians' operations or provide wallet-as-a-service platforms. Typically offer MPC-based solutions, API-first architectures, and flexible deployment options. Clients maintain more direct control over keys.
Custody services offered by or closely connected to cryptocurrency exchanges. Provide convenience for active traders with integrated trading and custody. Regulatory status varies by entity and jurisdiction. Consideration of exchange-specific counterparty risk is warranted.
Full-service providers offering custody alongside trading, lending, and other financial services. Model similar to traditional finance prime brokerage relationships. May aggregate custody across multiple underlying providers. Suitable for institutions requiring comprehensive service bundles.
Operating Model: The Custody Control Stack
Understanding how custody solutions actually operate requires examining the full stack of controls, from physical security to governance policies.
Custody Control Stack
Physical Security (Layer 1)
The foundation of custody security. Enterprise custody solutions typically utilize hardened data centers with 24/7 monitoring, biometric access controls, and redundant power/connectivity. Cold storage may involve geographically distributed secure facilities with strict access protocols.
Key Storage (Layer 2)
How and where private keys or key shares are stored. Options include Hardware Security Modules (HSMs), air-gapped computers, or distributed key shares across multiple locations. The storage approach directly impacts both security and operational flexibility.
Signing & Computation (Layer 3)
The mechanisms for authorizing transactions. Multi-party computation (MPC) allows signing without reconstructing the full key. Threshold signatures require M-of-N participants. Traditional multi-sig uses on-chain mechanisms. Each approach has different security and operational characteristics.
Application (Layer 4)
The interfaces through which users interact with custody services. This includes web dashboards, mobile apps, APIs, and integrations with portfolio management systems. Security at this layer involves authentication, session management, and secure communications.
Governance & Policy (Layer 5)
The business logic layer controlling how transactions are authorized. Policy engines can enforce approval workflows, velocity limits, whitelist restrictions, and time-based controls. This layer often differentiates enterprise solutions from consumer products.
Provider Readiness Matrix
This matrix provides a structural comparison of custody providers across key institutional dimensions. Categorization is based on publicly disclosed information and does not constitute an endorsement or quality ranking.
| Provider | Operating Model | Regulatory Posture | Institutional Orientation | Asset Breadth | Tokenized Asset Readiness | Interoperability Style |
|---|---|---|---|---|---|---|
| Anchorage Digital | Federally chartered bank | OCC federal bank charter; highest US regulatory tier | Banks, pension funds, registered advisers | ~60 curated assets | Dual custody support; settlement integration | Direct custody; fiat rails |
| BitGo | Qualified custodian + infrastructure | OCC national charter (Dec 2025); SD trust | ETF issuers, funds, tokenization platforms | 1,550+ assets across 69 chains | WBTC custodian; broad RWA support | Multi-sig + TSS; API-first |
| Coinbase Custody | Exchange-integrated custodian | NYDFS Trust Company; qualified custodian | ETF sponsors, corporates, advisers | 470+ assets | Limited; focus on native assets | Exchange liquidity integration |
| Fireblocks | Technology / infrastructure provider | NYDFS Trust (2024); primarily infrastructure | Exchanges, banks, neobanks (sub-custody) | 1,400+ tokens, 50+ chains | Tokenization rails; stablecoin support | MPC-CMP; 1,200+ counterparty network |
| Copper | Prime custody | FCA registered (UK); MiCA pending | Hedge funds, trading firms | Multi-chain support | Developing | ClearLoop off-exchange settlement |
| Zodia Custody | Bank-backed custodian | JFSC, FCA; multi-jurisdictional | Asset managers, family offices | Curated institutional set | Traditional-finance bridge | HSM + MPC hybrid |
| Komainu | Bank-backed custodian | Jersey, Dubai VARA | Institutional asset managers | Curated set | Ledger partnership | Segregated custody |
| Kraken | Exchange custodian | Wyoming SPDI (Kraken Bank) | Mid-market institutions, crypto-native | 200+ assets | Limited | Trading integration; staking |
| Fidelity Digital Assets | Traditional finance custodian | NY Trust; OCC conditional approval (Dec 2025) | ETF sponsors, asset managers | Select major assets | Fund administration integration | Traditional custody rails |
| BNY Mellon | Traditional finance incumbent | Federal bank supervision; post-SAB 121 | ETF sponsors, pension funds | Bitcoin, Ether (expanding) | On-chain NAV services | Fund admin integration |
Note: This matrix reflects publicly available information as of April 2026. Operating models and regulatory status are subject to change. "Tokenized Asset Readiness" refers to capacity to custody tokenized real-world assets alongside native crypto; not all providers have disclosed detailed capabilities. Inclusion does not constitute endorsement.
Interoperability & Integration Patterns
Institutional custody does not operate in isolation. Custodians connect to a broader ecosystem of exchanges, sub-custodians, staking providers, and settlement networks. Understanding these integration patterns is essential for evaluating operational fit.
Exchange Connectivity
Custodians may integrate directly with exchanges for trading, or maintain settlement relationships that allow assets to remain in cold storage while trading occurs. Off-exchange settlement networks (e.g., Copper ClearLoop, Fireblocks Network) enable trading across venues without prefunding or asset movement.
Sub-Custody Arrangements
Banks and traditional institutions often use crypto-native firms as sub-custodians for key management while maintaining the primary custodial relationship. MiCA and US interagency guidance address liability allocation in these arrangements. The primary custodian retains responsibility even when key management is delegated.
MPC Infrastructure Stacks
Multi-party computation (MPC) providers offer key-shard distribution across parties. Fireblocks uses MPC-CMP with Intel SGX enclaves; Copper employs 2-of-3 sharding. Some institutions operate hybrid models where they hold one share while the provider holds another, ensuring no single party can move assets unilaterally.
Omnibus Accounts
Some custodians pool client assets in omnibus wallets with internal ledger segregation. This approach offers operational efficiency but introduces reconciliation complexity and potential insolvency exposure. MiCA Article 75(7) requires on-chain segregation for EU CASPs; US practices vary.
Staking Provider Integration
Institutional staking requires separation of validator keys (online, signing blocks) from withdrawal keys (cold storage). Custodians may operate validators directly, delegate to third-party operators, or support client-selected operators. Slashing liability allocation varies by provider and contract.
Smart-Contract Wallets
Account abstraction (EIP-4337, EIP-7702) enables programmable wallet logic including multi-approver thresholds, time-locks, and recovery mechanisms. Safe (formerly Gnosis Safe) is the dominant EVM multi-sig framework. Custodians increasingly support or integrate with smart-contract wallet architectures for governance flexibility.
Tokenization Workflows
Tokenized real-world assets require dual custody: traditional custodians hold underlying assets (Treasuries, securities) while crypto custodians manage on-chain tokens. BNY Mellon, Securitize, and specialized platforms coordinate these flows. The DTC's December 2025 no-action relief enables tokenized entitlements for participants.
Off-Exchange Settlement Rails
Bilateral and multilateral settlement networks allow institutions to trade without moving assets from cold storage. Assets are mirrored or pledged within the network; settlement occurs via book-entry adjustments. This reduces counterparty exposure and prefunding requirements for active traders.
Interoperability Gaps
No SWIFT-equivalent messaging standard exists between crypto custodians. Institutional transfers rely on on-chain movements, proprietary networks, or bilateral arrangements. Permissioned tokens (e.g., ERC-3643) require re-whitelisting at each custodian. These gaps increase operational friction for institutions operating across multiple providers.
Asset & Standards Support
Custody requirements vary significantly by asset type. Different asset classes present distinct technical, regulatory, and operational considerations that affect provider selection.
Native Crypto Assets
BTC, ETH, SOL, etc.Layer-1 protocol tokens with established custody models. Bitcoin and Ether have mature institutional infrastructure; newer L1s may have limited qualified custodian support.
- Well-established cold storage practices
- Broad custodian support
- Clear regulatory treatment in most jurisdictions
Stablecoins
USDC, USDT, EURCFiat-pegged tokens with issuer-specific considerations. The GENIUS Act (July 2025) established a federal payment-stablecoin framework in the US; MiCA distinguishes asset-referenced tokens and e-money tokens.
- Issuer regulatory status varies
- Reserve transparency requirements
- May involve payment-services licensing overlay
ERC-20 & Fungible Tokens
Protocol tokens, governanceStandard fungible tokens on EVM chains. Custody is technically straightforward but asset-specific due diligence is required for each token's smart-contract risk and regulatory classification.
- Broad custodian support for major tokens
- Smart-contract risk at token level
- Governance/voting support varies
Staked Assets
stETH, validator positionsAssets locked in proof-of-stake validation. Requires separation of validator keys (hot) from withdrawal keys (cold). The May 2025 SEC staff statement addresses non-discretionary staking; MiCA ESMA Q&A 2067 addresses CASP liability.
- Key separation architecture required
- Slashing liability allocation varies
- Liquid staking tokens add complexity
Smart-Contract Wallets / Safe
Multi-sig, account abstractionProgrammable wallet contracts with embedded governance logic. Safe is the dominant EVM standard. EIP-7702 (Pectra upgrade) expanded account abstraction capabilities.
- Customizable approval thresholds
- Recovery mechanisms possible
- Smart-contract risk at wallet layer
- Key rotation without address change
Tokens with embedded compliance logic restricting transfers to whitelisted addresses. ERC-3643 is a leading standard for regulated securities on-chain. Portability between custodians requires re-whitelisting.
- Identity and compliance integration required
- Transfer restrictions limit custodian flexibility
- Issuer coordination for custodian changes
Tokenized Funds & Vault Wrappers
BUIDL, BENJI, tokenized TreasuriesOn-chain representations of traditional fund shares or treasury positions. Require dual custody architecture: traditional custodian for underlying assets, crypto custodian for tokens. Market grew significantly through 2025.
- Dual custody complexity
- NAV calculation integration
- Custodian-of-record questions under Advisers Act
- Fund administrator coordination
Custody Selection Implication: Asset mix significantly shapes custodian selection. Institutions holding only Bitcoin and Ether have broad options. Those with staked positions, governance tokens, or tokenized assets require providers with specific capabilities. Verify current support directly with providers, as asset coverage evolves rapidly.
Risk Framework for Custody Decisions
Custody risk is multi-dimensional. Institutions should evaluate potential providers across distinct risk categories rather than conflating them into a single assessment. Each dimension requires separate analysis and mitigation strategies.
Operational Risk
Risk of loss from internal failures, errors, or security breaches within the custody operation.
Key Considerations
- Key ceremony procedures and audit history
- Employee access controls and segregation of duties
- Incident response and disaster recovery capabilities
- Penetration testing and security audit results
- SOC 1/2 Type II attestation status
Mitigants
SOC reports, insurance coverage (crime, cyber, E&O), documented key ceremonies, and multi-party authorization requirements.
Counterparty Risk
Risk of loss if the custodian fails financially or operationally. The FTX collapse demonstrated this risk can materialize rapidly and severely.
Key Considerations
- Custodian financial stability and capitalization
- Asset segregation: on-chain vs. omnibus
- Bankruptcy remoteness of client assets
- Regulatory capital requirements
- Proof of reserves methodology
Mitigants
Segregated custody (MiCA Art. 75(7) requires this for EU CASPs), regulatory capital requirements, qualified custodian status, and clear contractual title to assets.
Governance / Control Risk
Risk arising from inadequate oversight, unclear authorization processes, or concentration of control that enables unauthorized actions.
Key Considerations
- Policy engine flexibility and enforcement
- Multi-party authorization requirements
- Whitelist and velocity limit capabilities
- Audit trail completeness
- Key-share distribution (for MPC/multi-sig)
Mitigants
MPC or multi-sig architectures where no single party can move assets; configurable policy engines; client-held key shares; immutable audit logs.
Smart-Contract / Policy Risk
Risk from vulnerabilities in smart contracts used for custody (multi-sig wallets, account abstraction) or in assets being custodied (token contracts, DeFi protocols).
Key Considerations
- Wallet contract audit history
- DeFi protocol whitelisting criteria
- Bridge and L2 exposure policies
- Oracle and MEV considerations
- Policy engine logic correctness
Mitigants
Audited and battle-tested contracts (Safe has extensive track record); policy engines with allowlists for contract interactions; specialized smart-contract insurance; transaction simulation before execution.
Regulatory / Perimeter Risk
Risk that regulatory changes affect custodian viability, service continuity, or the institution's ability to use a particular provider. Includes cross-border complexity.
Key Considerations
- Custodian licensing status and jurisdiction
- MiCA transition deadline (July 2026) compliance
- US qualified custodian status for RIAs
- Cross-border custody restrictions
- Regulatory examination history
Mitigants
Use of custodians with clear regulatory standing; monitoring transitional deadlines; multi-custodian arrangements for jurisdictional diversification; contractual provisions for regulatory change scenarios.
Applying the Risk Framework
These risk dimensions should be evaluated separately, not averaged into a single score. A provider may have strong operational controls but weak counterparty protections (or vice versa). Institutions should weight each dimension according to their specific risk tolerance, regulatory requirements, and use case. The right custody solution minimizes total risk across all dimensions relevant to your profile—not just the most visible ones.
Institutional Use Cases
Different institutional participants have distinct custody requirements based on their business models, regulatory obligations, and operational needs.
Asset Managers & Funds
Profile: Hedge funds, venture funds, family offices, and registered investment advisers managing crypto allocations for clients.
Key Requirements
- Qualified custodian status for regulatory compliance
- Segregated accounts for investor reporting
- NAV calculation and audit support
- Trade execution integration
- Multi-strategy support (trading, staking, DeFi)
Typical Approach
Regulated qualified custodian, often with prime brokerage relationship for trading. May use multiple custodians for diversification.
Corporate Treasury
Profile: Public and private companies holding digital assets as treasury reserves or for operational purposes.
Key Requirements
- Board-level governance controls
- Audit-ready record keeping
- Integration with corporate accounting
- Insurance coverage aligned with treasury policy
- Clear SLAs and liability frameworks
Typical Approach
Qualified custodian with strong governance controls. Often prefer regulated entities for audit and reporting simplicity. May maintain some self-custody capability.
Exchanges & Trading Venues
Profile: Centralized exchanges, OTC desks, and trading platforms that hold customer assets.
Key Requirements
- High-throughput transaction signing
- Hot/warm/cold wallet architecture
- Instant settlement capabilities
- Multi-asset support across chains
- Proof of reserves capabilities
Typical Approach
Often build proprietary solutions using infrastructure providers (MPC platforms). May partner with qualified custodians for cold storage component. Focus on operational efficiency.
Banks & Financial Institutions
Profile: Traditional banks entering digital asset services, either for proprietary positions or client services.
Key Requirements
- Bank-grade security standards
- Regulatory compliance (OCC, state regulators)
- Integration with existing infrastructure
- Sub-custody arrangements
- White-label capabilities
Typical Approach
Partner with established custody technology providers or qualified custodians. Focus on regulatory clarity and integration with existing systems. May pursue own regulatory approvals over time.
Web3 Protocols & DAOs
Profile: Decentralized protocols, foundations, and DAOs managing treasury assets or protocol-controlled value.
Key Requirements
- Transparent governance mechanisms
- Multi-sig with distributed signers
- On-chain verification capabilities
- DeFi protocol compatibility
- Decentralization-preserving solutions
Typical Approach
Self-custody via multi-sig wallets (Gnosis Safe/now Safe) with distributed signers. May use MPC for operational efficiency while maintaining decentralization principles. Hybrid approaches emerging.
High-Net-Worth Individuals
Profile: Wealthy individuals and family offices with significant personal crypto holdings.
Key Requirements
- Privacy and discretion
- Estate planning integration
- Personal liability protection
- Flexible access for active management
- Tax reporting support
Typical Approach
Mix of self-custody (hardware wallets, multi-sig) and qualified custodian for larger holdings. Often work through family office structures. May use multiple solutions for diversification.
How Institutions Should Use This Map
- Identify your profile: Understand which use case category (or combination) best describes your organization.
- Assess requirements: Use the decision framework to identify must-have vs. nice-to-have features.
- Evaluate providers: Map provider capabilities against your requirements, considering the control stack.
- Plan for evolution: Custody needs change as organizations mature—consider flexibility and portability.
- Conduct due diligence: This map is a starting point; detailed provider evaluation requires direct engagement and technical review.
Methodology & Neutrality Statement
About This Resource
This landscape overview is produced by the Enterprise Ethereum Alliance (EEA) as an educational resource for institutional participants evaluating digital asset custody solutions. The content is intended to provide a framework for understanding the custody landscape, not to recommend specific providers or solutions.
Methodology
The information presented is compiled from publicly available sources including:
- Provider websites and published documentation
- Regulatory filings and public records
- Industry reports and analysis
- Technical documentation and whitepapers
- News and press coverage
Categorization reflects observed operating models based on public information. Providers may offer services across multiple categories, and the primary categorization reflects the most prominent positioning.
Limitations
- This is a point-in-time snapshot of a rapidly evolving market
- Provider capabilities and regulatory status change frequently
- Not all providers are included; selection reflects prominence in institutional markets
- No independent verification of provider claims has been conducted
- This is not investment, legal, or regulatory advice
Neutrality Principles
This resource adheres to the following principles:
- No endorsements: Inclusion does not constitute recommendation or endorsement
- No competitive rankings: Providers are categorized by operating model, not quality
- No commercial relationships: Content is not influenced by provider sponsorship
- Educational purpose: Information is provided for educational use only
- Transparency: Methodology and limitations are clearly stated
EEA Engagement & Framework Validation
The Enterprise Ethereum Alliance is committed to developing credible, industry-informed resources that benefit the entire ecosystem. We invite custody providers and institutional participants to engage with this framework.
For Custody Providers
We welcome custody providers to:
- Validate categorization: Review how your organization is represented and provide corrections or clarifications
- Contribute insights: Share perspectives on custody trends, emerging requirements, and market evolution
- Participate in working groups: Join EEA initiatives focused on custody standards and best practices
- Engage with membership: Learn about EEA membership benefits and how participation advances industry standards
Provider engagement helps ensure this resource accurately reflects the market and serves institutional needs.
For Institutional Users
Institutions evaluating custody solutions can:
- Use this framework: Apply the decision framework and evaluation criteria to your specific needs
- Share requirements: Help us understand what institutional users need from custody resources
- Request deeper dives: Suggest topics for expanded coverage or additional analysis
- Join the conversation: Participate in EEA events and working groups on custody topics
About the Enterprise Ethereum Alliance
The EEA is a member-driven standards organization whose charter is to develop open blockchain specifications that drive harmonization and interoperability for businesses and consumers worldwide. Our global community of members includes leaders across industries working together to create enterprise-grade solutions.
This custody landscape resource represents one element of EEA's broader work to support institutional adoption of blockchain technology through education, standards development, and ecosystem coordination.