Add post-Savanna TelosZero node and finalizer templates#36
Merged
Conversation
TheJudii
marked this pull request as ready for review
July 22, 2026 16:57
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
nodeossmoke tests, and GitHub Actions CIWhy
The existing template targeted an older Leap deployment model and did not cover the BLS finalizer responsibilities introduced by Savanna instant finality. Block producers now need safe finalizer-key custody, persistent
safety.dathandling, vote-capable relay paths, and operational procedures for rotation and failover.These templates presume Savanna instant finality is already active; they do not cover one-time network activation choreography.
Operator impact
Operators can render a reviewed configuration for each node role while keeping producers private and vote relays correctly configured. Producer templates require separate K1 and BLS signing keys, unique per-instance finalizer state, and retain the production pause guard when finalizer votes disappear.
Existing installations should review and render the new profiles rather than replacing live configuration blindly. The compatibility runner refuses stale production and unsupported command-line overrides by default; systemd is the recommended production path.
Validation
scripts/validate.shsystemd-analyze verify systemd/[email protected]nodeosparsing/startup smoke tests for all ten mainnet/testnet role combinations