Adam Back backs covenant opcodes as a possible ‘last soft-fork’ for Bitcoin

Adam Back backs covenant opcodes as a possible ā€˜last soft-fork’ for Bitcoin

The Blockstream CEO argues covenant tools and formal verification could make Bitcoin Script safer and reduce the need for repeated protocol upgrades

Adam Back wants Bitcoin to stop upgrading so often. His proposed route to fewer upgrades is, somewhat ironically, one more upgrade.

On October 1, 2026, the co-founder and CEO of Blockstream publicly endorsed covenant opcodes and related technologies. He framed them as a potential “last soft-fork” that could cut down on future protocol changes while making Bitcoin Script more secure.

What Back is actually arguing

Back’s position rests on two linked ideas. The first is that covenant-enabling tools could reduce how often Bitcoin needs new soft forks.

A soft fork is a backward-compatible change to Bitcoin’s rules. Older nodes keep working, but the network collectively agrees to enforce a tighter set of conditions. These upgrades are slow, contentious, and require broad coordination across miners, node operators, and developers.

The second idea is security. Back emphasized formal semantics and mathematical proofs as ways to harden Bitcoin Script, the simple programming language that defines how coins can be spent.

Formal semantics means describing exactly what a piece of code does in precise mathematical terms. Mathematical proofs then let developers verify that a contract behaves as intended before anyone puts real money behind it.

Advertisement

Covenants, explained without the jargon

A covenant, in Bitcoin terms, is a rule attached to coins that restricts how they can be spent in the future. Today, Bitcoin Script mostly checks whether someone has the right to spend coins. Covenants would also let a script influence where those coins go next.

Several concrete proposals have picked up renewed attention in 2026. They include CTV, formally BIP 119, and OP_CAT, designated BIP 347.

Both have seen activity through signet testing and draft Bitcoin Improvement Proposals. Signet is a test network where developers can experiment with proposed features without risking actual Bitcoin.

None of these proposals has made it to Bitcoin mainnet. As of early October 2026, CTV and OP_CAT remain in draft or signaling stages.

The Simplicity connection

Back’s comments referenced Simplicity, a smart-contract language developed by Blockstream. Simplicity was launched on the Liquid Network in 2025.

Liquid is a Bitcoin sidechain operated by Blockstream. Simplicity aims to deliver covenant-like functionality and was built with formal verification in mind, which lines up with Back’s emphasis on mathematical proofs for script security.

That alignment is worth noting. The executive advocating for formally verifiable scripting runs the company that built a formally verifiable scripting language.

A long-running preference

Back’s latest remarks are not a sudden conversion. He has consistently promoted modular opcodes over highly specific approaches since as early as 2021.

The distinction is a core fault line in the covenant debate. Specific opcodes are designed to do one job well and are easier to reason about. Modular opcodes are general-purpose tools that can be combined in ways their designers may not have anticipated.

Back has planted his flag in the modular camp. His “last soft-fork” framing is essentially the logical endpoint of that position: build a general toolkit once, verify it rigorously, and let future innovation happen on top of it.

What this means for Bitcoin

Back’s statement carried no immediate market effects and no token launches. This is a protocol-level debate.

For developers, the near-term signal is to watch signet activity and the progress of draft BIPs like BIP 119 and BIP 347. Movement from testing to formal signaling on mainnet would mark a genuine change in momentum.

Simplicity’s track record on Liquid may also become a reference point. Its live deployment offers developers a working environment to evaluate covenant-like designs, which could inform how base-layer proposals are judged.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.
Adam Back backs covenant opcodes as a possible ā€˜last soft-fork’ for Bitcoin
Adam Back backs covenant opcodes as a possible ‘last soft-fork’ for Bitcoin

The Blockstream CEO argues covenant tools and formal verification could make Bitcoin Script safer and reduce the need for repeated protocol upgrades

Adam Back wants Bitcoin to stop upgrading so often. His proposed route to fewer upgrades is, somewhat ironically, one more upgrade.

On October 1, 2026, the co-founder and CEO of Blockstream publicly endorsed covenant opcodes and related technologies. He framed them as a potential “last soft-fork” that could cut down on future protocol changes while making Bitcoin Script more secure.

What Back is actually arguing

Back’s position rests on two linked ideas. The first is that covenant-enabling tools could reduce how often Bitcoin needs new soft forks.

A soft fork is a backward-compatible change to Bitcoin’s rules. Older nodes keep working, but the network collectively agrees to enforce a tighter set of conditions. These upgrades are slow, contentious, and require broad coordination across miners, node operators, and developers.

The second idea is security. Back emphasized formal semantics and mathematical proofs as ways to harden Bitcoin Script, the simple programming language that defines how coins can be spent.

Formal semantics means describing exactly what a piece of code does in precise mathematical terms. Mathematical proofs then let developers verify that a contract behaves as intended before anyone puts real money behind it.

Advertisement

Covenants, explained without the jargon

A covenant, in Bitcoin terms, is a rule attached to coins that restricts how they can be spent in the future. Today, Bitcoin Script mostly checks whether someone has the right to spend coins. Covenants would also let a script influence where those coins go next.

Several concrete proposals have picked up renewed attention in 2026. They include CTV, formally BIP 119, and OP_CAT, designated BIP 347.

Both have seen activity through signet testing and draft Bitcoin Improvement Proposals. Signet is a test network where developers can experiment with proposed features without risking actual Bitcoin.

None of these proposals has made it to Bitcoin mainnet. As of early October 2026, CTV and OP_CAT remain in draft or signaling stages.

The Simplicity connection

Back’s comments referenced Simplicity, a smart-contract language developed by Blockstream. Simplicity was launched on the Liquid Network in 2025.

Liquid is a Bitcoin sidechain operated by Blockstream. Simplicity aims to deliver covenant-like functionality and was built with formal verification in mind, which lines up with Back’s emphasis on mathematical proofs for script security.

That alignment is worth noting. The executive advocating for formally verifiable scripting runs the company that built a formally verifiable scripting language.

A long-running preference

Back’s latest remarks are not a sudden conversion. He has consistently promoted modular opcodes over highly specific approaches since as early as 2021.

The distinction is a core fault line in the covenant debate. Specific opcodes are designed to do one job well and are easier to reason about. Modular opcodes are general-purpose tools that can be combined in ways their designers may not have anticipated.

Back has planted his flag in the modular camp. His “last soft-fork” framing is essentially the logical endpoint of that position: build a general toolkit once, verify it rigorously, and let future innovation happen on top of it.

What this means for Bitcoin

Back’s statement carried no immediate market effects and no token launches. This is a protocol-level debate.

For developers, the near-term signal is to watch signet activity and the progress of draft BIPs like BIP 119 and BIP 347. Movement from testing to formal signaling on mainnet would mark a genuine change in momentum.

Simplicity’s track record on Liquid may also become a reference point. Its live deployment offers developers a working environment to evaluate covenant-like designs, which could inform how base-layer proposals are judged.

Disclosure: This article was edited by Estefano Gomez. For more information on how we create and review content, see our Editorial Policy.