DATx Technical Innovations

How does DATx realize the dream of cross-chain interoperability on the DATxChain?

Well, today we’re going to explore the DATxChain infrastructure’s key components, the parts that make the DATx cross-chain solution so elegantly simple:

The Meridians Plugin is responsible for ensuring PBFT (Practical Byzantine Fault Tolerance) for DATxChain’s cross-chain functions. It integrates cross-chain communication, on-chain monitoring, transaction verification, signature collection, and other cross-chain related functions. It is part of the DATx client.

When a user withdraws their off-chain assets from the DATx ecosystem, the Meridians Plugin will initiate a withdrawal request. It then collects signatures from CCVs. Once at least 15 CCVs sign off on the request, reaching the PBFT consensus, the Meridians Plugin will begin initiating the withdrawal and transfer off-chain assets held in the MSE Wallet (multi-signature escrow wallet) back to users’ off-chain wallets.

Figure 1. The withdrawal process, initiated by depositing mapped assets to the MASC. The Meridians plugin verifies the bound off-chain wallet, sets up the withdrawal request, collects CCV signatures, and initiates the withdrawal request.

The MASC (mapped asset smart contract), as the name suggests, is a smart contract in charge of on-chain mapped assets (dBTC, dETH, dEOS, etc). It resides on the DATxChain.

The MASC creates mapped assets, which correspond with the off-chain assets a user has bound to the DATxChain, or deposit. The MASC is also responsible for binding the user’s off-chain wallet and checking it to ensure it distributes the equivalent amount of mapped assets. To initiate the withdrawal process, users send their mapped-assets back to the MASC.

Figure 2. The MASC during the deposit process. Note the LSP monitoring of off-chain transactions to the MSE.

The LSP (listening server port) is active module on Anchor Nodes that monitor both on-chain and off-chain transactions.

For deposits, users transfer their off-chain funds to the MSE Wallet. The LSP continually monitors for off-chain transactions going to the MSE Wallet. This Anchor Nodes to form a consensus on whether or not a transaction happened and how much was transferred. For withdrawals, users transfer their mapped assets from their DATxWallets to the MASC.

Figure 3. LSP during the deposit process monitors transactions from the user to the MSE Wallet, ultimately ending with the MASC transferring mapped assets to the user’s DATxWallet.

These some of the key components of the DATx infrastructure which make cross-chain interoperability possible. Next month, we will be releasing the DATx Yellowpaper which will go even further in detail on DATx infrastructure, so stay tuned!