From 228d3e391c812a185a9d55adae27605f60992ad0 Mon Sep 17 00:00:00 2001 From: idea404 Date: Tue, 18 Jun 2024 13:52:09 +0200 Subject: [PATCH] docs(develop): no bridge dev info --- docs/site/docs/develop/introduction.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/site/docs/develop/introduction.md b/docs/site/docs/develop/introduction.md index c99497bde..bd98e135b 100644 --- a/docs/site/docs/develop/introduction.md +++ b/docs/site/docs/develop/introduction.md @@ -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). :::