The cockpit opens for the address you connect: the Node Operator Cockpit if it runs a node, the Bonder Cockpit if it bonds to one. Watch-only works too, nothing is signed to look.
The Node Cockpit is THORWallet's dashboard for THORChain node operators and bond providers. Connect a wallet or a watch-only address and it detects what the address does: a node operator gets the Node Operator Cockpit (node health, chains, slash points, providers, rewards and operator actions), a bond provider gets the Bonder Cockpit (bonds, rewards and node health), and an address that does both gets a switch. Nothing is signed to look.
Everything is read live from THORNode and Midgard. The network numbers below are the same reads.
Live data, read
A web dashboard for running or bonding to a THORChain node: the state of your node and its providers, the whole validator set, mimir votes, network security and emergency halts, read live from THORNode and Midgard. Operator actions such as setting the fee, adding providers, leaving or rotating the operator address build the exact THORChain memo for you to sign with the operator wallet.
No. The All nodes, Network, Votes and Emergency pages are public. The overview and Security open for the address you connect; a watch-only address works and nothing is signed to look. Actions need the operator or bonder wallet.
Only addresses on a node's provider list can bond to it. The operator whitelists you with a BOND memo that carries your address; you then send a BOND memo with your RUNE from your own wallet. Nodes listed on RuneBond take a slot request (0.1 RUNE with a TB:WHT memo) that the operator approves. The operator keeps a fee from the providers' rewards, set in basis points per node.
A node takes up to 100 bond providers. A node needs at least 300k RUNE of total bond to be churned in. Bond above the bond hard cap (now 1.03M RUNE) earns nothing. In THORWallet, Earn lists the RuneBond nodes and builds the slot request and the bond memo for you to sign.
A churn rotates the validator set. Every churn interval (now 43,200 blocks, about 3d 1h) THORChain removes the lowest bond, the worst performer and the oldest node, plus nodes that asked to leave or run an old version, and the ready standby nodes with the highest bond take their place (up to 4 new nodes per churn). At churn the accrued rewards are added to each bond. Unbonding and leaving are blocked while vaults migrate. While the HALTCHURNING mimir is set, no rotation happens and rewards keep building. Churning is halted right now.
Penalty points an active node earns when it does not observe a transaction the other nodes saw, fails or is slow on a TSS keysign, or misses signing blocks; a failed keygen or a double sign costs much more. They count per churn cycle: at churn they reduce that node's share of the rewards, which also lowers what its bond providers earn, and the worst performer of the active set is churned out. They start again from zero in the next cycle.
No. Operator actions are THORChain deposits with a memo, signed by the operator wallet you connect. Anything that needs the node key inside the THORNode pod (mimir votes, node pause, ban and upgrade votes) is shown as the exact command to run on your node.