Network

Staking & Rewards

Staking is Reaver GPU's economic security layer. Operators stake to back the honesty of their nodes, delegators stake to earn a share of network fees, and misbehavior is punished by slashing.

Why staking exists

In a permissionless compute market, a renter needs assurance that a node will actually run the job and report usage truthfully. Reaver GPU solves this with skin in the game: every active node has stake bonded against it. Complete work honestly and you earn; cheat or go dark mid-job and a portion of that stake is slashed.

Operator stake

To accept paid work, a node must bond a minimum stake. The bond scales with the GPU class — higher-value hardware handles higher-value jobs and therefore posts a larger bond.

Class	Minimum bond	Max concurrent job value
rtx4090	500 GNET	10× bond
a100	2,000 GNET	10× bond
h100	5,000 GNET	10× bond

Delegating to nodes

You don't need hardware to participate. Delegators stake the GNET token to a node they trust and share in that node's reward stream proportional to their stake. This deepens a node's bond, lets it take larger jobs, and aligns delegators with reliable operators.

bash

reaver stake delegate \
  --node node_8fK2...aQ --amount 1000

# view your positions and pending rewards
reaver stake positions

Reward calculation

Rewards come from protocol fees taken on every settled job, plus a network emission that decays over time. For a given epoch, a participant's reward is:

text

reward = (your_stake / node_total_stake)
       × node_fee_share
       × node_uptime_factor

Two factors matter most:

Node fee share — the fees that node earned this epoch from completed jobs. More work means more reward.
Uptime factor — a multiplier between 0 and 1 from the node's reliability. A node that drops jobs dilutes everyone delegated to it.

Pick nodes carefully. Delegation rewards are only as strong as the operator. Inspect a node's reputation and historical uptime before bonding to it.

Slashing

Stake is at risk for provable faults. Slashing is graduated — minor faults cost a small fraction, severe or repeated faults cost more.

Fault	Penalty
Job abandoned mid-run	2% of bond
Falsified usage receipt	30% of bond
Repeated downtime in epoch	Reward forfeiture

Slashed stake is split between the affected renter (as compensation) and a community treasury. Both operator and delegated stake share the penalty proportionally, which is why delegators are incentivized to back honest nodes.

On-chain settlement

All staking actions — bonding, delegating, reward claims, and slashing — are Solana program instructions. Stake accounts are PDAs owned by the staking program, so balances and penalties are fully auditable on-chain. Reward claims and unbonding are processed at epoch boundaries; unbonding has a short cooldown to prevent operators from exiting right before a slashable fault is detected.

bash

reaver stake claim          # claim accrued rewards
reaver stake unbond --amount 500   # begins cooldown

For the program-level view of how settlement and stake interact, continue to Architecture.