Bitcoin Script can do a lot. It just can’t do one specific thing cleanly: enforce sophisticated spending rules that depend on what the next transaction does.

Cointelegraph Research points to that “single missing feature” as the reason the Bitcoin ecosystem now has twelve competing proposals for “covenants” — mechanisms that let users constrain future spending of funds. If you’ve been around Bitcoin long enough, you’ve seen this movie before. In this version, the plot is tighter because the missing capability sits directly at the scripting layer.

What covenants are trying to fix

In the Cointelegraph Research overview, covenants are presented as a path to more complex spending conditions than today’s Script can reliably express. The core idea is simple even when the engineering isn’t. You want to lock coins now, then force (or strongly constrain) how they can be spent later.

That matters because Bitcoin today relies on a mix of timelocks, multi-signature setups, and off-chain coordination to approximate “policy” across time. Covenants aim to put more of that policy into consensus-enforced logic.

The catch is that Bitcoin is conservative by design. Any new spending primitive has to fit into Script without breaking assumptions around validation cost, flexibility, and network safety. Cointelegraph frames the explosion of proposals as a sign that multiple researchers think they can fill the gap, but no one design has won universal trust.

Why twelve proposals exist

Cointelegraph Research doesn’t treat “twelve” as trivia. It’s the central signal. When a single missing Script feature drives many competing designs, it usually means the engineering problem has multiple legitimate constraints.

For example, different covenant approaches can vary in what they enforce, where they put the logic (script vs opcode vs transaction structure), and how expensive they are to validate. Even if the end goal looks similar on paper, the operational and security implications can differ.

In that context, “competing proposals” also implies a deeper reality. Bitcoin doesn’t just need an idea. It needs a mechanism that implementers can ship, that miners and validators can handle without surprises, and that users can audit without taking a leap of faith.

The bigger question: complexity vs Bitcoin’s guardrails

Covenants are attractive because they broaden what Bitcoin transactions can express. But Cointelegraph Research’s framing suggests skepticism, too. Adding power at the scripting layer can increase the space of possible transaction behaviors. That can complicate wallet logic, auditing workflows, and edge-case handling.

Bitcoin developers have long treated “script expressiveness” as something that must earn its place. That’s because consensus-enforced rules don’t just affect cryptography. They affect reliability.

If covenant designs require more complex evaluation paths or new transaction semantics, they can shift the operational baseline for clients that validate blocks. Even small performance changes at scale become real network constraints.

What comes next in Cointelegraph’s series

Cointelegraph describes this as “Part 1” and positions it as an overview. That implies the next installments will get more specific about the proposals and what each one changes.

For readers, the practical takeaway is to watch for details that matter beyond headlines.

  • Do the proposals preserve the safety properties users expect from Bitcoin Script.
  • How do they constrain the “next step” of spending.
  • What execution cost do they add, if any, and where.
  • Whether the designs require new tooling or special-casing in clients.

Until those questions get answered, a covenant proposal is still a theory. A shipped feature is something else.

A missing feature can still be the whole story

Cointelegraph Research pins the whole wave on a single missing Script feature. That’s a useful way to cut through the noise. It suggests the community isn’t chasing covenants because “new stuff is cool.” It’s chasing them because the current scripting toolbox can’t express the kind of constrained spending policy that some developers want.

Twelve proposals later, the signal is clear. The demand is real. The path is not settled.

And in Bitcoin, “not settled” is often the correct status. Asset features at the consensus layer are high-stakes upgrades, not an academic exercise.