common: add support for new Sepolia chain

[emersonmacro]

Initial attempt at tackling #1558. Information for the new chain came primarily from the geth issue & PR here:
ethereum/go-ethereum#23730 (comment)
https://github.com/ethereum/go-ethereum/pull/23730/files#diff-c13a1b5c84048a832e07e3503cc35f66614816cb39fe1e2fdd992672a9e1d883R46

[codecov]

Codecov Report

Merging #1581 (5d2dc60) into master (3751bbd) will increase coverage by 0.05%.
The diff coverage is 100.00%.

Flag	Coverage Δ
block	85.06% <100.00%> (+0.09%)	⬆️
blockchain	85.08% <ø> (ø)
client	71.27% <ø> (ø)
common	100.00% <100.00%> (ø)
devp2p	83.31% <ø> (+0.27%)	⬆️
ethash	∅ <ø> (∅)
trie	86.09% <ø> (ø)
tx	88.62% <ø> (ø)
util	91.84% <ø> (ø)
vm	79.89% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

[holgerd77]

Review is not yet complete (to be continued by me or someone else).

Is this Sepolia network already running? If so: have you (@emersonmacro) tested this setup in the client?

[holgerd77]

Some change requests, I will directly push these after the review.

The initial connection to the bootnode is now working with this.

We get the following follow-up error though:

Guess that has something to do with the genesis block which might not be written properly to the chain. This will need some debugging. A good starting point here is likely the blockchain library and there the related genesis block initialization code parts.

[holgerd77]

What's the status of this?

[emersonmacro]

What's the status of this?

I was able to get the same initial connection to the bootnode and subsequent error that you posted. I'm doing some debugging trying to figure out what's causing the error.

[ryanio]

sync working! smooth so far

[ryanio]

i successfully sync'd to head but not sure why it didn't continue following the tip of the chain

This error:

(node:24407) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [BlockFetcher]. Use emitter.setMaxListeners() to increase limit

is concerning, might be related to lib/sync/fetcher/fetcher.ts:L348 -> this.on('close', () => {

[jochem-brouwer]

Maybe no one is mining Sepolia so there are no new blocks? Check the timestamp of the latest block?

[holgerd77]

But this Sepolia network is a great chance to really really test our client in production, and all the related tip of the chain behavior with it! 😀

[emersonmacro]

I got it fully synced yesterday and did not see the same error:

Just restarted the client and it synced back up very quickly, at a slightly higher block height:

[ryanio]

this LGTM!

we can address following the tip of chain behavior in a separate PR, and this should be a nice testnet to do that with :)