Testnet on Base Sepolia: 1 ZRO here is 0.0001 test ETH.
Docs · Contract addresses

Docs · For builders

Contract addresses

Eleven contracts of its own make up Submarine, all on Zero, and its pools run on two more from PancakeSwap Infinity's core, which Submarine deploys there itself. None of them is a proxy, so the code at each address is the code that runs, for good. Submarine is not deployed on Zero yet: the addresses and the network settings are filled in at launch.

Addresses

Once Submarine is deployed, the list below is read live from the API's /health route, which serves the deployment file for Zero's chain ID. Indexing starts at the block the contracts were deployed in.

Checking the live deployment…

The network

SettingValue
Chain id1337
CurrencyZRO, used for gas, trading and fees
RPChttps://testnet.zero.layerzero.network
MainnetScheduled for November 30, 2026

These are Zero's testnet settings from LayerZero's own chain list; its RPC answers only developers LayerZero has let in, and mainnet's aren't public yet. The site sends its own requests through /api/rpc on the same domain. A script or a server can use the RPC directly.

How they fit together

ContractTalks toHolds money?
LaunchpadZroInfinityPools (opens a pool at graduation), Referrals, the treasury, the router (asks who is trading)ZRO raised on every curve, unclaimed creator fees, treasury fees until collected
TokenFactoryLaunchpad, the only contract that may use itNothing. It deploys each token, whose whole supply goes to the launchpad
ZroInfinityPoolsInfinity's CLPoolManager (as every pool's hook) and Vault, Launchpad (pays each token's fee back to its earners and the terminal's cut to the treasury), the router (asks who is trading, for its rank)Fees not yet paid out, as claims on Infinity's vault, and a few wei left from rounding when each pool opened
ZroInfinityVenueInfinity's Vault and CLPoolManager (each trade), ZroInfinityPools (quotes, and paying out the fee after each trade)Nothing between calls
Infinity VaultCLPoolManager, the only app registered on itEvery pool's ZRO and tokens
Infinity CLPoolManagerThe Vault, and each pool's hookNothing. The Vault holds the money
RouterEvery listed venue, Referrals, the treasury, Staking (who is fee-free), partners (their share)Nothing between calls
LimitOrdersRouter, Launchpad (graduation and creator checks), the treasuryEscrow of open orders, and ZRO a wallet refused
CopyVaultRouter (the leader's trades and every copy), Launchpad (token age), each token (its max wallet), the treasury (the copy fee)Followers' ZRO and positions
BuybackVaultRouter (its buybacks), Staking (funding stakers)The treasury
StakingThe Submarine token. The router asks it who is fee-freeStaked tokens, and ZRO still streaming or unclaimed
AgentVaultFactoryRouter, through each vault it makesNothing. Each agent vault holds its owner's ZRO and tokens
ReferralsNothing. It only receivesUnclaimed referral earnings

Every place a token can trade has the same four functions, the IVenue interface: quoteBuy, quoteSell, buy and sell. The Launchpad and ZroInfinityVenue are venues, and so is the Router, which makes "the best price anywhere" one more venue for limit orders and agents. See the contract reference.

Pools on PancakeSwap Infinity

A graduated token trades on a pool on PancakeSwap Infinity, a concentrated-liquidity engine with hooks. Submarine deploys Infinity's core on Zero itself, unmodified, from pancakeswap/infinity-core-bsc-base at commit 7c04695: the Vault, which holds every pool's money, and the CLPoolManager, which runs the pools. ZroInfinityPools is the hook of every Submarine pool: it opens the pool at graduation with one locked position, refuses any other liquidity, and takes the token's fee on every trade. ZroInfinityVenue is how the router trades them. It is separate from the hook because Infinity doesn't call a hook for swaps the hook makes itself.

Why Infinity: Uniswap v4's core is under the Business Source License until 2027-06-15, so running it in production before then needs a grant from Uniswap governance. Infinity's core is GPL-2.0-or-later and may run in production. The two Submarine contracts that import it are GPL-2.0-or-later too.

Submarine's deployer owns the Vault and the CLPoolManager. What that lets it do, and the plan to move it to a multisig, is on Risks.

Set once at deployment

Some links can only be made after both contracts exist. Each of these is a one-shot setter that reverts if called again:

CallWhat it fixes
ZroInfinityPools.setLaunchpadThe only contract allowed to open a pool for a graduated token
Launchpad.setRouterThe router the launchpad and the pools ask for the real trader, for referrals and ranks
BuybackVault.setRouterThe router the treasury buys through
BuybackVault.setBuybackTokenThe one token the treasury may ever buy and burn. Set once the Submarine token launches
BuybackVault.setStaking, Router.setStakingThe staking contract the treasury may fund, and that the router asks who is fee-free
Staking.setTokenThe one token that can be staked. Set once the Submarine token launches
Launchpad.setNotEarningRouter, LimitOrders, BuybackVault, CopyVault, ZroInfinityVenue, Infinity's Vault and Staking, which hold or pass holder tokens through without earning on them. The same list, with ZroInfinityPools and the dead address, is what a max wallet doesn't apply to
Router.setForwardersLimitOrders and CopyVault, the only contracts that may trade in a user's name, so those trades count for the user
Router.finishSetupEnds free listing. Any venue after this waits 2 days in public first

The deploy script lists two venues on the router, the Launchpad and ZroInfinityVenue as "Submarine Pools", both with a router fee of 0, fixed for good: the curve and the hook each take Submarine's 0.4% themselves, less the trader's rank discount, and pay it to the treasury. It also registers the CLPoolManager on Infinity's Vault, the one app the vault serves.

In your own code

Read the live list instead of copying addresses, so a redeploy doesn't break your code:

ts
const res = await fetch('<Submarine API URL>/health');
const { chainId, deployment } = await res.json();
// deployment: { chainId, startBlock, launchpad, tokenFactory, pools, poolVenue, infinityVault, poolManager,
//               router, limitOrders, vault, copyVault, referrals, agentVaultFactory, staking }

pools is ZroInfinityPools, the hook. poolVenue is ZroInfinityVenue. infinityVault and poolManager are Infinity's Vault and CLPoolManager. vault is still the treasury, the BuybackVault. staking is missing from deployments made before staking existed.

The same file is in the repository at contracts/deployments/<chain id>.json, which is what the indexer, the keeper and the site all read. The API's address is filled in at launch.