This repository has been archived by the owner on Apr 4, 2024. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 566
Inconsistent baseFee check logic in code #755
Comments
ref: https://github.com/ethereum/go-ethereum/blob/master/internal/ethapi/api.go#L1211 |
It looks reasonable to me. For the case |
yihuang
added a commit
to yihuang/ethermint
that referenced
this issue
Dec 27, 2021
Closes: evmos#755 ``` if not london_hardfork { # reject DynamicFeeTx # no `baseFeePerGas` field in block response # baseFee = nil } else { # allow DynamicFeeTx # add `baseFeePerGas` field in block response if feemarketParams.NoBaseFee or height < feemarketParams.EnableHeight { # baseFee = 0 } else { # init baseFee to initBaseFee and adjust in later blocks } } ``` Update x/evm/keeper/keeper.go Co-authored-by: Federico Kunze Küllmer <[email protected]> add unit tests Update app/ante/utils_test.go Co-authored-by: Federico Kunze Küllmer <[email protected]> changelog
fedekunze
pushed a commit
that referenced
this issue
Dec 28, 2021
Closes: #755 ``` if not london_hardfork { # reject DynamicFeeTx # no `baseFeePerGas` field in block response # baseFee = nil } else { # allow DynamicFeeTx # add `baseFeePerGas` field in block response if feemarketParams.NoBaseFee or height < feemarketParams.EnableHeight { # baseFee = 0 } else { # init baseFee to initBaseFee and adjust in later blocks } } ``` Update x/evm/keeper/keeper.go Co-authored-by: Federico Kunze Küllmer <[email protected]> add unit tests Update app/ante/utils_test.go Co-authored-by: Federico Kunze Küllmer <[email protected]> changelog
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
System info: ethermint main
Following the discussion here: #671 (comment), @fedekunze
Steps to reproduce:
Currently, different places have different logic to check base fee:
Better to encapsulate a common logic to do this.
Expected behavior: consistent way to check base fee.
Actual behavior: inconsistency
Additional info:
The text was updated successfully, but these errors were encountered: