Definition
A covenant is a spending condition that constrains how bitcoin may be spent in the future, rather than only who may authorize the spend. Today, a standard Bitcoin script asks a single question: does the spender hold the right key or preimage? A covenant adds a second class of question: does the transaction that spends this output send the coins to a permitted destination, in a permitted amount, with a permitted structure? Covenants are not active on Bitcoin's base layer; they are a family of proposed and experimental soft-fork ideas under ongoing community review.
Why covenants are debated
Covenants would unlock self-custody tools such as vaults, congestion-control payment trees, payment pools, and more flexible Layer 2 channels. The trade-off is expressiveness versus restraint. A tightly scoped covenant applies to one forward hop only; a broad one can re-impose its own rules on every coin that descends from it. The latter, called a recursive covenant, raises questions about fungibility and whether coins could be permanently encumbered. Reasonable engineers disagree on where to draw the line, which is why no single proposal has reached consensus.
How they are built
Most covenant designs introduce transaction introspection: a way for a script to inspect fields of the spending transaction (outputs, amounts, scripts) and reject spends that do not match a committed template. Approaches differ in how much they expose and how composable they are. The leading proposals are evaluated on safety, simplicity, and review maturity rather than feature count.
For specific proposals, see OP_CHECKTEMPLATEVERIFY and the broader idea of a recursive covenant. These notes reflect D-Central's reading of the current research; they are not predictions about activation.
In Simple Terms
A covenant is a spending condition that constrains how bitcoin may be spent in the future, rather than only who may authorize the spend. Today,…