HostNexFlow › Library › Oasis ROSE staking
Staking ROSE on Oasis Network
Oasis staking has its own vocabulary — escrow instead of delegation, entities instead of validators, debonding instead of unbonding — and getting the mechanics right matters because the protocol's protections only work if you know what they are. This is the ROSE-specific how-to: the consensus-layer numbers, the commission bound schedule, and how to verify the entity you delegate to, including ours.
Consensus ROSE vs ParaTime ROSE — the distinction most guides blur
Oasis is a layered network: a consensus layer (a Tendermint-family BFT chain where ROSE lives natively and staking happens) and a ParaTime layer — parallel execution environments like Sapphire (the confidential EVM) and Emerald (plain EVM). ROSE can be bridged into ParaTimes as an ERC-20-style token for gas and contracts, but staking only exists on the consensus layer. If your ROSE is sitting in Sapphire as an ERC-20, it is not staked — to earn staking rewards it has to be on consensus, in an escrow position. That distinction decides which wallet, which explorer, and which addresses you use.
Escrow, not delegation: what you're actually doing
On Oasis you don't "delegate" in the Cosmos sense — you escrow ROSE to a validator's entity (the staking identity that owns one or more nodes). The escrow is a protocol-level position: your tokens stay in an account bound to your keys, attributed to the entity's stake weight, and subject to a commission the entity declares in its on-chain commission schedule. No tokens move to the validator — the operator never has custody. Committee selection is by stake weight: up to 120 entities form the consensus committee per epoch, with at most one node elected per entity — so a validator's "rank" is a real threshold for whether it earns at all.
The numbers that govern your position
| Parameter | Value | What it means for you |
|---|---|---|
| Min delegation | 100 ROSE | Protocol floor for opening an escrow position (genesis doc parameter) |
| Debonding period | 336 epochs ≈ 14 days | Unbonding wait — no rewards accrue during it, slash risk persists for the last active epoch |
| Consensus committee | ≤120 entities by stake weight | Outside the committee, an entity earns nothing — rank is the threshold that matters |
| Epoch reward gate | ≥75% of blocks signed | A validator below the threshold pays nothing for that epoch — uptime is the whole job |
| Slashing | Double-sign only | Slash of the min stake plus a node freeze; no liveness slashing — downtime costs rewards, not principal |
These are the chain's published genesis parameters, not our marketing numbers — you can read them in the Oasis genesis doc and on any consensus explorer.
The commission bound schedule — the protection that matters
Oasis's most under-rated delegator protection: validators can't just change their commission. An entity declares a commission schedule — a rate now plus bounds (a maximum rate and a maximum change per epoch) — and bound changes require a 336-epoch (~14-day) lead time. In practice: a validator that advertised 5% cannot quietly become 40% overnight; a bound tightening takes about two weeks to take effect, which gives delegators a real window to see the change and leave. When you evaluate an entity, the bound matters more than the current rate — the bound is what your future rate can never exceed. Our staking commission explainer covers why commission structure beats headline rate when comparing operators.
How to delegate, step by step
1. Get ROSE onto the consensus layer. If your ROSE is in Sapphire or on an exchange, move it to a consensus-layer address first — wallet support matters here, so use an Oasis-aware wallet (e.g. ROSE Wallet web/extension) that exposes the staking tab.
2. Pick an entity and verify it on-chain. Open the entity on a consensus explorer — Oasis Nexus or OasisScan — and read: is it in the committee? what's its commission rate and bound? how long has it been registered? Any address a stranger DMs you is guilty until verified.
3. Escrow. From the wallet's staking interface, delegate (escrow) your chosen amount to the entity address — remember the 100 ROSE minimum and leave a little unstaked for fees and future debonds.
4. Track it. Rewards accrue per epoch while the entity is in committee and meeting the 75% signature threshold. Debond when you want out — then expect the ~14-day wait.
The version of this that costs people money: "staking" offered anywhere off the consensus layer — a contract on Sapphire promising ROSE yield, a Telegram bot with a deposit address, a website that wants you to send ROSE to begin earning — is not delegation. Real escrow never asks you to send tokens to the validator. The full pattern is in fake staking pool scams.
Our entity — and how to check it yourself
NexFlow operates a registered Oasis consensus entity: oasis1qq3x3w7n4l6jge6kaw8k20ukakuf5rtqsveh84cy. It is on-chain and accepts delegations now; committee rank is a stake-weight threshold, so whether it is currently in the 120-entity set is a live fact you should verify rather than take from us. The entity's listing, status, and the explorer links are on /networks/oasis/ and the delegation entry point is /stake/. Verify before you delegate — open the entity on Oasis Nexus or OasisScan and confirm the address character-for-character; for Sapphire-side contract work our relay also serves /rpc/oasis-sapphire/.
For the cross-chain discipline — what to check on any validator before bonding anything — how to vet a validator is the companion piece, and how to stake without getting hosed is the flagship version of the general advice this page deliberately doesn't repeat.
Delegate to our ROSE entity
Entity address (verify on the explorer before trusting it):
oasis1qq3x3w7n4l6jge6kaw8k20ukakuf5rtqsveh84cy
Frequently asked
What is the minimum ROSE I can stake on Oasis?
100 ROSE — that is the protocol-level minimum delegation (the min_delegation genesis parameter), not a UI setting. Below it you can't open an escrow position at all. A separate 100 ROSE self-stake minimum applies to validator entities themselves, which is the bond an operator puts up to register.
How long does it take to unstake ROSE?
About 14 days — the debonding interval is 336 epochs (each epoch is roughly an hour). The position stops earning the moment you start debonding, the tokens stay locked for the full window, and they remain slashable for the entity's behavior in the last epoch the escrow was active. There is no faster path inside the protocol — anything offering instant unstaking is a swap, not an unbond.
What happens if my Oasis validator gets slashed?
Oasis slashes for double-signing: the protocol burns the minimum stake (100 ROSE) from the entity and freezes the node — a precaution against continued equivocation. There is no liveness slashing: a validator that simply goes offline loses rewards for the missed epochs (it must sign at least 75% of blocks per epoch to be paid) but doesn't get slashed. Delegator exposure is proportional to escrowed stake, so pick uptime and operations over brand.
What is an Oasis commission schedule and why does it matter?
The commission schedule is the entity's on-chain declaration of its fee: a current rate plus bounds — a maximum rate and a maximum change per epoch — that bound changes require a ~14-day (336-epoch) lead to take effect. It matters because it makes 'raise the fee quietly' impossible: a validator's current rate can only move inside its declared bounds, and bound changes give you two weeks to notice and leave. Read the bound, not just the rate.
Is staking ROSE custodial?
No. Escrow is a consensus-layer protocol position — your ROSE stays in an account your keys control, weighted toward the entity you chose. The validator gets voting power, not custody, and cannot withdraw your tokens. Leaving is an unbond+withdraw you initiate yourself. Any staking flow that asks you to send ROSE to an address owned by the operator is not delegation — it's a deposit, and on Oasis that's not how the protocol works.
Does NexFlow run an Oasis validator?
Yes — our consensus entity oasis1qq3x3w7n4l6jge6kaw8k20ukakuf5rtqsveh84cy is registered on-chain and accepts ROSE delegations today. Committee membership is by stake weight (top ~120 entities), so whether it's actively earning depends on current rank — check the live status on /networks/oasis/ or paste the entity address into Oasis Nexus/OasisScan and verify it yourself before delegating.