Implement config management with hot-reload and schema validation (fixes #122) - #147
Merged
elizabetheonoja-art merged 1 commit intoAug 29, 2026
Conversation
Utility-Protocol#122) Adds an on-chain schema-validated config system with staged rollout and community veto: register_config_schema, propose_config_change -> veto_config_change -> apply_config_change (48h default staging window, 5% active-user veto threshold, mirrors the existing admin-transfer veto pattern), emergency_set_config_value (admin-only, still schema-validated), rollback_config_field (one-step), and get_config_version() as the change signal off-chain services can watch for hot-reload. Delivers the on-chain half of the feature; off-chain file-watch hot-reload for usage-dashboard/meter-simulator is a follow-up. See CHANGES.md for full details. Note: the utility_contracts crate currently fails to compile on main (205 pre-existing errors, unrelated to this change, verified against a clean checkout) - confirmed this PR adds 0 new errors, only 8 additional warnings (deprecated env.events().publish(), same pattern already used throughout the existing codebase).
elizabetheonoja-art
merged commit Aug 29, 2026
a56d5a8
into
Utility-Protocol:main
7 of 11 checks passed
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
3 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.
Adds an on-chain schema-validated config system with staged rollout and
community veto: register_config_schema, propose_config_change ->
veto_config_change -> apply_config_change (48h default staging window, 5% active-user veto threshold, mirrors the existing admin-transfer veto pattern), emergency_set_config_value (admin-only, still schema-validated), rollback_config_field (one-step), and get_config_version() as the change signal off-chain services can watch for hot-reload.
Delivers the on-chain half of the feature; off-chain file-watch hot-reload for usage-dashboard/meter-simulator is a follow-up. See CHANGES.md for full details.
Note: the utility_contracts crate currently fails to compile on main (205 pre-existing errors, unrelated to this change, verified against a clean checkout) -, only 8 additional warnings (deprecated env.events().publish(), same pattern already used throughout the existing codebase).