RAORecycledForRegistrationSet

Event Re-added v118 → v120, v121 → v122, v123 → v127, v133 → v135, v136 → v148, v149 → v165, v195 → v219, v233 → v247, v252 → v265, v273 → v277, v290 → v315, v320 → current #51

Emitted when the RAO recycled amount for registration is changed.

View events on chain

Useful for: subnet ownersminersvalidatorsanalyticsdevelopers

The Big Picture

When you pay to register (burn), the TAO doesn't necessarily disappear entirely. Some portion may be 'recycled' back into the subnet's economics rather than being permanently burned. This parameter controls that split. Higher recycled amount means more TAO stays in circulation; lower means more is truly burned (deflationary).

Why This Matters

When you pay TAO to register, where does it go? By default, TAO goes into the subnet's liquidity pool and Alpha is burned. This recycling setting can redirect some of that TAO to subnet rewards instead. This affects registration economics.

Example Scenario

Subnet 6 had 0% recycling - all registration TAO went to the liquidity pool. To boost subnet rewards, they set 50% recycling. RAORecycledForRegistrationSet fires. Now half of registration fees go to the subnet's reward pool. Registration still costs you, but the subnet ecosystem benefits more directly.

Common Questions

Does recycled mean I get it back?: Not directly. Recycled RAO goes to subnet economics (reward pools, etc.), not back to you. It benefits the subnet ecosystem, not you personally.
What happens to non-recycled TAO?: It goes into the subnet's liquidity pool (SubnetTAO). The Alpha received from that swap is burned. So TAO stays in circulation while Alpha supply decreases.
How does this affect my registration decision?: Not much directly - you pay the same either way. But understanding where your TAO goes helps you evaluate whether you're supporting a healthy subnet ecosystem.

Use Cases

Track registration fee distribution policies
Understand where registration TAO goes
Monitor subnet economic configuration
Build registration cost analysis tools

How to Use This Event

→ Track registration burn vs recycle ratios
→ Monitor deflationary policies across subnets
→ Build registration economic analysis

From Chain Metadata

setting the RAO recycled for registration.

Triggers

Preconditions

Caller has admin/sudo privileges

Effects

Postconditions

RAORecycledForRegistration updated

Side Effects

Changes registration burn economics

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 RAORecycledForRegistrationSet events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "RAORecycledForRegistrationSet"
    )
    .forEach(({ event }) => {
      console.log("RAORecycledForRegistrationSet:", event.data.toHuman());
    });
});

On-Chain Activity

Emission Frequency

●●●○○○ Active 100K–1M emissions

Regular feature-level activity

#28 most emitted event

As of block 7,429,232

Version History

Version:

v118 block 222,600 2 args

v121 block 518,345 2 args

v123 block 720,235 2 args

v133 block 1,404,224 2 args

v136 block 1,756,781 2 args

v149 block 3,014,339 2 args

v195 block 3,791,350 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

v320 block 6,523,566 2 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 51
First Version: v118
Current Version: v393

Back to SubtensorModule Events