Great Consensus Cleanup Revival
Posted by harding
Feb 5, 2025/13:39 UTC
Introducing a per-transaction limit of 2,500 on the number of legacy input signature operations (sigops) represents a nuanced approach to managing blockchain transactions. This limit encompasses both bare and Pay to Script Hash (P2SH) inputs, proposing a standardized accounting method for sigops across various types of transactions. Specifically, the method for calculating the number of sigops for OP_CHECKMULTISIG (CMS) varies depending on the context. For bare scripts, traditionally only applied to output scripts, each CMS is counted as 20 sigops. However, when it comes to P2SH redeem scripts, the number of sigops is determined by the CMS parameter that specifies the number of public keys to be checked. For example, a script like 2 3 OP_CMS would count as three sigops.
Additionally, there's clarification sought on whether the 2,500 input limit applies to CHECK*SIG operations specified in a bare previous output script. This would mean, for instance, that spending a Pay to Public Key (P2PK) output would contribute one sigop towards the transaction's overall limit. This delineation emphasizes the broader effort to standardize and streamline transaction processing rules within the blockchain ecosystem, ensuring a balanced and efficient transaction throughput.
TLDR
Join Our Newsletter
We’ll email you summaries of the latest discussions from authoritative bitcoin sources, like bitcoin-dev, lightning-dev, and Delving Bitcoin.
Explore all Products
We'd love to hear your feedback on this project?
Give Feedback