Consensus and nodes
A shared market needs one answer to two questions: which actions happened, and what financial state did they produce? Novrinex validators answer both for every block.
They first agree on an ordered set of transactions. Each validator then applies Novrinex Core to the previous state and verifies the resulting balances, orders, fills, positions, and market state before committing the block.
Agreement and execution
Section titled “Agreement and execution”Consensus establishes the canonical order of transactions and finalizes the block. Core determines whether each transaction is financially valid and calculates its result.
Agreement on an invalid proposal is not sufficient. Validators independently verify FairFlow ordering, signatures, account sequences, transaction fees, and the complete Core state transition.
Novrinex uses CometBFT for peer networking, proposals, votes, validator-set changes, evidence, and deterministic finality. The application surrounding Core manages accounts, custody, staking, governance, upgrades, snapshots, queries, and events.
Node roles
Section titled “Node roles”A validator proposes and votes on blocks while executing every committed transition. A full node verifies the same blocks without participating in voting.
RPC nodes accept public transactions and serve direct queries. Sentry nodes relay network traffic while keeping validator endpoints private. Archive nodes retain complete history, while snapshot and state-sync nodes help a new or replaced node join from a recent verified state.
Validator signing keys remain separate from public RPC infrastructure. A public service failure can interrupt access without granting control over the validator key or changing committed financial state.
Services around the network
Section titled “Services around the network”Indexers, APIs, WebSocket servers, oracle publishers, archives, and snapshot services operate alongside consensus nodes. Each has a specific job and can recover independently.
An indexer outage removes a convenient data view but does not alter an account. An oracle quorum failure invokes the feed’s pause policy. An RPC failure can be routed around while validators continue to agree on blocks.
Verifying state
Section titled “Verifying state”Every node commits an application hash for each block. Nodes compare this commitment when replaying genesis, restoring a snapshot, restarting, or checking agreement across validators.
Snapshots shorten recovery but do not replace verification. A restored node checks the chain history and application state before serving it as authoritative.