NexFlow › Stake

Stake with validators you can verify

This page is our validator desk — every identity below is a real on-chain address with a public explorer link, an honest status label, and no promised yield. The instruction is deliberately backwards from most staking pages: verify us on-chain first; trust this copy last.

Validator desk · updated September 2026 · not financial advice

Staking pages usually work like marketing: a big APY number, a green "live" badge, and a delegate button. Ours works like a filing cabinet. Every validator or operator we run is listed with its real on-chain identifier — an entity address, a vote account, an operator id — and the explorer URL where a stranger can confirm the record without believing a word we wrote. If a validator is registered but not earning yet, the label says so. If a chain is a testnet where the token is worthless, the label says that too.

The live, continuously-probed version of this desk is /validators/ — it reads each network's public API at render time and reports what the chain actually says, including the failure states. This page is the static companion: what each registration is, what delegation to it would mean, and how to check every claim yourself.

The desk at a glance

Read the status column literally: "queued" and "pending" mean the registration is real but the validator is not producing rewards — for us or for you. Where a row says "not yet," that is the honest answer, not a teaser.

The validators, on the record

What "live", "queued" and "filed" actually mean

Validator marketing collapses three very different states into one green badge. We keep them separate because they pay differently:

Live means the validator is in the active set producing work — blocks, votes, signatures — this epoch. Only that state earns. Queued means the registration exists on-chain but the validator is not in the active set: a Solana vote account waiting for admission, an SSV operator with zero shares, an Oasis entity below committee rank. Queued registrations are real — you can verify them — but they pay nothing until the network admits them. Filed means the paperwork is in a program's queue — SFDP, a foundation delegation window, an operator intake — and the timeline belongs to them.

The reason this matters to a delegator: a queued validator converts your delegation into voting weight that earns zero until activation. That is not a reason not to delegate — early delegations are exactly what moves an entity up the rank list on Oasis — but you should know which state you are buying into.

What delegation pays — and what we refuse to promise

Staking yield is a network property, not a sales feature. Rewards come from issuance (the chain minting new supply to stakers), transaction fees, and in some ecosystems MEV — split with the validator by its commission. Three consequences worth pricing in before you delegate to anyone:

The headline number is nominal, not real. A chain paying 8% while inflating supply at 7% is paying about 1% in purchasing-power terms — and that is before commission. The honest comparison is always nominal rate minus inflation minus commission.

Network base rates are public. Solana's issuance follows its documented inflation schedule (disinflation toward a long-term floor, per the Solana docs); Oasis pays per-epoch rewards on the schedule in the Oasis Protocol documentation; Ethereum consensus issuance runs in the low single digits on public beacon-chain data. Those are network-level figures — what a specific validator pays is the base rate times its uptime minus its commission, and the only honest source for that is the validator's own record on the explorer.

Where a number would be invented, we link instead. This page carries no APY column on purpose. If a validator becomes worth delegating to, its real reward rate will be readable on the same explorers linked above — computed from what it actually produced, not what a landing page claims.

How delegation works (and what it never involves)

Delegation is a protocol operation, not a transfer. On Oasis, you delegate ROSE from your own wallet to an entity address — the coins never leave your custody; the entity gains escrow weight. On Solana, a stake account delegates to a vote account — again, your keys, your coins. On Babylon, BTC staking positions reference a finality provider by its pubkey. In every case the mechanic is the same: you keep custody; the validator borrows your weight. Any flow that asks you to send tokens to an operator's address is not staking — it is a deposit, and on this page it does not exist.

Before delegating anywhere, run the asset itself through the same skepticism you would apply to a contract: /check-token reads a token's on-chain risk surface, and our guide to liquid staking token risks covers the receipt-token variant of this decision.

The risks nobody's marketing removes

Slashing is real where the protocol enforces it. Oasis slashes on double-signing; Cosmos-family chains slash on double-sign and sustained downtime; Ethereum slashes for equivocation with correlation penalties. Solana does not auto-slash today — faults cost rewards rather than principal, though protocol-level slashing proposals exist. We operate the way a validator should to avoid it — separate keys, monitored infra — but the honest sentence is that slashing is a delegator-inherited risk on the chains that have it.

Lockups price you out of exits. Unbonding is real time: roughly 14 days on Oasis, ~2-3-day epoch boundaries on Solana, an exit queue on Ethereum. During unbonding you hold the price risk with no yield and no exit. Size accordingly.

And the boring one: performance. A validator that misses slots pays less — that is the entire risk most delegators actually experience. It is also the one you can audit: every identity above links to the explorer where missed blocks are public record. Ours included — that is the point of this page.

Frequently asked