Open
Conversation
Codecov Report❌ Patch coverage is Additional details and impacted files@@ Coverage Diff @@
## master #4313 +/- ##
==========================================
- Coverage 34.33% 32.40% -1.94%
==========================================
Files 483 483
Lines 57343 57344 +1
==========================================
- Hits 19690 18583 -1107
- Misses 34149 35502 +1353
+ Partials 3504 3259 -245 |
Contributor
|
✅ All tests successful. No failed tests were found. 📣 Thoughts on this report? Let Codecov know! | Powered by Codecov |
Tristan-Wilson
approved these changes
Feb 5, 2026
This file contains hidden or 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
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.
The
Genesis.Configfield was used in nitro (excludinggo-ethereum) in two places:genesis-generatortool - just checking that the field is empty and printing an error if not; this PR leaves this usage to ensuregenesis.jsondoesn't use old format. However, this could be removed if we decide to remove the field instead of deprecating it.init- this PR changes the logic to use the new getter that relies on the serialized format.Reasoning for not migrating whole geth codebase and not removing the
ConfigfieldThere are essentially two paths:
Genesis.Configas deprecated - this should prevent us from using it again in nitro, but there's a follow up issue - what about geth code?a. leave Geth as it is - this leaves us with a small probability, that there is some utility in geth relying on the
Configfield, that we might some day useb. migrate Geth to use the
SerializedChainConfigGenesis.Config- this will require doing 1bNow, the problem with migrating Geth is that:
Config()that would deserialized the string field, so the migration would be easyThis PR, after consultations, implements 1a variant.
closes NIT-4412
pulls in OffchainLabs/go-ethereum#618