// Section 13.7 · Operate
Account: Wallet, Node Keys, Notifications
Manage credentials, not nodes.
// 13.7 · account · three tabs · all self-contained
Three tabs. Each tab is self-contained; this surface manages the operator's credentials and settings, not the nodes themselves.
Tab 1 · Wallet
// connected address · available + staked balance · on-chain history
Connected address (abbreviated) with click-through to the block explorer.
$PRLX balance split into available and staked (locked across the wallet's nodes).
On-chain history: every registerNode, claim, requestUnstake, and withdrawStake the wallet has signed, with tx hash, block, and the nodeId it bound to.
Disconnect action that clears the local session without affecting any on-chain state.
Tab 2 · Node keys
// read-only nodeKeyHash references · the private key never leaves the machine
A read-only reference of each node's nodeKeyHash and the nodeId it is bound to, so the operator can match a Console node to the machine running its Node CLI.
The node keypair is a separate, low-value liveness key generated by the CLI, never the staking wallet's key.
The Console never holds or displays the node private key; it lives only on the operator's machine.
The nodeKeyHash here is the value passed to registerNode at registration time.
Tab 3 · Notifications
// node-state events · signed payloads · destination health
Optional destinations (email, webhook) for node-state events: node.offline, node.online, node.uptime_low, node.cooldown_started, node.withdrawable.
Each webhook payload is signed; consumers verify against the published signing key to drop spoofed events.
Retry policy documented inline: exponential backoff up to 24 hours, then drop.
Endpoint health: each destination shows last delivery, last failure, and rolling success rate.