[Proposal] 64-bit arithmetic in Script

The discussion initiated with concerns regarding the clarity of a proposal concerning Bitcoin development. The proposal outlines intentions to upgrade existing opcodes, a process traditionally associated with hardforks rather than soft forks, due to the necessity of altering the leaf version. Additionally, the proposal introduces the concept of OP_SUCCESSX as an alternative method involving different opcodes, suggesting a need for further analysis to validate the approach's feasibility and effectiveness.

There's a particular interest in understanding the rationale behind limiting upgrades to 64 bits instead of expanding them to 256 bits, which could potentially offer significant benefits for cryptographic applications. This point highlights a desire for a more in-depth examination of the proposal's technical specifications and its implications for future development. Furthermore, the proposal's focus on implementing functionality for pushing sums onto the stack, without addressing the capability for individual outputs, raises questions about the chosen scope and its limitations.

The email underscores a critical perspective on the proposed changes, suggesting that a more comprehensive analysis and justification are necessary to assess the proposal's viability fully. It reflects a broader conversation within the Bitcoin development community on how best to implement upgrades and enhancements while considering the technical and strategic implications of such decisions.