Joystream / Joystream/joystream
Idea: Ban CM Proposal
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Currently, CMs are voted via stake and if elected paid a certain amount of tokens by the platform. For this reason, the incentives alone may give reason for a user with enough tokens to repeatedly sit on the council and be inactive.
If a proposal was created and the council agreed that a certain CM was inactive, there could maybe be a proposal type to ban that CM.
There are far more reasons I can think of why this would be a very bad idea rather than a good idea, but it is something to maybe think about.
┆Issue is synchronized with this Asana task by Unito
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 locating the council member and proposal implementations in the Joystream repository, then determine whether the proposed ban mechanism has a defined scope and acceptance criteria. Done would require an agreed design and corresponding implementation and tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- blockchain, rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100