Blockstream co-founder and CEO Adam Back has publicly endorsed covenant opcodes as a candidate for Bitcoin's "last soft-fork," arguing that a general-purpose, formally verified scripting toolkit would reduce the need for repeated protocol changes while making Bitcoin Script safer.

Back laid out his position on October 1, 2026. His argument rests on two linked claims: covenant-enabling opcodes would cut the frequency of future soft forks, and formal semantics combined with mathematical proofs would let developers verify that a contract behaves as intended before real funds are committed.

What did Back actually propose?

A soft fork is a backward-compatible tightening of Bitcoin's rules: older nodes keep functioning while the network enforces stricter spending conditions. Each one demands slow, contentious coordination across miners, node operators and developers. Back's framing inverts that calculus — build one broad toolkit now, verify it rigorously, and let future innovation happen on top of it rather than through the base layer.

His endorsement carries a notable corporate dimension. Back referenced Simplicity, the smart-contract language Blockstream developed and launched on its Liquid sidechain in 2025. Simplicity was designed from the start for formal verification and delivers covenant-like functionality, aligning directly with Back's emphasis on mathematical proofs. The executive advocating formally verifiable scripting also runs the company that built a formally verifiable scripting language.

Where do CTV and OP_CAT stand?

The covenant debate in 2026 centers on two concrete proposals:

• CTV (BIP 119) — a covenant opcode restricting where coins can be spent next, currently in draft or signaling stages.
• OP_CAT (BIP 347) — a general-purpose opcode enabling covenant-like constructions through composition, also still in draft or signaling stages.

As of early October 2026, neither proposal has reached Bitcoin mainnet. Both have seen activity through signet testing and draft Bitcoin Improvement Proposals. Signet is a test network where developers experiment with proposed features without risking actual Bitcoin.

Why modular opcodes, not specific ones?

Back's position is not a recent conversion. He has promoted modular opcodes over highly specific alternatives since at least 2021. The distinction marks a core fault line in the covenant debate: specific opcodes do one job well and are easier to reason about, while modular opcodes are general-purpose tools developers can combine in ways their designers never anticipated.

The "last soft-fork" framing is the logical endpoint of the modular camp. Rather than shipping narrow opcodes one by one — each requiring its own consensus negotiation — Bitcoin would adopt a general toolkit once and route future capability-building to layers built on top.

What are the operational consequences?

Back's statement triggered no immediate market effects and no token launches; this remains a protocol-level debate among developers. The near-term signal for engineers is signet activity and the progress of BIP 119 and BIP 347. Movement from testing to formal signaling on mainnet would mark a genuine shift in momentum for the covenant camp.

Simplicity's live deployment on Liquid also gives developers a working production environment to evaluate covenant-like designs, and its track record there could inform how base-layer proposals are assessed during future review cycles.

Whether Back's "last soft-fork" thesis gains traction will become visible in the coming months as CTV and OP_CAT move — or stall — between signet experimentation and formal mainnet signaling.