Appearance
Community Good
JPool offers a dedicated stake allocation to operators of Community Good validators. These are teams actively building for the Solana ecosystem. 30% of pool stake flows to CG validators, distributed proportionally by their impact score.
You can apply for CG status via the CG application form. The Validator Council evaluates applications on a regular cycle.
CG scoring criteria
INFO
The Validator Council is currently calibrating the Community Good assessment criteria. The updated criteria and scoring framework will be published here before the next application round opens.
CG scores (0 to 9) are assigned by the Validator Council according to the published scoring criteria below; allocation is then executed algorithmically. Higher score = proportionally more stake from the CG bucket.
| Criteria | Points |
|---|---|
| Base points (monetization) | |
| Non-commercial (no paid services) | 3 |
| Free or freemium (≥50% free users) | 2 |
| Commercial (fee / subscription) | 0 |
| Bonus points (tracks) | |
| DEV | +1 |
| PROJECTS | +1 |
| LIQUIDITY | +1 |
| USERS | +1 |
| Bonus points (other) | |
| Open-source | +1 |
| Free license (MIT, Apache, GPL) | +1 |
| 1K+ MAU | +1 |
| 10K+ MAU | +2 |
| Media coverage (Tier 1 to 2 level) | +2 |
Tracks: a project is assigned to one or several of the following:
- DEV: encouraging developers to build on Solana
- PROJECTS: encouraging projects to expand or port to Solana
- LIQUIDITY: bringing additional liquidity (investments or TVL) to Solana
- USERS: attracting new users to Solana
Example: With 40 CG validators and a total score pool of 120, a validator with score 8 receives roughly 3x more CG stake than a validator with score 3.
WARNING
All parameters in the table are subject to change. Bonus point parameters may be updated from time to time; changes are published in advance, and scoring follows the published criteria.
The Validator Council
The Validator Council reviews applications to the Community Good program and assigns CG scores. The sections below set out how the Council is formed, how it scores applications and which rules its members follow.
Composition
The Council has five voting members, including the founding Chair. A member of the JPool team acts as Secretary: the Secretary supports the Council's work, handles communication with applicants and has no vote.
| Member | Role | Validator |
|---|---|---|
| Hervé Guillemet | Chair | Puffin |
| Lu | Member | Validator 1 |
| Viktor (CryptoVik Validator) | Member | CryptoVik |
| Johann Focke | Member | Blocksize |
| Vijay Pondini | Member | Decentra |
Eligibility
Council members are people, not validators: operators of active pool validators, developers or recognized community representatives.
Membership in the core team of another LST pool disqualifies a candidacy. Operating a personal LST with a TVL of up to 20,000 SOL is permitted.
Term and rotation
- Members serve a 12-month term.
- Rotation is staggered. At month 12, two seats rotate; they are selected by lottery. The remaining three seats rotate at month 18. After that, two and three seats rotate alternately every six months.
- Sitting members may re-apply. There is currently no limit on consecutive terms.
How applications are scored
- Evidence first. Scores are based on evidence the applicant provides or that members can verify: repositories, usage, public artifacts and third-party confirmation.
- Independent scoring. Each member scores each application on their own, without seeing other members' scores.
- Written justification. Every score comes with a written justification. Justifications are confidential and kept by JPool.
- Minimum number of scores. Each application needs at least four valid scores.
- Trimmed mean. The highest and the lowest scores are dropped, and the remaining scores are averaged.
- Publication. Only the final aggregated score of each application is published.
Conflicts of interest and recusal
A member does not score an application if they have a commercial, employment, hosting or infrastructure relationship with the applicant, or any other financial interest in the applicant. For example, a member does not score an application when they:
- Operate, or help to operate, the applicant validator or a competing stake pool.
- Host the applicant's node in their company's data center.
- Provide infrastructure services to the applicant.
- Have any other financial interest in the applicant.
Members keep their declarations of relationships up to date.
Applicant request. Each applicant may ask one named Council member to step aside from reviewing their application.
Council members' own validators
If a Council member's validator holds CG status, that status is frozen for the duration of the term: the validator keeps its CG points but receives no delegation from the CG bucket. This is not a removal for a violation of the program rules.
Compensation
Each member receives 10,000 SOL of delegation per 12-month term.
Confidentiality
Individual scores, written justifications and the Council's internal discussions are confidential.
Applicants should not contact Council members about their applications. All questions go to the JPool team on Discord or at [email protected].
End of membership
Membership ends early in one of three ways:
- Voluntary resignation.
- Automatic termination for a disqualifying violation.
- A Council decision adopted by at least three of the remaining four members. JPool confirms only that the procedure was followed.
A vacant seat is filled from the waitlist.
Changes to these rules
JPool may update these rules. Changes are published on this page.