Omnisea makes cross-chain ownership work through fixed rules: backing stays reserved for holders, each issuer has separate accounting, and existing assets expand when their issuer opts in.
The vault tracks the original tokens backing each asset. Returning tokens releases that asset’s backing to the recipient through the protocol’s transfer rules. Fees are accounted for separately.
The router, vault and token implementations are fixed at deployment. Peer connections become permanent once registered, preserving the routes an asset relies on.
An asset without an issuer compliance contract starts with the connected chains available at creation. Chains added later become available to that asset when its issuer explicitly enables them.
OFT compatibility, stronger custody boundaries
The OFT standard gives tokens a shared way to move between chains. Non-custodial operation also depends on the permissions behind each deployment. Omnisea builds those protections into its contracts.
Standard OFT deployments give owners and delegates control over peers and message verification settings. Omnisea makes registered peers permanent and uses fixed contract logic, reducing the administrative powers behind an asset’s backing.
Issuers manage transfer fees, new-chain opt-ins and optional compliance. Holder backing remains reserved for protocol transfers; claims pay only accrued fees. Each issuer’s accounting stays separate, even when the original token is the same.
Transfers use LayerZero’s default verification configuration through the shared router. Issuers get a configured path from creation. The full security model explains the defaults, chain finality, underlying-token permissions and optional compliance that remain part of the trust model.
A clear path back
A failed message caught by the router stays available for recovery. Holders can follow its status and choose the next action from the asset page.
Anyone can retry a recorded failure once its cause is resolved. Recovery uses the exact original message, keeping its recipient and transfer details intact.
The designated restorer can request a failed transfer’s return during the first seven days. After that, anyone can help request it. The return always pays the original sender, with source fees already spent.
Source confirmation, destination delivery and any return message each have their own status. Holders can follow progress through to the final receipt.