Owner: @Thomas Lavaur

Reviewers: 🟢@Daniel Kashepava 🟢@Youngjoon Lee 🟢 @Mehmet 🟢 @Marcin Pawlowski 🟨@David Rusu

Revision History

Introduction

This document outlines the cross-channel messaging framework. A channel is a reserved identifier where only authorized keys can post messages on-chain, while anyone can read them. Cross-channel messaging allows different channels (including channels representing a Zone) to communicate and coordinate actions (such as Zone state transitions), enabling interoperability while maintaining security and decentralization.

Reference: [1.3.0] Mantle.

Objectives

The primary objectives of this framework are to:

• Enable secure communication between different channels without compromising decentralization.
• Support both synchronous and asynchronous messaging patterns to accommodate different use cases and trust assumptions.
• Provide a standard message format while allowing flexibility for custom implementations.
• Provide atomicity guarantees for cross-channel operations when required.

Requirements

The cross-channel messaging framework must satisfy the following requirements:

• Synchronous operations must provide atomicity guarantees (all-or-nothing execution).
• Asynchronous operations must handle finality periods correctly.
• The framework should be flexible enough to support various channel implementations.

Overview

Cross-channel messaging allows different channels to interact and coordinate. The framework supports two distinct messaging modes.