Documentation menu

Deployments

Omnisea bridge and representation addresses are deterministic, so every address below is identical on every supported chain. See Deterministic addresses for the integration guarantee.

Contract addresses (all chains)

ContractAddress
OmniseaOFTs - ERC-20 bridge0xA98dF8b908F5a70b8036FD00239E66D9B73c64ad
OmniseaONFTs - ERC-721 bridge0x5c0cFc7B0758e5bedE5E9E3A8BA226591f09dC5b
OFT representation implementation0x6cd48A87251f059D092C241638598780C7A0EeAC
ONFT representation implementation0x17B33D4Aa7dc42F4f8A7E7456C5c3a83CB8d6001

Representation tokens deployed by the bridges also have chain-invariant addresses, computable ahead of time with predictRepresentation(originalChainId, originalToken).

Supported chains

ChainChain IDLayerZero EIDLayerZero EndpointV2Explorer
Base8453301840x1a44076050125825900e736c501f859c50fE728cbasescan.org
Arbitrum42161301100x1a44076050125825900e736c501f859c50fE728carbiscan.io
Polygon137301090x1a44076050125825900e736c501f859c50fE728cpolygonscan.com
BNB Chain56301020x1a44076050125825900e736c501f859c50fE728cbscscan.com
Optimism10301110x1a44076050125825900e736c501f859c50fE728coptimistic.etherscan.io
Tempo4217304100x20Bb7C2E2f4e5ca2B4c57060d1aE2615245dCc9C (Alt)explore.tempo.xyz

Protocol parameters

Configured at deployment:

ParameterValue
Fixed native protocol fee25000000000000 wei on ETH-denominated chains; Polygon and BNB use chain-specific native defaults
Fixed fee-token protocol fee100000 units (0.10 LZD at 6 decimals)
Dynamic protocol fee0% (none)
minTransferGas400000
minCreationGas500000

Live values are always readable on-chain: fixedProtocolFee(), fixedFeeTokenProtocolFee(), minTransferGas(), minCreationGas().

Route configuration

Every directed route is wired with the matching bridge peer on the remote chain and a LayerZero pathway configuration. Peers are immutable once set for an endpoint ID: the same peer can be submitted again as a no-op, but clearing or replacing it reverts. Same-address peers are trusted immediately. A first-time different-address peer is configured in one transaction but remains inactive for the 7-day activation period before inbound messages are trusted.

For messages to Tempo, integrators must buy at least 1500000 executor gas - see Executor options.

Feedback