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

Fix for compatibility with V4 #6503

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

yrong
Copy link
Contributor

@yrong yrong commented Nov 15, 2024

Description

Our smoke tests transfer WETH from Sepolia to Westend-AssetHub breaks, try to reregister WETH on AH but fails as following:

https://bridgehub-westend.subscan.io/xcm_message/westend-4796d6b3600aca32ef63b9953acf6a456cfd2fbe

https://assethub-westend.subscan.io/extrinsic/9731267-0?event=9731267-2

The transact call encoded on BH here in V4

0x3500020209079edaa8020300fff9976782d46cc05630d1f6ebab18b2324d6b1400ce796ae65569a670d0c1cc1ac12515a3ce21b5fbf729d63d7b289baad070139d01000000000000000000000000000000

can't be decoded on AH with V5.

0x3500020209049edaa8020300fff9976782d46cc05630d1f6ebab18b2324d6b1400ce796ae65569a670d0c1cc1ac12515a3ce21b5fbf729d63d7b289baad070139d01000000000000000000000000000000

Issue initial post in https://matrix.to/#/!qUtSTcfMJzBdPmpFKa:parity.io/$RNMAxIIOKGtBAqkgwiFuQf4eNaYpmOK-Pfw4d6vv1aU?via=parity.io&via=matrix.org&via=web3.foundation

@yrong yrong changed the title For compatibility with V4 Fix for compatibility with V4 Nov 15, 2024
@yrong yrong marked this pull request as ready for review November 19, 2024 22:26
@yrong yrong requested a review from a team as a code owner November 19, 2024 22:26
Copy link
Contributor

@vgeddes vgeddes left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can you be more specific about what the problem is? The element link does not seem to be working for me.

XCMv4 and XCMv5 each have their own NetworkId with different encoding layouts, and they need to be explicitly converted to each other using From or TryFrom traits.

So then surely BH needs to take care to send an XCM to AH that is in the correct format?

prdoc/pr_6503.prdoc Outdated Show resolved Hide resolved
@acatangiu
Copy link
Contributor

The PR makes sense if we have v4::NetworkId entries in storage that we want to directly interpret as v5::NetworkId entries without migrating them.

Is this the case?

Co-authored-by: Adrian Catangiu <adrian@parity.io>
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

Successfully merging this pull request may close these issues.

3 participants