A liquidation rebate for perp traders

Get liquidated.
Get reloaded.

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.

Token
Reload pool
—
USDG held by the pool
Paid to lockers
—
across all epochs
Coverage ratio
—
pool ÷ value locked
This epoch's budget
—
half of the opening balance
On-chain figures, refreshed every ten minutes.Payout history →

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 →
01

How a reload happens

Five events, in order. Two of them are yours; the rest are the pool's.

  1. Buy Pons

    $RELOAD launches on the Pons bonding curve, quoted in USDG. Creator fees are the only thing the dev earns, and they are split on-chain: 60% to the reload pool, 30% to buyback and burn, 10% to the survivor jackpot.

  2. Lock 7 · 30 · 90 days

    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.

  3. Declare and link on-chain

    Every perp account you control goes into a declaration. EVM-keyed accounts sign for themselves; the rest are confirmed by bonded attesters. An account becomes claimable seven days after it is linked.

  4. Get rekt exchange liquidation

    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.

  5. Get paid USDG, vested

    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.

02

The math

Two dimensions are stamped on each lock. Three caps decide every payout.

Dollar tier at lock → cap, m
TierValue lockedCap
Gold≥ $5,00035% of S
Silver≥ $1,00025% of S
Bronze≥ $25015% of S
Below Bronze< $250no cap · votes only
Lock duration → rate on loss, r
LockRateVote weight
90 days35% of loss2.5×
30 days20% of loss1.5×
7 days10% of loss1.0×
reload = min( hedge-adjusted loss × r , S × m , your locked tokens ÷ all locked tokens × epoch budget )
loss × rS × mshare × budget $1,400$1,050 ← paid$2,000 Example: $4,000 loss, 35% rate, $3,000 Gold lock, 40% of locked supply in a $5,000-budget epoch.

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.

Entry marking

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.

Hedge adjustment

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.

Epoch budget

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.

03

Why it cannot be farmed

Every rule here is enforced on-chain or by bonded attesters, and tested against the obvious attacks.

  1. 01

    Seven-day lead

    Locks and links must be at least seven days old before the liquidation. Coverage cannot be bought for a trade already going wrong.

  2. 02

    Equity-collapse test

    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.

  3. 03

    Sub-1× dollar caps

    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.

  4. 04

    Share-of-stake cap

    Your slice of the weekly budget is your share of locked tokens. Ten wallets holding a tenth each receive exactly what one wallet would.

  5. 05

    TWAP guard

    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.

  6. 06

    Lifetime throttle

    Once cumulative reloads exceed cumulative value locked, the wallet drops to the Bronze cap and the 7-day rate until it locks more.

  7. 07

    Cross-venue hedge scan

    Every supported venue, every wallet joined to yours by funding trails. Opposing positions reduce the payout; large ones remove it.

  8. 08

    Disclosure and strikes

    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.

04

Token

Nothing reserved, nothing to take. The split below is read live and can only move inside its bounds.

Dev allocationThe dev holds zero tokens and zero votes. Creator fees are the only income.0
PresaleFair launch on the Pons curve. No insiders, no allocations.0
Token contractMinted by Pons. No tax, reflections, blacklist or supply changes. Every mechanic lives in a separate contract.Untouched
Withdraw, rescue, sweepNot for the dev, not for the DAO. Pool funds leave only as reloads.None
Creator fee split · live
Reload poolbound: never below 50%60%
Buyback and burnmarket-buys RELOAD and sends it to the dead address30%
Survivor jackpotweekly draw among lockers with no reload that epoch10%
05

Figures

Read from the contracts by the indexer. If the feed is down, this section says so rather than showing stale numbers.

Pool balance—
Coverage ratiopool ÷ Σ value locked—
Epoch budget—
Pro-rata factor—
Reloads paid—
Burned—
Jackpot pot—
Linked accounts—
Locked by tier
    Last reloads
      06

      Governance

      Lock equals vote. Only locked positions vote, weighted by duration, effective seven days after locking. Unlocked tokens and the dev have zero votes.

      Total voting power—
      Guardian expires inThe dev multisig can only cancel a queued proposal. It expires 180 days after deploy and cannot be extended.—
      Proposals
      • loading…

      The standard track decides parameters within their bounds, the attester set, 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.

      07

      Market

      08

      Venues

      Where liquidations count, and how each venue is scanned.

      Scanned automatically · EVM-keyed

      Every wallet in your cluster is scanned on these venues whether you disclosed it or not.

        Disclosure only · non-EVM keys

        Scanned only for accounts you declared. An undeclared account found later is a flag.

          required  venues must be in every claim's scan. Marking a venue required takes effect 14 days after the vote executes.

          09

          Roadmap

          I

          Launch

          Pons curve, staking, links and attesters live. The pool begins filling from fees.

          II

          First reloads

          The first epoch settles. Evidence records are public; figures and coverage ratio go live.

          III

          Attester decentralization

          The DAO adds bonded attesters up to nine, raises the threshold and publishes the adapter guide.

          IV

          HyperEVM verifier

          Verification sits behind an interface: swap the attester set for native on-chain reads where they exist.

          10

          Questions

          Is this insurance?

          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.

          What if the pool is empty?

          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.

          What happens to my tier if the price drops?

          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.

          Who runs the attester?

          A set of bonded keys registered by the DAO: at most nine, each with a bond of at least 1,000 USDG, with a signing threshold of at least half. They scan venues, compute hedges and sign claims. Provably false attestations are slashed by vote, and slashed bonds go to the pool.

          What if I am wrongly flagged?

          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.

          What about hedges on a centralized exchange?

          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.

          Who controls the parameters?

          The DAO, only within hard-coded bounds, and each parameter at most once every 14 days. Changes apply only to positions created afterwards.

          Can the dev take the funds?

          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.