Cross Domain Messaging (XDM)
Cross Domain Messaging on the Autonomys Network
This guide explains what XDM is and walks you through how to transfer assets between consensus and domain chains.
Introducing Cross Domain Messaging (XDM)
Cross Domain Messaging (XDM) is a core feature of the Autonomys Network that enables secure and seamless communication between independent blockchain domains, such as the consensus chain and specialized domains like Auto EVM. XDM allows these separate blockchains to exchange assets, messages, and data reliably, enhancing interoperability and collaboration across the entire Autonomys ecosystem.
If you want to learn more about the technical nuances of XDM you can find further details in our protocol specs.
XDM Confirmation and Timing
To maintain security, there is a challenge period that has to expire when transferring tokens between domains and the consensus chain. Tokens are not fully available for use until the confirmation time has passed. Study the table below to understand confirmation blocks and rough timings:
| Source | Destination | Confirmation Blocks | Confirmation Time |
|---|---|---|---|
| Consensus | Domain | 100 consensus | ~10 minutes |
| Domain A | Domain B | 14,400 domain | ~1 day |
| Domain | Consensus | 14,400 domain | ~1 day |
Refunds due to a failure to complete an XDM transfer will take 28,800 blocks in total
As long as the XDM is confirmed on the source chain (100 consensus blocks or 14,400 domain blocks) the XDM is able to be relayed and executed (the transfer happens) on the destination chain.
The destination chain generates an XDM response that will be sent back to the source chain after the XDM response is confirmed on the destination chain (100 consensus blocks or 14,400 domain blocks), but the XDM response is mostly a no-op and only useful when the XDM is failed and it is necessary to refund the sender on the sender chain.