Definition
A recursive covenant is a covenant whose restrictions reproduce themselves in the outputs it creates, so the same rules can apply not just to the immediate next spend but to every transaction descending from it. Where a non-recursive covenant constrains a single forward hop, a recursive one can, in principle, carry its conditions forward indefinitely. Recursive covenants are not active on Bitcoin's base layer; they are a property of certain proposed and experimental covenant designs.
Recursive versus non-recursive
The distinction is about scope. A non-recursive design, such as a fixed-template commitment, forces coins into one predetermined next transaction and then releases them. A recursive design lets the spending transaction re-impose covenant rules on its own outputs, effectively maintaining state across a chain of spends. General-purpose introspection primitives (for example, script concatenation combined with signature checks) tend to make recursion possible, while narrowly scoped opcodes are often designed specifically to avoid it.
Why it is contentious
Recursion is what makes the most ambitious Bitcoin applications conceivable: long-lived vaults, sidechain-style pegs, and complex state machines. The same property worries some reviewers, because coins could become permanently encumbered by rules they cannot escape, which touches on fungibility. There is even ongoing debate among experts about exactly which constructions deserve the label. The practical takeaway is that recursion is a design dimension to weigh, not automatically good or bad.
See the general concept of a covenant and the introspection-enabling opcode OP_CAT for how recursion can arise. D-Central offers this as a neutral explainer of an open research area.
In Simple Terms
A recursive covenant is a covenant whose restrictions reproduce themselves in the outputs it creates, so the same rules can apply not just to the…