paritytech / substrate-api-sidecar

REST service that makes it easy to interact with blockchain nodes built using Substrate's FRAME framework.

Home Page:https://paritytech.github.io/substrate-api-sidecar/dist/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

When two XCM's are processed in a block, how to strongly correlate `balances.Deposit` event with `messageQueue.Processed` event?

will-yjn opened this issue · comments

For this block: https://kusama.subscan.io/block/22144324, two XCM's are processed. The response is:

    "onInitialize": {
        "events": [
            {
                "method": {
                    "pallet": "balances",
                    "method": "Deposit"
                },
                "data": [
                    "FyE2tgkaAhARtpTJSy8TtJum1PwNHP1nCy3SuFjEGSvNfMv",
                    "150028590711"
                ]
            },
            {
                "method": {
                    "pallet": "balances",
                    "method": "Deposit"
                },
                "data": [
                    "GCNeCFUCEjcJ8XQxJe1QuExpS61MavucrnEAVpcngWBYsP2",
                    "78327426"
                ]
            },
            {
                "method": {
                    "pallet": "messageQueue",
                    "method": "Processed"
                },
                "data": [
                    "0x2e36da6586a9374d34d51c9753af445ea63d6672731ee7d25ac63738022978e9",
                    {
                        "ump": {
                            "para": "2001"
                        }
                    },
                    {
                        "refTime": "293037000",
                        "proofSize": "7186"
                    },
                    true
                ]
            },
            {
                "method": {
                    "pallet": "balances",
                    "method": "Withdraw"
                },
                "data": [
                    "F7fq1inJcCWWCd8sT26fdZkcozCsbJwYAwshtADXqCMGcjd",
                    "3230000000000"
                ]
            },
            {
                "method": {
                    "pallet": "balances",
                    "method": "Deposit"
                },
                "data": [
                    "Ecwo5t2LukeQjGjzVPK7khdjbnpFSxP2iTpjJBsezY8Exzy",
                    "3229921672574"
                ]
            },
            {
                "method": {
                    "pallet": "balances",
                    "method": "Deposit"
                },
                "data": [
                    "GCNeCFUCEjcJ8XQxJe1QuExpS61MavucrnEAVpcngWBYsP2",
                    "78327426"
                ]
            },
            {
                "method": {
                    "pallet": "messageQueue",
                    "method": "Processed"
                },
                "data": [
                    "0xe2d1652ebad3249e2559d96c7320f2bc6eac9bb1601e4c64b629bce0311b97a5",
                    {
                        "ump": {
                            "para": "2090"
                        }
                    },
                    {
                        "refTime": "293037000",
                        "proofSize": "7186"
                    },
                    true
                ]
            }
        ]
    },

In this array, it seems every XCM ends with a messageQueue.processed event. But is this always true? How do I strongly correlates one balances.Deposit event with one messageQueue.Processed event?

I suppose this could a feature request.

Hello @will-yjn
I already addressed plenty of your XCM questions in #1401 and #1404 even though this is not the place to provide XCM training. Also, I already mentioned that these questions are better suited for our Stack Exchange in this comment and this comment, which you seem to have overlooked.

If you would to make correlations related to XCM messages, you are free to do so by parsing XCM messages and draw your own conclusions. In this repository, our role primarily involves explaining the functionalities of related endpoints and assisting with any reported bugs or proposed new features.

Finally, I will close this issue as I haven't identified any feasible feature requests or bugs.