Messaging and Alternatives

Cross-chain messaging is a layer that links an action in one network with an action in another network. It is needed when an operation consists of multiple transactions in different blockchains and they need to be reliably linked into one workflow.

How Messaging Differs from Bridge

• Bridge is responsible for transferring value or assets
• Messaging is responsible for message delivery and provable state linkage between networks
• In real protocols, these parts are often combined, but for wallet architecture it is important to separate responsibilities

Message Lifecycle

A typical cycle looks like this:

1. Transaction in the source network records an event and message parameters
2. Protocol confirms the message according to its security model
3. In the target network, a linked action is executed (mint, unlock, contract call, state update)
4. Wallet updates operation statuses based on network and indexer data

Related statuses and execution steps are described in the Cross-chain Workflow section.

Trust Models and Security (Brief)

In practice, three popular approaches are encountered:

• Light-client or proof-based approaches - strong cryptographic connectivity, but more expensive and complex
• Validator networks - faster to integrate, but there are trust assumptions to validators
• Separation of oracle and relayer roles - reduces the risk of a single point of compromise, but still requires trust in external infrastructure

Cost and Delays

The price of a cross-chain step usually consists of:

• fees of the source and target networks
• message delivery cost (depending on the protocol)
• additional gas for processing in the target contract
• confirmation and finality delays

How This Is Used in SAI Wallet

SAI Wallet abstracts the messaging layer so that the user sees a unified scenario, and the application can change providers and routes without UX changes.