[KGA-34] feat: update base fee starting from next block only #1606
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.
https://github.com/code-423n4/2024-09-kakarot-findings/issues/28
Updates the base fee mechanism.
In the EVM there can only be one base fee for a given block.
Thus, we use an index to manage two different base fees:
- The base fee to use for the current block (index: 'current_block')
- The base fee to use for the next block (index: 'next_block')
The startegy is:
current_block
and return the new valuecurrent_block
When setting the base_fee, it will be applicable starting from
block_number + 1
.Note: for tests we have to manually patch both
addr
andaddr+1
as we'restoring two values.This change is