Multi Asset (Sub-)Treasuries

[joepetrowski]

The Vision

High level described in https://forum.polkadot.network/t/collective-based-multi-asset-treasuries/2899

A Treasury can generally be thought of as (1) logic for spending assets, and (2) the assets themselves. The network may have multiple treasuries (e.g. a primary Treasury where inflation goes, but also collective-based treasuries).

• Users can make Treasury spend proposals in any asset.
• The Treasury is able to collect its funds on Asset Hub (e.g. have the Relay Chain DOT sent to AH when needed).
• The logic for a given Treasury "lives" in one place, probably the governance location. As in, for example, the Fellowship's Treasury would be on the Collectives parachain. However, the assets a Treasury holds can exist in many places (many other chains).
• A Treasury can schedule future spends that can be voided by another referendum. This should generally replace bounties.

The Plan

• [x] Primary implementation: https://github.com/paritytech/polkadot-sdk/pull/1333
• [ ] Get subscriptions for Asset Rate https://github.com/paritytech/polkadot-sdk/issues/101
• [x] Add instances of the Treasury pallet with collectives (Fellowship, Ambassador Program, &c.).
• [x] Configure Asset Hub with a computable AccountId for each Treasury and means of recognizing spend origins.
• [ ] UI &c. support.

Related

• Integration with Westend: https://github.com/paritytech/polkadot-sdk/pull/2532
• Integration with Polkadot Fellowship: https://github.com/polkadot-fellows/runtimes/pull/109

[wischli]

Could you please update the first item to the corresponding PR in the Polkadot SDK repository? Thanks!

[Polkadot-Forum]

This issue has been mentioned on Polkadot Forum. There might be relevant details there:

https://forum.polkadot.network/t/opengov-improvements-on-the-technical-level/6578/2