CommittingWeightsTooFast
Error v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v377, v385 → v393, v401 → current 7.81You're committing weights more frequently than allowed.
Why This Error Exists
Weight commits are rate-limited just like direct weight setting. This prevents spam and ensures fair access to weight setting across all validators. Each validator can only commit once per rate limit window, which is measured in blocks and varies by subnet configuration.
Deep Dive
WeightsSetRateLimit(netuid) defines the minimum blocks between weight operations (commit or set_weights). LastUpdate(netuid, uid) stores when you last set weights. The rate limit applies to both direct set_weights AND commit_weights calls. current_block - last_update must be >= rate_limit.
Debugging Example
You commit weights at block 200,000 for subnet 5. WeightsSetRateLimit(5) is 100 blocks. You try to commit again at block 200,050. Error: CommittingWeightsTooFast. 200,050 - 200,000 = 50 blocks elapsed. Need 100. Wait until block 200,100 to commit again.
Prevention Tips
- Query LastUpdate(netuid, your_uid) to know when you can next commit
- Calculate: next_valid_block = LastUpdate + WeightsSetRateLimit
- Build the rate limit check into your validator's commit scheduling
From Chain Metadata
A transactor exceeded the rate limit for setting weights.
What This Means
You're committing weights more frequently than allowed.
Common Causes
- Rate limit on weight commits
- Must wait between commits
How to Fix
- Wait for the rate limit period to pass
- Check WeightsSetRateLimit for timing
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 81
- Error Code
- 7.81
- Runtime Version
- v411