Figure 2: Crosschain Protocol - Flow Overview

[findthomas]

About you

Please include your name so your contribution can be publicly acknowledged in the final publication.

Name:
Organization/Company:

About your review

Document: EEA DLT Interoperability Specification
Section: Use the URL to identify the right section of the document.

Your review

Please describe the problem your feature request addresses.

Figure 2 looks good. For clarification to the reader perhaps you could add another new figure that has two (2) applications/users (DApp1 and DApp2) that shows a bi-directional flows. Let’s call it new Figure 3.

The reason is that in real-world transactions (e.g. De-Fi) the human user will be using business applications (DApp1 and DApp2) to interact with each other off-chain, where these applications may be integrated with exiting financial systems (e.g. financial databases; RTGS systems).

Here is a simple example for the basis of the new Figure 3:

User1/DApp1 will initially use the messaging layer to agree upon the transaction with User2/DApp2.

The DApp1 will eventually trigger the smart contract (6th flow in Figure 2), but it may be the case that DApp2 must also do something (e.g. contribute to the multisig; run its own MPC code; etc)

[anaisofranc]

We will add a "Figure 3" to illustrate crosschain flows between two users and two applications in section 5.2 Leveraging Crosschain Function Call.

[anaisofranc]

@weijia31415 - As discussed, find mermaid code attached. The live editor can be used here: https://mermaid.live/edit

mermaid.txt

[anaisofranc]

@weijia31415 will update.