Bitcoin OPCAT reactivation follows Taproot Wizards inscription

Taproot Wizards reached a 5,000 recursive inscription milestone, which follows the launch of their Quantum Cats collection. OP_CAT joins two data points on a stack and places them at the top of the stack. Satoshi Nakamoto removed this opcode in 2010 to prevent denial of service attacks where users pushed exponential amounts of data onto the blockchain. The 2021 Taproot upgrade allows 520 bytes of data within a single stack, which removes the original vulnerability by capping the expansion of data on the blockchain. The proposal to reintroduce OP_CAT as a Tapscript-only opcode is assigned the filing label BIP 347. This proposal redefines the existing opcode OP_SUCCESS126.

The mechanism relies on the ability to reconstruct structured data on the stack. Because Taproot uses Schnorr signatures, OP_CAT allows a script to reconstruct the sighash from transaction fields. If any field changes, the reconstructed sighash will not match, and the signature check fails. This enables an output address to be enforced because the script can inspect the transaction. This ability to examine transaction data is what enables covenant functionality.

The reintroduction of OP_CAT creates covenants, which are spending conditions that restrict how an authorized user spends bitcoin via script logic. These conditions allow for vaults that require two different transactions to appear in two separate blocks to spend the associated bitcoin. OP_CAT also enables tree signatures, which provide a multisignature script that remains small even as the number of public keys grows. This makes it possible for a transaction under 1KB to support tree signatures with a thousand public keys. By combining different pieces of information within a script, OP_CAT enables developers to build complex software like games or smart contracts that use data from existing inscriptions to bypass the 4MB block size limit without requiring new cryptography.

Taproot Wizards raised $30 million to build an ecosystem of applications using this opcode. They want to provide permissionless programmability for bitcoin, which allows lending and trading without giving up self custody. However, the debate over OP_CAT has split the Bitcoin developer community into multiple factions. Proponents argue that the implementation is a minimal change that restores functionality Satoshi originally included in the original design. Opponents warn that it could introduce miner extractable value and reduce fungibility by creating economies of scale that pressure miners toward centralization. Critics also fear that increasing programmability moves Bitcoin toward the model used by Ethereum. These recursive covenants could create coins that are permanently restricted, meaning they cannot escape certain conditions.

Non-equivocation contracts use OP_CAT to penalize double spending attempts in payment channels like the Lightning Network, which creates spending conditions reinforced by tapscript and Bitcoin consensus. This provides a way to enforce spending constraints through the protocol.

Activation and security

Bitcoin upgrades typically use soft forks to ensure the new rules do not conflict with older versions. Miners signal support for a change by adding a signal bit to the blocks they mine. The Taproot upgrade used a method called Speedy Trial, requiring a 90 percent threshold for three months.

Current discussions involve BIP-360, which proposes Pay-to-Merkle-Root (P2MR) to address the growing quantum threats currently facing the network. Google’s Quantum AI team published research in 2026 suggesting a powerful enough quantum computer could compromise Bitcoin transactions within a mere nine minutes. This research shows that a device with 500,000 error-corrected qubits could execute an attack using Shor’s algorithm to compromise the network. This attack would allow an attacker to derive a private key from an exposed public key. P2MR transactions are larger and more complex than standard Taproot transactions, but they preserve multisignature wallets and timelocks.

You know the basics of how signatures work, but the speed of a quantum attack changes the math. Can the community reach consensus on a path forward before these quantum threats arrive?