AlphaRecycled

Event Re-added v257 → v265, v273 → v277, v290 → v315, v320 → v326, v334 → v367, v372 → v377, v385 → current #94

Emitted when alpha tokens are recycled back to the subnet .

Useful for: stakerssubnet ownersanalyticsdevelopers

The Big Picture

Alpha recycling is the 'give back' way to exit a subnet position. Instead of converting Alpha to TAO (which extracts value from the subnet), recycling returns your Alpha to the subnet's available supply. This benefits remaining stakers by improving the Alpha/TAO exchange rate. Think of it as selling your shares back to the company instead of on the open market - better for the ecosystem, though you lose those tokens.

Why This Matters

When you want to reduce your subnet stake, you have choices: unstake (convert to TAO), recycle (return to subnet), or burn (destroy forever). Recycling is the altruistic option - you give up your Alpha, but the subnet benefits from improved token economics.

Example Scenario

You have 100 Alpha on subnet 5 but want to exit. Instead of unstaking (which would reduce the subnet's Alpha value for everyone), you recycle. AlphaRecycled fires with your account and 100 Alpha. Your position is gone, but the subnet's AlphaOut decreased, making remaining Alpha slightly more valuable.

Common Questions

What's the difference between recycling and unstaking?: Unstaking converts your Alpha to TAO (you keep value, subnet loses supply). Recycling returns Alpha to the subnet (you lose value, subnet keeps supply healthy).
Why would anyone recycle instead of unstake?: Community benefit, subnet support, or if you believe in the subnet long-term and want to exit without hurting other stakers. Some may recycle small dust amounts that aren't worth the gas to unstake.
Does recycling affect my other positions?: No, it only affects your Alpha on that specific subnet. Your stakes on other subnets are untouched.

Use Cases

Exit a subnet position while benefiting the subnet ecosystem
Track recycling activity to understand subnet health
Monitor when large holders reduce positions
Build subnet liquidity analytics tools

How to Use This Event

→ Monitor your own recycling transactions
→ Track subnet-wide recycling to gauge sentiment
→ Build dashboards showing recycling vs burning vs selling patterns

From Chain Metadata

Alpha has been recycled, reducing AlphaOut on a subnet. Parameters: (coldkey, hotkey, amount, subnet_id)

Triggers

Emitted by

recycle_alpha

Preconditions

Account has alpha to recycle
Recycle operation requested
Alpha amount is valid (non-zero)

Effects

Storage Modified

Alpha RAORecycledForRegistration SubnetAlphaOut TotalHotkeyAlpha TotalHotkeyShares

Postconditions

User's alpha decreased
SubnetAlphaOut decreased (more alpha available)
Subnet's available alpha supply increased

Side Effects

Improves subnet's alpha supply for future stakers
May improve Alpha/TAO exchange rate for the subnet
Reduces user's stake position on that subnet

Event Data

#	Name	Type	Description
0	arg0	AccountId	Event field #0 (AccountId) (hex -> SS58)
1	arg1	AccountId	Event field #1 (AccountId) (hex -> SS58)
2	arg2	u64	Event field #2 (u64)
3	arg3	u16	Event field #3 (u16)

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

Version History

Version:

v257 block 5,228,683 4 args

v273 block 5,659,032 4 args

v290 block 5,947,548 4 args

v320 block 6,523,566 4 args

v334 block 6,811,690 4 args

v372 block 7,430,358 4 args

v385 block 7,782,670 4 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 94
First Version: v257
Current Version: v393

Back to SubtensorModule Events