TooManyRegistrationsThisBlock
Error Re-added v101 → v120, v121 → v127, v133 → v141, v142 → v150, v151 → v212, v216 → v219, v233 → v315, v320 → current 7.20The registration rate limit for this block has been exceeded.
Why This Error Exists
To prevent registration spam and ensure fair access, each block has a maximum number of allowed registrations. This limit is per-subnet and per-block. During high-demand periods (new subnet launch, registration rush), you may need to retry across multiple blocks.
Deep Dive
RegistrationsThisBlock(netuid) counts registrations processed in the current block. MaxRegistrationsPerBlock(netuid) is the limit. When count >= limit, additional registrations in that block fail. The count resets each block. Blocks are ~12 seconds apart. Both POW registration and burned_register count toward this limit.
Debugging Example
You call burned_register(netuid=18, ...). Error: TooManyRegistrationsThisBlock. Query RegistrationsThisBlock(18) - returns 3. Query MaxRegistrationsPerBlock(18) - returns 3. Block is full. Wait 12 seconds for next block, then immediately retry. Consider adding jitter to avoid competing with other bots at block boundaries.
Prevention Tips
- Add retry logic with exponential backoff in your registration scripts
- Avoid peak hours when new subnets launch or incentives change
- Pre-register during low-activity periods if you know you'll need slots
From Chain Metadata
Number of registrations in this block exceeds the allowed number (i.e., exceeds the subnet hyperparameter "max_regs_per_block").
What This Means
The registration rate limit for this block has been exceeded.
Common Causes
- Too many registrations happening network-wide
- High demand period for this subnet
- Bot activity consuming registration slots
How to Fix
- Wait a few blocks and retry
- Try during lower-activity periods
- Consider using burned_register if available
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 20
- Error Code
- 7.20
- Runtime Version
- v393