Launching on Doppler

The Doppler contracts are deployed and enabled on Ethereum, Base and Robinhood Chain. You can launch from Ethereum, Base, Robinhood Chain, BNB Chain and Arbitrum. BNB and Arbitrum are source-only. Existing Pons and Clanker routes remain unchanged. Use GET /omniapps → launchOptions to confirm availability in your API deployment before requesting a quote.

Deployments

Each destination release includes all five source Gateways. All 12 cross-chain routes require LayerZero Labs, Horizen Labs and Luganodes DVNs. Contracts are controlled by the existing chain multisigs. Peers are write-once, initial activation delay is zero, and same-address peers bypass a subsequently configured delay.

Launching

Upload the image and metadata using the existing Omnipad upload flow. Request POST /omniapps/doppler/quote with platform: "doppler", destinationChainId, sourceChainId, initiator, name, symbol, imageURI, metadataURI, and optional description, website, twitter, allocationBps, cliff, and duration.

The API verifies the factory code hash, Gateway/composer bindings and approved upstream modules before quoting. For cross-chain requests it also simulates creation on the destination using a temporary balance override; the user does not need destination funds for that simulation.

For local launches, call launchLocal(request) on the returned composer with quote.value. For cross-chain launches, refresh quoteLaunch(destinationEid, request) and submit DopplerGateway.launch(destinationEid, request) with the returned native fee. Use the Doppler ABI: its request contains a separate tokenURI field and is not interchangeable with the Clanker or Pons request.

ABIs: Gateway, composer, allocation vault.

Creator allocation

Allocation defaults to zero and is capped at 25% (allocationBps: 2500). Positive allocations require a cliff of at least 30 days and a total duration of at least 365 days, including the cliff. The duration must exceed the cliff and cannot exceed 3,650 days. Both schedule fields must be zero when the allocation is zero.

An immutable per-token vault holds the allocation. Nothing vests during the cliff; the allocation then vests linearly until the end of the total duration. The indexed creatorAllocation.vault identifies the vault. Anyone can call claim(), but payment always goes to the original creator. There is no admin withdrawal, shortened schedule or beneficiary replacement.

The remaining supply goes into liquidity. This adapter uses the no-op governance module: receiving creator rewards does not grant token-admin or liquidity-withdrawal powers. Contract-wallet users must control their creator address on the destination chain too.

Markets and fees

This integration uses Doppler's locked Uniswap v4 pool mode with WETH, not an auction or a later graduation step. There is no initial purchase or configurable custom hook. The deployed policy uses a one-billion-token supply and a 1% pool fee; 95% of LP fee shares belong to the creator and 5% to Doppler's protocol beneficiary. These LP shares are separate from the optional token allocation.

Trading uses separate deployments of the shared Omnipad Router contract and a dedicated Doppler trading adapter. Buys wrap native ETH; sells unwrap WETH. Both are local to the token's chain and enforce the user's minimum output. The initial launch fee is 0.0002 ETH and the trade fee is 0.00004 ETH. These fees, pool fees, gas and any LayerZero fee are separate. Read current quotes rather than assuming fixed USD fees.

Existing Omnipad search, FDV, volume, charts, trades, holders and activity endpoints handle Doppler markets. Lifecycle webhooks follow the configured Gateway/composer; trading webhooks filter registered token addresses and pool IDs instead of all network swaps.

Delivery and refunds

Failed external creation reverts the compose transaction and remains retryable. Expired requests or fees exceeding the user's cap instead credit a terminal refund to the creator. Delivered unused ETH is claimable on the destination; source gas and LayerZero fees are not refundable.

Doppler is priority 1 on these three destinations. API/web deployments must include registry releases 5–7 and the corresponding webhooks; no new deployment-address environment variables are needed.