Queried by: validatorssubnet ownersdevelopers
The Big Picture
When enabled, bonds are periodically reset allowing miners to rebuild trust. This creates more dynamic ranking but less historical continuity. Different subnets may choose different bond reset policies.
Use Cases
- Check if bonds reset is active
- Plan validation strategy around resets
- Monitor subnet bond policies
From Chain Metadata
MAP ( netuid ) --> bonds_reset
Purpose & Usage
Purpose
Control if bonds are reset periodically.
Common Query Patterns
- Query by netuid
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | netuid | u16 | netuid (u16, hashed key component) |
Stored Value
bonds_reset (bool)
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);
// Query BondsResetOn storage
const netuid = 1;
const result = await api.query.SubtensorModule.BondsResetOn.getValue(netuid);
console.log("BondsResetOn:", result);Version History
v273 block 5,659,032 Added
v278–v289 · runtime versions skipped on chain (never deployed)
v290 block 5,947,548 Internal re-bind Current
Runtime Info
View Source- Pallet
- SubtensorModule
- Storage Kind
- Map
- First Version
- v273
- Current Version
- v411