P-Chain: Block-level fee Calculator #3032
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
…_block_level_fee_calculator
…_block_level_fee_calculator
…_block_level_fee_calculator
…_block_level_fee_calculator
…_block_level_fee_calculator
…_block_level_fee_calculator
…_block_level_fee_calculator
…_block_level_fee_calculator
…abs/avalanchego into p-chain_block_level_fee_calculator
Base automatically changed from
p-chain_improved_fee_calculator_structure
to
master
July 15, 2024 15:19
StephenButtolph
approved these changes
Jul 15, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Why this should be merged
Instantiate
fee.Calculatoronly once per block, instead of doing it once per each block transaction.How this works
fee.Calculatoris instantianted once in each block. UTs need to be modified to instantiate the calculator.How this was tested
CI