From 6cc1d38d7680e531056f8e9764920e0e47ab47cb Mon Sep 17 00:00:00 2001 From: Amanda L Martin Date: Tue, 24 Jun 2025 13:24:23 -0400 Subject: [PATCH 1/3] draft of weight changes --- processes/weight-changes.md | 53 +++++++++++++++++++++++++++++++++++++ 1 file changed, 53 insertions(+) create mode 100644 processes/weight-changes.md diff --git a/processes/weight-changes.md b/processes/weight-changes.md new file mode 100644 index 00000000..488f5677 --- /dev/null +++ b/processes/weight-changes.md @@ -0,0 +1,53 @@ +## Coordinating Weight Changes Across Networks + +### Purpose + +This process ensures that on-chain Super Validator weight votes remain in sync with our public GitHub configuration (`approved-sv-id-values.yaml`), and that any SV re-onboarding uses the correct, network-approved weights. + +### Process + +#### 1. Initiate on-chain vote +- Propose weight changes via on-chain governance under “Option 3a” (single synchronized vote across all networks with a common effective date). + +#### 2. Update the GitHub configuration +- After the vote passes, update `approved-sv-id-values.yaml` in the [SV config repo on GitHub](https://sync.global). +- Ensure the new weight values and effective date match the on-chain vote exactly. + +#### 3. Submit a Pull Request +- The node operator who proposed the weight change creates a PR against `approved-sv-id-values.yaml`. +- In the PR description, reference the on-chain vote transaction ID and effective date. +- Tag the maintainers (`@gsf-maintainers`) as reviewers. + +#### 4. Review & Merge +- Maintainers review the PR for accuracy and consistency. +- Once approved, merge the PR so the public file reflects the live network state. + +#### 5. Publication & Confirmation +- The merged file is automatically published at https://sync.global. +- SV operators may verify weights by inspecting this public file. + +#### 6. Re-onboarding behavior +- If an SV is off-boarded and then re-onboards, they will receive the weight defined in the merged `approved-sv-id-values.yaml`. + +#### 7. Enforcement & Escalation +- If the PR is not opened within 24 hours of vote finalization, the proposing node may be flagged for non-compliance. +- Repeated failures to submit or merge the PR may trigger an off-boarding vote or reconsideration of “Option 2” (automatic enforcement). + +--- + +### Prior discussion and votes for reference + +**YES: Separate PRs** +- *pros:* immediate config/runtime consistency; avoids drift +- *cons:* more PRs to manage; splits workflow into smaller steps + +**NOT Ignoring** (default) +- *pros:* simplest—no extra steps +- *cons:* renders the consistency check pointless; risk of unnoticed drift + +**Single PR + Reminders** +- *pros:* fewer PRs; single source of truth for all envs +- *cons:* requires active monitoring; notification fatigue leads to ignored reminders + +**Option 3a: Single PR with Common Effective Date** +- Keep one PR per vote round when all networks share the same activation date From ad68a521d073b3b412c54ee6514cfad84e93e1ce Mon Sep 17 00:00:00 2001 From: Amanda L Martin Date: Thu, 14 Aug 2025 07:55:28 -0400 Subject: [PATCH 2/3] changes from review --- processes/weight-changes.md | 48 +++++++++++-------------------------- 1 file changed, 14 insertions(+), 34 deletions(-) diff --git a/processes/weight-changes.md b/processes/weight-changes.md index 488f5677..9da59407 100644 --- a/processes/weight-changes.md +++ b/processes/weight-changes.md @@ -2,52 +2,32 @@ ### Purpose -This process ensures that on-chain Super Validator weight votes remain in sync with our public GitHub configuration (`approved-sv-id-values.yaml`), and that any SV re-onboarding uses the correct, network-approved weights. +This process ensures that on-chain Super Validator weights remain in sync with our public GitHub configuration (`approved-sv-id-values.yaml`), and that any SV re-onboarding uses the correct, network-approved weights. ### Process #### 1. Initiate on-chain vote -- Propose weight changes via on-chain governance under “Option 3a” (single synchronized vote across all networks with a common effective date). +- Propose weight changes via on-chain governance (single synchronized vote across all networks with a common effective date). -#### 2. Update the GitHub configuration -- After the vote passes, update `approved-sv-id-values.yaml` in the [SV config repo on GitHub](https://sync.global). -- Ensure the new weight values and effective date match the on-chain vote exactly. - -#### 3. Submit a Pull Request -- The node operator who proposed the weight change creates a PR against `approved-sv-id-values.yaml`. +#### 2. Submit a Pull Request +- The node operator who proposed the weight change creates PRs (one PR for each vote) in the [configs](https://github.com/global-synchronizer-foundation/configs) repository against `approved-sv-id-values.yaml` for each network. - In the PR description, reference the on-chain vote transaction ID and effective date. -- Tag the maintainers (`@gsf-maintainers`) as reviewers. + #### 4. Review & Merge -- Maintainers review the PR for accuracy and consistency. -- Once approved, merge the PR so the public file reflects the live network state. +- When one or more votes pass the votes initiator leaves comments about this fact on the related PRs +- Maintainers review the PRs for accuracy and consistency, approve and merge them so the public files reflect the live network state. #### 5. Publication & Confirmation -- The merged file is automatically published at https://sync.global. +- The merged file is automatically published at https://sync.global/sv-network. - SV operators may verify weights by inspecting this public file. -#### 6. Re-onboarding behavior -- If an SV is off-boarded and then re-onboards, they will receive the weight defined in the merged `approved-sv-id-values.yaml`. - -#### 7. Enforcement & Escalation -- If the PR is not opened within 24 hours of vote finalization, the proposing node may be flagged for non-compliance. -- Repeated failures to submit or merge the PR may trigger an off-boarding vote or reconsideration of “Option 2” (automatic enforcement). - ---- - -### Prior discussion and votes for reference - -**YES: Separate PRs** -- *pros:* immediate config/runtime consistency; avoids drift -- *cons:* more PRs to manage; splits workflow into smaller steps - -**NOT Ignoring** (default) -- *pros:* simplest—no extra steps -- *cons:* renders the consistency check pointless; risk of unnoticed drift +#### Notes +- Re-onboarding + - If an SV is off-boarded and then re-onboards, they will receive the weight defined in the merged `approved-sv-id-values.yaml`. -**Single PR + Reminders** -- *pros:* fewer PRs; single source of truth for all envs -- *cons:* requires active monitoring; notification fatigue leads to ignored reminders +- Enforcement & Escalation + - If the PR is not ready for merging within two business days of vote finalization, the proposing node may be flagged for non-compliance. + - Repeated failures to prepare the PRs within required time may trigger an off-boarding vote. -**Option 3a: Single PR with Common Effective Date** - Keep one PR per vote round when all networks share the same activation date From 041596d2286031814edc021903727c24c5486c8e Mon Sep 17 00:00:00 2001 From: "Stas German (SBI)" Date: Wed, 11 Mar 2026 09:14:55 +0900 Subject: [PATCH 3/3] weight changes: mention automated check Signed-off-by: Stas German (SBI) --- processes/weight-changes.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/processes/weight-changes.md b/processes/weight-changes.md index 9da59407..a49ec515 100644 --- a/processes/weight-changes.md +++ b/processes/weight-changes.md @@ -13,7 +13,6 @@ This process ensures that on-chain Super Validator weights remain in sync with o - The node operator who proposed the weight change creates PRs (one PR for each vote) in the [configs](https://github.com/global-synchronizer-foundation/configs) repository against `approved-sv-id-values.yaml` for each network. - In the PR description, reference the on-chain vote transaction ID and effective date. - #### 4. Review & Merge - When one or more votes pass the votes initiator leaves comments about this fact on the related PRs - Maintainers review the PRs for accuracy and consistency, approve and merge them so the public files reflect the live network state. @@ -26,7 +25,8 @@ This process ensures that on-chain Super Validator weights remain in sync with o - Re-onboarding - If an SV is off-boarded and then re-onboards, they will receive the weight defined in the merged `approved-sv-id-values.yaml`. -- Enforcement & Escalation +- Enforcement & Escalation + - There is an automated check in place which compares runtime weights with weights in this repository and alerts SV operators on any discrepancy. - If the PR is not ready for merging within two business days of vote finalization, the proposing node may be flagged for non-compliance. - Repeated failures to prepare the PRs within required time may trigger an off-boarding vote.