HostNexFlow › Library › NEAR staking guide
NEAR staking — how delegation actually works
NEAR is proof-of-stake with a twist most delegators never see: you do not delegate to a validator's address — you stake through a smart-contract pool that owns a lockup. This page is the mechanics and the numbers that are real.
Most proof-of-stake chains make delegation a protocol primitive — you point stake at a validator's registered address. NEAR routes it through a contract instead: a validator deploys a staking-pool contract, delegators call deposit_and_stake, and the pool's own account is what holds the seat in the validator set. The distinction matters because it changes what you check: the contract's fee logic and upgrade permissions are part of your counterparty surface, not just the operator's uptime.
NEAR's consensus is Nightshade — a sharded design where block producers each attest to chunks of a single logical chain rather than separate shard chains. For a delegator the practical takeaway is simpler: validators are picked per epoch (~12 hours), seats are priced by total stake through a threshold ("seat price"), and rewards come from a fixed ~5% annual issuance minus burned fees — historically landing in the 4–5% nominal band, which you should treat as a dated figure (the epoch-level numbers live on NEAR's own explorers).
How delegation differs from "send stake to a validator"
On NEAR you interact with a pool contract: deposit NEAR, call stake, and the pool routes your weight into its validator bid. Unstaking is a two-step call — unstake then withdraw after the lock clears, roughly 4 epochs (~48 hours, per NEAR's docs). The pool keeps a commission in its contract logic; reputable operators publish the rate on-chain where you can read it before staking, not after.
The contract layer is also where liquid staking lives: Meta Pool's stNEAR and similar tokens are issued by pools whose contracts hand you a transferable receipt. That buys liquidity at the price of one more contract layer between you and the validator — a real trade, not a free one.
Slashing and uptime — the honest risk surface
NEAR is gentler than Ethereum on delegators in one specific way: it does not slash routine downtime. A validator that falls below its online threshold simply loses its seat for the epoch — the penalty is foregone rewards, not burned stake. Slashing exists for provable misbehavior (equivocation and invalid state challenges), which makes operator competence the dominant risk axis: an incompetent operator costs you yield; a malicious one costs you principal.
That makes the evaluation checklist boring in the best way — uptime history, commission rate and change history, self-stake, the identity behind the operator. The same checklist we apply to our own fleet at /validators/, where statuses are labeled literally — a queued registration says queued, not "coming soon".
What "running infra on NEAR" actually means
A NEAR full node is moderate infrastructure by validator standards — the node tracks the chain and answers RPC reads without needing a validator seat. That is also the lane public RPC relays ride: a full node answers standard NEAR JSON-RPC (status, block, query, tx) for wallets and low-throughput tools.
The validator lane is a separate bar: a seat needs enough delegated stake to clear the epoch's seat price, which is why credible operators publish their pool terms publicly — curated delegation programs exist precisely to route community delegation toward operators who pass a vetting round.
Where NEAR staking still goes wrong
Most lost-stake stories on NEAR are not protocol failures — they are pool selection failures. A pool whose contract lets the operator raise commission unannounced, a fake "official" pool imitating a known operator's name, or a liquid-staking receipt bought at a premium its redemption math can't support are all investor-side mistakes the protocol never sees. The fixes are equally unglamorous: read the pool contract's fee method before depositing, confirm the pool address from the operator's own channels (not a DM), and if you hold a liquid receipt, know the redemption path before you need it. Explorer history — not marketing — is what settles "does this operator miss epochs".
On the operator side the failure mode is operational, which is exactly why honest operators publish a degraded state instead of hiding it: an offline node is a fact the chain will report either way. Pages that only ever say "live" are the ones to doubt, because a status that cannot go down was never a status at all.
Numbers worth reading literally
Three figures do most of the dishonest work in staking marketing:
Nominal APY. NEAR issues on the order of 5% annually to stakers before fees and commission — but that is token-denominated issuance. If you price your stake in anything else, the real yield is the nominal rate minus whatever NEAR's price does while you're locked through the ~2-day unbond. APY banners quote the first number; your account lives on the second.
Commission. A pool's fee is a fraction of your rewards — published in the contract call, readable before you stake. A "0% fee" pool is either a promotion (temporary by definition) or a business model you should be suspicious of; sustainable commission is how an operator pays for uptime.
Uptime. NEAR kicks out rather than slashes on downtime, so a bad operator's cost shows up as missed epochs in explorer history — seat time per epoch is the number to read, not a green badge.
Frequently asked
How do I stake NEAR?
Through a staking-pool contract: deposit NEAR to the pool's account and call stake. The pool's contract is what sits in the validator set — so check the contract's commission logic and upgrade permissions as well as the operator's uptime before you deposit.
How long does NEAR take to unstake?
Two contract calls — unstake, then withdraw once the lock clears, roughly 4 epochs or about 48 hours per NEAR's protocol parameters. During the unbond window the stake earns nothing and sits locked.
Does NEAR slash delegators?
Not for downtime — a validator that misses its online threshold just loses its seat and the epoch's rewards. Slashing exists for provable misbehavior like equivocation, which makes operator competence the main thing you are actually vetting.
What APY does NEAR staking pay?
The protocol issues roughly 5% annually to stakers before validator commission and burned fees — historically around 4–5% nominal. That is a token-denominated rate: your real yield depends on what NEAR is worth when it arrives, so treat any single APY banner as a dated snapshot.
What is a staking pool on NEAR?
A smart contract a validator deploys that holds delegated stake — delegators deposit to it, its own account bids for the validator seat, and its code carries the commission and upgrade rules. It is your counterparty layer: read it like one.