Documentation
A launchpad for coins that trade against another coin instead of the gas token, on Avalanche. One transaction deploys a fixed-supply ERC-20, opens a Uniswap V4 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.
| 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 |
$SHERPA
There is no $SHERPA token yet. The protocol's share of every fee is earmarked for buying one back, and until it exists that share is collected by the protocol treasury.
Which means that today, anything calling itself SHERPA is not this. When the token exists its address will be published on this page and in the app, and nowhere else first — anyone can deploy a token and give it any name they like.
What these pages cover
How the protocol works. Where something is designed but not yet live — the buyback, most of all — it says so in the section that covers it.
Sherpa.fun is live on Avalanche C-Chain, deployed on 21 September 2026. Contracts carries the addresses, and that page and the app are the only places they are published first — any other address presented as Sherpa.fun's is not.
Every contract is verified on Snowtrace, 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 Avalanche 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.