Omnipad
Omnipad lets your application create tokens on supported launchpads and trade the resulting tokens. Pons V2 on Robinhood Chain is the first integration.
Current release
The active deployment version is 2. Launch on Pons from Ethereum, BNB Chain, Arbitrum or Base, or launch directly on Robinhood. Buying and selling execute locally on Robinhood; the trading Router does not accept cross-chain trade requests. Previous-release Gateway addresses must not be used for new v2 launches.
| Contract | Chain ID | Address |
|---|---|---|
| Source Gateway | 8453 (Base) | 0xf8F68CeC81BEBa31fEb01EE80ae5bC0d7FFE6EB4 |
| Source Gateway | 1 (Ethereum) | 0x222Be77974CCFa0425B3EFcbf840ee3FB31ae9a8 |
| Source Gateway | 56 (BNB Chain) | 0x91258576eAb49FF271Bf08E4aE71e872DF148256 |
| Source Gateway | 42161 (Arbitrum) | 0xc94ACe9b410cA5585c51211DCF5002B628b02693 |
| Destination Gateway | 4663 (Robinhood) | 0x0e0A6C4cDBac768145697DEC8f888aDaF0cC467f |
| Pons composer / local launch entrypoint | 4663 | 0xE4818ED8b7829E02f35415D85BE7944D3F517fBA |
| Trading Router | 4663 | 0x7d8c90Ca9A28D041e07824D1209d6Abc3178C0F7 |
| Pons trading adapter | 4663 | 0xcfc8213dCB3218732446381BaE76cb7A81289f5E |
| Pons V2 factory | 4663 | 0x7eD598BcEf8bd9Edd8C97A195C6d13f40801EC7e |
LayerZero EIDs are Ethereum 30101, BNB Chain 30102, Arbitrum 30110, Base 30184 and Robinhood 30416. Chain IDs select wallets and RPCs; EIDs identify LayerZero routes. Pons remains on Robinhood; the other Gateways are launch sources, not additional Pons destinations.
These are non-upgradeable deployments, not UUPS proxies. The checked-in api/config/omnipad.json selects the active version. GET https://api.omnisea.io/omniapps exposes API availability and configuration. Pin the expected addresses in your client and reject a response that points elsewhere. Older indexed requests retain their deployment version for recovery.
Download integration ABIs
- Gateway ABI: cross-chain quote and launch.
- Pons composer ABI: local launch, status and refunds.
- Trading Router ABI: buy and sell.
- Pons factory integration ABI: launch economics and availability reads.
These JSON arrays work with ethers or viem. Download and pin them with your integration rather than relying on an unversioned ABI at runtime.
Fees and custody
Read protocolFee() on the composer and flatFee() on the trading Router. The deployment was configured with a 0.0002 ETH launch fee and 0.00004 ETH trading fee, targeting approximately $0.50 and $0.10 at deployment. They are native amounts, not USD pegs. Pons fees and network gas are additional; cross-chain launches also pay LayerZero. Always use live quotes.
The composer holds accrued protocol fees and claimable refunds. The Router holds accrued trading fees. They are not arbitrary custodial wallets or generic call executors. Trading returns outputs to msg.sender; a contract caller must forward those outputs to its intended user.
Choose an integration
- Launch on Pons: upload metadata, quote and submit either launch mode.
- Buy and sell: local trades with approval, slippage protection and a fee cap.
- API and tracking: launches, market data, pagination and recovery.
- Omnigas: fund a wallet on Robinhood before a separate local trade.