Launch mechanism

1. The token is deployed with CREATE2, using a salt derived from the sender, the previous block hash and a counter. The full supply is minted to the factory.
2. A pool is created against WETH at Uniswap's 1% fee tier, and initialised at a price outside the range the liquidity will occupy.
3. The whole supply is added as liquidity in a single-sided position: only tokens, no ETH. Buyers supply the ETH side as they trade.
4. The position NFT stays with the factory. Nothing transfers it out because nothing can.
5. The dev buy runs, if ETH was sent beyond the launch fee. The factory swaps it through the router and the tokens go straight to the creator's wallet. Because this happens inside the launch transaction, nobody can buy between the pool opening and the creator's first buy, so the opening price cannot be sniped.

A pool address is derivable in advance. Without a salt, someone could create the pool first at a price of their choosing, and the launch would land into a pool already skewed against the creator. The factory predicts its own pool address, checks it is untouched, and steps to a different salt if it is not. It tries a bounded number of times and then reverts rather than launching into a poisoned pool.

That bound matters: an earlier version used plain CREATE, and a revert does not advance a nonce, so a single poisoned address could brick the factory permanently.

The position covers a fixed tick range that the initial price sits below. In practice this means the coin starts at the bottom of its range and rises through it as ETH enters. The width of that band and the amount of ETH needed to cross it are the same number seen from two directions: raise = sqrt(startMcap × endMcap).