Instant Launch

How It Works

InstantLaunchStrategy is called via LiquidityLauncher.distributeToken() like other strategies. In a single transaction, it:

1. pulls the full token supply from Liquidity Launcher into the strategy
2. initializes a hookless Uniswap v4 pool pairing native ETH with the token, using the strategy's fixed parameters
3. mints a single position holding the entire token supply as a single-sided position
4. if a BeneficiaryVault address was provided during the deployment of that Instant Launch strategy contract, it registers the fee beneficiary provided via the InstantLaunchConfig struct inside the configData.
5. transfers the position to the FeeSplitter, which holds it permanently and allows only to collect fees or to increase the position's size.

The pool allows the token to be traded instantly after the launch.

Fixed Token and Launch Parameters

The strategy calls token.totalSupply() and token.decimals() to verify they match the required launch parameters, before proceeding to create a pool. All pool parameters are fixed during the strategy's deployment to ensure every launch from a specific deployment of Instant Launch shares these parameters.

LP Fees

LP fees accrue to the launch position, which the FeeSplitter owns and cannot transfer out. Collection is permissionless, and collected amounts are split by immutable shares set at deployment, with separate basis points for the native and the token side.

• UERC20BeneficiaryVault holds the creator's share. It mints a transferable ERC-721 at registration; only its holder can claim. Registration does not have to happen at launch: a claim on an unregistered position registers it, provided the caller matches the token's graffiti.
• CompoundingClaimRecipient allows any caller to compound collected swap fees back into the locked position, via a contract implementing IClaimExecutor. See Collect and Compound Fees.

Compared to CCA

Where to Go Next

• Collect and Compound Fees
• Liquidity Strategies
• Deployments