Skip to content
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.

Commit fe74ed8

Browse files
committedJun 10, 2025·
wip
1 parent 724b183 commit fe74ed8

File tree

2 files changed

+68
-1
lines changed

2 files changed

+68
-1
lines changed
 

‎docs/yc3-blog.md

Lines changed: 66 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -6,6 +6,10 @@ title: "How Yuma Consensus 3 Makes Bittensor More Fair"
66

77
YC3 is the next evolution of Bittensor's consensus mechanism, designed to reward miner innovation and early recognition by validators.
88

9+
:::tip Migration Guide Available
10+
For subnet owners looking to migrate to Yuma3, see the [Yuma3 Migration Guide](./subnets/yuma3-migration-guide.md) for step-by-step instructions and best practices.
11+
:::
12+
913
## Introduction: Understanding Yuma Consensus
1014

1115
At the heart of every Bittensor subnet lies a fundamental challenge: how do you fairly distribute rewards for work, when that work can include a wide range of different digitial commodities or services? Bittensor approaches this as a distributed judgment problem: **Validators** serve as judges for the whole community, with trust in them being measured by the total stake they have been delegated. Their ratings of the performance of **miners** (who produce the commodities and services for each subnet) determine emissions to those miners.
@@ -122,6 +126,55 @@ YC3 creates a healthier ecosystem by encouraging validators to:
122126

123127
This transformation means innovation and early recognition are properly rewarded, while maintaining the security and reliability that makes Bittensor networks trustworthy.
124128

129+
## Practical Implementation: Migration to YC3
130+
131+
### Deployment Status
132+
133+
YC3 is designed as a **drop-in replacement** for existing consensus mechanisms. Subnet 2 has already successfully migrated to YC3, experiencing:
134+
- Seamless activation with no downtime
135+
- A brief stabilization period of 2-3 tempo periods
136+
- Improved fairness for validators of all sizes
137+
138+
### Migration Process
139+
140+
For most subnet owners, **no action is required**. YC3 maintains backward compatibility with existing configurations. However, to leverage the full benefits:
141+
142+
```bash
143+
# Check current YC3 status
144+
btcli subnet hyperparameters --netuid YOUR_NETUID
145+
146+
# Enable YC3 features (if not already enabled)
147+
btcli sudo set --param yuma3_enabled --value true --netuid YOUR_NETUID
148+
149+
# Enable Liquid Alpha for enhanced benefits
150+
btcli sudo set --param liquid_alpha_enabled --value true --netuid YOUR_NETUID
151+
```
152+
153+
### Configuration Parameters
154+
155+
YC3 introduces several tunable parameters for advanced customization:
156+
157+
```bash
158+
# Alpha sigmoid steepness (affects reward distribution curves)
159+
btcli sudo set --param alpha_sigmoid_steepness --value YOUR_VALUE --netuid YOUR_NETUID
160+
161+
# Bonds moving average (default: 975000 for 2.5% adjustment per epoch)
162+
btcli sudo set --param bonds_moving_avg --value 975000 --netuid YOUR_NETUID
163+
164+
# Alpha range parameters
165+
btcli sudo set --param alpha_high --value YOUR_VALUE --netuid YOUR_NETUID
166+
btcli sudo set --param alpha_low --value YOUR_VALUE --netuid YOUR_NETUID
167+
```
168+
169+
### Monitoring Your Migration
170+
171+
After enabling YC3, monitor these key metrics:
172+
173+
- **Bond distribution patterns** using sparse matrix queries
174+
- **Individual alpha values** being applied to validator-miner pairs
175+
- **Small validator performance** to ensure fairness improvements
176+
- **Early recognition rewards** for validators discovering new miners
177+
125178
## For Subnet Owners
126179

127180
Yuma 3 works best in subnets where validators can independently evaluate miners and benefit from early recognition of promising innovations. The system distributes dividends more fairly than previous versions, and when combined with Liquid Alpha, provides powerful tools to encourage independent evaluation.
@@ -132,11 +185,24 @@ YC3 can be [toggled per subnet](https://github.com/opentensor/subtensor/blob/mai
132185
- Liquid Alpha must be enabled to get full YC3 benefits
133186
- The system requires active consensus formation to function optimally
134187
- Bond reset functionality is available for subnets that need it
188+
- Testing on testnet is recommended before mainnet deployment
189+
190+
**Migration Timeline:**
191+
- **Current**: YC3 is live and being adopted by subnets
192+
- **No forced deadline**: Subnets can adopt when ready
193+
- **Recommendation**: Monitor performance and consider gradual parameter tuning
135194

136195
## Looking Forward
137196

138197
As Bittensor continues to grow, YC3 provides a solid foundation for fair and efficient consensus. The system's ability to reward early recognition while maintaining security makes it well-suited for the network's future development.
139198

140199
For subnet owners ready to embrace more sophisticated consensus mechanisms, YC3 combined with Liquid Alpha provides a powerful toolkit for creating equitable and efficient subnet ecosystems.
141200

201+
**Next Steps for Subnet Owners:**
202+
1. Review the [Yuma3 Migration Guide](./subnets/yuma3-migration-guide.md) for detailed implementation steps
203+
2. Test YC3 features on testnet before mainnet deployment
204+
3. Consider enabling Liquid Alpha to maximize validator incentives
205+
4. Monitor subnet performance during the migration period
206+
5. Engage with the Bittensor community for migration support
207+
142208
YC3 was introduced to the Subtensor Code base in [PR 1593](https://github.com/opentensor/subtensor/pull/1593).

‎sidebars.js

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -41,7 +41,8 @@ const sidebars = {
4141
"learn/anatomy-of-incentive-mechanism",
4242
"emissions",
4343
"yuma-consensus",
44-
"yc3-blog"
44+
"yc3-blog",
45+
"subnets/yuma3-migration-guide"
4546
],
4647
},
4748
{

0 commit comments

Comments
 (0)
Please sign in to comment.