Lock $RELOAD and link the perp accounts you trade from. If an exchange force-liquidates one of them, a USDG reload is paid from a pool funded by creator fees. Rationed to a weekly budget, capped by what you locked, governed by lockers. 1
1 Reloads are paid from a shared USDG pool funded by trading fees. This is a rebate, not insurance. Nothing is guaranteed; if the pool is thin, payouts are scaled down or zero.
Lock at least $250 of $RELOAD for 7, 30 or 90 days, then link your accounts. There is nothing to claim until an exchange liquidates you, and nothing to do before then.
Already locked? Link an account →Five events, in order. Two of them are yours; the rest are the pool's.
$RELOAD launches on the Pons bonding curve, quoted in USDG. Creator fees are the only money the protocol receives. After the first 1,000 USDG of creator fees, which repays the launch costs and goes to the dev, the dev takes none of them. They are split on-chain: 60% to the reload pool, 30% to buyback and burn, 10% to the survivor jackpot.
The dollar value of the lock is marked once, from a 30-minute TWAP, and never recomputed. Longer locks earn a higher rate on loss and more votes.
Every perp account you control goes into a declaration. Exchanges whose accounts use Ethereum-style keys sign for themselves. Exchanges whose accounts cannot yet prove control on-chain are off at launch. An account becomes claimable three days after it is linked. Launch window: link and lock within six hours of the launch and you are covered from the moment that window closes, once, for everyone who made it in.
An exchange force-liquidates a linked account. Not a manual close. The position must have real size and age, account equity must actually collapse, and every required venue is scanned for hedges before anything is signed.
Attesters sign the claim, you submit it within 72 hours, the epoch settles pro-rata to its budget, and USDG vests to your wallet over 72 hours.
Two dimensions are stamped on each lock. Three caps decide every payout.
| Tier | Value locked | Cap |
|---|---|---|
| Gold | ≥ $5,000 | 35% of S |
| Silver | ≥ $1,000 | 25% of S |
| Bronze | ≥ $250 | 15% of S |
| Below Bronze | < $250 | no cap · votes only |
| Lock | Rate | Vote weight |
|---|---|---|
| 90 days | 35% of loss | 2.5× |
| 30 days | 20% of loss | 1.5× |
| 7 days | 10% of loss | 1.0× |
Three caps; you receive the smallest. The first is a fraction of what you actually lost. The second is your tier cap, frozen when you locked. The third is your share of this week's budget, measured in raw tokens, so neither price moves nor splitting across wallets changes it.
S = tokens × the 30-minute TWAP of RELOAD/USDG at lock time. If that TWAP sits more than 20% from the 24-hour TWAP, the lock reverts. S is stored once. Price can go to zero and the tier stands; it never marks up either.
Attesters scan every supported venue and every wallet clustered to yours. If you were hedged for h% of the position, the loss is scaled down by h. At 50% or more the claim is rejected. A hedge opened within an hour after the liquidation rejects it too.
Each 7-day epoch may pay at most half of the pool balance at its start. If accepted claims exceed that, every claim in the epoch scales down pro-rata. The remainder rolls forward and is never paid to that epoch.
Every rule here is enforced on-chain or by bonded attesters, and tested against the obvious attacks.
Locks and links must be at least three days old before the liquidation, so coverage cannot be bought for a trade already going wrong. One exception, once: links and locks in place within six hours of the launch count from the moment that window closes.
Account equity after the liquidation must be at most half of what it was before the position opened. A sub-account inside a large account does not qualify.
The most any claim returns is 35% of the dollars locked. Losing on purpose to collect is net-negative at every tier and every parameter bound.
Your slice of the weekly budget is your share of locked tokens. Ten wallets holding a tenth each receive exactly what one wallet would.
Entry value comes from a 30-minute TWAP checked against the 24-hour TWAP, written only by registered observers. A one-block pump cannot enter it.
Once cumulative reloads exceed cumulative value locked, the wallet drops to the Bronze cap and the 7-day rate until it locks more.
Every supported venue, every wallet joined to yours by funding trails. Opposing positions reduce the payout; large ones remove it.
An undisclosed account found in the 30-day sweep forfeits unvested payouts, bans the wallet for 90 days and records a strike. Two strikes is permanent.
Nothing reserved, nothing to take. The split below is read live and can only move inside its bounds.
Read from the contracts by the indexer. If the feed is down, this section says so rather than showing stale numbers.
Lock equals vote. Only locked positions vote, weighted by duration, effective seven days after locking. Unlocked tokens and the dev have zero votes.
The standard track decides parameters within their bounds, attester rules and penalties, venues, the fee split, pauses and flag reversals. The supermajority track (66.7% for, 15% quorum) can move bound ranges, change governance settings and swap peripheral contracts. No vote can withdraw pool funds, alter the token, block unstaking, or re-mark a position.
No company runs this. A handful of jobs keep it working, and most of them are open to anyone.
Lock $RELOAD, link trading accounts, claim reloads and vote. From $250 locked a wallet is eligible for reloads; every lock votes after seven days and is entered in the jackpot.
Confirm liquidations, scan for hedges and sign claims. Anyone who bonds $RELOAD can be one. A false signature costs half the bond, and an attester cannot sign its own claim.
Anyone can dispute a claim that passed by posting about $250 of $RELOAD with evidence. If lockers uphold it, the challenger earns a fifth of the slashed bonds. If it fails, the $250 is burned.
Supply the randomness for the jackpot. Each posts a sealed secret with a USDG bond ($10 at launch), reveals it after the period and takes the bond back. A draw needs three.
Approved wallets that record the price about every ten minutes. They choose when to record, never what. If they stop, new locks and claims wait; withdrawals do not.
Press the buttons anyone may press: split the fees for a 0.5% bounty, run the buyback, enter lockers in the jackpot and draw it. Usually a bot.
A contract with no owner. It collects the creator's share of Pons' trading fee and sends all of it to the Splitter when anyone presses its button. It has no other destination, and the dev takes no cut. Disclosure: until the first 1,000 USDG of creator fees has repaid the launch costs, the launch wallet collects instead and keeps that amount; then it hands the job to the forwarder, one way, and the pool starts filling from that moment.
One multisig that can cancel a vote before it takes effect. It can do nothing else, and it expires for good 180 days after launch.
The docs cover each job in full: what it costs, what it earns, and what keeps it honest →
Chart embed not configured. Set CONFIG.chartEmbedUrl.
Where liquidations count, and how each venue is scanned.
Every wallet in your cluster is scanned on these venues whether you disclosed it or not.
Off at launch. These accounts are not Ethereum-style keys and cannot yet prove on-chain who controls them.
required venues must be in every claim's scan. Marking a venue required takes effect 14 days after the vote executes.
Pons curve, staking, links and attesters live. The pool begins filling from fees.
The first epoch settles. Evidence records are public; figures and coverage ratio go live.
Anyone bonds $RELOAD and runs an attester. The adapter guide is published and the remaining venue readers are finished.
Verification sits behind an interface: swap the attester set for native on-chain reads where they exist.
No. Reloads are paid from a shared USDG pool funded by trading fees. This is a rebate, not insurance. Nothing is guaranteed; if the pool is thin, payouts are scaled down or zero.
Then the epoch budget is zero and claims pay zero. Each epoch is rationed to half the pool balance at its start, and the remainder rolls forward. The pool can never owe more than it holds.
Nothing. The dollar value S was marked when you locked and is never recomputed, in either direction. Top-ups are new positions marked at their own entry price.
Anyone who bonds $RELOAD and runs the attester software. Nobody is appointed and there is no minimum. Attesters scan venues, compute hedges and sign claims, and a signature only counts for as much as the bond behind it: a claim needs at least two attesters whose bonds, valued conservatively, cover the payout. An attester cannot sign a claim for its own wallet. Provably false attestations are slashed, by public challenge or by vote, and slashed $RELOAD is burned.
Submit further disclosure or evidence to the attester; re-attestation is allowed after 48 hours. The DAO can reverse a flag on the standard track, which restores forfeited vests from the pool and removes the strike.
Attesters cannot see inside a CEX, so undetectable hedges are bounded by construction: a payout is capped at S × m, at most 35% of the dollars locked, and the lifetime throttle drops a wallet to Bronze once it has been reloaded more than it ever locked.
By a draw that never pays to steer. During each period several committers post a sealed secret with a bond; after it ends they reveal, and the winner is picked from all the secrets mixed together, weighted by tokens locked and lock length. One draw pays at most the bond, so holding a secret back to change the result always costs more than it can win. A wallet that took a reload in the period cannot win. More in the paper.
Only from trading. Pons charges 1% on every trade of $RELOAD and keeps 30% of it. The creator's 70% goes to the Splitter contract (after a disclosed first 1,000 USDG that repays the launch costs), which sends 60% to the reload pool, 30% to buyback and burn, and 10% to the jackpot. Followed through with numbers in the paper.
The DAO, only within hard-coded bounds, and each parameter at most once every 14 days. Changes apply only to positions created afterwards.
No. There is no withdraw, rescue or sweep function anywhere, for anyone, including the DAO. The dev holds zero tokens and zero votes; the only dev power is a Guardian cancel that expires 180 days after deploy. The one disclosed exception is the first 1,000 USDG of creator fees, which repays the launch costs: the launch wallet claims it from Pons' escrow before the forwarder takes over, every transfer is visible on-chain, and it never touches the pool.