Supported Chains

LP24 deploys the same protocol on 5 chains. Economics are denominated in each chain's native asset and scaled to it; the curve shape, supply and lifecycle are identical everywhere.

Chain Matrix

Parameter	Base	BSC	Polygon	Robinhood	Gnosis
Chain ID	8453	56	137	4663	100
Native asset	ETH	BNB	POL	ETH	xDAI
DEX venue	Uniswap V4	PancakeSwap Infinity	Uniswap V4	Uniswap V4	Uniswap V3
Post-graduation manager	PrimaryHook	PrimaryHook	PrimaryHook	PrimaryHook	GraduationManager
Secondary $LP24 pool	Yes	Yes	Yes	Yes	No
Deployment fee	0.06 ETH	0.18 BNB	1,440 POL	0.06 ETH	144 xDAI
Inclusion window	10 blocks	44 blocks	12 blocks	200 blocks	5 blocks
Graduation liquidity	4 ETH	12 BNB	96,000 POL	4 ETH	9,600 xDAI
→ primary pool	3.6 ETH	10.8 BNB	86,400 POL	3.6 ETH	9,600 xDAI (no split)
→ secondary pool	0.4 ETH	1.2 BNB	9,600 POL	0.4 ETH	—
Fee tier 2 threshold	12 ETH	36 BNB	288,000 POL	12 ETH	—
Fee tier 3 threshold	24 ETH	72 BNB	576,000 POL	24 ETH	—
Fee split (deployer / protocol / reinvest)	30 / 10 / 60	30 / 10 / 60	30 / 10 / 60	30 / 10 / 60	40 / 20 / 40
CTO vote fee	0.01 ETH	0.03 BNB	240 POL	0.01 ETH	24 xDAI
`P_START`	1_200_000_000	3_600_000_000	28_800_000_000_000	1_200_000_000	2_880_000_000_000
`PRICE_SLOPE`	8_410_810_800	25_232_432_400	201_859_459_200_000	8_410_810_800	20_185_945_920_000

Why the numbers differ

Every chain targets the same approximate fiat-denominated launch economics. The curve constants P_START and PRICE_SLOPE are scaled by the native asset's value, which is why Polygon's are five orders of magnitude larger than Base's and Gnosis — denominated in a stablecoin — sits in between. Token supply, lot size and the tax schedule are the same everywhere.

Venue Differences

Uniswap V4 — Base, Polygon, Robinhood

The reference implementation. Pools are keyed on (currency0, currency1, fee, tickSpacing, hooks) with the hook address last. The hook's permission bits are encoded in its address, so the deployment salt must be mined to produce 0x20CC in the low bits. Fees are taken via PoolManager.take() and the pool manager holds custody, so it is also the LP custodian for circulating-supply math.

PancakeSwap Infinity — BSC

A faithful port, not a separate design. Differences are all in the integration layer:

PoolKey has six fields — (currency0, currency1, hooks, poolManager, fee, parameters) — with hooks third and tick spacing folded into parameters
Permissions are declared by getHooksRegistrationBitmap() returning 0x0CC1, so no address mining is needed
Accounting is split from the AMM: take() targets the Vault, while the CLPoolManager runs the pool and holds a zero token balance
Callback selectors differ because the PoolKey shape changed: beforeInitialize 0xfecd2159, beforeSwap 0xe592dc93, afterSwap 0x6f6657cb
Infinity's own router and Permit2 deployment replace the Uniswap ones

BalanceDelta packing, the return shapes of both swap callbacks, and take(currency, to, amount) are unchanged and ported verbatim.

LP custodian

Circulating supply for CTO quorum subtracts the balance held by whichever contract custodies pooled tokens — not whichever contract runs the pool. On Uniswap V4 those are the same contract. On Infinity they are not: custody sits in the Vault. Using the pool manager there subtracts nothing and inflates the quorum denominator.

Uniswap V3 — Gnosis

V3 has no hook mechanism, so GraduationManager replaces both hooks and behaves differently in three visible ways:

Fees must be collected. They accrue inside the position; anyone calls collectFees(token) to pull them out before they can be distributed.
Two fee buckets. V3 pays fees in both currencies. Native goes to pendingFees; the token side goes to pendingTokens and is never sold — it is burned or paired back into liquidity.
Different split. 40 / 20 / 40 instead of 30 / 10 / 60, because the deployer and protocol cuts come exclusively from the native side.

There is one static 1% pool fee tier rather than dynamic tiering, no secondary pool, and no per-token pool custodian singleton — each pair has its own pool contract, resolved through the V3 factory at read time.

Cross-Chain Design

$LP24, the protocol token, deploys to the same address on every chain. Each chain's protocol pair is created by a one-shot deploy_protocol_token() call that uses CREATE rather than CREATE2, so the address depends only on the factory address and its internal nonce — which is why the factory's first deployment slot is reserved for it.

Because the same asset trades against four different native assets across five chains — Base and Robinhood share ETH — price divergence between them is arbitrageable. Gnosis, denominated in xDAI, serves as the stablecoin anchor for that network.