How it works
Every token launched here pays its creator fees into a contract that can only buy the token and burn it.
The idea
On Pons, whoever launches a token sets a creator fee — up to 10% of every trade — and names a wallet to collect it. Normally that wallet belongs to the creator, and the fees leave the token.
A Flow launch names a vault instead. The vault is a contract deployed in the same transaction as the token. It collects the fees, spends them buying the token back, and burns everything it buys. It has no owner, no withdrawal, and no way to pay anybody — the only thing it can do with money is destroy supply.
So the fee is not a tax the creator collects. It is a permanent bid under the token, funded by its own trading, that gets stronger the more the token is traded.
What happens when you launch
- 1. One transaction. The launchpad works out the vault’s address before it exists, launches the token on Pons naming that address as the creator, and then deploys the vault there.
- 2. It checks. Before the transaction can succeed, the launchpad asks Pons where the fees are actually going. If the answer is anything but the vault, the whole transaction reverts and no token is created. There is no path that produces a Flow token without the guarantee in force.
- 3. The name and ticker are claimed. Together, case-insensitively: nobody can ship a second Flow token calling itself the same thing yours does. Either half on its own stays free, so an honest launch is not blocked by somebody who got to a common word first.
- 4. Then nothing more is needed. From that point the engine runs on its own and anyone can turn the handle.
The engine
Anyone can call flow() on a vault. It collects whatever fees are waiting, buys the token with them, and burns the lot — on the bonding curve before graduation, and in the Uniswap v4 pool after it. The caller pays gas and receives nothing, which is fine, because the caller is usually someone who holds the token.
There is nothing to trust here. The vault has no admin function at all, and the fee route cannot be moved: Pons only lets the current recipient hand a fee stream to someone else, and the recipient is a contract with no such call in it. The route is pinned by the same rule that would otherwise let it move.
What it trades against
A launch does not have to be denominated in ETH. Pons keeps an allowlist of quote assets and almost all of them are Robinhood Chain’s tokenised equities, so a token can trade against NVIDIA, or gold, or Bitcoin.
Whatever it is paired with is also what its fees arrive in, and what the vault spends buying it back. The amount needed to graduate is set per asset by Pons and read live at launch rather than assumed.
What Flow does not control
Fees do not land in the vault the instant a trade happens. Pons banks them — inside the curve before graduation, inside the Uniswap v4 hook after it — and only Pons’ own sweep operator can move them into the escrow the vault claims from.
Nothing is lost when that happens: the amount is recorded against the vault either way, and it can only ever be claimed by the vault. But the timing belongs to Pons, not to Flow. Every token page shows both figures separately — what the engine can spend now, and what has been earned but not yet swept — so a quiet engine is never mistaken for a broken one.
Two other things worth saying plainly: a burn raises the floor under a token, it does not guarantee a price. And buying a token on a launchpad is a speculative act with no protection, on either this one or any other.