This repository has been archived by the owner on Jul 2, 2022. It is now read-only.
Refer to actual block size in sigops limit #20
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
For compatibility with peers that may not be observing BIP100, the scaled sigops limit will refer to actual block size rather than hardLimit.
This was referenced Mar 23, 2017
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
For compatibility with peers that may not be observing BIP100 per se, but have manually configured themselves to track along, the scaled signature hashing operations limit will refer to actual block size rather than hardLimit.
The effect is that a block sufficiently smaller than hardLimit doesn't get as much higher sigops density as before.