Are you an LLM? Read llms.txt for a summary of the docs, or llms-full.txt for the full context.
Skip to content

Multichain EUL

Some EUL deployments use LayerZero OFT adapters. The set of networks, trusted peers, routes, limits, fees, and any preferred hubs are configuration facts that can change. Do not assume every EUL deployment can transfer directly to every other deployment, or that a historical hub-and-spoke proposal still describes current peers.

Ethereum's address files identify the original EUL token and an eulOFTAdapter; other chains may identify a bridged token or adapter. A label such as MintBurnOFTAdapter describes contract behavior, not current connectivity or governance.

Before bridging

  1. Obtain token and bridge addresses from EUL addresses and the linked source files.
  2. Verify the source and destination chain IDs and deployed bytecode.
  3. Inspect the adapter's configured LayerZero peers and enforced options for that exact route.
  4. Use the adapter/bridge quote for fees and limits; do not rely on a copied route diagram.
  5. Confirm the recipient and expected destination token address before signing.
  6. For accounting, reconcile locked canonical EUL with minted/burned remote representations; do not add all chain supplies as independent EUL.

The LayerZero bridge governance proposal is historical rationale, not a live route registry.