Launching on Clanker
Omnipad supports launching on Clanker on Base and Arbitrum from Ethereum, Robinhood Chain, Base, Arbitrum and BNB Chain. Launches on the same chain are local; other routes use LayerZero. Use the dedicated Clanker contracts below, not the Pons Gateway.
Deployments
| Contract | Base (8453, EID 30184) | Arbitrum (42161, EID 30110) |
|---|---|---|
| Gateway | 0x78Da39d825E0ac927fE3A669B3816Dd94f989A52 | 0x8a396d91a5A5f2Beae12567c7a122Fa9DabbdECf |
| Composer | 0x87c753AFD84d1E1298C4DD873ff93c74D6adb31E | 0xbda5b41Bfb585fcf8f447ec654138CB9d27104f3 |
| Trading Router | 0x9A05206300C0bF20E53cfE453BF2800996aC6058 | 0x0d20337BcEB75bF9f50f8831f106778e2aE058F5 |
| Trading adapter | 0xB8Cb10e500E86235f42e7daf821f7214ceC52217 | 0xeB90c918294CC6a248C0Af9f84c203160556405e |
These contracts are verified on their chain explorers. Registry release 3 targets Base; release 4 targets Arbitrum. Both use the existing chain multisigs. Required DVNs are LayerZero Labs, Horizen Labs and Luganodes.
Additional source-only Gateways (no Clanker composer or trading deployment on these chains):
| Source | Chain ID | EID | Gateway |
|---|---|---|---|
| Ethereum | 1 | 30101 | 0x86af111C5BF12d969A6c78f81806B9B5B36F976B |
| Robinhood Chain | 4663 | 30416 | 0xbda5b41Bfb585fcf8f447ec654138CB9d27104f3 |
| BNB Chain | 56 | 30102 | 0x1ea4bc151bb9084baf6901041f6168bac0ee9acd |
Ethereum and BNB Gateways are explorer-verified; the Robinhood Gateway is verified through Sourcify. All source Gateways connect to both Clanker destinations. BNB users pay the source quote in BNB; the quote includes funding the destination fee in ETH. Use quote.value, not a fixed source-chain amount.
Launch flow
GET /omniapps includes Clanker entries in launchOptions, each with a destination and supported source chains. Upload the token image through the existing upload endpoint, then request POST /omniapps/clanker/quote with platform: "clanker", destinationChainId, sourceChainId, initiator, token details and optional allocation fields.
For a same-chain launch, submit launchLocal(request) to the returned composer with the quoted value. For a cross-chain launch, call ClankerGateway.launch(destinationEid, request) with the freshly quoted LayerZero fee. Chain IDs select wallets; destination EIDs select LayerZero routes. Never use the Pons request ABI for Clanker.
ABIs: Clanker Gateway and Clanker composer.
The connected caller becomes token admin, LP-reward admin and recipient, and creator-allocation beneficiary. A contract wallet must be controlled by the user on the destination too; matching addresses alone do not establish ownership there.
Creator allocation
The optional allocation defaults to zero. The contract enforces:
| Field | Unit | Rule |
|---|---|---|
allocationBps | Basis points of total supply | 0–2500 (0–25%) |
cliff | Seconds from creation | At least 2,592,000 (30 days) when allocation is positive |
duration | Total seconds from creation, including cliff | At least 31,536,000 (365 days), greater than cliff, at most 315,360,000 |
With zero allocation, both schedule fields must be zero on chain. With positive allocation, the API defaults to 30 days / 365 days. This follows the Bankr launch schedule: the cliff is included in the year. The Clanker vault receives a 30-day lockup followed by 335 days of linear vesting. Nothing unlocks before the cliff. Longer schedules are allowed; shorter ones are not.
The rest of the supply funds liquidity. There is no initial purchase or arbitrary extension selection. The allocation is held in Clanker's vault, not the Omnisea composer. Its admin is the creator. The token page shows the indexed allocation percentage and schedule.
Trading and tracking
Clanker pools trade on Uniswap v4 from creation; there is no Pons-style graduation step. Omnipad uses a dedicated trading adapter for registered token/WETH pools. It wraps native ETH for buys and unwraps WETH proceeds for sells. Trading is local to the token's chain and uses the shared Router's flat fee and minimum-output protection.
The pool configuration uses a 1% static pool fee and WETH-denominated creator rewards. Omnipad's launch fee is initially 0.0002 ETH and its trading fee is 0.00004 ETH. These are native-token amounts, not USD-pegged fees, and are separate from pool fees, gas and LayerZero fees. Read current quotes before signing.
Launch events, market data, search, charts, holders, activity and recovery use the existing Omnipad endpoints. Lifecycle webhooks watch configured Gateway/composer addresses; trading webhooks watch only registered tokens and pool IDs. Allocation metadata is retained in the indexed request.
Factory failures revert composition and remain retryable. Expired requests or a protocol fee above the user's cap become terminal refund credits. The creator can claim delivered unused value on the destination; source gas and LayerZero fees are not refundable.
Consult launchOptions before integrating a route; it reflects the API's currently enabled deployment registry.