Omnisea documentation
Your token. Across chains.
Create an Omniasset for your existing token, or build transfers and destination actions into your application. Start with the path that fits your role.
Choose your path
An Omniasset is scoped to an original token and a permanent creator. Create it on the origin; its destination token is created automatically on the first successful transfer or sync.
Build the complete flow
Go from a verified asset identity to a quoted transaction, then follow destination settlement. Each guide explains what to check and what to do when something fails.
Choose the right asset
Identify the origin token and issuer together. Separate official and community-created assets.
Reuse your OFT integration
Understand standard calls, approval targets and Omnisea-specific differences.
Transfer and deposit
Build an authenticated destination vault composer with minimum shares and refunds.
Discover and track
Read indexed assets and messages with cursor pagination and precise settlement states.
Recover a failed transfer
Choose router retry, restore or Endpoint retry from the actual failure state.
Bridge native gas
Use Omnigas, a separate product with its own deployed contracts, route registry and recovery flow.
Documentation directory
Task guides first; exact signatures, events and security assumptions when you need them.