register_limit
Call v401 → current New #134User register a new subnetwork via burning token, but only if the
View calls on chainCall Workflow
This diagram shows the call execution flow: starting with register_limit, passing through validation
(signature, nonce, mortality, fee payment), then pre-dispatch checks where it may fail with errors like HotKeyNotRegisteredInSubNet, NotRegistered, HotKeyNotRegisteredInNetwork, followed by dispatch, and finally post-dispatch where ExtrinsicSuccess is emitted and fees are settled.
Press enter or space to select a node. You can then use the arrow keys to move the node around. Press delete to remove it and escape to cancel.
Press enter or space to select an edge. You can then press delete to remove it or escape to cancel.
Click items to navigate. Pan and zoom to explore.
From Chain Metadata
User register a new subnetwork via burning token, but only if the on-chain burn price for this block is <= `limit_price`. `limit_price` is expressed in the same TaoCurrency/u64 units as `Burn`.
Input Parameters
Permissions
Origin
Unknown
Required Role
Permission data inferred from metadata. May be incomplete.
Requirements
- Required conditions for addition met
Effects
Postconditions
- Item successfully added/registered
Possible Errors
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 });
// Build register_limit call
const netuid = 1;
const hotkey = "5GrwvaEF5zXb26Fz9rcQpDWS57CtERHpNehXCPcNoHGKutQY";
const limit_price = 0;
const call = api.tx[stringCamelCase("SubtensorModule")][stringCamelCase("register_limit")](
netuid,
hotkey,
limit_price
);Runtime Info
View Source- Pallet Index
- 7
- Call Index
- 134
- First Version
- v401
- Current Version
- v401