Lets assume we want to introduce arbitrary precision into Bitcoin’s Script language. This requires being able to push operands of arbitrary size to the stack.
BIP342 states
Stack element size limit The existing limit of maximum 520 bytes per stack element remains, both in the initial stack and in push opcodes.
It also states that new opcodes could circumvent the 520 byte push limit
Since OP_SUCCESSx precedes size check of initial stack and push opcodes, an OP_SUCCESSx-derived opcode requiring stack elements bigger than 520 bytes may uplift the limit in a softfork.
Script already has a handful of arithmetic operations such as OP_ADD and OP_SUB.
Is it accurate to say that these opcodes could only be repurposed up to 520 bytes of precision? If more precision was desired, you would need to create new versions of these opcodes (OP_ADD_ARB, OP_SUB_ARB)?
