consensus – Why was the 520 byte push restrict retained in Taproot?

It appears the way in which you’re interested by it’s backward. One ought to make the case that it secure to take away a DoS restrict. Retaining it ought to be the default place. Particularly as different limits are being lifted.

For example, with no stack ingredient dimension restrict it could possibly be attainable to assemble a Script which makes use of ~4GB of reminiscence to validate by utilizing the next Tapscript:

<396000 bytes push> OP_3DUP OP_3DUP .. OP_3DUP

With 333 OP_3DUPs this can create a stack with a thousand 3.96MB ingredient, utilizing about 3.96GB of reminiscence simply to retailer these. In fact there may be extra you might do, however a reminiscence blowup might be the obvious instance.