CommitRevealVersionSet
Event v301 → v315, v320 → v326, v334 → v367, v372 → v377, v385 → v402, v411 → current Changed in v411 #105Emitted when the required commit-reveal version is updated.
View events on chainThe Big Picture
Commit-reveal has multiple protocol versions (v1, v2, CRV3, etc.). This event signals when a subnet requires a specific version. Validators using older versions will have their commits rejected. It's how subnets coordinate upgrades - set the version requirement and validators must comply or be excluded.
Why This Matters
If your validator software speaks commit-reveal v2 but the subnet requires v3, your commits fail. This event warns you: 'Upgrade now or stop working on this subnet.' It's critical for maintaining validator operations across protocol upgrades.
Example Scenario
Subnet 5 is upgrading from CRV2 to CRV3 for improved security. CommitRevealVersionSet fires with netuid 5 and version 3. Your validator using CRV2 will now have commits rejected. You must update to CRV3-compatible software to continue validating on subnet 5.
Common Questions
- How much time do I have to upgrade?
- Immediate - the new requirement is effective from this event. Any commits using the old version will fail. Upgrade ASAP to avoid missing validation rounds.
- What if I have pending commits with the old version?
- They may still be revealable (depends on implementation), but you can't make new commits until you upgrade. Finish pending work, then update.
- Where do I find the new version's protocol documentation?
- Check the bittensor repository or subnet-specific documentation. Each version has different commit/reveal function signatures and requirements.
Use Cases
- Track commit-reveal protocol upgrades
- Alert validators when software updates are needed
- Monitor subnet protocol evolution
- Build version-aware validator tools
How to Use This Event
- → Monitor subnets for version requirement changes
- → Build alerts for required software upgrades
- → Track version adoption across the network
From Chain Metadata
Commit Reveal Weights version has been updated. **version**: The required version.
Triggers
Preconditions
- Caller has admin/sudo privileges
Effects
Postconditions
- New version requirement in effect
Side Effects
- Validators must update to compatible software
Event Data
| # | Name | Type | Description |
|---|---|---|---|
| 0 | arg0 | u16 | Event field #0 (u16) |
Code Examples
import { createClient, Binary } from "polkadot-api";
import { getWsProvider } from "polkadot-api/ws";
import { sub } from "@polkadot-api/descriptors"; // generated by: npx papi add sub -w wss://entrypoint-finney.opentensor.ai:443
const client = createClient(getWsProvider("wss://entrypoint-finney.opentensor.ai:443"));
const api = client.getTypedApi(sub);
// Subscribe to CommitRevealVersionSet events
client.finalizedBlock$.subscribe(async (block) => {
const events = await api.event.SubtensorModule.CommitRevealVersionSet.get(block.hash);
for (const evt of events) {
console.log("CommitRevealVersionSet:", evt.payload);
}
});Version History
Runtime Info
View Source- Pallet Index
- 7
- Event Index
- 105
- First Version
- v301
- Current Version
- v411