coupons

Hold a day.
Get paid at the close.

Every buy starts a coupon. It matures in twenty-four hours, and from then on it draws a share of the Pons creator fee at the end of every day. It does so for as long as you keep holding it.

coupons
The bookloading

      
closed and paid the day you're in waiting

How it works

Three things, and no fourth

01

Buy

Your tokens arrive as a dated parcel. Nothing happens tonight because they haven't been held for a day yet, so they aren't in the split.

02

Wait a day

Twenty-four hours later that parcel matures. The page gives you the exact hour in advance, because the moment is fixed the instant you buy.

03

Paid at the close

Every day ends and the creator fee is split by matured tokens. Keep holding and it happens again tomorrow, and the day after.

In the bag
loading
every token held
Matured
loading
the only thing that gets paid
Still green
loading
bought inside the day
Closes in
loading
loading

Why a day

A day is a low bar and it's meant to be. This isn't trying to punish people who trade. It is trying to stop the fee paying a wallet that was in the token for forty seconds, which on this chain is most of them.

It also means there's no moment to plan around. Buying an hour before the close earns nothing at that close. You can't arrive for the payout; you have to already be here.

Selling takes the newest first

Your bag isn't one number, it's a stack of dated parcels. When you sell, it comes out of the newest parcel first. The parcel you bought this morning goes before the one you've held since launch.

That single choice is the difference between a mechanism you can live with and one that makes you frightened to touch your own position.

The tool

What's in this wallet's book?

Paste any address. Every parcel it holds, which have matured, the hour the rest do, and the stubs from every day it has actually been paid.

The number nobody publishes

loading
of circulating supply survived the night

The share of every token in circulation that has sat in the same wallet for a full day. It can't be staged for a screenshot. A wallet that buys this morning to inflate it contributes nothing until tomorrow, by which time the screenshot is old.

Wallets holding
loading
loading
Flipped inside a day
loading
sold before it matured
Matures after
loading
the only parameter there is
Paying at this close
loading
loading
Dev holdings + claimed fees
loading
native balance plus new scanned fees

The standing

Every wallet, and what it's owed

WalletIn the bagMaturedRipe ParcelsShareThis closeNext matures
reading…

Every wallet holding the token is here, including the ones on zero and why. The same thing as a file: ledger.csv.

What it survives

You can't arrive for the payout

Buying just before the close

Earns nothing at that close because the tokens haven't been held for a day, so they aren't in the split. They join tomorrow's, at an hour this page has already told you.

no snapshot to stand on

Selling straight after one

Works once, for the day you actually held. Buy back and you're green again for a day. There's no penalty and no blacklist. You simply pay the day back.

costs a day, every time

Splitting across wallets

Weight is linear in matured tokens. Two wallets holding half a parcel each weigh what one wallet holding the parcel weighs. Nothing gained, so nothing policed, and nobody honest flagged by a clustering guess.

gains nothing

Shuffling to a second address

Strictly worse than doing nothing. The tokens leave one wallet and arrive green in the other, so the pair earns nothing at the next close where one wallet would have earned in full.

costs, never helps

Airdrops and transfers in

Arrive green and wait a day like everything else. Nothing turns up already matured, which means maturity can't be bought, borrowed or sent.

no shortcut in

Trimming your position

Takes the newest parcels first, so selling a tenth off the top doesn't touch what you've held since launch. Nobody has to choose between managing a position and keeping their coupons.

old parcels are the last to go

Where the money comes from

Pons creator fees. That's the model.

Pons takes 1% of every swap and splits it 70/30 with the creator. The creator's side is claimed in ETH to one address, and the pot is whatever has actually arrived there. It is read off the chain, not asserted here.

Every claim counted is a transaction that was looked up, with its destination checked against the treasury. A claim that doesn't land there isn't counted, and money leaving is never counted. Only money arriving.

It is not money from new buyers. Nothing to stake, nothing to lock, nothing to bond, and no contract that holds your tokens. They stay in your wallet and this reads public transfer logs.

If volume is zero, the pot is zero. Nothing here promises a yield.

Claimed this day
loading
Carried in
loading
left over yesterday
Rolls to tomorrow
loading
nothing is kept
Balances
loading
to the wei
Dev holdings + claimed fees
loading
native balance plus new scanned fees

Claim transactions

    paid + rolled = pot, exactly, checked before anything is published. A day that doesn't balance to the wei refuses to publish at all.

    Fee treasury

    The wallet that receives the fees

    Creator fees arrive here before the daily close is calculated. This is a public wallet, and its balance is read directly from Robinhood Chain.

    0x0efe36fc42bfb3e10fab227717f5925765d22e4c
    Fees tracked loading starting with the wallet balance
    Wallet balance loading

    The token

    Market cap
    loading
    loading
    24h volume
    loading
    Liquidity
    loading
    Survived the night
    loading
    of circulating supply

    Paid out, by day

    loading

    What it reads, and what it can't

    Balances are rebuilt from transfer logs, which are deltas rather than balances. Miss one and the number is wrong permanently, and nothing inside the reconstruction would notice. So every wallet is checked against a live balanceOf before anyone is paid, and a wallet that disagrees is held back. It is named in the ledger and paid nothing rather than paid on a number nobody can defend.

    A coupon doesn't care why a balance moved, so this needs no swap decoding and no venue event shape. It only needs to know when a balance changed, which is the one thing a transfer log actually says.

    What this holds

    Nothing.

    No keys. No signing. No connect-wallet button, no account, no record of who looked up what. There's no route in this codebase that can spend anything, and the tests grep the source for private keys, seed phrases and signing calls and fail the build if they find one.

    Payments are sent by a person, from their own wallet, using a file the closing tool writes. Deliberately unglamorous. Every custody failure in this category began with something that held funds briefly on someone's behalf.