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
JoeTom: "can we export a daily snapshot of the archive for people who would like to run their own nodes? can we cryptographically mark a complete epoch somehow to unsure the archive is complete?"
luk: "I think we can add a flag(which anyone can enable or disable) to check at startup store hash of lastProcessedTick against a predefined(also configurable by env) store hash which we can publish along with latest snapshot"
Rationale
Whenever a new archiver node runner wants to spin up a new archive node, he may want to start his archive node with all the historical data already stored and this snapshot provides this data.
Open issues
The question for who should host and where the snapshots are not clear at this point.
The text was updated successfully, but these errors were encountered:
JoeTom: "can we export a daily snapshot of the archive for people who would like to run their own nodes? can we cryptographically mark a complete epoch somehow to unsure the archive is complete?"
luk: "I think we can add a flag(which anyone can enable or disable) to check at startup store hash of lastProcessedTick against a predefined(also configurable by env) store hash which we can publish along with latest snapshot"
Rationale
Whenever a new archiver node runner wants to spin up a new archive node, he may want to start his archive node with all the historical data already stored and this snapshot provides this data.
Open issues
The text was updated successfully, but these errors were encountered: