TxDelegateTakeRateLimitSet

Event Re-added v149 → v219, v233 → v247, v252 → v265, v273 → v277, v290 → current #40

Emitted when delegate take rate limit is changed.

Useful for: validatorsdelegatorsanalyticsdevelopers

The Big Picture

Validators can't change their take constantly - they're rate limited. This is a key delegator protection: a validator can't bait you with low take then immediately jack it up. The rate limit forces stability and gives delegators time to react to announced changes.

Why This Matters

As a delegator, this limit protects you from take manipulation. As a validator, it constrains how quickly you can adjust pricing. Changes to this limit affect the entire delegation marketplace's dynamics and trust model.

Example Scenario

Delegators complained about validators gaming take rates. The rate limit is increased from 1 day to 1 week. TxDelegateTakeRateLimitSet fires. Validators now wait a week between take changes. Delegators have much more time to react to any take increase announcements.

Common Questions

Does the rate limit apply to increases and decreases equally?: Often decreases are allowed immediately or with shorter limits (good for delegators), while increases have longer limits (protect against manipulation). Check specific implementation.
What if I need to change take urgently?: You wait. The rate limit is enforced by the chain. Plan take changes in advance and communicate with your delegators about upcoming adjustments.
Does this affect new delegates?: New delegates start at default take. They're subject to rate limits for any changes from there. They can't immediately drop then spike - same rules apply.

Use Cases

Track validator take change frequency limits
Plan take adjustments around rate limits
Monitor delegator protection policies
Build validator management tools

How to Use This Event

→ Monitor rate limit changes for delegation planning
→ Track governance policies protecting delegators
→ Build rate-limit-aware validator tools

From Chain Metadata

setting the delegate take transaction rate limit.

Triggers

Preconditions

Caller has admin/sudo privileges

Effects

Postconditions

Rate limit for delegate take changes updated

Side Effects

Delegates must wait between take changes

Event Data

#	Name	Type	Description
0	arg0	u64	Event field #0 (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 TxDelegateTakeRateLimitSet events
api.query.system.events((events) => {
  events
    .filter(({ event }) =>
      event.section === stringCamelCase("SubtensorModule") &&
      event.method === "TxDelegateTakeRateLimitSet"
    )
    .forEach(({ event }) => {
      console.log("TxDelegateTakeRateLimitSet:", event.data.toHuman());
    });
});

Version History

Version:

v149 block 3,014,339 1 args

v233 block 4,920,350 1 args

v252 block 5,163,656 1 args

v273 block 5,659,032 1 args

v290 block 5,947,548 1 args Current

Runtime Info

View Source

Pallet Index: 7
Event Index: 40
First Version: v149
Current Version: v393

Back to SubtensorModule Events