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

Allow TreasuryOrigins to do XCM transfers #1428

Closed
samelamin opened this issue Sep 6, 2023 · 2 comments · Fixed by #1447
Closed

Allow TreasuryOrigins to do XCM transfers #1428

samelamin opened this issue Sep 6, 2023 · 2 comments · Fixed by #1447
Labels
I10-unconfirmed Issue might be valid, but it's not yet known.

Comments

@samelamin
Copy link
Contributor

I raised this in the fellows channel but raising this as a separate issue to hopefully keep track of discussions

We want to build out a way for treasury and spender tracks to support reserve asset transfers

Currently, the only way to do this is through the utility pallet dispatchAs. It is very little work to enable the treasury tracks to use XCM

@github-actions github-actions bot added the I10-unconfirmed Issue might be valid, but it's not yet known. label Sep 6, 2023
@bkchr
Copy link
Member

bkchr commented Sep 7, 2023

Should also be part of the fellowship runtimes repo.

@samelamin
Copy link
Contributor Author

Closing ticket and reverting to fellowship repo. Apologies for the confusion

bkchr added a commit that referenced this issue Oct 12, 2023
This pr resolves #1428.

*Added only to Kusama for now*

I did raise it
[here](polkadot-fellows/runtimes#19) and we
discussed creating a chopsticks test to run an end-to-end test

however, to do that I will need a build agent/custom runner that is
powerful enough to run the build

I will be doing that separately as I still think having chopsticks test
your runtime with each commit will be very powerful and extremely useful
for the ecosystem

For now I have used XCM simulator and replicated what the other reserve
tests do

---------

Co-authored-by: Gavin Wood <github@gavwood.com>
Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: Bastian Köcher <git@kchr.de>
franciscoaguirre added a commit to paritytech/xcm that referenced this issue Jan 25, 2024
This pr resolves paritytech/polkadot-sdk#1428.

*Added only to Kusama for now*

I did raise it
[here](polkadot-fellows/runtimes#19) and we
discussed creating a chopsticks test to run an end-to-end test

however, to do that I will need a build agent/custom runner that is
powerful enough to run the build

I will be doing that separately as I still think having chopsticks test
your runtime with each commit will be very powerful and extremely useful
for the ecosystem

For now I have used XCM simulator and replicated what the other reserve
tests do

---------

Co-authored-by: Gavin Wood <github@gavwood.com>
Co-authored-by: Francisco Aguirre <franciscoaguirreperez@gmail.com>
Co-authored-by: Branislav Kontur <bkontur@gmail.com>
Co-authored-by: Bastian Köcher <git@kchr.de>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
I10-unconfirmed Issue might be valid, but it's not yet known.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants