Omnisea Docs
On this page

How Omniassets work

Omnisea gives an existing ERC-20 a separate cross-chain asset for each creator. Creating an asset does not transfer tokens or change ownership of the original ERC-20.

Create, enable, transfer

  1. The issuer calls createAsset(originToken, compliance) on the origin router. The caller becomes the permanent asset owner.
  2. An asset without an issuer compliance contract includes the router's current peers. Later peers need an owner-approved enableChain call. Assets with an issuer compliance contract start without pre-approved destinations.
  3. Holders approve the asset's OFTAdapter, not the router or vault, when sending original tokens.
  4. Holders call the local facade's standard quoteOFT, quoteSend, and send functions.

The origin adapter locks original tokens in the shared vault. Remote OFTs mint against that backing. Sending remotely burns the net amount; returning to the origin releases it. Remote tokens are created on first successful transfer or sync.

Contracts

ContractRole
OmniseaThe single LayerZero OApp, registry, configuration and recovery router
OFTAdapterPer-asset origin entry point; pulls the approved original ERC-20
OFTPer-asset remote token and IOFT entry point
OmniseaVaultCustody with separate backing per asset and aggregate token solvency checks
OmniseaLensStateless quotes for enable, sync, remote owner actions and restore

An asset's creator is not necessarily the original token issuer. Verify the token and creator before depositing. See Asset identity and Security.