Skip to content
Network economics nothing is priced yet

A request records a max_fee that the programs never charge. ADR 0005 names the roles a fee would be split across and stops there. This page says what is true today and what is still a decision.

What the fee model rests on today

  • max_fee
  • ADR 0005
  • Apache-2.0
  • Coming soon

A tick marks something the programs do today. A dash marks something a later milestone has to decide.

Developers

Open a request, receive a verified output. No lamports move for the job itself.

No feecharged by the programs

Start building
  • max_fee is stored on the request and never charged
  • The proof is verified on-chain before the output is written
  • The callback receives the output and no accounts
  • You pay the Solana rent for the request account
  • A fee charged when a request is fulfilled
  • A quote for that fee before the request is opened
  • Priority between competing requests

Node operators

Stake, heartbeat, fulfil. Fulfilment pays nothing, because nothing is collected.

Coming soonno reward is paid

Node operation
  • Stake locks lamports in the node account
  • A node turns active at the configured minimum stake
  • The registry authority sets the heartbeat window
  • Fulfilment is first-come among eligible nodes
  • A node share of a request fee
  • Reward accounting and payouts
  • Automatic slashing with an evidence instruction

Protocol and treasury

The roles exist in a decision record. The split between them does not.

Coming soonno basis point is set

Read ADR 0005
  • Four roles named: node, verifier, treasury, security fund
  • Treasury and security-fund authorities stay on separate keys
  • No request transition moves a lamport to the protocol
  • Basis points for each role
  • A treasury account that receives fees
  • A funded security reserve

ADR 0005 is the fee model record. It names four roles a fee would be split across, the node, the verifier, the treasury and a security fund, and it chooses no basis points. Until it does, every cell in the planned column is a decision and not a schedule.

Capability
Today
Planned
Decision record

Requests

Request fee
Todaymax_fee is stored on the request and never charged
PlannedA fee collected when a request is fulfilled
Decision recordADR 0005
Account rent
TodayThe requester pays rent for the request account
PlannedUnchanged; rent is a chain cost, not a protocol fee
Decision recordADR 0002
Cancel and expire
TodayBoth transitions run and move no lamports
PlannedWhatever the fee model says about a refund
Decision recordADR 0001

Nodes

Minimum stake
TodaySet by the registry authority, not a constant in the program
PlannedA minimum chosen against a real Sybil cost
Decision recordADR 0003
Fulfilment reward
TodayNothing is paid for a fulfilment
PlannedA node share of the request fee
Decision recordADR 0005
Selection weight
TodayFirst come among nodes that meet the eligibility predicate
PlannedOpen; there is no weighted lottery
Decision recordADR 0003
Slashing
TodayNo automatic percentage and no evidence instruction
PlannedPenalties tied to recorded misbehaviour
Decision recordNot recorded yet

Protocol

Fee split
TodayRoles are named; no basis point is set
PlannedA share for each of the four roles
Decision recordADR 0005
Treasury balance
TodayNo lamports reach a treasury account
PlannedCollection and distribution
Decision recordADR 0005
Upgrade authority
TodayNo program is deployed, so nothing is upgradeable
PlannedMultisig upgrades before any deployment
Decision recordADR 0007

The programs charge no fee. max_fee is stored on the request and never collected. The requester pays Solana rent for the request account, which is a chain cost and not a protocol price.