Skip to content

Restart services on chain version change #769

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.

Sign up for GitHub

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

Jump to bottom
Open
dmtrskv opened this issue Apr 7, 2025 · 2 comments · May be fixed by #884
Open

Restart services on chain version change #769

dmtrskv opened this issue Apr 7, 2025 · 2 comments · May be fixed by #884
Assignees
@dmtrskv
Labels
archive node cometa indexer

Comments

@dmtrskv
Copy link
Contributor

dmtrskv commented Apr 7, 2025

Chain version is defined by the hash of the main shard's genesis block.
The following services should wipe their databases (based on an argument) on version change detected at the start:

  • archive node
  • cometa
  • indexer
    They should also restart if the version change is detected during their lifetime.
@dmtrskv dmtrskv self-assigned this Apr 7, 2025
@olegrok
Copy link
Contributor

olegrok commented Apr 7, 2025

Just drop of DB is not enough (at least for archive node). You need to have a trusted genesis block source or zerostate config.
Cometa and indexer probably also need to verify their state against nil config

@dmtrskv
Copy link
Contributor Author

dmtrskv commented Apr 9, 2025

I plan to hardcode some chain data here: #786

This was referenced May 8, 2025
Open
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@dmtrskv dmtrskv

Labels
archive node cometa indexer
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

[version] Restart services on chain or protocol change NilFoundation/nil
2 participants
@olegrok @dmtrskv