Docs
launch x is a fee bridge. A token launched through this site points its creator fees at our treasury, we claim them on chain, and 75% is paid to an X account in dollars through X Money. Nobody has to sign up to be paid.
Overview
A deployer launches a token on the Pons V2 launchpad on Robinhood Chain through our form and points its creator fees at the launch x treasury. The token's description names an X account, and that account is who the fees are for.
Everything after that is mechanical. Fees accrue to the treasury as the token trades, launch x claims them on chain, 75% is converted to dollars and paid to the recipient through X Money, and 25% buys the protocol token and burns it. Every step is recorded against the claim that produced it.
The recipient is not asked to do anything first. There is no account to make and no wallet to connect, so a payment can arrive from a token they have never heard of. Section "Stopping payments" covers how to stop that.
Supported venues
One venue today: the Pons V2 launchpad on Robinhood Chain, chain id 4663, paired with native ETH. The fee direction is part of creating the token, and the Pons contract lets only the current recipient hand the fee wallet on, so once it is ours the deployer cannot take it back.
Directing fees
Fees are directed at creation. The launch form sets creatorFeeRecipient to the launch x treasury and creatorTaxBps to 2%, on top of the 1% curve fee Pons charges, so a trade pays 3% in all once the launch window has passed; for the first seconds after a launch Pons charges an extra snipe tax on top, decaying to zero. The whole creator share goes to the treasury, because a partial share would make the payment we publish a fraction of what the token earned with no way for the recipient to tell which.
Naming the recipient
The token description carries one line: Fees to @handle via launch x. The indexer reads that line first, then the first @mention in the description, then the X link in the token's socials. The handle is normalised to 1 to 15 characters of letters, digits and underscores; the handle x is refused.
A handle is resolved to a numeric X user id through the public X API. Until it resolves, obligations accrue against the handle and move to the id when it is known.
The 75/25 split
Every claim is split the same way: 75% to the named recipient and 25% to buying and burning the protocol token. There is no third share and no discretionary cut. Rounding of a claim goes to the buyback bucket.
Converting the recipient share to dollars costs the exchange its trading fee, and that fee comes out of the dollars the sale produced, so what is credited is what the exchange actually paid. Splitting those dollars over the recipients of one batch leaves each of them a remainder under one cent; the sub-cent remainder of converting a batch to dollars pays for running the service rather than going to the buyback.
A token whose recipient cannot be determined still has its fees claimed, but they sit in an unattributed account until a recipient is set. The protocol token is the one exception in the other direction: it is registered like any other token, but it is not split, and the whole of its own fee stream pays for running the service.
How claims work
Fees accrue inside the Pons fee escrow. A keeper sweeps each token's curve or pool and then claims the escrow balance in one transaction. The claimed amount is attributed across tokens in proportion to the fees each of them contributed since the previous claim, and the split is written as immutable ledger entries.
Corrections are made with new entries, never by editing old ones.
Getting your fees
Payments arrive in X Money, sent to the handle from our account. If an account has X Money set up, the money lands there. If it does not, X Money holds the payment until the account claims it.
A payment is queued once what a recipient has already been paid plus what they are currently owed reaches the next threshold in the list $5, $10, $20, $50, $100, $250, $500, $1,000, and then every further $1,000. At most one payment per recipient every 24 hours, at most $10,000 to one recipient within 24 hours, and never less than $1.
X Money setup
Nothing is needed in advance. To claim a payment the recipient needs an X account in a country where X Money operates, and has to complete whatever X requires of them. That is between them and X; launch x has no visibility into it and no ability to influence it.
Unclaimed payments
A payment that is not accepted within 14 days expires under X Money's own policy, and the dollars return to the account they were sent from. The expiry is recorded as a ledger entry and the money pays for running the service. The payment is not re-sent.
The public confirmation
Every payment is published with the X transaction id and a link to its receipt, on the Payments page and on the recipient's profile page. That is the record; nothing is paid without one.
The treasury and the buyback
The treasury is a single hot wallet on Robinhood Chain, 0xb0b27b35eb87628ABC26bed0e8625990fEb9f2BE. It is the only address the Pons escrow will pay, so it also signs the sweeps, the buybacks and the transfers to the exchange. Balances above a float are moved off it regularly.
The buyback spends the 25% bucket in batches, buying the protocol token on its Pons curve or its Uniswap v4 pool and burning what it buys. Each batch is capped by its price impact so a thin book is not moved.
Stopping payments
Ask us — at to be published, or through @xmoneyfees on X — and the handle goes on the do-not-pay list. Tokens naming a listed handle stop having their fees swept and claimed, and no further payment is queued. Anything already sent through X Money is between the recipient and X.
X Money itself also decides who may pay an account; blocking our account there stops payments regardless of what we do.
If a token is not registering
A token registers itself when the chain shows its creator fee recipient is our treasury. If it was launched elsewhere and the recipient was transferred to us afterwards, the indexer picks it up from the transfer event. If neither happened, the token is not ours and will not appear here.
Glossary
Creator fee the share of each trade the Pons contracts route to the token's creator fee recipient. Claim one withdrawal from the Pons escrow, the unit our ledger is built from. Attribution the split of a claim across the tokens that produced it. Recipient the X account a token names. Graduation the moment a Pons curve raises its threshold and liquidity moves into a locked Uniswap v4 pool.