> For the complete documentation index, see [llms.txt](https://kawa-fi.gitbook.io/kawa/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kawa-fi.gitbook.io/kawa/overview/xcm-aggregator.md). # XCM Aggregator Kawa's Cross-chain Message (XCM) infrastructure focuses on enhancing the security and resilience of cross-chain asset transfers, overcoming the vulnerabilities and complexities associated with traditional XCM protocols. Kawa achieves this by employing a proprietary XCM Aggregation protocol, which leverages multiple XCM protocols to establish a quorum. ### XCM Aggregator The XCM Aggregator serves as the core of Kawa's cross-chain messaging infrastructure. By utilizing multiple XCM protocols simultaneously, it ensures that the compromise or exploitation of a single bridge or XCM protocol doesn't affect the overall integrity of Kawa.\ \ Kawa aims to utilize on launch three well-known XCM protocols: **Axelar**, **Layer Zero**, and **Wormhole** ### **Key Features** * **Increased Security**: Exploiting or compromising enough XCM protocols simultaneously to maliciously influence consensus is significantly more challenging than exploiting a single protocol. * **High Availability**: The aggregator ensures high liveness, minimizing the risk of critical security issues due to downtime. * **Scalability**: As XCM Aggregator volumes increase, transactions can be batched to enhance security while minimizing costs for users. * **Interoperability**: The XCM Aggregator can be utilized by other cross-chain applications, becoming a new DeFi primitive and industry standard for cross-chain messaging. ### Quorum Kawa's XCM Aggregator contracts communicate with each other via multiple XCM (Xn) infrastructure simultaneously. A quorum (Qn) must be met for a transaction to be confirmed and the user state updated. ### Future Developments Kawa plans to continue enhancing its XCM Aggregator by incorporating additional protocols, expanding interoperability with other DeFi platforms, and refining its security features in response to the evolving DeFi landscape. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## 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, and the optional `goal` query parameter: ``` GET https://kawa-fi.gitbook.io/kawa/overview/xcm-aggregator.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.