RELOADperps Docs
SiteApp
How it stays honest·Chapter 12

Attesters

A blockchain cannot see what happened on an exchange. Attesters are the people who look. They run software that watches linked accounts, confirms a liquidation, hunts for hedges, and signs a statement of what it found. A claim cannot pass without their signatures.

Anyone can be one

Nobody is appointed and nobody is voted in. You become an attester by bonding $RELOAD in the verifier contract and running the attester software. There is no minimum bond. A bond is a separate deposit from a lock: it earns no votes and no rebate coverage, and a lock can never be taken as a penalty.

A signature counts for what stands behind it

  • Your bond is valued in dollars at the lower of the 30-minute and 24-hour average price.
  • Half of that value counts. Lockers can set this anywhere from 20% to 100%.
  • One attester counts for at most $50,000, however large the bond.
  • A new bond starts at zero and grows to full weight over 7 days. Tokens added later start cold as well.

For a claim to pass, at least two attesters must sign, and what their bonds count for has to add up to at least what the pool would pay for the claim: the loss after the three caps, never more than the loss. So to push through a false claim that would pay $750, the signers must have at least $750 of counted bond at risk between them, and a successful challenge takes at least that much from them.

What happens to a false signature

  • Anyone can challenge a claim that passed, by posting about $250 of $RELOAD and their evidence.
  • Lockers vote on it. If the challenge holds, every attester who signed loses half their bond. The challenger gets their own bond back plus a fifth of what was taken. The rest is burned.
  • If the challenge fails, the challenger's bond is burned. That is the price of a frivolous challenge.
  • Lockers can also slash an attester directly when there is evidence.
  • An attester who wants to leave waits 45 days for the bond, so penalties can still reach it. If a claim it signed is under challenge, the bond stays until the DAO has ruled.

Two more guards

  • An attester's signature never counts on a claim for its own wallet.
  • If the price feed is stale, no bond can be valued, so no claim passes until it is fresh again.

Attesters are not paid by the contracts. They bond because they hold the token and want claims to be honest. At launch the dev runs the first attesters; the software and the rules are the same for everyone who joins after.

Where this is headed

The launch set is small on purpose: a few known operators, each running a server and bonding its own tokens, while the software proves itself in public. The plan after launch is to grow the attester set the way proof-of-stake validator sets grow, into the shape Hyperliquid's has today: a few dozen operators and many thousands of people bonded behind them. That takes a second version of the verifier, and every step of it is a lockers' vote:

  • Pay for signers. A slice of each week's budget to the attesters who signed that week's claims, split by the weight behind them, so running a node earns something.
  • Delegation. Bond $RELOAD behind an operator from the app, with one signature and no server. Delegators share the operator's weight, its pay and its penalties.
  • A minimum self-bond for operators, so an operator has its own tokens at risk before it takes anyone else's.
  • Uptime rules. A node that keeps going silent stops counting, so a claim never waits on an operator who went away.
  • Bonds in $RELOAD or USDG. An attester could bond either, or both. USDG would count at face value, since it cannot fall on a crash day; $RELOAD would keep counting at the conservative price with the haircut. Slashed USDG would go to the reload pool, slashed $RELOAD would burn as now. $RELOAD would stay the favoured bond in two ways that cost nothing in safety: it reaches full weight in 7 days where USDG would take 30, and weight backed by it would earn a larger share of signer pay.

Alongside it: a join page in the app for the on-chain part, and a one-line installer that turns a rented server into a node in minutes. The pool reads the verifier's address from the registry on every claim, so the DAO can vote the new verifier in without touching anything else, and until it does, the rules above stand unchanged.