Polkassembly Logo

Create Pencil IconCreate
OpenGov

Notice: Polkadot has migrated to AssetHub. Balances, data, referenda, and other on-chain activity has moved to AssetHub.Learn more

View All Small Tipper

Kusama Asset Hub Treasury - Testing the Payout to a Kreivo Community

inSmall Tipper
2 years ago
treasury
kreivo
xcm
Executed

Following the spirit of Proposal 382 of testing the brand-new Treasury on Kusama Asset Hub, and since we've recently introduced controlling accounts via XCM, we'd like to make a small test:

We transferred 1.1 KSM to the remote treasury account on Asset Hub.

This proposal is expected to spend 1.1 KSM on CuYrHbj4PNqVnpA17o8LDigdNXXYvEU7UaYW3kVyAdQskpE (../Parachain(2281)/Body(1)/Voice on KAH) as the beneficiary.

Once the proposal is executed, we'll submit a referenda in Kreivo, from our community governance. The outcome of that referenda is to send an XCM call to Asset Hub, to execute Balances::transfer_keep_alive to move 1 KSM back to the original sender (me).

We proposed this proof with two goals in mind:

  1. Prove we can execute XCM Calls from our communities anywhere on Kusama Network.
  2. Prove it's possible to make payouts to any XCM Location, not just accounts.

FAQ

Q: Have you ever tried if this works?
Yup, we made some tests using Chopsticks to ensure this is an acceptable behaviour given the current limitations of XCM on Kusama Asset Hub. What we found out is that we could use Balances, but no PolkadotXcm due to the SafeCallFilter, nor use something like Proxy. So, we're kinda limited, but we still want to try using this system with the limitations we have. That's how we designed the scope of this test proposal.

Comments (0)

PleaseLogin to comment

Proposal Passed

Help Center

Report an Issue
Feedback
Terms and Conditions
Github

Our Services

Docs
Terms of Website
Privacy Policy

A House of Commons Initiative.

Polka Labs Private Limited 2026

All rights reserved.

Terms and ConditionsTerms of Website
Privacy Policy