2

I am looking at BIP 109. It said, "The existing MAX_SIGOPS limit of 20,000 signature operations per block shall be retained, but only ECDSA verifications actually performed to validate the block shall be counted." What do MAX_SIGOPS and signature operations stand for?

2

Signatures are how all bitcoins are proven to be able to be spent by the owner of an address. If you receive bitcoins to an address, that address will generally correspond to at least one (maybe more in a multi-signature address) ECDSA private key, which is used when you spend those bitcoins later. But for other nodes to verify signatures to make sure all transactions are valid, that takes work, so there is a limit of how many of these signature operations a block can contain. That makes sure a block doesn't put too much workload on nodes verifying it. That limit is the MAX_SIGOPS.

4
  • Thank you! One more question: A transaction should includes at least one signature(more if sending to multi-signature address), so MAX_SIGOPS also limits the amount of transaction in a block. Is this a issue?
    – Anderson
    Nov 13 '17 at 10:35
  • No, the max number of signatures should be much higher than the number of transactions limited by the blocksize :)
    – meshcollider
    Nov 13 '17 at 10:57
  • Btw, then I have no idea why Gavin Andresen combined this with block size scaling in a BIP.
    – Anderson
    Nov 13 '17 at 11:47
  • Because if the blocksize increases, the signature operations may become a limiting factor as you mentioned, so that limit should be increased too
    – meshcollider
    Nov 13 '17 at 11:48

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.