OP_CAT
The concatenation opcode Satoshi disabled in 2010, proposed for return in Tapscript by BIP-347: active on Bitcoin Inquisition signet, no mainnet activation plan.
The wiki's angle: OP_CAT is the general-purpose end of the covenant debate. That generality is why supporters like it and why sceptics hesitate.[1][3]
Proposal
A single 2010 commit disabled OP_CAT along with 15 other opcodes, according to BIP-347[1].
BIP-347 introduces OP_CAT as a Tapscript opcode that concatenates two stack values, activated by soft fork by redefining OP_SUCCESS126, the same opcode value the original OP_CAT used[1]. The BIP argues that Tapscript lacks a general way to combine stack objects, which prevents building and evaluating Merkle trees and other hashed data structures[1].
Uses claimed
The BIP lists vaults and replicating CHECKSIGFROMSTACK among the constructions OP_CAT would enable, citing Andrew Poelstra's “CAT and Schnorr Tricks” posts and Robin Linus's work on covenants with ECDSA[1].
Status
BIP-347 is marked Complete in the BIP repository and is active on the Bitcoin Inquisition signet, but no Bitcoin Core release carries activation parameters for it[2][3]. See covenants for how it compares with other proposals.
References
- primaryBIP 347, “OP_CAT in Tapscript”, bitcoin/bips
- primarybitcoin/bips repository [archived]
- secondaryDelving Bitcoin, “Bitcoin Inquisition 29.4” (signet activation heights for APO, CTV, OP_CAT, CSFS, IKEY, BIP54, TEMPLATEHASH)
Related in the wiki
Related articles



