CommitmentOf

Storage Map v140 → current

Stores commitment data for an account on a specific subnet .

Explore chain

Queried by: validatorsminersdevelopersanalytics

The Big Picture

This is the main storage for commitments. Each (netuid, account) pair can have one Registration record.

Use Cases

Retrieve account metadata for a subnet participant
Look up serving endpoints for miners

From Chain Metadata

Identity data by account

Purpose & Usage

Purpose

Main storage for account metadata and timelocked data per subnet.

Common Query Patterns

Query by (netuid, account) to get commitment data
Iterate by netuid to list all commitments

Part of: On-Chain Commitments

Query Keys

#	Name	Type	Description
1	key1	u16	key1 (u16)
2	key2	AccountId	key2 (AccountId) (hex -> SS58)

Stored Value

Registration

value (Registration)

Relationships

Modified By

set_commitment

Related Events

Commitment TimelockCommitment

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 CommitmentOf storage
const key1 = 0;
const key2 = "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY";

const result = await api.query
  [stringCamelCase("Commitments")]
  [stringCamelCase("CommitmentOf")](
  key1,
  key2
);

console.log("CommitmentOf:", result.toHuman());

On-Chain Activity

Write Frequency

●●●●●○ High 1M–10M est. writes

1M–10M estimated writes

#16 most written storage item

Write Source User Extrinsics

Modified via user-submitted extrinsics

As of block 7,429,232

Runtime Info

View Source

Pallet: Commitments
Storage Kind: Map
First Version: v140
Current Version: v393

Back to Commitments Storage