AddStakeBurnRateLimitExceeded
Error v385 → current 7.130"Add stake and burn " exceeded the operation rate limit
From Chain Metadata
"Add stake and burn" exceeded the operation rate limit
What This Means
"Add stake and burn" exceeded the operation rate limit
Common Causes
- You called set_weights again before the rate limit window passed
- Rate limits are typically 100-1000 blocks depending on the subnet
- Your previous tx is still in the mempool (not yet included in a block)
How to Fix
- Query SubtensorModule.LastUpdate(netuid, uid) to see your last update block
- Query SubtensorModule.WeightsSetRateLimit(netuid) to get the minimum blocks between updates
- Wait until: current_block > LastUpdate + WeightsSetRateLimit, then retry
Storage to Check
Runtime Info
- Pallet Index
- 7
- Error Index
- 130
- Error Code
- 7.130
- Runtime Version
- v411