One coin on three chains, held at one market cap.

One coin opens on three pads in the same tick.

The same coin — name, ticker, image, supply — is created on pump.fun on Solana, PONS on Robinhood Chain and flap.sh on BNB Chain in a single launch second. Each chain mints its own supply; nothing is bridged. A pad that fails to land is retried; nothing moves on a pad until the first one is live.

The launch is atomic where the chain allows it and quiet where it does not: no order is sent in the launch second except the launch itself. A venue the pair names that has not landed yet reads as attaching everywhere on this site.

One market cap, held inside a band.

On every tick the engine reads all three books and takes the reference as the mid of the highest and the lowest market cap. The widest gap is the distance from the lowest to the highest. While it is under 5% the engine holds. When a venue runs ahead it sells there and buys where the coin is cheap, in the same tick, sized to the real quote depth on each side — never more than the book can absorb.

The maker promises the band, not the price. It never decides what the coin is worth; it decides that the coin is worth the same thing everywhere. A venue that stops answering is marked stale after 90 s rather than traded against. The gap read-out on Live is exactly this number; this site reads it every 20 s.

Fees feed the maker; the surplus burns.

Creator fees from every chain flow back to the engine. It keeps every fee until its reserve holds on each side — enough SOL, ETH and BNB to defend the band through a bad hour. Above that line, fees buy the coin back and burn it, on every chain, in the open, so the three supplies fall in step.

Nothing leaves the loop for the operator: the maker earns nothing on the spread it closes. The claim, the buyback and the burn are on-chain and listed on the reserve page as they happen.

Anyone can launch a coin the same way.

A dev fills in one form and deposits once, in the asset the desk offers. The reserve fronts gas and seed on every pad; the same engine mirrors the new coin under the same band. The coin's own fees repay the reserve first, then refund the deposit, and once the reserve holds on every side the dev gets a share of every claim. Admission is capacity, not curation: a launch needs a free maker slot.

1. 01

   Deposit once, in the asset you hold

   The launch desk quotes the deposit in the asset the desk offers at live FX: —. Pay it from the wallet you declare; a transfer from any other wallet is refunded to its sender minus the network fee and never counts. Unpaid after —, the request lapses.

2. 02

   Approval

   An operator checks the launch (same art as another coin, a wallet on cooldown, a name that misleads). Undecided after —, the deposit goes back. Approved: the launch is queued behind the ones before it and goes out when a maker slot is free.

3. 03

   Launched on every pad in one tick

   The reserve fronts the seed and the gas (—): pump.fun first, then the other pads in the same tick. The seed split per venue is — of supply, each coin with its own supply on its own chain.

4. 04

   The maker mirrors the caps

   The engine reads all three books every tick. Widest gap wider than 5%: it sells the expensive side and buys the cheap one. When it cannot, it holds and says so on the coin page.

5. 05

   Fees go down the waterfall

   Creator fees from every chain are claimed by the treasury and run through one order: the maker's reserve on each side up to its target, then the front repaid to the launch reserve, then the deposit refunded to the dev, then the split below. Every step is written on the coin page as it happens.

6. 06

   Dev share, refund, burn

   Once the reserve holds on every side the dev gets a share of every claim, paid in the deposit asset through the reserve. What the maker does not need buys the coin back and burns it, on every chain, in the open.

Launch a token → · the form quotes pump.fun, PONS and flap.sh live.