# Multi-bridge Message Aggregation

<figure><img src="/files/ZlDmOjrTVbpQSbLqVmNu" alt=""><figcaption><p>Bridge world with MMA.</p></figcaption></figure>

**Multi-bridge Message Aggregation (MMA) is an additive security module for cross-chain communication.** It utilizes multiple [Arbitrary Messaging Bridges](https://blog.li.fi/navigating-arbitrary-messaging-bridges-a-comparison-framework-8720f302e2aa) (AMB) to send messages from one EVM chain to another EVM chain.

Instead of relying on a single AMB, MMA allows the message sender to relay the message through multiple AMBs. This way, even if one AMB is exploited, no malicious actions can be executed on the destination chain.

This approach can offer the following key advantages:

1. **Increases** **safety guarantees** by verifying cross-chain messages across multiple bridges.
2. **Improves liveness and censorship resistance** guarantees by providing redundancy through multiple bridges.
3. **Increases flexibility** by allowing for a more seamless integration of new cross-chain protocols and a less disruptive phasing-out of defunct protocols over time. This also **reduces vendor** lock-in, especially when coupled with cross-chain standard interfaces such as [ERC-5164](https://eips.ethereum.org/EIPS/eip-5164).
4. Offers a common architecture for cross-chain governance across disparate Uniswap Protocol deployment chains. This can reduce friction, delays, and risk associated with new Uniswap Protocol deployments, as well as with proposing cross-chain governance actions.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://multi-message-aggregation.gitbook.io/multi-message-aggregation/start-here/multi-bridge-message-aggregation.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
