Safe vs Fireblocks vs Qualified Custody: Choosing a Crypto Custody Model

Safe is the smart-contract multisig standard for self-custody: signers approve transactions on-chain under a threshold you set, and Safe Modules add custom authorization such as spending limits, time-locks, and allowlists. Safe reports tens of billions in assets secured across millions of accounts, and Safe{Core} supports ERC-4337 account abstraction and passkeys. Because it is fully on-chain, anyone can audit the signer set, threshold, and every execution, and it integrates natively with DeFi. We are an official Safe partner, so this is the model we know most deeply, and it is the standard for DAO and protocol treasuries.

The trade-off is that it is shared control you operate, not a managed workflow, and on-chain transparency does not make it foolproof. The February 2025 Bybit hack, the largest crypto theft on record at roughly $1.5B, exploited a Safe multisig by compromising the signing front-end and deceiving signers into approving a malicious transaction; the contracts were fine, the humans were tricked. That is the concrete case for the discipline this model demands: a high signer threshold, transaction simulation, hardware signing, and defenses against blind-signing.

Fireblocks is the most widely deployed MPC wallet infrastructure for institutions, with roughly $10T in cumulative secured transfers (about $6T in 2025 alone). MPC here is threshold signing (MPC-CMP, with proactive key-share refresh), not multisig: key shares are distributed so a whole key never exists in one place, and share distribution is configurable, in a self-custody setup the customer can hold all shares. A policy engine gates approvals off-chain before shares are released, and on-chain it produces one ordinary-looking signature, so lower gas, broad compatibility, and one workflow across chains.

An important 2026 correction to the old "Fireblocks is not a custodian" line: Fireblocks now operates its own NYDFS-chartered qualified custodian, Fireblocks Trust Company (used by Galaxy, FalconX, Bakkt, and others), so a regulated institution can get qualified custody from Fireblocks directly rather than only through third-party trusts. The ~2,400-organization Fireblocks Network adds direct settlement between counterparties. Peers in the MPC model include Copper, Cobo, Fordefi (DeFi-native), and Dfns. We integrate MPC custody into products as part of our custody work.

A qualified custodian is a chartered entity that holds the keys under a regulated trust, running MPC or HSM cold storage behind the scenes: Anchorage (OCC national trust), Coinbase Custody (NYDFS-chartered, and approved in April 2026 for an OCC national trust charter), and BitGo Trust (South Dakota and New York trust, MiCA CASP license in Germany, insurance around $250M; BitGo went public on the NYSE in January 2026). "Qualified custodian" is a legal status layered on custody technology, not a technology itself.

Infrastructure providers such as Fireblocks, Copper, Cobo, Fordefi, Dfns, and Safe are not themselves qualified custodians unless paired with a chartered entity, though Fireblocks and some peers now operate or hold their own licenses. Custody insurance is also narrower than it sounds: it typically covers third-party theft and crime up to an aggregate limit shared across all clients, not market loss, protocol hacks, or client-authorized transactions, and it is available across models, not only qualified custodians.