From 0e29eff76bad9e90524aae4d0b9a4975afc13878 Mon Sep 17 00:00:00 2001 From: Oliver Tale-Yazdi Date: Wed, 25 Sep 2024 23:45:03 +0200 Subject: [PATCH] Mention that MQ processed events can happen in any phase (#6265) * Update build-integrate-assets.md * More verbose and linebreak Signed-off-by: Oliver Tale-Yazdi --------- Signed-off-by: Oliver Tale-Yazdi --- docs/build/build-integrate-assets.md | 11 ++++++----- 1 file changed, 6 insertions(+), 5 deletions(-) diff --git a/docs/build/build-integrate-assets.md b/docs/build/build-integrate-assets.md index b0ae902fa5fe..31f3c7095d9f 100644 --- a/docs/build/build-integrate-assets.md +++ b/docs/build/build-integrate-assets.md @@ -210,11 +210,12 @@ account via XCM. However, in some cases, it may be interesting to identify the c that emitted the relevant `balances.minted` event. This can be done as follows: 1. Query the relevant chain `at` the block the `balances.minted` event was emitted. -2. Filter for a `messageQueue(Processed)` event, also emitted during block initialization. This - event has a parameter `Id`. The value of `Id` identifies the cross-chain message received in the - relay chain or in the Asset Hub. It can be used to track back the message in the origin parachain - if needed. Note that a block may contain several `messageQueue(Processed)` events corresponding - to several cross-chain messages processed for this block. +2. Filter for `messageQueue(Processed)` events. These can be emitted during any phase of the block, + not just initialization. This event has a parameter `Id`. The value of `Id` identifies the + cross-chain message received in the relay chain or in the Asset Hub. It can be used to track back + the message in the origin parachain if needed. Note that a block may contain several + `messageQueue(Processed)` events corresponding to several cross-chain messages processed for this + block. #### Additional Examples of Monitoring XCM Transfers