-
Notifications
You must be signed in to change notification settings - Fork 698
[NIT-4242] Add initial L1 base fee to node configuration #4171
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: master
Are you sure you want to change the base?
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #4171 +/- ##
==========================================
+ Coverage 33.01% 33.14% +0.13%
==========================================
Files 459 459
Lines 55830 55853 +23
==========================================
+ Hits 18430 18512 +82
+ Misses 34185 34091 -94
- Partials 3215 3250 +35 |
❌ 3 Tests Failed:
View the top 3 failed tests by shortest run time
📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
|
LGTM |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As you mentioned in a meeting, since there are multiple valid ways to serialize chain config, in order to Execution build parsedInitMessage only through its local config, users will also need to have a way to provide the serialized chain config.
This can be done in this PR, a new PR, or even a new linear task can be created for that, up to you to decide the best path to move forward 🙂
|
@diegoximenes regarding serialized chain config I'd go with another linear ticket (I'm about to create it) |
| Name string `koanf:"name"` | ||
| InfoFiles []string `koanf:"info-files"` | ||
| InfoJson string `koanf:"info-json"` | ||
| InitialL1BaseFee string `koanf:"initial-l1base-fee"` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Something that I didn't notice in previous reviews.
This flag will be better placed at the InitConfig instead of L2Config.
arbostypes.DefaultInitialL1BaseFeetogo-ethereum/paramsL2ConfigwithInitialL1BaseFeefield. Since the fee might exceed1<<64, the field type isstringand we have a getterInitialL1BaseFeeParsedthat returns:DefaultInitialL1BaseFeewhen the string is empty or it cannot be parsed in decimal systemcmd/nitro/init.goresolve† the initial L1 base fee from either CLI flag or genesis configuration. Ensure it matches what was in the parsed init message on the parent chain.† config resolution:
genesis.jsonis absent, use the--chain.initial-l1base-feeflag valuegenesis.jsonis present and--chain.initial-l1base-feeis not empty, ensure the values matchgenesis.jsoncloses NIT-4242
pulls in OffchainLabs/go-ethereum#603