EarningPonsShare (EPS)

Version 1.0 · September 2026

On this page9 sections
  1. Summary
  2. Fee flow
  3. Payout schedule
  4. Weight and eligibility
  5. Verification and veto
  6. Contract guarantees
  7. Portfolio and prize pool
  8. Risks
  9. Contract addresses

Summary

EarningPonsShare (EPS) is a token on Pons, a launchpad on Robinhood Chain. Part of the fee on every EPS trade buys PONS, which is paid out to EPS holders six times a day.

EPS is an independent project, not affiliated with Pons or Robinhood.

Fee flow

Each EPS trade pays a 4% fee.

Fee Rate Destination
Pons base fee 1% 0.3% to Pons, 0.7% to the EPS payout contract
Creator tax 3% all of it to the EPS payout contract
Total 4% 3.7% of volume reaches the payout contract

The payout contract receives its share as ETH and splits every wei that arrives:

Bucket Ratio Share of volume Leaves as
Holders 20/37 2.0% PONS, paid to EPS holders
Treasury 17/37 1.7% ETH, sent to the treasury wallet

Fees collect on the Pons side until harvest() pulls them in, and payTreasury() forwards the treasury bucket. Both functions are open to any caller. The keeper, an off-chain service operated by the team, spends the holder bucket on PONS through the PONS/WETH pool as it fills.

Payout schedule

Rounds last 4 hours and close at 00:00, 04:00, 08:00, 12:00, 16:00 and 20:00 UTC. Round r covers timestamps from (r - 1) * 14400 up to, but not including, r * 14400.

A few minutes after a round closes, the keeper computes its payout list and commits it on chain. The list becomes payable 30 minutes after the commit.

If rounds pile up because the keeper fell behind, it processes them in order and splits the available PONS evenly across them.

Weight and eligibility

A wallet's weight in a round is the lowest EPS balance it held at any moment inside that round.

  • EPS bought during a round does not count in that round. It counts from the next round on.
  • Selling or sending away part of a balance cuts the weight to what was left.
  • A wallet whose low point is under 1,000 EPS sits that round out.

The pot for a round is all PONS held by the payout contract that is not reserved for a committed round or owed to a wallet. It is split pro-rata to weight. Rounding dust stays behind and joins the next pot.

Shares smaller than 0.05 PONS are recorded as owed and added to later shares until the total reaches 0.05 PONS. A wallet that is owed PONS but has no weight in a round receives everything it is owed with that round, however small.

Never paid

  • Pons contracts that hold EPS for others or run the launch: the launch curve, the Uniswap v4 PoolManager, the Pons hook, fee escrow, buyback vault, factory, locker and the executor that opens the pool.
  • The EPS token contract and the payout contract.
  • The zero address and 0x…dEaD.
  • The launch wallet, every wallet the launch declared exempt from the Pons snipe tax, and the team wallet.
  • Third-party DEX pools and vaults. Any other contract, such as a smart wallet, is paid unless it answers token0(), asset() or getReserves().

Verification and veto

Weights are computed off chain from public EPS Transfer events, so anyone can redo the math.

For every round the keeper publishes a raw file, rounds/<id>.core.json, with the block window, the excluded addresses, every weight, every payout and the batch hashes. Its keccak256 is the listHash emitted in RoundCommitted, and the website links the file from each round.

Payouts go out in batches of up to 250 wallets. For each batch the contract stores keccak256(abi.encode(treasury, round, batch, recipients, amounts)). Once the delay has passed, any address may call distribute with a batch. The call reverts unless the recipients and amounts hash to the stored value, and no batch pays twice.

Until a round is fully paid, the owner can call vetoRound. Its unpaid PONS goes back to the free balance, and the keeper adds each wallet's unpaid amount to what it is owed and carries it into the next round.

The contract cannot check that a list follows the weight rule. The public file, the delay and the veto cover that gap. A stolen keeper key could commit a list of its own for up to all free PONS, once per closed round. That commit would sit on chain for the whole delay before any batch could pay, and the keeper flags any commit it did not make.

Contract guarantees

These hold no matter who controls the owner or keeper key.

  • Holder ETH leaves only as PONS, bought on the PONS/WETH pool through the swap router listed below, for no less than the pool's 15-minute time-weighted price minus 5%. The keeper supplies an amount and a minimum output, never a route or calldata.
  • PONS leaves only through a committed batch after its delay. The owner's rescueToken refuses PONS and EPS.
  • A commit cannot reserve more PONS than is free, round ids only move forward, and a round cannot be committed before it closes.
  • The 20/37 split, the treasury wallet address, the pool, the router, the payout delay and the round length are immutable.
  • The payout contract binds to one launch, once, and only if that launch already pays it, trades against native ETH, carries a 3% creator tax and has buyback turned off.

Timelocks

  • Replacing the keeper, or sending future creator fees to a different recipient, requires a public 3-day notice. After the notice the change must be executed within 3 days or it lapses. The fee move harvests everything claimable first.
  • The owner can pause the keeper at once. That stops buys and commits; committed rounds can still be paid or vetoed.
  • Ownership moves in two steps, a proposal and an acceptance, with no notice period.

Portfolio and prize pool

The treasury wallet holds a portfolio of tokens, shown live on the website. The portfolio is set aside as a prize pool for EPS holders. When and how it is shared is announced on the official X account, @earningpons. This wallet is separate from the payout contract, and none of the contract rules above govern it.

Risks

  • Payouts come from trading fees. Less volume means less PONS, and when trading stops, payouts end once the PONS on hand is paid out.
  • PONS can drop in price after it is paid.
  • PONS buys wait whenever a swap would return less than the floor under Contract guarantees, so a round's pot can come out smaller.
  • Bugs in the payout contract, the Pons contracts or the PONS/WETH pool could lose funds.
  • If the keeper stops, rounds wait. If its list is wrong, only public checking and the owner's veto stand in the way.
  • Whoever holds the owner key can hold payouts back at once by vetoing rounds or pausing the keeper. After the notice under Timelocks, it can also install a new keeper or send future fees elsewhere.
  • Whoever owns Pons can move EPS creator fees to a new recipient, effective after a delay set by Pons. If that happens, fees stop reaching the payout contract. The keeper raises an alert while such a move is pending.
  • EPS can lose all of its value.

Contract addresses

Robinhood Chain, chain id 4663.

Contract Address
EPS token announced at launch
Payout contract (EpsTreasury) announced at launch
Treasury wallet (portfolio) 0x95e742D24469447B7fD103b8cD0549A52153B206
PONS token 0x39dBED3a2bd333467115dE45665cC57F813C4571
PONS/WETH pool 0xEd50bDeeA8aDC232f159486192a4157281D722ff
Swap router 0xCaf681a66D020601342297493863E78C959E5cb2