Add internal settings generation for passive node#968
Merged
Conversation
badrogger
approved these changes
Mar 6, 2026
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
2 participants
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.
This pull request introduces an important update to the initialization and update processes for passive SKALE nodes. The main change ensures that internal settings are consistently saved whenever a passive node is initialized or updated, improving reliability and configuration management.
Configuration consistency improvements:
save_internal_settingsin theinit_passivefunction to ensure internal settings are saved when initializing a passive SKALE node.save_internal_settingsin theupdate_passivefunction to ensure internal settings are saved during passive node updates.