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

Support Engine API for POS Single Slot Finality Dev #13471

Open
mh0lt opened this issue Jan 16, 2025 · 0 comments
Open

Support Engine API for POS Single Slot Finality Dev #13471

mh0lt opened this issue Jan 16, 2025 · 0 comments
Assignees
Labels
imp1 High importance polygon

Comments

@mh0lt
Copy link
Contributor

mh0lt commented Jan 16, 2025

Polygon have a single slot finality project which aim to deliver single slot finality to the POS network by the end of 2025.

To support that development there is a requirement to have a version of erigon which will sync to the tip of Amoy and then change mode so that it relies on the engine api to process block insertions.

A suggested prototypical flow is as follows:

--pos,ssf=true // flag which initiates the flow
--pos.ssf.block=latest|block specified the block to start ssf from (default latest)

If the block is set to latest and a split block has not been previously defined - sync to the tip and wait for the end of the latest milestone and then stop synching.

If the block is passed the split point will be updated to that block and synching will stop there after which the engine API will be utilized.

@mh0lt mh0lt changed the title Support Engine API for POS Single Slof Finality Dev Support Engine API for POS Single Slot Finality Dev Jan 16, 2025
@mh0lt mh0lt added polygon imp1 High importance labels Jan 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
imp1 High importance polygon
Projects
None yet
Development

No branches or pull requests

2 participants