Bitcoin Covenants: OP_CAT (BIP 347)
Briefly

This article discusses OP_CAT, which was originally built into Bitcoin's first release for stack manipulation but was deactivated in 2010 due to security concerns. It explores how OP_CAT operates by concatenating data on the stack and its potential to emulate covenants via Schnorr signatures. Although not a covenant itself, OP_CAT's functionality can achieve similar objectives due to its ability to manipulate transaction data effectively, thus enriching the capabilities of Bitcoin's scripting environment.
OP_CAT, originally included in Bitcoin's first release, was deactivated in 2010 due to potential denial of service threats, but can emulate covenants with Schnorr signatures.
While OP_CAT isn't a covenant itself, it enables functionalities that mimic covenants through its integration with Schnorr signatures, highlighting Bitcoin's evolving capabilities.
Read at Bitcoin Magazine
[
|
]