Field guide
What happens when you launch, where the fees go, how the burn works, and what nobody can do to your token afterwards.
Pick a name, a ticker, an image, a supply and a starting market cap. Choose what your token trades against, choose a mode and a burn share, and launch. One transaction creates the token, opens its market and locks the whole supply.
The supply goes into a single-sided position that only the locker can add to. Nobody, including us, can pull it out.
Every launch burns. At launch you choose how much of the 70% that is not the platform's goes to the burn, from nothing to all of it. That share piles up in a pot, and at most once every five minutes the pool spends it on its own token and sends what it buys to the dead address.
On Uniswap V4 the burn rides inside the first trade after the five minutes, so nobody has to press a button. It only buys while the price sits within 1% of where the block opened. If someone has just pumped it, the burn waits for the next trade instead of buying the top. A quiet pool can be burned by anyone with a public call, and our keeper does it.
On Pharaoh there are no hooks. Fees paid in your own token burn the moment they are collected. Fees paid in the pair asset wait in the pot, and the keeper, or anyone, spends them every five minutes. That buyback only runs while the price sits within 1% of the pool's 30-second average.
The mode decides how the fee behaves and where the rest of it goes. It is fixed for the life of the token, and so is the burn share.
First Chair only fades buys. Sells pay your resting fee from the first second, and your own first buy, made inside the launch transaction, is exempt. Switchback steps down with the highest price the pool has traded at, so a step once taken stays taken. Patrol caps all the buys in one block together, which a bot cannot dodge by splitting its order. Last Run pays the wallet that signed the last qualifying buy. A smart wallet sent through a relayer would make the relayer the buyer.
Uniswap V4 is home. Our hook takes the fee on each trade, in the pair asset, which is what lets every mode exist and the burn run on its own.
Pharaoh is the deepest DEX on Avalanche, with no hooks. It runs Groomed, Off-Piste and Meltdown, at a fee set by the pool tier, 1% or 2%. Fees arrive in both currencies there. Pharaoh governance decides how much of each pool's fee goes to its own voters, and nothing in our contracts can prevent that. The launch page says so before you pick it.
A pair asset is what people trade your token against. AVAX is the default, and the right answer for most launches. USDC, USDt, BTC.b, WETH.e, sAVAX and LINK.e are there too, each read off the chain before it was listed.
Tokenized stocks are listed as they reach Avalanche, once each one has been checked on chain. Where a third party controls a token, we say so on the pair itself. Pair with one and your holders earn fees in it, which is the part worth thinking about first.
Your share can go to up to three recipients. Each is a wallet or an X account, with a percentage you set at launch. The percentages never change.
An X account does not need a wallet. Its fees accrue to an address derived from the handle, which nobody holds a key to. When the owner signs in with X on the Earnings page, the handle is bound to their wallet, once, and everything waiting is paid out.
Launched tokens are plain ERC-20s. No owner, no mint, no pause, no blacklist, no tax on transfer. The supply that exists at launch is the supply forever. A burn sends tokens to the dead address; it never mints or destroys anything.
The fee rule, the mode and the burn share are set once. The liquidity belongs to the locker and cannot be removed. Fees already credited to you cannot be moved by anyone.
One operational power exists. An admin key can point a pool's future creator fees at a new address, which is how a community takes over a token its creator abandoned. It only affects fees taken from then on and can never reach the liquidity, the supply, the burn or a balance already earned.
Contract addresses land here once the protocol is deployed.