// Section 13.9 · Operate
Reading the Network Without the UI
The Console is a thin client over two sources.
// 13.9 · on-chain reads + coordinator liveness · no public submitter api
Everything the Console shows comes from on-chain reads of NodeRegistryLocker and OperatorStakeRewardsV2, plus the coordinator's per-node liveness. The on-chain actions (registerNode, claim, requestUnstake, cancelUnstake, withdrawStake) are wallet transactions to those contracts. There is no public submitter API at launch: the coordinator's intake is internal to ParalleliX AI, and a documented, permissionless submitter API is part of the planned open marketplace.
On-chain actions and read routes
// registerNode · claim · unstake on-chain · nodes, uptime, rewards on read
Node lifecycle states
// active <-> idle -> cooling -> retired · only active earns
How to read it
// any ethereum rpc for chain state · coordinator for liveness
Read NodeRegistryLocker and OperatorStakeRewardsV2 over any Ethereum RPC. No API key, no permission: stake, tier, lifecycle flags, and the live earned(nodeId) balance are public on-chain reads. Writes are wallet-signed transactions to the same contracts.
Whether a node is currently online comes from the coordinator. The Console polls it to render the per-node online dot and the per-second reward ticker between on-chain reads. There is no public submitter API; that surface ships with the planned open marketplace (§16.2).