Skip to content

Conversation

emlautarom1
Copy link
Contributor

Solves #8065

Changes

Types of changes

What types of changes does your code introduce?

  • Bugfix (a non-breaking change that fixes an issue)
  • New feature (a non-breaking change that adds functionality)
  • Breaking change (a change that causes existing functionality not to work as expected)
  • Optimization
  • Refactoring
  • Documentation update
  • Build-related changes
  • Other: Description

Testing

Requires testing

  • Yes
  • No

If yes, did you write tests?

  • Yes
  • No

Notes on testing

Added tests to verify that we're properly decompressing generated ChainSpec files. Some tests were updated to use a new ChainSpecFileLoader that is format-aware of ChainSpec files, thus is able to decompress them if needed.

Documentation

Requires documentation update

  • Yes
  • No

Requires explanation in Release Notes

  • Yes
  • No

Once this feature is properly working we need to document that Nethermind now supports all OP Superchain chains, not only a small subset (currently: OP, Base and Worldchain).

Remarks

The generated ChainSpec files are stored in a compressed format due to their excessive size when in .json format. Just like in the Superchain Registry repository (https://github.com/ethereum-optimism/superchain-registry/blob/cb9a0ca8eda1608bf9958137a736fd2c18884fbd/superchain/README.md) we use zstandard as the compression algorithm. This is due to the OP team already figuring out that this is one of the best algorithms for this use case, and also to reduce the required amount of code (our scripts already deal with decompression so might as well compress the resulting artifacts using the same algorithm).

Currently, 45 configs are generated: 28 in Mainnet and 17 in Sepolia.

We're still missing a GitHub action that automatically runs this script either periodically or when the Superchain Registry repository gets updated (the latter being preferable)

@kamilchodola
Copy link
Contributor

@stdevMac Can you take care of checking this and making sure it works accordingly with Sedge? Also add to our CI BUT limit those side chains to trigger once per week.

@emlautarom1
Copy link
Contributor Author

@kamilchodola @stdevMac Do not test this branch yet since it's not working ATM. I'll change the status to "ready to review" once I figure out what is the issue (currently Nethermind can't find peers).

@emlautarom1 emlautarom1 requested a review from rubo February 7, 2025 15:21

on:
schedule:
- cron: '0 0 * * 0'
Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The workflow will run weekly. Does this sound OK @kamilchodola ?

@emlautarom1 emlautarom1 merged commit cece96f into master Feb 11, 2025
79 checks passed
@emlautarom1 emlautarom1 deleted the feat/superchain-registry branch February 11, 2025 13:53
@rubo
Copy link
Contributor

rubo commented Mar 26, 2025

It looks like after this commit, the fast sync settings update always failed.

@emlautarom1
Copy link
Contributor Author

@rubo Fixed in #8422

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants