Here’s what you need to know about XCM integrations. XCM integrations are already happening all over the Polkadot & Kusama universe. But what is this acronym and what does it stand for? Here’s an explainer of what it does and why is it so important for Integritee and the ecosystem we’re in.
In layman’s terms, it can be said that XCM — cross-consensus messaging — is a universal language that enables different systems to speak to each other. It is supposed to be general enough to be widely used across growing ecosystems such as Polkadot. Even if a said system doesn’t fully comprehend the entire message, it is expected that some of those elements are “readable”.
It represents a new era of communication between parachains. Among (many) other things, Polkadot is designed to support and link projects, so it’s fair to say communication is key. These projects — parachains — are connected to the Relay Chain — Polkadot’s L0 security chain.
Kusama — Polkadot’s Canary network — follows the same structure. Integritee is one of such parachains on Kusama, and the XCM’s main function is to link parachains together so they become interoperable. These connections open up a whole new world of possibilities for Polkadot, Kusama, and its parachains in terms of functions and offers, as they enable different projects to leverage each other’s singularities.
There is already a high degree of communicability within the system, but the goal is to keep going and have a completely interoperable network where projects can benefit from each other’s characteristics.
XCM is very useful for networks looking for more reach and exposure. Being listed on major platforms, or having their token available on other networks are just two of the advantages. Some integrations are made for specific purposes, like enabling the use of unique technology or application from a certain network. The XCM integration between Integritee and Moonbeam has been completed. You can read about it here.
It’s important to understand that XCM is different from XCMP: the first is a language, and the latter is the messaging protocol itself, which actually allows messages to be sent between parachains. This cross-consensus messaging format enables information to be passed on from one parachain to the other through an HRMP channel. In some cases, this channel is bidirectional (between parachains), and in others, unidirectional (from a specific parachain to the other).
Integration is made once both parachains finalize all the technical steps. Some integrations on Polkadot and Kusama have already been completed, and more are expected to come, including with Integritee. These links are vital for the whole ecosystem, as it’s supposed to be interoperable and able to communicate internally.
Why don’t we just stick to the traditional messaging format?
This is still possible, but it is much more time-consuming and tiresome when compared to XCM. Different chains speak different languages, so traditional communication between parachains means a system would have to learn different languages when wanting to send the same message to several parachains.
Looking to starT a project with us or just want to RECEIVE news?
Subscribe to our newsletter
The only thing we need to tell you in advance is that you need to agree to our terms and conditions to sign up!
Thank you! Your submission has been received!
Oops! Something went wrong while submitting the form.