Yuma
Validator
Yuma is proud to share our updated validator weighting framework, which reinforces our commitment to fairness, transparency, and innovation within the Bittensor ecosystem. This framework is designed to ensure that Yuma acts as a judicious and transparent validator while continuing to support the growth of accelerated and incubated subnets.
Key Changes to the Validator Weight Selection Process (Updated: 12/23/24)
Subnet Program Reserve
Yuma will reserve up to 35% of validator weight capacity to be allocated across Yuma-accelerated and incubated subnets during the first year those subnets are operating.
Data Repository
Yuma will build a subnet data repository for subnet owners to submit information to which validators can access in a centralized location. For simplicity, we’ve reduced our initial intake form by a third and created a 3-question monthly update for existing subnet owners.
Updated Evaluation Criteria & Process
Yuma will update weights monthly based on a refined 10-point framework.
Through these updates, the Yuma validator will more accurately and transparently assign weights as well as provide key resources for others in the Bittensor community to better evaluate subnets and their development moving forward.
The Subnet Program
Yuma grants a minimum weight allocation for a one-year period for each Yuma-accelerated or incubated subnet, up to a total of 35% of Yuma’s total weight, across all such Yuma-accelerated and incubated subnets. By committing weight to subnets we partner with, Yuma provides these subnets the stability and support required to become established, drive innovation, and contribute meaningfully to the growth of the Bittensor ecosystem, reducing the risk of de-registration. Remaining weight capacity (i.e., unused amounts up to the 35%) will initially remain in Subnet 0, but be available for future (non-Yuma accelerated and incubated) subnets or adjustments as necessary.
- ACCELERATED SUBNETS: Receive a minimum weight allocation of 1.5% for one year.
- INCUBATED SUBNETS: Receive a minimum weight allocation of 3% for one year.
During the initial 1-year period, all Yuma accelerated and incubated subnets are also subject to the global evaluation criteria and treated as global subnets, which are re-evaluated monthly. As a result, those subnets may receive additional weight allocation based on those evaluation scores.
After the initial one-year period, minimum weight allocation will be removed from accelerated and incubated subnets, which will then be subject to Yuma’s global evaluation criteria.
Information Repository
A centralized repository with information provided by subnet owners is available for validators to access key information. This includes:
- Subnet Assessment: An initial intake form for new subnets.
- Monthly Subnet Update: A simplified three-question monthly update form to track changes, milestones, and relevant documentation.
Subnets with incomplete or missing information will not be scored during evaluations, ensuring accountability and accuracy.
Assessment + Monitoring Forms
Yuma accepts submissions for evaluation on a rolling basis, with re-weighting occurring monthly on the 1st day of each month.
To be eligible for weighting from Yuma, subnet owners must submit the Initial Subnet Assessment by the last day of the month, to be included in the re-weighting released the following day.
After submitting the initial Subnet Assessment, subnet owners are expected to complete the Monthly Subnet Update (3-question form) to share significant changes, milestones and relevant documentation for consideration in the monthly re-weighting. This process abides by the same schedule, requiring form submissions by the last day of the month, with re-weighting released the following day (the 1st of the month).
Information Repository (for Validators)
Validators interested in accessing the information repository may reach out using the form below.
Our Commitment to the Bittensor Ecosystem
Through this framework, Yuma aims to balance its support for emerging subnets with a steadfast commitment to fairness and transparency. While Yuma seeks to assist certain subnets through its accelerator and incubation programs, the rigorous evaluation system ensures that all participants in the ecosystem are eligible to receive weighting subject to transparent evaluation criteria.
The recent update reflects Yuma’s role as a leader in decentralized intelligence and a trusted participant in the Bittensor network. We remain dedicated to fostering innovation, collaboration, and growth across the ecosystem.
Global Subnet Evaluation Criteria
- THE SUBNET OWNER: Assessment of the team, problem-solving focus, value proposition, and business model.
- THE MARKET: Analysis of market size and competition.
- INTELLIGENCE + TRACTION: Evaluation of the interface, roadmap, traction, and rewards model.
The scores are translated into a grading scale that determines the earned weights for each subnet. This method of scoring ensures a comprehensive review of all subnets, which will occur on a monthly basis to reflect subnet performance and ensure alignment with evolving market conditions.
Scorecard
| Theme | Criteria |
|---|---|
| The Subnet Owner | Team:
Problem:
Value Proposition:
Business Model: |
| The Market | Market Size:
Competition: |
| Intelligence + Traction | Interface: -Is the output embedded into an existing product?
Roadmap:
Traction:
Rewards Model + Distribution: -Is the mining incentive distribution fair? |
This framework is subject to change at any time at Yuma’s sole discretion as we learn, iterate, and incorporate any protocol changes. Yuma intends to review this framework on a quarterly basis. Yuma reserves the right to remove validator weight from a subnet without notice at any time at Yuma’s sole discretion. Reasons Yuma may remove a validator weight could include, but is not limited to, if Yuma suspects that a subnet is engaging in improper activity, violating this policy or community guidelines and practices, or otherwise acting in a manner that Yuma considers harmful, disruptive, or otherwise inconsistent with the intended use of the Bittensor protocol.