CommitRevealDisabled
Error v151 → v202, v205 → v212, v216 → v216, v217 → v219, v233 → v315, v320 → v326, v334 → v393, v401 → current 7.54Commit-reveal is disabled but you tried to use it.
Why This Error Exists
Not all subnets use commit-reveal. Some prefer the simplicity of direct weight setting. When commit-reveal is disabled, calling commit_weights or reveal_weights is unnecessary overhead. The subnet owner configures this based on whether front-running is a concern for their use case.
Deep Dive
CommitRevealWeightsEnabled(netuid) returns false for subnets that don't use this mechanism. In this mode, just call set_weights directly with your weights. The commit_weights and reveal_weights calls will fail since there's nothing to commit to or reveal from.
Debugging Example
You call commit_weights(netuid=1, hash=0xabc...). Error: CommitRevealDisabled. Query CommitRevealWeightsEnabled(1) - returns false. Subnet 1 uses direct weights. Solution: Skip commit/reveal entirely. Call set_weights(netuid=1, uids=[...], weights=[...]) directly.
Prevention Tips
- Check CommitRevealWeightsEnabled(netuid) before choosing weight-setting method
- Make your validator software handle both modes dynamically
- Monitor subnet configuration changes - this setting can be toggled
From Chain Metadata
Attemtping to commit/reveal weights when disabled.
What This Means
Commit-reveal is disabled but you tried to use it.
Common Causes
- Subnet doesn't use commit-reveal
- Should use set_weights directly instead
How to Fix
- Use set_weights instead of commit/reveal
- Check CommitRevealWeightsEnabled to verify
Storage to Check
Thrown By
Version History
Runtime Info
- Pallet Index
- 7
- Error Index
- 54
- Error Code
- 7.54
- Runtime Version
- v411