RevealedCommitments
Storage Re-added Map v257 → v258, v261 → currentStores revealed timelocked commitment data after auto-reveal.
Explore chainQueried by: validatorsdevelopersanalytics
The Big Picture
When timelocked commitments are revealed, the decrypted data is stored here.
Use Cases
- Access revealed timelocked data
- Verify commit-reveal scheme outcomes
Purpose & Usage
Purpose
Archive of revealed timelocked data with timestamps.
Common Query Patterns
- Query by (netuid, account) to get revealed data
Query Keys
Stored Value
Value in RAO (÷10⁹ for TAO)
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 });
// Query RevealedCommitments storage
const key1 = 0;
const key2 = "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY";
const result = await api.query
[stringCamelCase("Commitments")]
[stringCamelCase("RevealedCommitments")](
key1,
key2
);
console.log("RevealedCommitments:", result.toHuman());Version History
v257 block 5,228,683 Added
v261 block 5,328,895 Re-added Current
Runtime Info
View Source- Pallet
- Commitments
- Storage Kind
- Map
- First Version
- v257
- Current Version
- v393