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
Is your feature request related to a problem? Please describe.
Currently adding support for Superchain chains requires manual work to convert the required configs and assets into something compatible with Nethermind. This usually results in PRs like #8044.
Describe the solution you'd like
We would like to automate this process as follows:
Create a script that fetches the required assets from the Superchain Registry and generates corresponding config files.
Modify Nethermind to load the assets in their uncompressed format directly rather than preprocessing them.
Describe alternatives you've considered
Instead of fetching the assets we could add the superchain registry as a git submodule and then trigger a pull. This will most likely result in additional assets that we don't care about, but we avoid any potential issues regarding fetching.
We could add an additional step to the script to convert the assets to something that Nethermind can understand right now but we believe that this will result in a lot of used storage (see Add Worldchain support #8044 (review)).
Fetching the assets could be done at runtime instead of build time. This could cause issues during initialization and makes harder to know what configurations is being used, alongside the fact that each run could end up with potential different configs. Overall we think it's a bad idea.
Is your feature request related to a problem? Please describe.
Currently adding support for Superchain chains requires manual work to convert the required configs and assets into something compatible with Nethermind. This usually results in PRs like #8044.
Describe the solution you'd like
We would like to automate this process as follows:
Describe alternatives you've considered
Additional context
The text was updated successfully, but these errors were encountered: