Launchpad overview

The launchpad is one contract call. ArmoryLauncher.launch deploys a token, creates its Armory V3 pool against WAPE, mints the entire supply into that pool as one position, locks the position permanently, and optionally makes the first buy for the creator. There is no presale, no bonding-curve contract to graduate from, and no migration step later.

Launching is permissionless. The app front end is at /deploy, launched tokens are listed at /launches, and creators manage their tokens at /creator.

What one launch does

In order, inside a single transaction:

1. Deploy the token. A fixed-supply ArmoryToken is created with CREATE2. Supply defaults to 1,000,000,000 (18 decimals) when the caller passes zero. The whole supply is minted to the launcher, which keeps none of it.
2. Register the owner. The caller becomes the token's owner in TokenOwnerRegistry. That record gates every creator power afterwards.
3. Open the pool. The launcher creates and initializes the token/WAPE pool on the 2.5% tier (fee 25000, tick spacing 500) at the start tick the caller chose.
4. Mint the curve. The entire supply goes in as one single-sided position, from the start tick to the maximum usable tick, 887000. No WAPE goes in. The rounding remainder of the mint is burned, so the launcher ends the transaction holding zero tokens.
5. Lock it. The position NFT is transferred to ArmoryLaunchLocker with the creator and the current creator fee share stamped into it.
6. Dev buy, optionally. Any APE sent above the launch fee is swapped into the new token through the V3 SwapRouter, paid to the caller.
7. Pay the launch fee to the platform treasury and emit TokenLaunched.

Why the pool is the curve

A V3 position that holds only the token, starting at the pool's current price, is a sell wall that runs all the way up the tick range. The first buyer takes tokens from the bottom of it and moves the price up. Every later buyer pays a little more. That is a bonding curve, implemented by an ordinary pool.

Because the curve already is the pool, nothing has to graduate. The token is tradable on the DEX, through the aggregator, and on any router that reads Armory V3, from the block it launches. Selling walks the price back down the same range.

The starting market cap is set by the start tick. The app asks for a target market cap in dollars and converts it to a tick, snapped down to a multiple of 500, so the realised cap lands at or just below the target.

The liquidity is locked forever

ArmoryLaunchLocker accepts positions from the launcher only and has no withdrawal path at all. There is no unlock time to reach, no decreaseLiquidity, no transfer, no approval and no upgrade. The admin of the locker cannot move a position either. What the locker does allow is collecting the swap fees the position earns, which is covered on Fees.

This is a different contract from the public V3 position locker. That one has expiries, owners and fee modules. The launch locker has none of them.

The token

ArmoryToken is a plain ERC-20 with burn. It has no owner, no mint, no pause, no tax and no transfer hooks. Two things can change after deployment:

• pool is set once by the launcher inside the launch transaction.
• Metadata (image, description, socials, contractURI) can be edited exactly once by the token owner, then locks forever. See Creator tools.

Addresses

Where to go next

• Fees: the launch fee, the pool fee, and how collected fees split between creator and protocol.
• Creator tools: fee recipient, the one-time metadata edit, ownership transfer and renounce.
• Contracts: functions, events and admin powers for all five contracts.
• Integration recipes: launch from a script, read and collect fees, read metadata.