CRV3WeightsRevealed

Event Re-added v261 → v265, v273 → v277, v290 → v315, v320 → v326, v334 → v367, v372 → v377, v385 → current #97

Emitted when CRV3 committed weights are revealed.

View events on chain
Useful for: validatorssubnet ownersminersanalyticsdevelopers

The Big Picture

The reveal phase of CRV3 makes your committed weights official. Just like standard commit-reveal, but using the CRV3 protocol's reveal mechanism. This event confirms your reveal succeeded, your weights are now live and affecting miner rankings, and your commit is cleared.

Why This Matters

Your CRV3 commit is a promise; the reveal makes it real. This event confirms you successfully revealed using the CRV3 protocol. If you don't see this event after a reveal attempt, something went wrong - check your reveal call and parameters.

Example Scenario

You committed CRV3 weights on subnet 5. The reveal period opens. You call CRV3 reveal with your weights and salt. CRV3WeightsRevealed fires, confirming success. Your weights are now active in the consensus mechanism, affecting miner rankings and emissions.

Common Questions

Is CRV3 reveal timing different from standard reveal?
Potentially. CRV3 may have different reveal windows or synchronization requirements. Check your subnet's CRV3 configuration for exact timing parameters.
What happens if my CRV3 reveal fails?
Your weights don't count for that period. Common causes: wrong reveal window, hash mismatch, or protocol version mismatch. Check error details and try again if time permits.
Can I reveal CRV3 commits with non-CRV3 reveal functions?
No, CRV3 commits must be revealed with CRV3 reveal functions. The protocols aren't interchangeable.

Use Cases

  • Confirm CRV3 weight reveal succeeded
  • Track when validators' CRV3 weights go live
  • Monitor CRV3 reveal activity on subnets
  • Build CRV3-compatible validation monitoring

How to Use This Event

  • → Confirm your CRV3 reveals complete successfully
  • → Track reveal rates for CRV3-enabled subnets
  • → Monitor protocol health based on reveal success rates

From Chain Metadata

CRV3 Weights have been successfully revealed. **netuid**: The network identifier. **who**: The account ID of the user revealing the weights.

Triggers

Emitted by

reveal_weights

Preconditions

  • CRV3 commit exists for this validator
  • Reveal matches commitment
  • Reveal period has started

Effects

Postconditions

  • Weights applied
  • CRV3 commit cleared

Side Effects

  • Affects consensus calculations

Event Data

#NameTypeDescription
0
arg0
u16 Event field #0 (u16)
1
arg1
AccountId Event field #1 (AccountId) (hex -> SS58)

Code Examples

import { ApiPromise, WsProvider } from "@polkadot/api";
import { stringCamelCase } from "@polkadot/util";

const provider = new WsProvider("wss://entrypoint-finney.opentensor.ai:443");
const api = await ApiPromise.create({ provider });

// Subscribe to CRV3WeightsRevealed events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "CRV3WeightsRevealed"
    )
    .forEach(({ event }) => {
      console.log("CRV3WeightsRevealed:", event.data.toHuman());
    });
});

On-Chain Activity

Emission Frequency
●●●●○○ Significant 1M–5M emissions

Major features with millions of emissions

#19 most emitted event

As of block 7,429,232

Version History

v261 block 5,328,895 2 args
v273 block 5,659,032 2 args
v290 block 5,947,548 2 args
v320 block 6,523,566 2 args
v334 block 6,811,690 2 args
v372 block 7,430,358 2 args
v385 block 7,782,670 2 args Current

Runtime Info

View Source
Pallet Index
7
Event Index
97
First Version
v261
Current Version
v393
Back to SubtensorModule Events