Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[V2 Bridges] Add possibility to track events "over bridge" #2422

Open
bkontur opened this issue May 2, 2023 · 1 comment
Open

[V2 Bridges] Add possibility to track events "over bridge" #2422

bkontur opened this issue May 2, 2023 · 1 comment

Comments

@bkontur
Copy link
Contributor

bkontur commented May 2, 2023

Useful e.g. for some dedicated UI/indexer, where it could show the full track of events from source to target:

  • one parachain fires let em_message = xcm::ExportMesage(dest, inner_message);, so we can now track em_message_id (ump/dmp)
  • on BridgeHub ExportMesage is unwrapped and inner_message is sent over bridge, so on the other side we can track just inner_message_id
    • (em_message_id, em_message) -> (inner_message_id, inner_message) -> | BRIDGE | -> (inner_message_id, inner_message)

Possible solutions:

  • e.g. when unwrapping fire event with mapping em_message_id -> inner_message_id (but neither id is unique so this is not exact solution)
  • e.g. add some "unique context id", so we could track flow:
    • (contextId, em_message_id, em_message) -> (contextId, inner_message_id, inner_message) -> | BRIDGE | -> (contextId, inner_message_id, inner_message)
  • e.g. maybe to extend events with XcmContext or use topic somehow?
  • ...

Context:
e.g. polkaholic.io is already tracking (xcm) events: paritytech/cumulus#2468

Relates to: paritytech/polkadot-sdk#1905

@bkontur
Copy link
Contributor Author

bkontur commented May 16, 2023

@EmmanuellNorbertTulbure EmmanuellNorbertTulbure transferred this issue from paritytech/parity-bridges-common Aug 25, 2023
@the-right-joyce the-right-joyce transferred this issue from paritytech/polkadot-sdk Aug 25, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants