#proof-of-stake

Read NEAR's validator set and network economics live from a public NEAR RPC endpoint — no key. NEAR is sharded proof-of-stake: validators stake NEAR, produce blocks and chunks across shards, and earn rewards. The NEAR on-chain reader resolves a single account's state and the view reader runs contract view methods, but neither surfaces the validator set, the next-epoch staking proposals, or the live network economics. This opens that. List the current epoch's validators ranked by stake — each with its account id, stake in NEAR, the blocks and chunks it produced versus expected (its uptime) and slash status; read the next-epoch staking proposals (the validators entering, leaving or re-staking for the upcoming epoch); and read the live network economics — the gas price (in yoctoNEAR), the epoch length in blocks, the protocol version and the block/chunk producer kickout thresholds. The validator / staking / network layer for NEAR explorers, staking dashboards, delegators and analytics. Distinct from the NEAR on-chain account reader and the NEAR view-function reader. Live from RPC; short cache only.

api.oanor.com/nearvalidators-api

The Mina Protocol blockchain — the "succinct blockchain" — live from a public Mina GraphQL node, no key, nothing cached. Mina uses recursive zk-SNARKs to keep the entire chain a constant ~22 KB regardless of history, and secures itself with delegated proof-of-stake (Ouroboros Samasika). This is the first Mina reader in the marketplace. Read the live network status — the blockchain length (tip height), sync status, chain id, the current consensus epoch and slot and the total number of accounts. Read the best (tip) block with its state hash, height, epoch, the block producer who created it and the total MINA supply at that block. And look up any account by public key for its MINA balance (total and liquid), its transaction nonce and the staking delegate it has assigned its stake to. The on-chain layer for Mina wallets, explorers, stakers and analytics. Live from api.minascan.io.

api.oanor.com/mina-api

The Radix Network validator set and ledger status — Radix's proof-of-stake — live from the official public Radix Gateway API, no key, nothing cached. Radix is a layer-1 built for DeFi with its own asset-oriented ledger; its network is secured by validators who stake XRD and accept delegations. This is the first Radix reader in the marketplace. Rank the validators by staked XRD, each with its name, total stake, share of network stake, fee factor and whether it is in the current active set. Look up a single validator by its component address for its stake, rank, share and fee. And read the live ledger status — the current epoch and round, the ledger state version, the validator count and the total XRD staked across the network. The validator-and-staking layer for Radix wallets, staking dashboards, delegators and analytics. Live from mainnet.radixdlt.com.

api.oanor.com/radixvalidators-api

The Avalanche Primary Network validator set — Avalanche's proof-of-stake — live from the official public Avalanche API, no key, nothing cached. Avalanche secures its Primary Network with hundreds of permissionless validators who stake AVAX (and accept delegations) on the P-Chain; this is the first Avalanche reader in the marketplace. Rank the current validators by stake weight, each with its node id, total stake (own plus delegated, in AVAX), share of network stake, uptime, delegation fee, delegator count and the validation reward pending at the end of its term. Look up a single validator by node id for its stake, rank, delegators and uptime. And read a live staking overview — the validator count, how many are connected, the total AVAX staked on the Primary Network, the current circulating AVAX supply and the average uptime of the set. The validator-and-staking layer for Avalanche wallets, staking dashboards, delegators and analytics. Live from api.avax.network.

api.oanor.com/avaxvalidators-api

The Aptos proof-of-stake validator set and staking economics, live from the official public Aptos fullnode — no key, nothing cached. Where the Aptos account and resource readers cover balances and the view reader runs Move calls, this curates the consensus layer they miss. Rank the active validators by voting power — each with its share of total network stake, its operator and its pool address. Read the network-wide staking config: minimum and maximum stake (in APT), the recurring lockup period, the per-epoch reward rate, the voting-power increase limit and the current epoch. And inspect any single stake pool for its active, inactive and pending stake (in APT), the operator that runs the validator, the account delegated to vote, and the unlock timestamp. The staking-and-validator layer for Aptos wallets, staking dashboards, delegators and on-chain analytics. Live from fullnode.mainnet.aptoslabs.com.

api.oanor.com/aptosvalidators-api

The live Ethereum validator entry and exit queues, read keyless straight from a public consensus-layer (Beacon) node. To stake on Ethereum you join a queue to activate a validator, and to unstake you join a separate queue to exit — both rate-limited by the protocol churn limit. The size of these queues is the cleanest real-time signal of staking demand and exit pressure: a long entry queue means capital is rushing in to stake, a long exit queue means validators are leaving. Liquid-staking protocols, exchanges, stakers and ETH analysts watch the queue to time deposits and withdrawals. The queue endpoint is the headline dashboard — how much ETH is waiting to activate (entry) versus exit, the validator counts behind each, the net flow, and an estimate of how long each queue takes to clear at the current activation/exit churn limit (256 ETH per epoch, ~6.4 min). The entry endpoint breaks down the activation side (validators already eligible and churning in, plus freshly-deposited validators not yet eligible). The exit endpoint breaks down the exit side (voluntary exits plus validators forced out by slashing). The validator endpoint looks up any single validator by index or public key: status, balance, effective balance, slashed flag and activation/exit epochs with wall-clock times. ETH amounts are the meaningful queue metric — a single post-Pectra validator can hold up to 2048 ETH — with counts given alongside. Distinct from beaconchain-api (consensus finality), the Solana validator feeds and the liquid-staking protocol feeds. Live, keyless, nothing stored beyond a short cache.

api.oanor.com/ethstakingqueue-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

Who secures Solana and how decentralised it is, read straight from a public Solana RPC node. Solana is proof-of-stake: validators vote with the SOL delegated to them, and the distribution of that stake decides both rewards and security. The validators endpoint ranks validators by activated stake, with each one's stake in SOL, its share of total stake, its commission and whether it is delinquent (currently failing to vote). The staking endpoint returns the staking economics — total active stake, the circulating and total SOL supply, the percentage of supply that is staked, the current inflation rate broken into its total, validator and foundation components, and the current epoch with its progress. The centralization endpoint computes the stake-centralisation metrics — the Nakamoto coefficient (the fewest validators that together control more than one third of the stake, the amount that could halt the chain under Byzantine-fault-tolerant consensus), the top-10 and top-20 stake share, and the Herfindahl concentration index. This is the Solana validator, staking and decentralisation data-cut, distinct from the Solana on-chain account/transaction API and the other staking and exchange APIs in the catalogue. Live from a public RPC, no key on the upstream, nothing stored.

api.oanor.com/solanavalidators-api