Register

A subnet node registers itself and transfers at least the minimum required balance as a stake. This registration is used as the subnets' proof-of-stake.

Call register_subnet_node to register

pub fn register_subnet_node(
    origin: OriginFor<T>, 
    subnet_id: u32, 
    hotkey: T::AccountId,
    peer_id: PeerId, 
    bootstrap_peer_id: PeerId,
    client_peer_id: PeerId,
    delegate_reward_rate: u128,
    stake_to_be_added: u128,
    a: Option<BoundedVec<u8, DefaultSubnetNodeUniqueParamLimit>>,
    b: Option<BoundedVec<u8, DefaultSubnetNodeUniqueParamLimit>>,
    c: Option<BoundedVec<u8, DefaultSubnetNodeUniqueParamLimit>>,
)

Registration Inputs

subnet_id: The subnet ID to register the node to.

hotkey: The hotkey of the node. This key is used to run non-fund-based extrinsics, such as consensus (validating and attesting).

1. Hotkeys are network-unique. Meaning, no one hotkey can be used twice.

2. Hotkeys can also never match the coldkey.

peer_id: The peer ID of the node. This is used for signature validation within the subnet, proof-of-stake, and more.

bootstrap_peer_id: The bootstrap peer ID is the bootnode of the subnet node, used for the same signature validation within the subnet, but only expected to be a public-facing bootnode.

client_peer_id: The client peer ID is the bootnode of the subnet node, used for signature validation within the subnet, but only expected to be a client-side peer. This is useful for hosting frontends for subnets that require outside world functionality, such as a chatbot.

delegate_reward_rate: The rate of rewards given to users who stake to the node.

stake_to_be_added: The amount of stake to be added. The blockchains has a minimum required of 100 TENSOR, but subnets may require more (check subnet documentation for required proof-of-stake balance).

---

Once registered, the node is given the Registered classification, put into a queue, and given a start epoch.

Queue

The length of the queue is based on epochs and is unique to each subnet.

Start Epoch

The start epoch is the epoch a node must activate itself on; otherwise, it can no longer activate.

Note

A subnet can utilize grace epochs (ActivationGraceEpochs) that allow nodes to register on the start epoch, plus the grace epochs.