General Message Passing

In the future, we plan on offering the option to select between two messaging modes: Fast and Slow. These modes offer different trade-offs between the risk of block reorganization and overall user experience.

The Fast Messaging Mode is ideal for operations with lower security demands, such as receiving a random number, triggering an in-game event or querying the state of a blockchain. In scenarios where an occasional block reorganization would have minimal impact on the end user, this mode is particularly suitable and provides the best user experience with lowest amount of latency.

On the other hand, the Slow Messaging Mode is recommended for high-stakes use cases that demand robust security and finality guarantees, such as the bridging funds or settling large sums of capital. This mode waits for chain finality on the originating blockchain to ensure maximum finality guarantees.

There are 3 options for general message passing between an L1/L2 and Inco:

  • Externally validated bridges (Hyperlane, Axelar, Wormhole, etc,)

  • Inter-Blockchain Communication (IBC)

  • Native Bridging to Ethereum (via Eigen operator) - more details soon

CaaS is still experimental and the existing option for general message passing is based on a modified version of Hyperlane. These are the supported options:

One way (query & execution):

  • Base Sepolia -> Inco

  • Inco -> Base Sepolia

Bi-directional (query & execution with callback):

  • Base Sepolia -> Inco -> Base Sepolia

Last updated