// Section 13.4 · Operate
Register a Node: Three Steps
A three-step linear flow.
// 13.4 · register a node · url changes per step · refresh-safe
Declare the tier the machine will run. The Node CLI verifies the declared tier; a mismatch zeroes uptime for the affected period.
Set the stake for this node. Minimum 50,000 $PRLX, variable above the floor. The Console shows inline how stake maps to reward weight.
Single registerNode(stakeAmount, hardwareTier, nodeKeyHash) call. Once it confirms, the Console assigns the nodeId and pivots to My Nodes.
Step 1 · Hardware tier
// four tiers · CLI verifies the declared tier
Basic CPU, light RAM. The entry tier for commodity machines.
Mid-tier GPU, large RAM.
Heavy GPU / HPC (A100, H100).
Specialised (TPU, FPGA, custom ASIC).
The Console states plainly that the Node CLI verifies the declared tier. A mismatch zeroes uptime for the affected period; the stake is never touched.
Step 2 · Stake amount
// 50,000 PRLX floor · variable above · one stake one node
50,000 $PRLX floor. The Console rejects anything below it.
Any amount above the floor. Higher stake means higher reward weight.
No top-up. To commit more, register another node. No per-wallet cap.
┌──────────────────────────────────────────────────────────────┐ │ REWARD WEIGHT · preview │ ├──────────────────────────────────────────────────────────────┤ │ stake 100,000 PRLX │ │ tier_mult tier 3 = ×2.5 │ │ ────────────────────────────────────────────────────────── │ │ reward_weight (at full uptime) = 250,000 │ │ │ │ reward rate = weight / total online weight × stream rate │ │ one stake = one node · no top-up · no per-wallet cap │ └──────────────────────────────────────────────────────────────┘
Step 3 · Sign registerNode
// single transaction · console transitions to my nodes
Wallet signature on a single registerNode(stakeAmount, hardwareTier, nodeKeyHash) call. nodeKeyHash comes from the Node CLI's node keypair, never the staking wallet's key. Once the transaction confirms, the Console assigns the returned nodeId and transitions to Surface 03 (My Nodes). The operator then attaches a machine with the Node CLI to bring the node online.