Share this article
The OP_CAT covenant proposal was officially introduced as “BIP-420” with the goal of enabling smart contracts, secure bridges, and on-chain transactions on the Bitcoin network.
Introducing BIP-420: Official Bitcoin Improvement Proposal for OP_CAT
It’s a historic day!
Today, after a long wait, the OP_CAT proposal officially received its BIP number. Meet BIP-420!
BIP-420 enables contracts on Bitcoin, allowing smart contracts, secure bridges, and on-chain. pic.twitter.com/z6ItJT7LX4
— Woody | BIP-420 🐱 (@udiWertheimer) April 22, 2024
that much , written by Ethan Heilman and Armin Sabouri, seeks to reintroduce the OP_CAT opcode to Bitcoin through a backwards compatible soft fork by redefining opcode OP_SUCCESS126. This is the same opcode value used in the original OP_CAT, which was disabled by Satoshi Nakamoto in 2010 due to concerns surrounding potential vulnerabilities.
“BIP-420 enables contracts on Bitcoin, allowing for smart contracts, secure bridges, on-chain transactions, zk proof verification, and more,” said Udi Wertheimer, OP_CAT advocate and co-founder of Taproot Wizards.
Bitcoin Covenant
Bitcoin’s covenants are an advanced scripting feature that allows specific conditions on how Bitcoin can be used in future transactions. This enables use cases such as creating secure “vaults” for reversible transactions, automatic recurring payments, time-locked transfers for inheritance, and complex financial products such as escrows and bonds.
In this sense, Bitcoin contracts currently exist as a proposed mechanism to enforce conditions on how BTC will be transferred in the future. It acts as a set of rules that govern how certain Bitcoins can be used and adds an additional layer of security and functionality to the network. Bitcoin contracts operate through Bitcoin’s scripting language and specify the conditions that must be met for a Bitcoin transaction to be processed.
There are many different types of contracts, each with their own advantages and disadvantages. The most common types are:
value-based contracts: Limits the value of transaction output.
Address-based contracts: Limit transaction output addresses.
Script-based covenant: Restrict transaction output scripts.
The Bitcoin Covenant could revolutionize the way Bitcoin is used today by allowing a wide range of financial products and services to be built on top of the Bitcoin network. This could make Bitcoin more versatile, enabling more complex transactions and smart contracts.
However, implementation of the Bitcoin protocol is not without difficulties. Key risks include potential issues related to fungibility, added complexity, and the introduction of new security vulnerabilities. Bitcoin’s covenant concept has been discussed since at least 2013.
Feature extension
According to the proposal, the OP_CAT opcode simplifies and extends the functionality of Bitcoin, making the decentralized protocol more practical and supporting advanced multi-signature setups. Essentially, OP_CAT significantly improves the performance and flexibility of Bitcoin scripting, making it easier to develop more sophisticated applications directly on the Bitcoin blockchain.
In particular, the likelihood that an OP_CAT soft fork will actually occur will depend on a combination of factors, including the technical capabilities of the core developers, on-chain security considerations, and community consensus.
But OP_CAT is not the only Bitcoin contract proposal being discussed. Other proposals include Check Template Verification (CTV), OP_CHECKSIGFROMSTACK (CSFS), and LNHANCE, each with different approaches and pros and cons, and at different stages of research and discussion.
Share this article