The launchpad, and where the money goes

The short version

A launch here is not a launch for Ztek. It is a launch for an agent that needs a token, and the fee the coin carries is that swarm's compute budget rather than our revenue.

Every coin launched here sets a 2% creator tax and names one fee recipient: the pool address printed further down this page. Trading it costs 3%, of which 2.7% reaches that pool and converts into API credits for the models the agents run on. The launcher keeps the tokens they buy; Ztek takes none of the supply.

Two fees, not one

Trading a coin on the curve touches two separate charges, and it is worth keeping them apart because they behave differently.

1 — Pons' curve fee: 1%

This one belongs to the protocol, not to us. The factory's launch config sets it, the same value for every coin on Pons, and we could not change it if we wanted to. It splits: 0.7% of the trade is credited to the coin's fee recipient through Pons' fee escrow, and the remainder stays with the protocol.

2 — The creator tax: 2%

This one is ours to set, and we set it to 2% on every launch. It is charged on top of the curve fee and goes to the fee recipient in full. Pons enforces a ceiling on it — the launch form reads that ceiling live before signing, and refuses to launch if the ceiling has dropped below what this page promises.

Together

1% + 2% = 3% out of each trade, and 0.7% + 2% = 2.7% of each trade lands in the wallet above. The gap is Pons' own cut.

What cannot be changed

This matters more than the numbers, because a fee you can edit later is not really a fee — it is a promise. These are not promises:

• The tax is immutable. It is written into the curve at deployment. There is no setter, no owner, no proxy and no upgrade path that raises it, lowers it or removes it.
• The recipient is immutable. Same reason. Ztek cannot repoint your coin's fees at a different wallet, and neither can you, and neither can Pons.
• The supply is fixed. Pons' launch config sets it at deployment and there is no mint function afterwards.
• Ztek takes none of your tokens. There is no allocation, no vesting and no treasury slice. Whatever you buy in the launch transaction is yours. The pool is funded out of trading, or it is not funded at all.

Check it yourself

You do not have to believe any of the above. Every claim on this page is a public read against contracts we do not control:

1. Call getLaunchedToken(token) on the factory. The struct it returns contains creatorFeeRecipient and creatorTaxBps.
2. Compare that recipient to the address above. If it matches, that coin's fees are pointed here — and that is exactly the test the coin index uses to decide what to list.
3. Watch the fee escrow for the Credited events that carry the payments, per coin.

What a launch costs you

Pons charges a launch fee, read live from the factory at the moment you sign, plus gas. Ztek adds nothing on top — there is no separate charge for using this site. If you set a dev buy, that ETH is spent buying your own coin in the same transaction and the tokens land in your wallet.

Graduation

A coin trades on its bonding curve until it has raised the graduation threshold in ETH. At that point Pons drains the curve and opens a Uniswap v4 pool for the pair. The coin index marks this as graduated. The creator tax continues to apply — it belongs to the coin, not to the curve.

Where this sits on the rest of the site

The agent network described everywhere else on Ztek — shielded settlement, swarms, viewing keys, post-quantum authorization — is a design preview with no backend behind it, and every page says so. The launchpad is not. It is live, it signs real transactions, and it spends real ETH. The two are kept apart deliberately, and we would rather label it awkwardly than blur the line.