AddStakeBurnRateLimitExceeded

Error v385 → v422, v423 → v424, v432 → v432, v437 → v440, v441 → current 7.131

"Add stake and burn " exceeded the operation rate limit

From Chain Metadata

"Add stake and burn" exceeded the operation rate limit

What This Means

"Add stake and burn" exceeded the operation rate limit

Common Causes

  • You called set_weights again before the rate limit window passed
  • The rate limit is WeightsSetRateLimit(netuid), which each subnet sets for itself
  • Your previous tx is still in the mempool (not yet included in a block)

How to Fix

  • Query SubtensorModule.LastUpdate(netuid, uid) to see your last update block
  • Query SubtensorModule.WeightsSetRateLimit(netuid) to get the minimum blocks between updates
  • Wait until: current_block > LastUpdate + WeightsSetRateLimit, then retry

Storage to Check

Version History

v385 block 7,782,670 Added
v423 block 8,486,593 Shape modified
v432 block 8,636,190 Shape modified
v437 block 8,679,056 Shape modified
v441 block 8,765,683 Shape modified Current

Runtime Info

Pallet Index
7
Error Index
131
Error Code
7.131
Runtime Version
v490