RevealTooEarly
Error Re-added v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v377, v385 → current 7.78You're trying to reveal weights before the reveal period starts.
Why This Error Exists
Commit-reveal has two phases: the commit phase (when everyone submits hashes) and the reveal phase (when hashes are opened). You can't reveal during the commit phase because that would let others see your weights and potentially copy them. Wait for the epoch boundary when the reveal window opens.
Deep Dive
After committing, you must wait until the next epoch boundary for reveals to open. The exact timing depends on Tempo (blocks per epoch) and when you committed within the current epoch. WeightCommits stores your commit block, and the chain computes the earliest valid reveal block from this.
Debugging Example
You commit at block 100,000 (epoch 277). The reveal window opens at epoch 278 (block 100,360). You try to reveal at block 100,100 (still epoch 277). Error: RevealTooEarly. Wait until block 100,360 when epoch 278 starts, then reveal.
Prevention Tips
- Query the current epoch and calculate when reveals open
- Use Tempo to determine epoch boundaries: epoch = block_number / Tempo
- Add logic to wait for next epoch before attempting reveal
From Chain Metadata
Attempted to reveal weights too early.
What This Means
You're trying to reveal weights before the reveal period starts.
Common Causes
- Must wait for commit period to end
- Reveal window hasn't opened yet
How to Fix
- Wait for the reveal period to start
- Check when the commit was made and calculate reveal window
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 78
- Error Code
- 7.78
- Runtime Version
- v393