Extend fork activation blocks data

[klkvr]

Describe the feature

Extend https://github.com/paradigmxyz/reth/blob/main/crates/ethereum-forks/src/hardfork.rs with fork activation block numbers data for more chains.

This data is non-trivial to obtain, so comments/links to lists of hardfork->block mappings are appreciated as well even if you have no plans for creating a PR with those.

Especially useful would be data for Arbitrum and any other chains enabling Shanghai/Cancun support in the near future.

Additional context

No response

[altugbakan]

Can I work on this? Which chains would be beneficial to add?

[mattsse]

arbitrum would be great

[altugbakan]

So, I’ve started doing some research. Are Arbitrum One and its testnet sufficient, or should we consider Arbitrum Nova and others?

[mattsse]

happy to accept all :)

up to you how much you'd like to do, but one+testnet would be sufficient

[altugbakan]

Quick update: I've found the corresponding upgrades (ArbOS 11 for Shangai, ArbOS 20 Atlas for Cancun), but I could not find the actual blocks where the upgrade has happened. They have the update information here, but there is no information on the block number, just the date. I'm continuing my research, but if there are any tips you would like to give, I'm open to them.

[mattsse]

you can try cast find-block <timestamp> to find the block that corresponds to a timestamp

[gakonst]

We don't support Arbitrum yet so not sure we should include this?

[klkvr]

We've discussed this in context of this being useful as a separate crate which we could also pull in as a foundry dep to address https://github.com/foundry-rs/foundry/issues/6228#issuecomment-1812843644 by determining spec for forked env.

Agreed that it'd be confusing to have arbitrum feature flag in any of Reth packages at this point

@mattsse wdyt?

[mvares]

@mattsse think you should close this issue... (it's still in reth tracker)

[github-actions[bot]]

This issue is stale because it has been open for 21 days with no activity.

[github-actions[bot]]

This issue was closed because it has been inactive for 7 days since being marked as stale.