NoWeightsCommitFound
Error v151 → v202, v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v393, v401 → current 7.51You're trying to reveal weights , but no commit was found.
Why This Error Exists
The reveal phase of commit-reveal requires a matching commit to exist. If you never committed, or your commit expired, or you're revealing for the wrong hotkey/subnet, there's nothing to reveal against. The chain needs the original commitment hash to verify your reveal matches what you promised.
Deep Dive
WeightCommits or CRV3WeightCommits stores (hotkey, netuid) -> (hash, commit_block). When you reveal, the chain looks up this entry, computes hash(revealed_weights, salt), and compares. If no entry exists (returns None), you get this error. Commits expire after RevealPeriodEpochs epochs from the commit block.
Debugging Example
You call reveal_weights(netuid=5, hotkey=5Xyz..., weights=[...], salt=123). Error: NoWeightsCommitFound. Query WeightCommits(5Xyz..., 5) - returns None. No commit exists for this hotkey on subnet 5. Solution: First call commit_weights(netuid=5, hash=keccak256(weights||salt)), wait for reveal period, then reveal.
Prevention Tips
- Always commit before revealing - track your commits in your validator state
- Set a timer after committing to remind yourself to reveal before expiry
- Double-check hotkey and netuid parameters match your commit
From Chain Metadata
No commit found for the provided hotkey+netuid combination when attempting to reveal the weights.
What This Means
You're trying to reveal weights, but no commit was found.
Common Causes
- Never committed weights for this netuid
- Commit expired before reveal
- Wrong hotkey or netuid
How to Fix
- Commit weights first using commit_weights
- Make sure to reveal before commit expires
- Verify hotkey and netuid match the commit
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 51
- Error Code
- 7.51
- Runtime Version
- v411