Verified assets for issuers

Verified assets give token issuers a clearer route story on Omnisea and a direct share of fixed protocol fees from transfers that use eligible verified asset routes.

Omnisea is permissionless: holders can move supported assets without waiting for an issuer to operate every destination chain. Verification adds an issuer-aware layer on top of that flow. It helps users understand which asset page, route, and representation context the official team recognizes.

What verification means

A verified asset connects an issuer or token team to a specific token on a specific source chain.

That lets Omnisea display better issuer context around the asset:

• the original asset identity
• the chains where representations exist
• the route status and transfer history
• official resources users should review
• whether the issuer or token team has claimed the asset route

Verification is route context. It does not make Omnisea the issuer, broker, custodian, transfer agent, investment recommender, or eligibility gate for the asset.

For OFT representations, verification also gives issuers a clearer operational path for owner-gated representation features. Representation ownership is synced from the original token's owner() on the original chain. Omnisea does not manually transfer representation ownership to teams.

Revenue share

Verified issuers can earn 25% of Omnisea's fixed protocol fee from every eligible OFT transfer that starts from a token address mapped to that issuer.

The split is applied at transfer time:

If no issuer is configured for the source-chain token, 100% of the fixed protocol fee goes to the Omnisea protocol fee receiver.

The share applies to the fixed protocol fee only. Omnisea does not charge a percentage fee on the transferred token amount, and LayerZero messaging fees remain separate infrastructure costs. Pilot terms can be updated prospectively as the program evolves.

Source-chain attribution

Issuer attribution is set per chain and per token address. The mapped token can be either:

• the original token on its canonical chain
• an Omnisea OFT representation on a destination chain

This matters because transfers are source-chain actions. If a holder sends a verified representation from one chain to another, the issuer share depends on whether that source-chain representation address has an issuer configured.

What stays the same

Verification does not change token custody or bridge mechanics.

• Originals are still locked by the bridge on the home chain.
• OFT representations are still minted and burned only by verified bridge messages.
• Issuers do not gain mint, burn, or balance-moving powers over Omnisea representations.
• Representation ownership follows the original chain's current owner() and can be refreshed by original-chain messages, as described in Representations.
• Users still decide whether to bridge, where to bridge, and which asset-specific terms apply.

Review and eligibility

Verification is a pilot review process. Omnisea may ask for official issuer contact, route details, token contract context, and links to asset-specific terms before configuring issuer attribution.

Verification does not decide whether any user may hold, transfer, redeem, trade, or otherwise use an asset. Those questions remain with the user, the issuer, the relevant token contracts, and any third-party venues or networks involved.

Omnisea may decline, pause, or remove verification where a route is unclear, unsafe, misleading, inactive, legally sensitive, or outside the intended use of the program.

Compliance features

OFT representations include Permit by default. Pausable, Blacklistable, and external Compliance are off by default.

If the current synced representation owner wants one of those features, they request it on-chain from the representation. Omnisea can authorize a pending request after review, but Omnisea cannot use the feature. Once authorized, only the current synced owner can pause or unpause, update the local blacklist, set the compliance contract, or disable the feature.

This gives issuers a practical compliance path for assets with issuer-side requirements without giving Omnisea custody-like representation owner powers.

Fallback payouts

The bridge tries to pay the issuer and protocol fee receiver directly during the transfer.

If a payout fails, the transfer still continues. OmniseaFeesManager records the unpaid amount as a liability under the issuer or protocol receiver. It can later be paid through the Safe-controlled core withdrawal path without touching canonical backing. This keeps transfers from reverting only because a fee receiver cannot accept the native gas token or fee token.

Current status

Verified assets are part of the Verified Asset Pilot. Issuers and token teams can now contact Omnisea about claiming a route and share the asset, source chain, target chains, and expected usage path for review.