How it works

Tripools deploys tokens via a canonical CREATE2 deployer so the same contract address exists on Robinhood Chain, Ethereum, and Base. When you Triple Launch, you sign one transaction on your chosen primary chain. That transaction mints the full supply, seeds the primary chain's pool, burns its LP position, bridges each secondary chain's reserved share through LayerZero, and emits an event for the off-chain keeper to finish deployment and pool seeding on the other chains.

The launch flow

1. You pick name, ticker, base tax (1%–10%), optional whitelist, optional dev buy, and which chains to target.
2. On the primary chain, the factory deploys TripoolsToken, mints the full supply, and seeds a single-sided Uniswap v4 pool. The LP position is burned in the same transaction.
3. For each target chain, 10% of supply is bridged out via TripoolsLzBridge — burned here, verified by LayerZero DVNs, minted on arrival.
4. The keeper relays token deployment to other chains and seeds each target chain's pool once the bridged balance is confirmed on chain. The keeper can sequence but never mint supply.

Supply split

Each secondary chain receives a fixed 10% of total supply. The primary chain's pool gets whatever remains:

• Triple Launch (all three chains): 80% / 10% / 10%
• Two chains: 90% primary / 10% secondary
• Single chain (Standard Launch, coming soon): 100% on one chain

Trading and fees

Every pool uses TripoolsAntiSnipeHook for tax collection — the AMM pool fee is zero. Ordinary buy/sell tax splits 80% to the creator and 20% to the protocol treasury, enforced on chain. The flat 50% anti-snipe tax on non-whitelisted buys in the first 6 seconds goes entirely to the protocol treasury as a bot deterrent, not creator revenue.