Documentation
A launchpad for coins that trade against another coin instead of the gas token, on Sonic. One transaction deploys a fixed-supply ERC-20, creates a Uniswap V3 pool for it against the pair asset of your choice, and seeds that pool with the entire float. No bonding curve, no migration, no seed capital.
ArcadeFun is the product. Its domain and its ticker are not chosen yet; everything below describes the protocol, which does not change with them.
| What it is | The mechanism in one page: single-sided liquidity, why the creator brings nothing, why the price has no ceiling |
| Launching a coin | Every parameter, what it does, and what happens if you get it wrong |
| Fees | The 1% split, who gets what, and what you can do with your share |
| Pair assets | What can be paired against, how eligibility is measured, and the two depth bars |
| Contracts | The contracts, the external ones they rely on, and the calls worth knowing |
The protocol coin
There is no protocol coin yet. When there is one, it will be launched through this launchpad like any other coin — fixed supply, no mint, no owner, its liquidity locked in the fee vault for good — and its address will be published here and in the app before anywhere else. Anyone can deploy a token and give it any name they like, so check the address, not the name.
The protocol's share of every trading fee on the platform is earmarked for buying that coin back and burning it. Until the coin exists and the buyback is switched on, that share is collected by the protocol treasury.
What these pages cover
How the protocol works. Where something is designed but not yet live — the buyback, holder rewards' distributor, the deployment itself — it says so in the section that covers it.
Nothing is deployed on Sonic yet. Contracts will carry the addresses once there are any, and that page and the app are the only places they will be published first — any other address presented as this protocol's is not.
When they are deployed, every contract will be verified on Sonicscan, and your coin's own will be
too: PairToken takes no constructor arguments, so every launch produces byte-identical code and
the explorer can match all of them from a single verification.
None of this has been audited. The tests are thorough and run against live Sonic state, but they were written by the same people who wrote the contracts. Treat the liquidity lock as permanent, because it is, and size your launch accordingly.