Search results for staking on this network are full of guesses. Some pages mention returns as if they were already live. Others mix up testnet activity with mainnet plans.
The truth is simpler. The team has published a clear staking model, but it is a plan for the future and not a product that runs today. This Orbinum staking guide goes through that plan step by step, using only the official documentation, and marks clearly what is confirmed and what is still open.
Key Takeaways
Staking is planned for mainnet. The current testnet uses a permissioned validator set with no bond, no nomination and no slashing.
A pool of 300,000,000 ORB, which is 30% of the total supply, is reserved for staking rewards and will be released block by block over roughly ten years.
Nominators earn a share of rewards, but they also share the penalty if a validator they back is slashed.
Orbinum is a privacy-focused blockchain. It combines zero-knowledge cryptography with full Ethereum compatibility. The chain is built on Substrate's FRAME framework with Frontier integration.
The project tries to solve a familiar problem. Public blockchains expose every transaction detail permanently, so activity can be traced and linked over time. Orbinum builds privacy into the protocol itself, using cryptographic commitments and zero-knowledge proofs.
In practice, this works through a shielded pool. Value sits inside notes, which are hidden commitments, and observers cannot tell who owns what. Notes of every asset share the same pool, so a private transfer blends into a much larger crowd.
Privacy does not come at the cost of familiarity. Solidity contracts deploy without changes, and tools such as MetaMask, Hardhat and Remix work normally. The native asset is the ORB token, with a fixed supply of 1,000,000,000.
Two components keep the chain running. Aura produces a block every six seconds, and GRANDPA finalizes blocks in about twelve seconds. Both matter later, because validators need keys for each of them. For a deeper look at the privacy side, the private transactions guide on this site covers it in detail.
Source: official website
Staking means locking tokens to help a blockchain stay secure and honest. People who take part earn rewards for their work, and those who misbehave can lose part of their locked tokens.
Orbinum network staking is the planned way ORB holders will help secure the network after mainnet launch. The network will use Nominated Proof-of-Stake, or NPoS. In this model, validators run nodes and produce blocks, while ORB holders can back the validators they trust. Both sides share the rewards.
The model also lets holders take part without running any hardware, so security does not depend on how many people can operate infrastructure. Any ORB holder can contribute.
One point needs to be clear from the start. Orbinum staking is not live today. The current testnet works with a permissioned validator set, and staking is the target model for mainnet. Consensus will keep running on Aura for block production and GRANDPA for finality.
Source: official staking documentation
The process follows a simple chain of roles. Validators put their own ORB at risk and run the network. Nominators add their stake behind the validators they trust. The network pays everyone from a shared reward pool.
ORB holders ── nominate ──▶ Validators ── produce blocks ──▶ Secured network
▲ │
└──── rewards shared by era points + total stake ◀───────────┘
Here is how the two roles compare:
Validators | Nominators | |
Main job | Run full nodes, produce blocks, validate transactions | Back validators they trust |
Stake | Bond their own ORB, which is at risk | Nominate using their ORB |
Earn | Block rewards plus a share of fees | A proportional share of the validator's rewards |
Main risk | Slashing | Slashing, if the backed validator misbehaves |
Before a validator can author blocks, it must register both Aura and GRANDPA session keys.
Rewards are paid per era, which is a fixed period of network activity. Two factors decide each payout.
Era points come from producing blocks and performing validation duties. Total stake is the validator's own bond plus every nomination behind it. A validator's reward therefore depends on both performance and backing, and each nominator receives a proportional share.
The reward system has two income sources: block emission and transaction fees.
Thirty percent of supply, which is 300,000,000 ORB, funds staking rewards. This pool is not pre-allocated. Tokens are emitted per block as the network is secured, and they enter circulation gradually over roughly ten years.
Readers who want the full supply picture can check the Orbinum tokenomics breakdown, since this emission directly affects circulating supply over time.
Fees will be split between validators and the Treasury. The split percentage has not been set yet.
Today, a user declares the fee inside the proof, and the runtime enforces a minimum called MinRelayFee. Its default is 0.001 ORB, set as an anti-spam floor. Sudo can raise it, up to a hard cap of 1 ORB. Whether mainnet keeps a fixed fee or a floor with user discretion is still undecided.
The documentation openly says that it is unclear whether fee revenue can secure the network once the staking pool is used up. No privacy network has shown fee revenue at that level yet, and the team states it does not assume Orbinum will be the first. That kind of candor is uncommon and worth noting.
No APY has been published. This is not a gap in research, because the numbers do not exist yet.
The documentation lists what is still undefined:
The per-era issuance schedule for the 300M pool
The decay curve
The target staking ratio
The minimum validator self-stake
The validator and Treasury fee split
How emission relates to fee revenue
The team says it is working through these with external economic review before mainnet. Until then, any specific percentage is speculation.
Under NPoS, misbehavior costs stake. Three kinds of behavior are planned to trigger penalties:
Equivocation, meaning signing duplicate blocks or conflicting finality votes
Invalid block production, meaning attempting an invalid state transition
Extended downtime, meaning staying offline long enough to harm network liveness
Slashed funds are taken from the validator and also from the nominators backing it.
This shared exposure is deliberate. It gives nominators a direct reason to research their choice of validator, instead of chasing the highest advertised return.
Today, on the testnet
Right now, ORB cannot be staked. The Orbinum testnet runs a permissioned validator set. Operators are evaluated off-chain, and sudo adds them directly. There is no on-chain candidacy, no bond, no nomination and no slashing.
Anyone interested in running a node can start with the Running a Node and Becoming a Validator pages in the official docs. The Public RPC Node page covers day-to-day maintenance.
Once the Orbinum mainnet launches with NPoS, the steps are expected to look like this:
Validators bond their own ORB and register Aura and GRANDPA session keys.
A minimum self-stake will replace governance approval as the entry gate.
ORB holders who do not run nodes can nominate validators and share the rewards.
The amount of minimum self-stake has not been announced yet.
Once the system is live, a few things happen continuously in the background:
Validators produce blocks and earn era points for their work.
At the end of each era, rewards are shared based on era points and total stake.
Fees are split between validators and the Treasury.
Misbehavior triggers slashing for the validator and its nominators.
Each of these loops reinforces the others. Good performance earns more, and poor performance costs real stake.
ORB holders can earn without running any hardware.
Rewards come from two sources, block emission and fees.
Both validators and nominators have stake at risk, so everyone has a reason to act honestly.
Emission is gradual over about ten years, not released all at once.
The validator set is designed to open up over time instead of staying closed.
The permissioned set is a launch measure, not the final design. The Orbinum roadmap includes a staged opening so each step can be verified before the next one begins.
Stage | Who can validate | Nomination | Slashing |
Today | Sudo adds each operator after off-chain review | No | No |
Next | Governance approves, and stake decides the active set | Yes | Yes |
Then | Any candidate meeting objective requirements | Yes | Yes |
Target | Fully open NPoS, where stake alone decides | Yes | Yes |
Source: official ORB documentation
Feature | Testnet (today) | Mainnet (planned) |
Validator entry | Sudo approval | Minimum self-stake |
Bonding | None | Required |
Nomination | Not available | Available |
Slashing | None | Active |
Rewards | Not applicable | 300M ORB pool plus fee share |
The staking design is thoughtful, and the team is open about what is unfinished. The reward pool is large, the penalties are clear, and the road to open validation is staged.
Until the missing parameters are published, the safest approach is to follow official channels and treat any early staking offer from other sources with caution.
Disclaimer: This article is for information only and is not financial advice. All staking details are planned and may change before mainnet.