Fix: RPC calls (gasLimit, gasPrice) use the intial state of the block #2161
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.
Description
The RPC calls to the gasPriceMinimum and blockLimit (also ethCompatibility flag) before the gingerbreadFork (also the gasPrice for alternative currencies after the fork) require to read state from the block, but instead of reading the state from the beginning of the block, both were using the state of the end of the block
This means that the gasPrice/gasLimit of the block N that the client was sending, was actually the gasPrice/gasLimit of the block N+1
Tested
Run tests/e2e
Backwards compatibility
Yes