How Ember works.

Your browser prepares the coin's address, then one transaction deploys the token, registers its pool on the Ember hook, opens the market at your starting price and puts the whole supply into a single-sided Uniswap V4 position. If you sent AVAX along, the same transaction buys your first tokens before anyone else can.

1%, on buys and sells alike, taken in the pairing asset: AVAX, USDC, BTC.b, or whatever you chose. The rate is a constant in the hook contract. Nobody can raise it, lower it, or add another one.

Half to the creator address, half to Ember's treasury. Both halves accrue as claimable balances inside the hook and leave only when their owner calls claimFees. The Earnings page does that for you.

Yes. The current creator can hand future fees to any address with setCreator. Fees already credited stay with the address that earned them. An admin key can also point future fees at a new address, which is how a community takes over a coin its creator abandoned; it cannot touch a balance already earned.

AVAX by default. USDC, USDt, BTC.b, WETH.e, LINK.e and sAVAX have one-click routes, so buyers can pay in AVAX and you can make a first buy. Tokenized stocks and a few Avalanche memecoins are listed too, without a route: they pair and pay fees like anything else, but buyers trade with the asset itself. Anything with $10,000 of real liquidity against AVAX can be listed from the Pairs page.

In three overlapping bands below the starting price, owned by the Ember factory. The pool's own LP fee is zero and nobody but the factory can add to it. The factory owner can withdraw a pool's liquidity in full, both sides, to any address. A coin page carries a visible mark once that has happened, and the trade panel closes.

It is a plain ERC-20: no owner, no mint after launch, no pause, no blacklist, no tax on transfer. The supply at launch is the supply forever. The fee cannot change. Fees credited to you cannot be moved by anyone else.

The coin's address has to sort above its pair in the address space, and the browser searches for one that does. Against AVAX that takes a moment. Against a pair whose address sits near the top of the space it can take minutes, so the launch page refuses pairs that would take too long and warns about the slow ones.