Queried by: minersvalidatorsdevelopersanalyticswallets
The Big Picture
Even during extreme demand, burn cost won't exceed MaxBurn. This protects against runaway costs that would make registration prohibitively expensive. The cap ensures accessibility even in high-demand scenarios.
Why This Matters
What's the worst-case registration cost? MaxBurn. No matter how high demand gets, you won't need more than this to register via burn.
Example Scenario
Query MaxBurn(netuid=1) returns 10000000000000 (10,000 TAO). Even if the subnet is extremely popular, burn cost caps at 10,000 TAO.
Common Questions
- Can burn actually reach the max?
- During sustained high demand, yes. If RegistrationsThisInterval consistently exceeds target, burn climbs toward the cap.
- What if I can't afford max burn?
- Try POW registration instead, or wait for demand to cool and burn to decrease.
Use Cases
- Plan maximum registration budget
- Build registration cost displays with bounds
- Understand worst-case registration costs
- Research registration economics
- Design subnet cost parameters
From Chain Metadata
MAP ( netuid ) --> MaxBurn
Purpose & Usage
Purpose
Cap on registration burn cost - prevents runaway costs during high demand.
Common Query Patterns
- Query by netuid
- Plan registration budget
- Understand cost ceilings
Query Keys
| # | Name | Type | Description |
|---|---|---|---|
| 1 | netuid | u16 | netuid (u16, hashed key component) |
Stored Value
Relationships
Modified By
Related Events
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 MaxBurn storage
const netuid = 1;
const result = await api.query.SubtensorModule.MaxBurn.getValue(netuid);
console.log("MaxBurn:", result);Version History
v101 block 1 Added
v123 block 720,235 Internal re-bind
v149 block 3,014,339 Internal re-bind
v166–v194 · runtime versions skipped on chain (never deployed)
v195 block 3,791,350 Internal re-bind
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
- v101
- Current Version
- v411