MaxBurn

Storage Map v101 → current

Maximum burn for registration .

Explore chain
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

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

#NameTypeDescription
1
key1
u16 key1 (u16)

Stored Value

Value in RAO (÷10⁹ for TAO)

RAO -> TAO (/ 10^9)

Relationships

Modified By

Related Events

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 MaxBurn storage
const key1 = 0;

const result = await api.query
  [stringCamelCase("SubtensorModule")]
  [stringCamelCase("MaxBurn")](
  key1
);

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

Runtime Info

View Source
Pallet
SubtensorModule
Storage Kind
Map
First Version
v101
Current Version
v393