Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add Support for Pre-Merge Networks #1999

Open
rzmahmood opened this issue Sep 8, 2024 · 1 comment
Open

Add Support for Pre-Merge Networks #1999

rzmahmood opened this issue Sep 8, 2024 · 1 comment

Comments

@rzmahmood
Copy link

rzmahmood commented Sep 8, 2024

Several pre-merge networks could take advantage of a stack like this.

Currently, when executing the merge on a pre-merge network, the hard fork fails as beaconkit attempts to continue ForkchoiceUpdated from the Genesis file of the execution client. Obviously, this is rejected by the Execution Client as it is an attempt to rollback to a pre-merge block (the genesis block).

Ideally, BeaconKit can pick up after the TDD point is reached. I'm not sure how Mainnet Eth did this, but an idea:

  • BeaconKit is started with a flag/config that informs it of the TDD. Beaconkit queries the execution client for the current TDD and employs some strategy to figure out when the TDD is passed. It then continues from there. Strategy would be fairly easy for Clique networks given the constant difficulty of each block.
@imanpajand
Copy link

nice idea

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

No branches or pull requests

2 participants