Why it matters
Most bitcoin losses happen quickly: a compromised key, a phishing attack, a moment of panic. Vaults introduce friction that slows down or prevents unauthorized transfers, even if an attacker gains access to credentials.
For long-term holders, immediate access is rarely necessary. A vault structure acknowledges this reality and designs security around it.
How vaults work
Time delays: Withdrawals require a waiting period (hours or days) before execution. During this window, the legitimate owner can cancel unauthorized transactions.
Multi-party approval: Withdrawals require signatures from multiple parties: different individuals, different devices, or different organizations. No single compromised credential enables theft.
Velocity limits: Restrictions on how much can be withdrawn in a given period. Even a successful attack can only drain funds slowly, giving time for detection and response.
Geographic distribution: Key material or approval authority spread across locations. An attacker would need to compromise multiple physical sites simultaneously.
Vault vs hot wallet
| Characteristic | Vault | Hot wallet |
|---|---|---|
| Access speed | Hours to days | Immediate |
| Security focus | Maximum protection | Operational convenience |
| Use case | Long-term storage | Active spending |
| Attack resistance | High | Lower |
| Complexity | Higher | Lower |
Most institutional custody architectures use both: vaults for the majority of holdings, hot wallets for operational liquidity.
Implementation approaches
Custodial vaults: A custody provider implements time delays and approval workflows. The provider controls the infrastructure but clients control approvals.
Multisig vaults: Native Bitcoin scripts requiring multiple keys, potentially with time-lock conditions. Fully on-chain, no trusted third party.
Collaborative custody vaults: Key material distributed between holder and service provider. Neither can act unilaterally.
Considerations
Vault security comes with tradeoffs:
- Emergency access may be slow when legitimately needed
- Approval processes add operational complexity
- Time delays must be long enough to detect attacks but short enough for legitimate use
- Vault infrastructure itself must be secure
