Testnet Tensor
  • Introduction
  • Explorer
  • GPT
  • DSN Dashboard
  • Create Account
    • Wallet
    • CLI
    • Faucet
  • Hypertensor CLI
    • Hypertensor CLI
  • Run A Subnet Node
    • Getting Started
    • Wiki
      • Running on AMD GPU
      • Running on Windows Using WSL
      • Troubleshooting
    • Generate Keypair
    • Register & Stake
    • Add
    • Start Validator Node
    • Start Bootstrap Node
    • Activate
    • Update Delegate Reward Rate
    • Deactivate
    • Remove
    • Keys
  • Delegate Staking
    • Introduction
    • Add Delegate Stake
    • Transfer Delegate Stake
    • Remove Delegate Stake
    • Claim Delegate Stake
  • Node Delegate Staking
    • Introduction
    • Add Node Delegate Stake
    • Transfer Node Delegate Stake
    • Remove Node Delegate Stake
    • Claim Node Delegate Stake
  • Delegate Staking Utils
    • Introduction
    • Subnet to Node
    • Node to Subnet
  • Build a Subnet
    • Introduction
    • DSN Standard
    • Subnet Consensus Protocol (SCP)
      • Incentives
      • Accounting
      • Proposals
    • Subnet
      • Registration
      • Activation
      • Deactivation
    • Subnet Nodes
      • Registration
      • Activation
      • Deactivate
  • Contribute
Powered by GitBook
On this page
  1. Run A Subnet Node

Add

PreviousRegister & StakeNextStart Validator Node

Last updated 1 month ago

Register and activate in one call.

This registers and activates the subnet node all in one call. Unless the subnet you run a node on suggests this, this is not suggested. Instead, use and separately.

This is useful if the subnet node can load the subnet requirements (such as loading a model) before the next epoch where the node will be included in the consensus. Otherwise, use the and flow.

python -m subnet.cli.hypertensor.subnet_node.add--subnet_id [int] --peer_id [str] --stake_to_be_added [float]
python -m subnet.cli.hypertensor.subnet_node.add--subnet_id 1 --peer_id 12D3KooWGmoSHnvRsktrGzNTfCEwzY2TKAYPRtdaA9AwxHwLKfLa --stake_to_be_added 1000.00

Parameters:

--subnet_id: The ID of the subnet. This can be checked by querying the model path through the SubnetPaths storage element.

--hotkey: (Suggested but optional) The key used to perform frequent subnet node operations like validating and attesting.

--peer_id: The Peer ID generated in .

--bootstrap_peer_id: (Optional) The bootstrap Peer ID generated in .

  • A bootstrap peer ID isn't required but Hypertensor allows setting the variable once. Once set, it cannot be updated.

  • Once a bootstrap node is registered on-chain, this cannot be updated.

    • If a subnet node doesn't register with a bootstrap node, it can set its bootstrap node using the register_subnet_node_a_parameterfunction on the Hypertensor blockchain.

--delegate_reward_rate: (Optional) The subnet node emissions reward rate to allocate to delegators.

--stake_to_be_added: The minimum staked is 1000.00.

--local: (Optional) Argument for local testing to use the LOCAL_RPC environment variables.

--phrase: (Optional) The coldkey phrase. The latest command will be removed from your CLI's history if used.

--b: (Optional) Any non-unique variable. The feature is for subnet developers to utilize.

--c: (Optional) Any non-unique variable. The feature is for subnet developers to utilize.

Notes

  • If the hotkey and phrase arguments are not passed, the key in the environmental variables (.env file) will be used for both the hotkey and coldkey.

This will:

  • Stake the minimum required balance.

and your subnet node on-chain and claim a subnet node slot on the Hypertensor blockchain.

Register
Activate
Register
Activate
Generate Keypair
Generate Keypair
Register
activate