What a node is
A Vorliq node runs the blockchain API, validates blocks, stores the chain, receives transactions, mines blocks when requested, and can connect to other peers.
Node identity, trust, and health history
Vorliq nodes maintain the blockchain, share blocks and transactions, and help the network become more resilient as independent operators join.
How the registry works
Operators can register a public node URL with display metadata. Heartbeats update chain height, last block hash, software version, sync status, and recent health history.
Lifecycle and archival
Registry lifecycle states are active, stale, inactive, archived, and retired. Archived and retired nodes are hidden from default live views but preserved in history. Old localhost or test nodes may appear as stale or inactive until a protected admin archives them. Do not manually edit registry.json.
Trust signals
Reliability is the percentage of recent checks that were online and synced. Uptime is the percentage of recent checks that were online. These are operational signals, not identity verification.
Sync states
synced means the node is active, valid, at the same trusted height, and has the same latest hash. behind means it is valid but lower. ahead means higher but not automatically trusted. forked means a comparable hash mismatch. stale means the heartbeat is outside the active window. unreachable means diagnostics could not be checked. unknown means safe comparison data is missing.
Peer propagation
Active synced HTTPS registry nodes may relay signed pending transactions and newly mined direct-next blocks when broadcast is enabled. Receiving nodes still validate every payload and quarantine non-next blocks instead of replacing the local chain. See Peer Propagation.
Register and connect
Use the Run Your Own Node guide to verify the trusted public node first, install the app, configure node identity, register with heartbeat metadata, run a dry-run verified chain bootstrap, and run the doctor. Use the Registry page to inspect public nodes with a safe HTTP or HTTPS URL, display name, region, country, and optional operator wallet. Use the Network page to add active registry nodes to your peer list. See Node Lifecycle before archiving, restoring, or retiring nodes.
More independent nodes improve availability and make it easier for the community to compare chain height, block hash, and live sync status. Use Node Sync or the live comparison page to see fork awareness. Do not manually edit chain.json; recover forked nodes with dry-run bootstrap first.