Launchpads and pool compatibility
Support follows deployed contracts and each pool’s behaviour.
Pons
Flea targets Pons v2 tokens after they graduate into a supported V4 market. Tokens still on their bonding curve do not yet have that graduated liquidity pool.
Pons hook fees have separate distribution rules. The deposit preview states whether an external position earns ordinary LP fees; a launchpad fee stream is not automatically payable to a new liquidity provider. Pons v1 is outside the launchpad-specific integration scope.
Pools.trade
Flea resolves compatible hookless V4 markets, including the native-asset pool configurations used by Pools.trade launch strategies. Current and historical pool keys can differ in tick spacing.
Pool compatibility is determined from the key and contracts. Where launch provenance has not been verified, the market is labelled by its underlying protocol rather than inventing a launchpad attribution. pools.fun is not part of this integration.
Flap
For supported Flap deployments, Flea reads the token lifecycle and actual migrated pool from the portal. The inspected launch route uses a V2 migrator; generic migration descriptions from another chain do not determine the destination.
Some tax-token implementations require a dedicated accounting path and remain unavailable for deposits. A Flap badge alone does not mean all versions or all tax configurations are supported.
Other pools
Verified V2/V3 factories and hookless or explicitly supported V4 configurations can be used independently of a launchpad. Paste the pool address or supported V4 pool ID to inspect the exact market.
Unknown factories, managers and hooks are not automatically executable. Pool discovery, swap support and liquidity-deposit support are separate capabilities.