Staking
OPEN secures the coordination layer: every protocol role is bonded. Stake for your role — merchant, node operator, arbitrator, or one of the four service-provider roles. Bonds are enforced by the real openfiat-staking program on Solana devnet.
Stake by role
Connect a wallet to see what you have staked for each role.
Merchant bond
Not startedRequired to publish advertisements. OFS-4100 §4 scales the requirement with the position taken; the program enforces the floor.
Minimum
…
You staked
—
Unbonding
…
Arbitrator bond
Not startedEligibility for dispute seats. Seats are a per-case draw over qualifying stakes, not first-come — so the barrier is the number of independent stakes, which no per-wallet minimum can price.
Minimum
…
You staked
—
Unbonding
…
Notification Provider stake
Not startedRegistration stake for an OFS-1500 notification gateway.
Minimum
…
You staked
—
Unbonding
…
Oracle Provider stake
Not startedRegistration stake for an OFS-1500 price oracle.
Minimum
…
You staked
—
Unbonding
…
Risk Intelligence stake
Not startedRegistration stake for an OFS-1500 risk intelligence service.
Minimum
…
You staked
—
Unbonding
…
Snapshot Provider stake
Not startedRegistration stake for an OFS-1500 snapshot provider.
Minimum
…
You staked
—
Unbonding
…
Minimums and unbonding periods are read from the deployed StakingConfig account, one of each per role — they are governance-updatable, so neither is a constant in this app. A dash means the account could not be read; it never means zero.
Unstaking is request_unstake, then withdraw_unstaked once that role's cooldown elapses — the periods are in the table above, one per role. Rewards accrue as pending_rewards and are claimable via claim_rewards — not yet wired to this page's UI, and the schedule that fills that field is an off-chain cranker's, published nowhere this app can read.