Activating

Once registered, a subnet owner can activate the subnet to begin running consensus in parallel with the base layer blockchain, provided the activation conditions are met.

Activation Conditions

  • Must have the minimum required subnet nodes based on MinSubnetNodes.

  • Must have the floating minimum subnet delegate stake balance based on the percentage (see MinSubnetDelegateStakeFactor) of the total supply of tokens in the network.

    • This balance gradually increases and must be met on each epoch, or the subnet is removed.


Enactment Period

The enactment period is the period after the registration period (the period during which initial coldkeys can register).

In this period

  • No new nodes may register.

  • Users can continue to delegate stake.

    • This is useful because users now know if a subnet has the minimum nodes.

Activation

The owner can activate a subnet at any time if the subnet meets the activation conditions; otherwise, if the subnet is called to be activated while in the enactment period, the subnet is removed from the registration process.

Once activated

  • Subnet is activated and given an open slot.

    • Each slot is a block on the epoch where the subnet has its rewards distributed from consensus.

  • The initial_coldkeys list is removed, and anyone can register.

Extrinsic

pub fn activate_subnet(
    origin: OriginFor<T>, 
    subnet_id: u32
)

Slots

Once activated, the subnet will be placed in an open slot. Each slot is a block in the epoch unique to each subnet, where consensus data is compiled, emissions are distributed, and the next epoch's validator is elected.

Last updated