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: explicitly use passed in dest locations for bridgeTransfers #406

Merged
merged 4 commits into from
May 22, 2024

Conversation

marshacb
Copy link
Contributor

@marshacb marshacb commented May 21, 2024

Changes

  • removed assumption that a bridge transfer location of Polkadot (eg. {"parents":"2","interior":{"X1":{"GlobalConsensus":"Polkadot"}}}) should be intended as Polkadot AssetHub ( e.g. {"parents":"2","interior":{"X2":[{"GlobalConsensus":"Polkadot"},{"Parachain":"1000"}]}}). Instead relies on the location value passed in
  • updates AssetHub bridgeTransfer example dest locations to explicitly be global consensus AssetHub locations (e.g. {"parents":"2","interior":{"X2":[{"GlobalConsensus":"Polkadot"},{"Parachain":"1000"}]}}) rather than the relay chains location
  • updated SystemToBridge integration tests to explicitly provide AssetHub locations for p<>k bridge cases
  • updated assetHubWETHToRhala example to a transferAssetsUsingTypeAndThen call in order to explicitly set AssetHub as the reserve location
  • added parseLocationStrToLocation util function

closes: #407

marshacb added 3 commits May 21, 2024 13:11
…s AssetHub locations rather than the relay chains location

removed assumption that polkadots location should be intended as polkadot assethub
added parseLocationStrToLocation util function
updated SystemToBridge tests to explicitly provide AssetHub locations for polkadot kusama bridge cases
@marshacb marshacb changed the title fix: update bridgeTransfer dest locations to explicitly be global consensu… fix: update bridgeTransfer location parsing May 21, 2024
@marshacb marshacb changed the title fix: update bridgeTransfer location parsing fix: explicitly use passed in dest locations for bridgeTransfers May 21, 2024
@marshacb marshacb requested review from TarikGul and bee344 May 21, 2024 17:39
Copy link
Contributor

@IkerAlus IkerAlus left a comment

Choose a reason for hiding this comment

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

LGTM

@marshacb marshacb merged commit b3a199a into main May 22, 2024
20 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

BridgeTransfers should explicitly use passed in location values
3 participants