What’s OP_CAT?
In a nutshell, OP_CAT takes the highest two values from a script stack, joins them, after which places the end result again onto the stack.
This operation affords numerous scripting prospects which was beforehand eliminated as a result of threat of excessive reminiscence consumption.
BIP 420 proposes to handle this threat by preserving the concatenated end result inside a 520-byte restrict, and the modifications would solely apply to tapscript, particularly OP_SUCCESS126, and never on another components of the Bitcoin protocol.
Why Reintroduce OP_CAT?
The reintroduction of OP_CAT is believed to reinforce Bitcoin’s scripting capabilities.
By permitting concatenation, builders might construct extra complicated scripts that help superior functionalities like multisig transactions.
The opcode might additionally play a task in enabling new cryptographic strategies to enhance Bitcoin’s resilience towards future threats.
A Tender Fork for Compatibility
BIP 420 suggests utilizing a tender fork to reintroduce OP_CAT, which might preserve the remainder of the Bitcoin protocol unchanged. This strategy is meant to take care of backward compatibility whereas permitting builders to experiment with the brand new performance.
The Bitcoin group is discussing BIP 420, with various opinions on its deserves, with some builders seeing the potential for better scripting flexibility, whereas others are involved about safety dangers and community stability.
The proposal is ongoing, with no closing choice made at this level.
