[SIMD-LAUNCH]

A custom token: Swarmy (SWARM).

Token name: Swarmy

Token symbol: SWARM

Token supply: 1,000,000,000 with 18 decimals, all minted once to the deployer in the constructor.

Minting after launch: none, the supply is fixed forever.

Who can call what: no owner and no admin functions; every parameter is a fixed constant.

What it does:

1. Implements an ERC20 token named Swarmy with symbol SWARM, fixed supply of 1,000,000,000 tokens and 18 decimals, minted once at deployment.
2. Supply distribution: 90% (900,000,000 tokens) is allocated for the Uniswap v4 pool seeded by the deployer; 10% reserved for the swarm via separate distribution (not minted or transferred by the token contract).
3. Uniswap v4 PoolManager address is 0x000000000004444c5dc75cB358380D2e3dE08A90; pool fee is fixed at 1.25% (12500 bps) and tick spacing of 60.
4. Transfer fees apply only on buys, defined as transfers FROM the PoolManager address:
   • 1% of the transferred amount is permanently burned, reducing total supply.
   • 2% of the transferred amount is sent to a fixed treasury wallet address (immutable, set at deployment).
5. Transfers TO the PoolManager (including sells and pool seed) are fee-exempt to avoid CurrencyNotSettled errors.
6. Wallet-to-wallet transfers outside the PoolManager address have no fees.
7. The token contract has no owner or admin functions; all parameters including treasury wallet and fee rates are fixed constants and cannot be changed post-deployment.
8. Includes a public view function totalFeesCollected() returning the cumulative total of tokens burned plus tokens sent to the treasury since deployment.
9. The token contract is named SWARMToken.

Who can call what:

• No owner or admin powers present; all parameters and state changes happen solely through token transfers.
• Anyone can call totalFeesCollected() to view total accrued fees.

Tests:

1. Verify that at deployment the total supply is 1,000,000,000 tokens and no tokens are held by the treasury or PoolManager.
2. Confirm that transfers from the PoolManager burn exactly 1% and transfer 2% to the treasury, and recipient receives 97%.
3. Confirm that transfers to the PoolManager have zero fees and the full amount is received by the pool.
4. Confirm that wallet-to-wallet transfers pass the full amount with zero fee.

Mechanics specification (authoritative: where anything above differs, follow these exactly):

M1. Burn on trade: 1% of every buy (transfers FROM the Uniswap v4 PoolManager 0x000000000004444c5dc75cB358380D2e3dE08A90) is burned, permanently reducing the supply. Transfers TO the PoolManager (sells and the launch factory's pool seed) are never taxed, so Uniswap v4 settlement always balances. Plain wallet-to-wallet transfers pay no fee.

Build requirements (mandatory):

• Context: an ordinary, legitimate token launch on Ethereum. The coin's name, story and theme are branding only; nothing here is real-world harm or offensive security work.
• A complete Foundry project at the repository root: foundry.toml with solc 0.8.26, evm_version cancun, optimizer on and bytecode_hash = "none", so the build is reproducible and verifiable: deployed contracts live in src/ and every import resolves to a committed file.
• Token contract: SWARMToken. No selfdestruct and no delegatecall anywhere. No proxies, no owner, no upgradeability.
• Supply distribution is done by the launch factory: it mints the supply, seeds the pool from the deployer balance, sends the swarm's 10% through its Merkle distributor and any remainder to remainderTo. No contract here sends the swarm allocation, and the token always mints the entire 1,000,000,000 (1e27 units) to its deployer: never subtract the swarm's 10% (IMD's protected invariants park any launch whose deployer holds less).
• Chain: Ethereum mainnet (set by the order, not a launch.json field). Swaps happen in Uniswap v4, so the pool's tokens move to and from the PoolManager 0x000000000004444c5dc75cB358380D2e3dE08A90.
• launch.json top-level keys, exactly: kind ("custom_token"), token {contract, name, symbol, decimals, constructorArgs, totalSupply}, contracts ([] if none), pool, economics, notes (one string). No chainId or other keys.
• launch.json pool: pairedCurrency 0xd34a99bc0f67ae1bbd63c660e6d0b0dd03e263b7, fee 12500, tickSpacing 60, initialPrice "125270724187523965593206900" (paired-currency minor units per SWARM minor unit with SWARM as currency0, provenance only; the deployer derives the real opening price from the economics using the deployed currency order). launch.json also carries the economics block below.
• launch.json economics, exactly: poolBps 9000, initialMarketCapWei "2500000000000000000000" (2500 IMD opening market cap), remainderTo 0x000000000000000000000000000000000000dead.