MaxBurnSet

Event Re-added v101 → v127, v133 → v219, v233 → v247, v252 → v265, v273 → v277, v290 → current #37

Emitted when maximum burn for registration is changed.

Useful for: minersvalidatorssubnet ownersanalyticsdevelopers

The Big Picture

Burn registration cost can spike during high demand, but there's a ceiling - it can't go above MaxBurn. This protects registrants from exorbitant costs during demand surges. Even if everyone wants to register simultaneously, the cost is capped.

Why This Matters

MaxBurn is the worst possible burn registration cost. Even during massive demand spikes, you won't pay more than this. Understanding the ceiling helps you set maximum budgets and decide whether a subnet is affordable for you in all conditions.

Example Scenario

Subnet 8 had MaxBurn of 10 TAO. To make registration more accessible during demand spikes, they lower it to 5 TAO. MaxBurnSet fires. Even during the craziest demand periods, burn registration now costs at most 5 TAO instead of 10 TAO.

Common Questions

What happens if demand pushes burn above MaxBurn?: It's capped at MaxBurn. The registration queue might get longer, but cost doesn't exceed the ceiling. More people compete for limited slots at the max price.
Is MaxBurn common or just during extreme demand?: On popular subnets, burn can regularly hit MaxBurn during busy periods. On quiet subnets, you might never see it. Track historical burn to understand your subnet.
Can I wait for lower burn if it's at MaxBurn?: Yes, if demand decreases, burn will drop (down toward MinBurn). But on consistently hot subnets, MaxBurn might be the norm. Evaluate whether to pay or wait.

Use Cases

Track maximum registration costs on subnets
Plan registration budget with known ceiling
Monitor subnet registration economics
Build registration cost tracking tools

How to Use This Event

→ Track maximum burn as your worst-case registration cost
→ Monitor ceiling changes affecting budget planning
→ Build registration cost estimation tools

From Chain Metadata

setting max burn on a network.

Triggers

Preconditions

Caller has admin/sudo privileges

Effects

Postconditions

MaxBurn updated for subnet

Side Effects

Sets ceiling for burn registration cost

Event Data

#	Name	Type	Description
0	arg0	u16	Event field #0 (u16)
1	arg1	u64	Event field #1 (u64)

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 });

// Subscribe to MaxBurnSet events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "MaxBurnSet"
    )
    .forEach(({ event }) => {
      console.log("MaxBurnSet:", event.data.toHuman());
    });
});

Version History

Version:

v101 block 1 2 args

v133 block 1,404,224 2 args

v233 block 4,920,350 2 args

v252 block 5,163,656 2 args

v273 block 5,659,032 2 args

v290 block 5,947,548 2 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 37
First Version: v101
Current Version: v393

Back to SubtensorModule Events