On this page

Addresses

Omniassets is deployed on seven EVM mainnets. Every supported chain uses the same public core and shared module addresses.

Do not use addresses from archived deployments.

This page covers Omniassets v1 only. Omnipad and Omnigas use separate contracts and independent versions: see Omnipad deployments and Omnigas deployments. Arbitrum, Optimism and Avalanche are not in the current Omniassets v1 registry; older deployments there are not current routes. Arc is not enabled.

Core contract

Most integrations only call this address:

Omnisea
0x7AEEBd64211eB405C081a2085BF712fb5ad2e133

It exposes token discovery, representation lookup, gas-floor reads, quotes, sends, retries, and restores.

Supported networks

Network	Chain ID	LayerZero EID	Core contract
Ethereum	`1`	`30101`	`0x7AEE…e133`
Base	`8453`	`30184`	`0x7AEE…e133`
Polygon	`137`	`30109`	`0x7AEE…e133`
BNB Chain	`56`	`30102`	`0x7AEE…e133`
Robinhood Chain	`4663`	`30416`	`0x7AEE…e133`
Ink	`57073`	`30339`	`0x7AEE…e133`
HyperEVM	`999`	`30367`	`0x7AEE…e133`

Use LayerZero EIDs in contract calls and EVM chain IDs in wallet and RPC configuration.

Contract modules

Contract	Address	Role
`Omnisea`	`0x7AEEBd64211eB405C081a2085BF712fb5ad2e133`	Public entrypoint and accounting
`OmniseaRouter`	`0x89Eb516C53D17D74B3592ebFF5FCf88c4Ca07326`	LayerZero messaging and failed-message recovery
`OmniseaRegistry`	`0x92e357A88836D3Fc907bcD00400eA58CcD87f69f`	Asset identity, metadata, and deterministic deployments
`OmniseaVault`	`0x69C834366e19152fB5F001Ab4188b60666ad688e`	Original ERC-20 backing
`OmniseaFeesManager`	`0x1A930aBBD0fCB9C69c3c081a80c4d51Fb7045290`	Protocol-fee accounting
`OFT` implementation	`0xCC4c81c073203F6BBc09167f68d5567434c053f2`	Implementation for Omniasset minimal proxies

Applications should approve and call Omnisea. Do not approve the Vault or call the Router directly.

HyperEVM exposes the same Omnisea address and transfer interface. Its facade delegates execution across four immutable modules to fit HyperEVM's transaction gas cap; client integrations do not call those modules directly.

HyperEVM-only module	Address
Original-token operations	`0xe09376Edc8a759A6affF2c848f8cb1AD84Ce4d14`
Omniasset operations	`0x2903a7C6822aabf17761a16209290a6efAC4aeC1`
Inbound settlement	`0x300BD9C9395d3aa45CDc66eD154AddEB55381073`
Administration	`0x5D9623BFf476383d275b287815e0B07AaAEDA7e0`

Verify live configuration

Before production use, read the contract on the intended source chain and verify:

localEndpointId() matches the expected LayerZero EID;
endpointNativeToken() matches the fee currency expected by the client;
minTransferGas() and minCreationGas() are reflected in your options;
the selected destination returns a successful quote.

The live contract and successful quote are authoritative for route availability and pricing.