Fees arrive on their own.
pons pays the creator's share of trading fees to whatever address the launch named. When that address is the foundry's, ETH simply accumulates there — no claim call, no permission, nothing to remember to do.
Mechanism
Take. Split.
Give.
Three steps, run on a timer by a contract that gets no say in anything. It cannot skip a token, it cannot change the split, and once a deposit lands there is no instruction that takes it back out. This page describes that contract. It is not deployed — what runs today is the launch itself, on the launch page.
Chain Robinhood Chain · 4663
Withdraw path Does not exist
Status Design — not deployed
One sweep, step by step
What happens in
a single minute.
The balance is cut in two.
The collected ETH is divided along a split fixed when the contract is deployed — 50/50 by default. Neither side can be rebalanced afterwards, and no share goes to a team wallet, because there is no such wallet in the contract.
Both legs are bought on market.
One half buys the token itself on the open market. The other half buys wBTC. Both are ordinary swaps — the same price impact any other buyer takes at that size.
The pair is deposited and left there.
The two legs are deposited together as liquidity. The position belongs to the contract, and the contract has no function that removes liquidity. The floor beneath the token can only move one way.
Why it holds
The money was already
leaving the table.
Creator fees are paid on every launchpad. The only question is who ends up with them. Here the answer is fixed before the first trade.
Funded by
Volume
Not by emissions, not by a treasury, not by new buyers subsidising old ones.
Paid to
Holders
Half of every sweep is a market buy of the token the holders already own.
Stored in
Bitcoin
The reserve leg is wBTC, so the floor does not move with the chain’s own gas token.
Reversible
Never
No withdraw instruction, no admin key over the pool, no upgrade authority retained.
Questions
What people ask first.
Nobody, in the sense that matters. The sweep is meant to be permissionless: if whoever normally triggers it goes offline, anyone can call it and pay the gas. The call does the same thing regardless of who signs it. ("Keeper" is just the name for that trigger — a small job that pokes the contract on a schedule. It decides nothing.)
The creator fee wallet is set inside the launch transaction, before the token can be traded. Nothing on this site can change it afterwards — and if a creator launches without pointing it at the foundry, that is simply an ordinary pons launch.
That is the design: the liquidity position belongs to the contract and the contract has no remove-liquidity function. Not a policy — a function that does not exist in the deployed bytecode. It has to hold true when the contract ships; today the contract does not exist yet.
Because the point is a floor that does not erode. pons quotes launches in ETH, which is the chain’s own gas asset, so a reserve held in ETH moves with the same cycle as everything else on it. A reserve held in wrapped Bitcoin does not.
Nothing, at no cost. With no trading there are no creator fees, so the sweep finds a zero balance and does nothing. A launch that goes quiet for months sweeps normally the day volume returns.
The sweep pays its own gas and nothing else. pons takes its own launch and graduation fees — that is between you and pons — but the foundry adds no cut on the split.