You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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
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.
The text was updated successfully, but these errors were encountered: