ExpiredWeightCommit
Error Re-added v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v377, v385 → current 7.77The weight commitment has expired before reveal.
Why This Error Exists
Commits have a limited validity window. After RevealPeriodEpochs epochs, unrevealed commits expire and are discarded. This prevents stale commitments from clogging storage and ensures validators actively participate in each weight-setting round. You must reveal within the window or start over.
Deep Dive
RevealPeriodEpochs defines how many epochs a commit remains valid. An epoch is typically Tempo blocks (360 blocks = ~72 minutes). If you commit at epoch E, you must reveal before epoch E + RevealPeriodEpochs. After that, the commit is automatically cleared and this error occurs on reveal attempts.
Debugging Example
You committed at block 100,000 (epoch 277). RevealPeriodEpochs is 3. Your reveal window is epochs 278-280. You try to reveal at block 105,000 (epoch 291). Error: ExpiredWeightCommit. Your commit expired after epoch 280. Solution: Make a new commit and reveal within the valid window.
Prevention Tips
- Calculate your reveal deadline immediately after committing
- Set up monitoring to alert if reveal is approaching deadline
- Automate the commit-reveal cycle in your validator software
From Chain Metadata
Attempted to reveal weights that are expired.
What This Means
The weight commitment has expired before reveal.
Common Causes
- Waited too long to reveal
- Commit has a limited validity period
How to Fix
- Commit again with fresh weights
- Reveal sooner next time
- Check RevealPeriodEpochs for timing
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 77
- Error Code
- 7.77
- Runtime Version
- v393