It actually does address the rune problem. Runes protocol relies on embedding "Runestone" metadata within these outputs, capping them at 83 bytes renders the majority of Runes transactions (especially "etchings," which require more space) technically impossible to include in a valid block. Also by limiting data pushes and witness elements to 256 bytes, the proposal prevents protocols from using alternative methods to "pack" their data across multiple pushes. Finally BIP-110 consensus rules state that any transaction with a ⁠scriptPubKey⁠ exceeding 34 bytes is invalid unless it is an ⁠OP_RETURN⁠ (up to 83 bytes). Any attempt to use larger scripts or bypass these limits will cause a BIP-110-enabled node to reject the transaction outright. So yes. Runes are fucked.

Replies (1)