I was just rereading the SegWit benefits page and noticed that the section Moving towards a single combined block limit contains an example in which sigops count towards the blockweight.

Did this become part of the final version of SegWit? If not, what happened to this idea?

1 Answer 1


No. The block weight is only calculated from the bytes themselves, not the sigops. Accounting for the sigops would need a hard fork, as explained by the section above the example:

It is not possible to solve this problem without either a hardfork, or substantially decreasing the block size. Since segwit can’t fix the problem, it settles on not making it worse: in particular, rather than introducing an independent limit for the segregated witness data, instead a single limit is applied to the weighted sum of the UTXO data and the witness data, allowing both to be limited simultaneously as a combined entity.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

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