Vaults and Covenants

💡 The Plain-English Definition

Covenants are Bitcoin spending conditions that restrict not just who can spend Bitcoin, but where it can go next. Vaults use covenants to create a withdrawal delay with a cancellation window — so if your keys are stolen, you can claw back the Bitcoin before the thief finalises the transaction.

🤔 But Why Though?

Standard Bitcoin security has an unavoidable weakness: if someone gets your private key, they can immediately move your Bitcoin — instantly and irrevocably. Self-custody requires that the holder accepts this risk and manages it through operational security. Covenants change this by adding a temporal constraint to spending: even with the correct key, the Bitcoin can’t go just anywhere — the script defines a restricted set of destinations or enforces a delay before the funds are accessible.

A Bitcoin vault built on covenants would work like this: you send Bitcoin into a vault address. When you want to withdraw, you initiate the withdrawal to a pre-defined “recovery” address — not the final destination. After a delay of, say, 24 hours enforced by a CSV timelock (a Bitcoin script condition requiring a set number of blocks to pass after the initiating transaction confirms), the Bitcoin moves to the final destination. During that 24-hour window, if you see the withdrawal happening and didn’t initiate it — because a thief triggered it — you can broadcast a “clawback” transaction that returns the Bitcoin to a cold storage address, cancelling the theft. The thief can’t finalize the move because the delay gives you time to react.

Two proposed opcode upgrades make this possible. OP_CTV (CheckTemplateVerify — BIP119, proposed by Jeremy Rubin) allows a transaction to commit to exactly which future transaction can spend its output — enforcing the “where it goes next” restriction simply and efficiently. OP_VAULT (BIP345, proposed by James O’Beirne) implements the full vault pattern with delay and clawback in a more expressive way. As of 2025–2026, neither has been activated in Bitcoin — both remain proposals under active community debate about whether their benefits justify the scripting complexity they introduce. The Winternitz Vault (a quantum-resistant vault design using hash-based signatures rather than elliptic curve cryptography) is a notable variant that addresses both the custody security and the post-quantum cryptography threat simultaneously — making vaults potentially relevant for both current and future security concerns.

🌍 The Real-World Analogy

A Bitcoin vault with covenants is like a bank transfer with a mandatory 24-hour review period before it clears. If you initiate the transfer, it sits pending — visible to you — before completing. If someone fraudulently initiates a transfer from your account, you see the pending transaction, call the bank, and cancel it before it clears. Today’s Bitcoin doesn’t have this cancellation window: once broadcast with a valid signature, a transaction is permanent. Covenants add that pending window back — not by involving a bank, but by encoding the delay and cancellation logic directly in the Bitcoin script.