Skip to content

Commit

Permalink
docs(develop): no bridge dev info
Browse files Browse the repository at this point in the history
  • Loading branch information
idea404 committed Jun 18, 2024
1 parent a78951d commit 228d3e3
Showing 1 changed file with 4 additions and 2 deletions.
6 changes: 4 additions & 2 deletions docs/site/docs/develop/introduction.md
Original file line number Diff line number Diff line change
Expand Up @@ -24,8 +24,10 @@ xmsg.sender // who sent it (msg.sender of the source xcall)

`omni` is a reference to the [OmniPortal](./contracts.md#omniportal) contract. One portal is deployed on each supported chain. To make interacting with the portal easier, inherit from the [XApp](./xapp/xapp.md) contract.

:::info Only Finalized Cross-Chain Messages are Relayed
:::info Omni is a Cross-Chain Messaging Protocol

`XMsg` can only be relayed to the destination chain once the transaction it belongs to finalizes on Ethereum.
Omni is a cross-chain messaging protocol that allows contracts to send and receive messages across different chains. It is a simple and secure way to interact with contracts on other chains. That means you can call a contract on another chain as if it were on the same chain, and you can receive messages from other chains as if they were sent from the same chain.

However, Omni is not a bridge. If you need to move assets between chains, you will need to use a bridge or implement your own bridge (with a transfer token proxy and liquidity for source and destination rollups).

:::

0 comments on commit 228d3e3

Please sign in to comment.