batch_reveal_weights
Call v205 → v277, v290 → current #98Reveals committed weights on multiple subnets in a single transaction.
View calls on chainCall Workflow
Click items to navigate. Pan and zoom to explore.
The Big Picture
The companion to batch_commit_weights. Once your commits are in and reveal windows open, batch_reveal_weights completes the cycle for multiple subnets atomically. Critical for timing - if reveal windows are similar, batching ensures all your weights update together without the risk of missing individual windows.
Why This Matters
Missing a reveal window means your weights don't count for that epoch. Batching reduces the chance of partial reveals (where some subnets update and others don't). One transaction, all reveals, consistent validator behavior across your subnet portfolio.
Example Scenario
You committed weights to subnets 1, 3, 7, 18. Reveal windows all open at block 1,000,000. Call batch_reveal_weights(netuids=[1,3,7,18], uids_list=[[...],[...],[...],[...]], weights_list=[[...],[...],[...],[...]], salts=['salt1','salt2','salt3','salt4']). All four reveals execute atomically. Weights applied, commits cleared.
Common Questions
- What if reveal windows don't align perfectly?
- You can only batch subnets whose windows are currently open. If subnet 1's window is blocks 1000-1100 and subnet 3's is 1050-1150, batch during the overlap (1050-1100).
- What if I reveal with wrong weights/salt?
- The hash won't match, and that subnet's reveal fails. Depending on batch semantics, this might fail the entire batch. Double-check all parameters.
- Can I mix batch_commit with individual reveals?
- Yes - commits and reveals are independent. Batch commit then reveal individually, or individual commits with batch reveal. Use whatever fits your timing needs.
Use Cases
- Complete multi-subnet commit-reveal cycle in one transaction
- Synchronized weight updates across subnet portfolio
- Gas-efficient reveals for large validator operations
- Ensure all weights land in same block for consistency
From Chain Metadata
- The implementation for batch revealing committed weights.
Input Parameters
| # | Name | Type | Description |
|---|---|---|---|
| 0 | netuid | u16 NetUid | netuid: Subnet ID (u16, 0-65535) |
| 1 | uids_list | Vec<Vec<u16>> Vec | uids_list (Vec<Vec<u16>>) |
| 2 | values_list | Vec<Vec<u16>> Vec | values_list (Vec<Vec<u16>>) |
| 3 | salts_list | Vec<Vec<u16>> Vec | salts_list (Vec<Vec<u16>>) |
| 4 | version_keys | Vec<u64> Vec | version_keys (Vec<u64>) |
Permissions
Permission data inferred from metadata. May be incomplete.
Requirements
- Commits exist for all target subnets
- Reveals match their commitments
- Within reveal windows for all subnets
Effects
Events Emitted
Storage Modified
Postconditions
- Weights applied on all subnets
- Commits cleared
- Weight versions incremented
Side Effects
- Efficient multi-subnet weight reveal
- Affects next epoch's consensus on all subnets
Possible Errors
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);
// Build batch_reveal_weights call (typed, named args)
const netuid = 1;
const uids_list = [] as [];
const values_list = [] as [];
const salts_list = [] as [];
const version_keys = [] as [];
const tx = api.tx.SubtensorModule.batch_reveal_weights({
netuid,
uids_list,
values_list,
salts_list,
version_keys,
});Version History
Runtime Info
View Source- Pallet Index
- 7
- Call Index
- 98
- First Version
- v205
- Current Version
- v411