TxRateLimitExceeded
Error Re-added v101 → v117, v118 → v120, v121 → v127, v133 → v141, v142 → v148, v149 → v150, v195 → v202, v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v377, v385 → current 7.63You're sending transactions too frequently.
Why This Error Exists
Many SubtensorModule operations have rate limits to prevent spam and ensure fair access. This generic error indicates you've hit a rate limit for some operation. The specific limit depends on the call type - weight setting, staking, delegation changes, etc. each have their own cooldown periods.
Deep Dive
TxRateLimit is a general mechanism tracking when accounts last performed certain operations. LastTxBlock stores per-account timestamps. The cooldown varies by operation type: WeightsSetRateLimit for weights, TxDelegateTakeRateLimit for delegate changes, etc. This error might fire before more specific ones.
Debugging Example
You call add_stake(...) and get Error: TxRateLimitExceeded. This is a general rate limit. Query LastTxBlock(your_coldkey) for your last operation block. Query TxRateLimit for the general cooldown. Wait until current_block > LastTxBlock + TxRateLimit.
Prevention Tips
- Track when you perform rate-limited operations
- Build cooldown awareness into your automation
- Batch operations when possible instead of rapid-fire individual calls
From Chain Metadata
Default transaction rate limit exceeded.
What This Means
You're sending transactions too frequently.
Common Causes
- General rate limit on transactions
- Per-account rate limiting
How to Fix
- Wait a few blocks before retrying
- Check TxRateLimit for the cooldown period
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 63
- Error Code
- 7.63
- Runtime Version
- v393