A single absent capability in Bitcoin Script has ignited one of the most contested upgrade debates in the network's history, producing twelve competing proposals and no consensus in sight. Cointelegraph Research has published the first installment of a deep-dive series examining what Bitcoin covenants are, how they would work, and what their addition could mean for the network's future.
What Covenants Would Change
Covenants are a category of spending condition that would allow $BTC transactions to enforce rules not just on who can spend coins, but on where those coins can go next. In plain terms, a covenant would let a sender program constraints that travel with the bitcoin itself, binding future transactions to specific conditions rather than simply requiring a signature at the point of spend. This is a meaningful departure from how Bitcoin Script currently operates, where control over funds effectively ends the moment a valid signature is produced.
The gap between what developers want to build and what Bitcoin Script currently permits is the engine driving the proposal backlog. According to Cointelegraph Research, that single missing feature — the inability to inspect or restrict an output's destination within the script itself — is the common root of all twelve proposals under discussion.
Twelve Proposals, One Problem
The proliferation of competing covenant designs reflects both the technical difficulty of the problem and the philosophical tensions within the Bitcoin development community. Each proposal represents a different opinion on how much expressive power to add, what the security trade-offs look like, and how changes should interact with the network's existing architecture. The fact that one missing primitive has generated a dozen distinct solutions suggests developers broadly agree a gap exists, even as they disagree sharply on how to close it.
What Comes Next
Cointelegraph Research frames this first piece as an overview — a map of the landscape before the technical terrain gets examined in later installments. For market participants, the covenant debate matters because the outcome will shape what kinds of applications can be built natively on Bitcoin: more sophisticated self-custody arrangements, new forms of smart contracting, and programmable spending logic that currently requires moving assets off-chain or onto a separate layer. None of those possibilities can be fully evaluated until the community settles on which proposal, if any, moves toward activation.
The debate is live. With twelve proposals competing for attention, the path from whitepaper to soft fork remains uncertain — but the research community is clearly taking the question seriously.