Intelligence DisruptMining Disrupt Buy ticketsTickets

Bitcoin covenant proposals

Nine proposals to let Bitcoin script control where coins go next, compared.

Nine proposals, one theme: letting Bitcoin script control where coins can go next, not just who can spend them. Here they are side by side, with when each was numbered.

2020202120222023202420252026BIP 119BIP 119 · 2020-01-06BIP 347BIP 347 · 2023-12-11BIP 348BIP 348 · 2024-11-26BIP 443BIP 443 · 2025-05-08BIP 446BIP 446 · 2026-02-06BIP 449BIP 449 · 2026-03-05BIP 448BIP 448 · 2026-03-11BIP 440BIP 440 · 2026-03-25BIP 441BIP 441 · 2026-03-25
When each proposal was assigned its BIP number. Source: bitcoin/bips, read Nov 7, 2026.
BIPProposalWhat it doesStatusAssigned
BIP 119OP_CHECKTEMPLATEVERIFY (CTV)Commits an output to the exact transaction that may spend it: vaults, congestion control, simple payment pools.Draft2020-01-06
BIP 347OP_CAT in TapscriptConcatenates two stack items, re-enabling Satoshi's original opcode inside Tapscript.Complete2023-12-11
BIP 348OP_CHECKSIGFROMSTACK (CSFS)Checks a signature against data on the stack, not only against the spending transaction.Draft2024-11-26
BIP 443OP_CHECKCONTRACTVERIFY (CCV)Lets outputs carry committed data and constrain the next outputs: state machines and vaults.Draft2025-05-08
BIP 446OP_TEMPLATEHASHPushes a hash of the spending transaction, a Taproot-native relative of CTV.Draft2026-02-06
BIP 448Taproot-native (Re)bindable TransactionsBundles OP_TEMPLATEHASH, CSFS and OP_INTERNALKEY to improve second-layer protocols such as Lightning.Draft2026-03-11
BIP 449OP_TWEAKADDAdds a tweak to an x-only key inside script, mirroring the Taproot tweak signers already use.Draft2026-03-05
BIP 440Varops budgetGeneralises the sigops budget to every operation, so script limits follow actual computation.Draft2026-03-25
BIP 441Restoration of disabled script (Tapleaf 0xC2)Re-enables Bitcoin's original opcodes under the varops budget, with far larger stack limits.Draft2026-03-25

How they fit together

Template commitments
CTV (119) and OP_TEMPLATEHASH (446) commit to the next transaction. BIP 448 packages TEMPLATEHASH with CSFS and INTERNALKEY.
General building blocks
OP_CAT (347), CSFS (348) and OP_TWEAKADD (449) are small opcodes that combine into covenants and more.
Full script programs
CCV (443) adds committed state. BIPs 440 and 441 (the Great Script Restoration) bring back the original opcodes under a computation budget.

For how these would reach the chain, see how miners activate soft forks.

Questions

What is a covenant in Bitcoin?
A rule that limits how a coin can be spent next, for example only to a pre-agreed transaction. Today's Bitcoin script can check who signs, but not where the money goes.
Which covenant proposal is closest to activation?
None is scheduled. All are drafts except BIP 347 (OP_CAT), which the repository lists as Complete. Activation would need a soft fork that nodes and miners adopt.
Why do people want covenants?
Vaults that stop thieves from emptying a wallet, cheaper shared UTXOs, and simpler Lightning channels. Critics worry about complexity and unforeseen uses.
What do covenants mean for miners?
Like any soft fork they need miner signalling. Some designs (CTV-based congestion control) also change how fee demand reaches blocks.

Sources

  1. BIP 119
  2. BIP 347
  3. BIP 348
  4. BIP 443
  5. BIP 446
  6. BIP 448
  7. BIP 449
  8. BIP 440
  9. BIP 441

Meet the people who mine and build Bitcoin

Soft forks only happen when miners, node operators and developers line up. Mining Disrupt 2027 puts them in one room, March 22–24 at the Irving Convention Center, Dallas. Get a pass or exhibit.

Buy ticketsExhibit

More: All BIPs · BIPs for miners · BIP 54 · BIP 323 · Quantum BIPs · Taproot · BIP 110

Three days. One floor. The whole industry.

March 22–24, 2027 · Irving Convention Center · Dallas

Mining Disrupt 2027Dallas · Mar 22–24Passes from $199Get tickets