TooManyUnrevealedCommits
Error v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v377, v385 → v393, v401 → current 7.77You have too many pending weight commits awaiting reveal.
Why This Error Exists
To prevent storage bloat from unrevealed commits, there's a limit on pending commitments. You must reveal or let commits expire before making new ones. This ensures validators complete the commit-reveal cycle rather than endlessly committing without following through.
Deep Dive
The exact limit depends on the commit-reveal version (CRV3 has different rules than earlier versions). WeightCommits or CRV3WeightCommits stores your pending commits. If you hit the limit, you must either: 1) Reveal existing commits, or 2) Wait for them to expire (after RevealPeriodEpochs epochs).
Debugging Example
You call commit_weights(netuid=5, hash=0xnew...). Error: TooManyUnrevealedCommits. Query CRV3WeightCommits(your_hotkey, 5) - returns [(hash1, block1), (hash2, block2), (hash3, block3)]. You have 3 unrevealed commits (limit might be 3). Solution: Reveal one of them or wait for one to expire.
Prevention Tips
- Always reveal commits before making new ones
- Set up monitoring to track unrevealed commits
- Implement automatic reveal in your validator to prevent accumulation
From Chain Metadata
Maximum commit limit reached
What This Means
You have too many pending weight commits awaiting reveal.
Common Causes
- Committed multiple times without revealing
- Maximum pending commits limit reached
How to Fix
- Reveal your pending commits before making new ones
- Let expired commits clear out
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 77
- Error Code
- 7.77
- Runtime Version
- v411