-
Notifications
You must be signed in to change notification settings - Fork 91
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
Drop Tranche location
#1336
Comments
@mustermeiszer @offerijns what do you think? Any objections? |
Sounds good and agreed! |
Great, done in 61f2960. I will also include a migration that sets the |
I am not the biggest fan of having this in 38. But I also know that having intermediate branches is annoying. But could cherru pick the commit and create a PR. Especially given we need a migration. WDYT? |
You are absolutely right. I am always advocating for smaller, self-contained PRs but this time I went against my own principle. I will backport it to a new PR based of the latest main and add the migration part as well. Thanks for the feedback 🤟 |
Currently, the
pool_system::tranches::create_metadata
function defines theAssetMetadata.location
field as follows:I remember suggesting this structure many months back, but as I am updating the codebase to Polkadot v0.9.38 and XCM v3 and bumped into this, I realised we don't need a location for
tranche
tokens at all. Tranche tokens are not to be handled through XCM due to their permissions nature and we are building support for permissioned transfers through Connectors.Suggestion
Basically set
location
toNone
and adjust all tests.The text was updated successfully, but these errors were encountered: