HostNexFlow › Library › Oasis vs NEAR staking
Oasis vs NEAR staking: a 14-day debond vs four epochs
Two chains that are rarely compared. Oasis holds your stake for two weeks after you leave and slashes hard for one specific crime. NEAR releases it in about two days and never touches principal at all. The rest of the differences are quieter but matter more day to day.
We operate a registered validator entity on Oasis mainnet — live in the active set as of today, per our Oasis page. That means we have read one of these staking systems from the operator side, and the operator side is where the differences a delegator cares about actually come from: how long the chain holds your tokens when you leave, what a validator can lose and pass on to you, and who decides the commission.
Every row below was read on 2026-09-27 and names its source — the chain's own documentation, a live RPC read via our relays, or the Oasis Nexus indexer for our own validator's state. Where a figure is not published in a form we could verify, the cell says so. There is no yield figure on this page and no projection.
The parameter table
| Parameter | Oasis (consensus layer) | NEAR |
|---|---|---|
| Time to get stake back | 336 epochs of debonding, about 14 days at roughly one epoch per hour (Oasis docs, "Delegation" / staking consensus parameters, as of 2026-09-27). | Four epochs after the unstake call in the core staking-pool contract (NUM_EPOCHS_TO_UNLOCK = 4); an epoch is 43,200 blocks, about 12 hours, so roughly two days (NEAR core staking-pool source; EXPERIMENTAL_protocol_config via a public RPC relay, as of 2026-09-27). |
| Validator seats | 120 active consensus validators, selected by stake (Oasis docs, "Validator node" consensus parameters, as of 2026-09-27). | 100 block-producer seats; 405 validators in the current set including chunk-only validators (protocol config num_block_producer_seats and validators RPC, epoch height 4808, as of 2026-09-27). |
| Minimum delegation | 100 ROSE (min_delegation, Oasis staking consensus parameters, as of 2026-09-27). | No protocol minimum for delegators; each staking-pool contract may set its own (NEAR docs, "Staking pool", as of 2026-09-27). |
| Slashing of principal | Yes — double-signing slashes 100 ROSE from the validator's escrow and freezes the node from the validator set permanently (Oasis docs, "Consensus slashing parameters", as of 2026-09-27). Delegators share the slash pro rata because slashing is applied to the escrow pool. | Not active — validators that fall below the kickout thresholds are removed for the next epoch and forfeit that epoch's reward; stake is not burned (NEAR docs, "Validator rewards and slashing", as of 2026-09-27). |
| Downtime handling | Liveness failures lead to the node being frozen out of the set for a period; principal slash for downtime: not published in a form we could verify (Oasis docs, as of 2026-09-27). | Kicked out of the set for the next epoch if produced blocks or chunks fall below 80% of expected (block_producer_kickout_threshold, chunk_producer_kickout_threshold, protocol config via our relay, as of 2026-09-27). |
| Commission | Set by the entity within a published rate schedule; changes are bounded and take effect on a delay (Oasis docs, "Commission schedule", as of 2026-09-27). Our validator's rate reads 0% (Oasis Nexus, as of 2026-09-27). | Set per staking-pool contract as reward_fee_fraction, no protocol floor or ceiling (NEAR core staking-pool source, as of 2026-09-27). |
| Issuance | Fixed per-epoch staking reward schedule set in the genesis document; current annualised percentage: not published in a form we could verify. | Maximum 2.5% of total supply per year (max_inflation_rate = 1/40, protocol config via our relay, as of 2026-09-27); the protocol treasury share is currently zero (protocol_reward_rate = 0/1, same source). |
| Reward handling | Rewards are added to the escrow pool, so a delegation's share value grows; nothing to claim (Oasis docs, "Staking and delegation", as of 2026-09-27). | Rewards accrue to the staking-pool contract each epoch and are re-staked automatically (NEAR core staking-pool source, as of 2026-09-27). |
| Redelegation | None — you must debond (14 days) and then delegate again (Oasis docs, as of 2026-09-27). | None at the protocol level — unstake from one pool, wait four epochs, stake to another (NEAR docs, as of 2026-09-27). |
| Our footprint | Active validator, rank 73, escrow 200,011.89 ROSE (Oasis Nexus indexer, as of 2026-09-27). | None. |
Debonding: two weeks versus two days
Oasis is at the long end of the industry on this. When you undelegate, the tokens enter a debonding pool for 336 epochs, and because an Oasis consensus epoch is about an hour, that is two weeks during which the tokens earn nothing and cannot be moved. The reason is the standard one — a stake that can leave instantly cannot be punished for what it did yesterday — and Oasis chose a window long enough to make that punishment enforceable. There is no redelegation shortcut: switching validators means a full debond and a fresh delegation.
NEAR is short and epoch-based. You call unstake on the pool contract; the tokens stop earning at the next epoch boundary and become withdrawable four epochs after that, roughly two days at 12-hour epochs. NEAR can afford the short window because it does not slash principal at all — there is nothing to hold the tokens for. That is a coherent design, and it is also the reason NEAR's security argument rests on seat competition and kick-outs rather than on a penalty a delegator would feel.
Slashing: one hard rule versus none
Oasis slashes for exactly one thing in the parameters we could read: double-signing. The penalty is a fixed 100 ROSE taken from the entity's escrow and a permanent freeze from the validator set. Because delegations on Oasis are shares of that escrow pool, a slash is spread across every delegator pro rata. One hundred ROSE is small against a validator with two hundred thousand in escrow, but the permanent freeze is the real cost — the validator is finished, and every delegator must debond and wait two weeks to move. Downtime is handled by liveness rules that can freeze a node out temporarily; we could not find a published principal penalty for downtime and have said so in the table rather than guess.
NEAR does not burn stake. The protocol config carries kick-out thresholds — 80% of expected blocks and 80% of expected chunks — and a validator that misses them is dropped for the following epoch and forfeits that epoch's reward. Delegators in that pool lose the reward for the epoch and nothing else. It is a gentler regime, and it means the diligence a NEAR delegator owes is about uptime history and commission rather than about catastrophic risk.
Both chains hold rewards inside the pool. On Oasis your delegation is a share of the entity's escrow; on NEAR it is a balance inside a staking-pool contract. In neither case do rewards arrive in your wallet — the pool grows and your share grows with it. That is convenient, and it also means "how much have I earned" is a question you answer by reading the pool, not your balance.
Seats, commission and who gets a say
Oasis caps the active consensus set at 120 validators, chosen by stake. Entities publish a commission schedule with bounds and a delay on changes, so a validator cannot quietly move from 0% to 100% overnight — a delegator can read the schedule before committing. Our own entity currently reads 0% on Nexus; that is our operating choice today and the schedule mechanism means any change is visible in advance. NEAR has 100 block-producer seats and a wider set of chunk-only validators — 405 in the current epoch when we read it — and commission is a plain fraction in each pool contract with no protocol bound. A NEAR pool owner can change the fee; check the contract, not the marketing page.
NEAR's issuance is bounded in the protocol config at 2.5% of supply per year, and the protocol treasury's cut reads zero in the same config today. Oasis's staking reward follows a per-epoch schedule fixed in the genesis document, which we could not turn into a verifiable current percentage, so the table says "not published" rather than inventing one. Neither figure is a yield. Both get diluted by the same issuance, taxed by commission, and reduced by any downtime.
Who should pick Oasis, who should pick NEAR
Pick Oasis staking if you want a delegation whose validator is disciplined by a real, permanent penalty, whose commission cannot change without notice, and whose active set is small enough to actually read — and you can live with two weeks of dead time whenever you leave or switch. The trade is illiquidity, plain and simple, and a pro-rata share of any slash the entity suffers.
Pick NEAR staking if you want to be able to move between pools in a couple of days, prefer a regime where the worst case is a missed epoch rather than a burned principal, and are comfortable reading a pool contract's fee fraction yourself. The trade is that the chain's discipline of validators is softer, so the burden of picking a reliable operator sits more heavily on you.
On either chain the practical step is the same: read the operator's on-chain record before delegating. Our validator desk reads the live state of every network we run, including the Oasis entity in the table above. If you need raw chain reads for your own diligence, the public RPC lanes cover Oasis.
Frequently asked
How long does it take to unstake ROSE on Oasis?
336 epochs of debonding, about 14 days at roughly one epoch per hour, as of 2026-09-27. The tokens earn nothing during debonding and cannot be moved. There is no redelegation shortcut — switching validators means a full debond and a new delegation.
How long does it take to unstake NEAR?
Four epochs after the unstake call in the core staking-pool contract, about two days at 12-hour epochs (43,200 blocks per epoch as of 2026-09-27). The tokens stop earning at the next epoch boundary and become withdrawable four epochs later.
Can delegated ROSE or NEAR be slashed?
Oasis: yes — double-signing slashes 100 ROSE from the entity's escrow and permanently freezes the validator; delegators share the slash pro rata as of 2026-09-27. NEAR: no — validators that miss the 80% block or chunk production thresholds are kicked out for the next epoch and forfeit that epoch's reward, but stake is not burned.
Is there a minimum amount to delegate on Oasis or NEAR?
Oasis sets a protocol minimum delegation of 100 ROSE as of 2026-09-27. NEAR has no protocol minimum; individual staking-pool contracts may impose their own, so check the pool before sending.
Does NexFlow run a validator on Oasis or NEAR?
Oasis: yes — an active consensus validator, rank 73 with about 200,012 ROSE in escrow and a 0% commission as read from the Oasis Nexus indexer on 2026-09-27. NEAR: no.