Joystream / Joystream/joystream
Council can hold XCM fungible assets in treasury
Open
Nobody has claimed this yet.
council-pallet
interoperability
post-mainnet
proposal-system
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Background
Currently, the council can only hold $JOY, this is a bit restrictive, for example
- What if we wanted to the council to be able to hold $DOT, for example to pay for a parachain slot.
- What if someone wants to do a large OTC transaction for $JOY against a stablecoin or something similar.
- What if the council wanted exposure to some $CRT.
Proposal
Introduce new treasuries for such assets that
- can be spent from the council through dedicated funding proposals
- can be spent into by third parties
- can do swaps with third parties, with one asset for another (OTC use case).
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue names no files, tests, or entry points. Start by identifying the council treasury and XCM asset-handling components, then determine how funding proposals, third-party deposits, and asset swaps are represented. Done means the proposal's three treasury capabilities are implemented with tests, but the issue does not define specific acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100