You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Most Genesis JSON files have null as config, but Unichain, for example, has a populated field. I came across #763 but am unsure if this "inconsistency" is intended and what the expected behavior will be in the future. Will only new chains have this config section, or will all Genesis files be adapted?
Most Genesis JSON files have
null
asconfig
, but Unichain, for example, has a populated field. I came across #763 but am unsure if this "inconsistency" is intended and what the expected behavior will be in the future. Will only new chains have this config section, or will all Genesis files be adapted?File:
superchain/extra/genesis/mainnet/base.json.zst
:File:
superchain/extra/genesis/mainnet/unichain.json.zst
:ref: Working currently on parsing those files in reth here: paradigmxyz/reth#14562
The text was updated successfully, but these errors were encountered: