Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Added XCM transfers monitoring with minimal changes to the internal API. The goal was to integrate XCM pallet monitoring alongside the existing Balances pallet monitoring based on the Transfer event.
The XCM format is evolving to be more flexible, allowing extrinsics to take custom XCM messages as input. Currently, the processing is tied to a standard message format created by the extrinsics themselves. The extrinsics operating with the custom messages like
execute
andsent
are not widely used yet, except for thetransfer_assets_using_type_and_then
.Overview
extractTransferInfoFromEvent
+isTransferEvent
(both Balances and XCM).networkId => chainInfo
._balanceTransferHandler => _transferNotificationHandler
.extractTransferInfoFromEvent
dependency injection.The event processing logic is described on the picture below.
Tests
Added integration tests based on the Polkadot and Kusama chains.