Docs · Tools
Launch it, then get paid.
A token deployed through Clanker, whose trading fees accrue forever to an address you choose. Point that address at a split and one launch pays a whole team — with no second transaction and nobody trusting whoever holds the wallet.
What actually gets deployed#
Clanker’s v4 factory, on Base, Arbitrum, Ethereum, Robinhood. We build the deploy call and your wallet signs it — the contracts are Clanker’s, the liquidity is Clanker’s, and SwapsPro never holds a key or a token at any point.
The factory divides the LP fee stream between named recipients, permanently. One of them can be the interface that hosted the launch, which is where our share comes from.
text
// what goes into the deploy call, in basis points of 10000
[
{ recipient: <your address or a split>, bps: 8000, admin: <you> },
{ recipient: <swaps.pro>, bps: 2000, admin: <swaps.pro> },
]
// admin is the right to move a recipient later.
// Each side administers only its own — neither can redirect the other's.You keep 80% of the recipient stream; SwapsPro takes 20%. Clanker takes its own protocol cut before this division. The exact recipients are listed on the review screen before anything is signed.
Nothing is signed before you have seen it#
A launch divides revenue that has not been earned yet, and every failure in this area is somebody discovering the division afterwards. So Review shows the recipients, the amounts, and the address the token will have — before the wallet opens, not after it confirms.
- The basis points must total exactly 10000 — a split that does not is refused, never rounded.
- The predicted token address is shown, so it can be checked, saved, or walked away from.
- Any edit invalidates the review: a preview that outlives its inputs is worse than none.
The launch is simulated against the chain first#
Review runs the real deploy call as a simulation before asking for a signature. This is not ceremony — it caught something:
| Chain | Factory deployed | Launch simulates |
|---|---|---|
| Base | yes | yes |
| Arbitrum | yes | yes |
| Ethereum | yes | yes |
| Robinhood Chain | yes — 12kB of code | no — LockerNotEnabled() |
Four layers of “this looks available”
Clanker lists Robinhood Chain as supported. Its factory is deployed there and has real bytecode. The SDK builds a valid transaction for it. And the launch still reverts, because the locker — the module that holds the liquidity and pays out the fees — has not been switched on. Nothing short of asking the chain distinguishes those, so the page asks, and a revert becomes a sentence instead of a wallet prompt that costs gas to be told no.
A chain we could not reach is reported as unreachable, never as a launch that would fail. One is our outage and the other is your problem, and only one of them means do not sign.
Pointing your fees at a split#
The payout field takes any address, and a split contract is the reason it exists. A split pays several people automatically, forever, from every fee the token earns — no monthly transfer, no treasurer, and nobody has to be trusted to pass money on. You still administer it, so recipients can change later.
After the launch#
- A buy box for your own site, themed to match it.
- CSV Airdrop to pay holders, with every line checked before anything sends.
- The page lists what this browser has launched. Clanker credits the launch to us in their index but does not let anyone filter on it, so that list is our own copy — the transaction hash is what proves it.