This error was removed in v265
This error is no longer present in the current runtime. Existed from v151 to v265. Shown here for historical reference.
CommitmentSetRateLimitExceeded
Error Removed v151 → v265 (removed) 18.2Account is trying to commit data too fast, rate limit exceeded
From Chain Metadata
Account is trying to commit data too fast, rate limit exceeded
What This Means
Account is trying to commit data too fast, rate limit exceeded
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
SubtensorModule.LastUpdate (removed)SubtensorModule.WeightsSetRateLimit (removed)
Runtime Info
- Pallet Index
- 18
- Error Index
- 2
- Error Code
- 18.2
- Removed In
- v265