Skip to content

cip 0050 - Existing Validator Operators may operate nodes for individuals and entities #39

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.

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

Merged
merged 17 commits into from
Jul 14, 2025
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,7 @@ Global Synchronizer CIPs
| [cip-0047](cip-0047/cip-0047.md) | | Featured App Activity Markers| Moritz Kiefer | Tokenomics | Approved |
| [cip-0048](/cip-0048/cip-0048.md) | | Raising the Rewards Cap for Validators and Application Providers | Wayne Collier | Tokenomics | Final |
| [cip-0049](/cip-0049/cip-0049.md) | | Incentivizing Cold Backups for Super Validators to Enhance Network Resilience | Vinh Nguyễn | Governance | Draft |
| [cip-0050](/cip-0050/cip-0050.md) | | Controlled Validator Growth Through Trusted Operators | Wayne Collier | Process | Withdrawn |
| [cip-0051](/cip-0051/cip-0051.md) | | Streamline onchain governance votes | Itai Segall | Governance | Approved |
| [cip-0052](/cip-0052/cip-0052.md) | | Monstera FZE as a SV at Weight [3] | Eric Saraniecki | Governance | Approved |
| [cip-0053](/cip-0053/cip-0053.md) | | AngelHack as a Weight 2.5 SV | Eric Saraniecki | Governance | Approved |
Expand All @@ -59,4 +60,3 @@ Global Synchronizer CIPs
| [cip-0063](/cip-0063/cip-0063.md) | | Add Kaiko as a Super Validator of Weight 6.5 | Ambre Soubiran | Governance | Approved |
| [cip-0064](/cip-0064/cip-0064.md) | | Delegateless Automation | Julien Tinguely | Standards Track | Approved |
| [cip-0066](/cip-0066/cip-0066.md) | | Mint Canton Coin from Unminted/Unclaimed Pool | Jose Velasco| Tokenomics | Approved |

58 changes: 58 additions & 0 deletions cip-0050/cip-0050.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,58 @@
## CIP 0050

<pre>
CIP: CIP 0050
Title: Controlled Validator Growth Through Trusted Operators
Author: Wayne Collier
Status: Withdrawn
Type: Process
Created: 2025-03-11
License: CC1
</pre>

## Abstract

- Allow existing Validator operators to create up to 10 additional Validators for third-party participants.
- Redirect new individual Validator applicants to approved existing operators.
## Specification

- Existing Validator operators will be authorized to create up to 10 additional Validators for third-party participants. Once an existing Validator operator has spun up the ten (10) allotted nodes, they can request an additional alottment from the Tokenomics committee.
- Third-party applicants wishing to run a Validator will be redirected to an existing operator.
-Whitelisting requests, if the node will not share an existing IP address, will come from the existing Validator operator who sponsors the new node
In the case that the onboarded node receives its own IP address in the whitelist, the whitelist will indicate the Validator Operator as the responsible party for the node.
-Credit for onboarding the Validator goes to the sponsoring Validator Operator
-The Validator onboarding secret will be issued by a Super Validator, as before.
- Pre-approved operators, such as Kiln, Dfns and Copper, who have already been granted the right to operate up to 30 validator nodes, will retain that right.
- Operators will be given discretion in onboarding third-party Validator nodes. After reaching the limit of ten additional nodes onboarded through this process, these operators may request additional node hosting permissions from the GSF Tokenomics committee.
- This policy ensures a structured and scalable approach to Validator expansion while maintaining network integrity and supportability.
- The [application process](https://sync.global/validator-request/) will remain in place for requests to become a Validator Operator.

## Motivation

- As interest in the network grows, there is increasing demand from individuals wanting to become Validators. However, onboarding independent Validators without oversight could introduce operational and security risks. This proposal establishes a controlled mechanism for growth, leveraging existing trusted operators to facilitate expansion while maintaining an orderly network.
- Maintain a controlled, trusted, and orderly network expansion.


## Rationale

The current approach ensures:
- Network stability by limiting Validator growth to approved operators.
- A direct point of contact for any network-related issues.
- A structured expansion process that aligns with the network’s steady rollout.
- Efficient use of existing operators' expertise and infrastructure.

Alternative approaches, such as an open application process, were considered but deemed too difficult to manage at this stage. This proposal strikes a balance between controlled growth and decentralization.


## Backwards compatibility

This proposal does not introduce any backwards incompatibilities. It only modifies the policy for onboarding new Validators.

## Reference implementation

No code changes are required for this proposal. Implementation involves updating policy documentation and communicating guidelines to existing Validator operators.

## Copyright

This CIP is licensed under CC0-1.0: [Creative Commons CC0 1.0 Universal](https://creativecommons.org/publicdomain/zero/1.0/).