Multi-bridge Message Aggregation
  • 😇Start here
    • Multi-bridge Message Aggregation
    • Life-cycle of a Transaction
    • Getting Started
    • Links
    • Glossary
  • 🪨Core Contracts
    • Message Structure
    • Multi-bridge Message Sender
    • Multi-bridge Message Receiver
  • 🥅Bridge Adapters
    • What are adapters?
    • Message Sender Adapters
    • Message Receiver Adapters
  • 🔐Security
    • Access Control
    • Governance Timelock
    • Emergency Response
Powered by GitBook
On this page
  1. Bridge Adapters

What are adapters?

PreviousMulti-bridge Message ReceiverNextMessage Sender Adapters

Last updated 1 year ago

Different providers' AMB endpoints require different function signatures for sending and receiving messages between different chains. These functions are specific to each AMB.

To bridge (no pun intended) this gap, adapters act as an intermediary between the core MMA contracts and individual bridge endpoints. Their main purpose is to establish a standardized communication protocol between the core MMA contracts and each individual bridge endpoint.

In order to include an AMB solution in the MMA design, two adapters are required: the , which handles outbound messages from Ethereum to other chains, and the , which handles inbound messages from non-destination chains. These adapters follow the as implemented .

A diagram is available below that illustrates the interactions between the core MMA contracts and an AMB infrastructure. Contracts that live on the source chain (Ethereum) are represented in light grey, while those that live on the destination chain are represented in dark grey.

🥅
Sender Adapter
Receiver Adapter
EIP-5164 standard
here