#consensus

Read Hedera's network layer live from the public Hedera Mirror Node — no key. Hedera runs on a permissioned set of council-operated consensus nodes; the Hedera on-chain reader resolves account, token and HBAR-supply state, but it does not surface the node set, the live HBAR/USD exchange rate the network itself uses, or the current network fee schedule. This opens that. List the consensus nodes with their node id, account, operator description (e.g. "Hosted by Google | US"), current and min/max stake in HBAR, rewarded vs not-rewarded stake and whether they decline rewards; read the live HBAR↔USD rate the network pins for fee calculation — current and next period, with a derived USD-per-HBAR price — the protocol's own oracle rate, not a market ticker; and read the current network gas fee schedule per transaction type. Stake is reported in HBAR (1 HBAR = 100,000,000 tinybars). The network / validator / economics layer for Hedera explorers, staking dashboards, wallets and analytics. Distinct from the Hedera on-chain reader (account / token / supply), the HCS topic reader and the HTS token browser. Live from the mirror node; short cache only.

api.oanor.com/hederanetwork-api

Nano's Open Representative Voting (ORV) consensus — the representative layer — live from the public Nano RPC, no key, nothing cached. Nano has no miners and no staking rewards: every account delegates its balance as voting weight to a representative, and online representatives vote to confirm transactions, with a quorum threshold securing the network. The base Nano reader covers accounts, blocks and history, but not the representative layer; this opens it. Rank the online representatives by delegated voting weight (in NANO), each with its share of total online stake and whether it clears the 0.1%-of-online-stake principal-representative threshold that earns a vote in consensus. Look up a single representative by address for its weight, stake share, principal status and whether it is currently online and voting. And read the live confirmation quorum — the total online voting stake, the trended and peer stake, the quorum delta and percentage, and the minimum weight a representative needs to count. The consensus-and-voting layer for Nano wallets, representative dashboards, delegators and analytics. Live from rpc.nano.to and peer nodes.

api.oanor.com/nanoreps-api

The Hive blockchain's delegated-proof-of-stake consensus — the witness election — live from the public Hive RPC nodes, no key, nothing cached. Hive is secured by 20 elected witnesses plus a rotating backup, voted in by HIVE holders with their staked (vested) weight; witnesses produce the blocks, publish the HBD price feed and set the chain parameters. The Hive content reader covers accounts, posts and communities, but not the witness consensus; this opens it. Rank the witnesses by vote weight, each with its vote total converted to HIVE Power, missed block count, running node version, published HBD price feed and the chain parameters it sets. Look up a single witness by account for its votes, rank and production. And read a live network overview — the head block, the current witness producing it, witness participation over the last 128 slots, the total vesting (staking) fund and the HIVE-per-MVESTS rate. The consensus-and-governance layer for Hive wallets, witness dashboards, voters and analytics. Live from api.hive.blog and peer nodes.

api.oanor.com/hivewitness-api

Read the Hedera Consensus Service (HCS) live from the public Hedera mirror node — no key. HCS is Hedera's signature feature: a decentralized, ordered, timestamped message log that powers audit trails, supply-chain tracking, oracles and tokenization registries — the layer that account- and token-readers miss entirely. Look up any topic for its memo, admin/submit-key control, auto-renew and deleted state; read a topic's most recent messages, decoded from base64 to text, each with its consensus sequence number, timestamp and the account that paid to submit it; or discover the topics that are actively receiving messages right now. The consensus-messaging layer for Hedera wallets, explorers, dApps and auditors. Live from the mirror node; short cache only.

api.oanor.com/hederatopic-api

The live consensus state of Ethereum's Beacon Chain — the proof-of-stake layer that secures Ethereum — read keyless straight from a public consensus-layer node. The single thing that matters for the health of proof-of-stake Ethereum is whether it is finalizing: every epoch (about every six and a half minutes) the validators are supposed to justify and then finalize the chain, and on the rare occasions that finality stalls — as it briefly did in 2023 — staking services, exchanges and bridges need to know immediately. The status endpoint returns the current head slot and epoch, how far through the current epoch the chain is and how long until the next one, the finalized and justified epochs, the finality lag (how many epochs behind finality the head is — a lag of two is healthy, a growing lag is trouble) and whether the node is fully synced and finalizing. The finality endpoint returns the finalized, current-justified and previous-justified checkpoints in detail, with how far behind the head each is in epochs and minutes. The genesis endpoint returns the chain's genesis time, how long Ethereum proof-of-stake has been running and the slot/epoch timing constants (a slot every 12 seconds, 32 slots per epoch). This is the Ethereum consensus / finality cut — distinct from the execution-layer feeds (gas, blocks, transactions), the staking-token and restaking feeds and the price feeds: it is the beacon chain's own heartbeat. Note it reports consensus state (slots, epochs, finality), not per-validator economics, which a public consensus node does not serve in one call. Times are UTC; epochs and slots are integers. No key, nothing stored beyond a short cache.

api.oanor.com/beaconchain-api