-
Notifications
You must be signed in to change notification settings - Fork 1.6k
No "transfered" events triggered by XcmPallet #3489
Comments
CC @apopiak |
I'm a little confused. |
I miss an event that shows me the actually executed transfer of tokens (exact number) somewhere (e.g. to parachain). Something like For the other direction (transfer parachain -> relay chain) there seems to be no event at all on the relay chain. Background: |
By the way, I still have some understanding problems with the
|
Note that both of those XCMs were malformed and failed. |
Ok. Did you see the |
This is what a successful teleport from the relaychain would like from the sending side: https://westend.subscan.io/extrinsic/0x530307214d7b08d723f4568f982b2af50d62a7f2bbd8db4869bd891a029eb3ea |
The teleport goes out to Westmint which does not seem to trigger events when the funds are received. Will look into improving that. |
Hm, even though the transactions are obviously malformed, they have gone through (Result:Success). How can I tell if and how many tokens have been transferred? |
|
yes, but i see no difference from the malformed extrinsic above |
Yep, would be good. Another problem is the transfer from westmint to westend. There is no indication (on the westend side) that tokens have been received. |
You will notice a difference in structure (e.g. both multilocations are |
yes you are right, i had overlooked the complete flag, thx |
This should be adressed by paritytech/substrate#9425 |
In which runtime it will be active? |
Cross-chain transfers are using the XcmPallet. Unfortunately I cannot find an event to track the transactions. I'm looking for something like the "balances(Transfer)" event. Nothing there like this (on kusama side).
Because of the missing events there is no indication of incoming coins on the kusama side, if ksm sent from a parachain to the relay chain.
Example:
https://karura.subscan.io/extrinsic/135681-2
This transaction is not visible at destination (Hv8cTn...):
https://kusama.subscan.io/account/Hv8cTnQ9aVCQzCBgQRbR8K13uTTb8b7NMsoPApybaUzHnGx
The text was updated successfully, but these errors were encountered: