Joystream / Joystream/joystream
Generalized decision method for proposals
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Right now we only have binary decisions for proposals, however, there are decisions that may be needed which go beyond this. For example
- Set the parameter value to one among N values
- Pick M candidates to accept among N alternatives that applied
We should extend the proposal engine to account for these two decision forms as well. One decision method, which also subsumes normal binary decisions, as well as the two above, is the following:
There are N => 2 alternatives, there will be exactly N > M >= 1 winners, and each decision-maker has to provide a ranked list of M >= K >= 1 alternatives. There are many ways to decide the winners, see
The proposal execution code only receives the identifiers for the M winning alternatives, and may do anything with this.
If we support this, we may, in the end, drop the normal binary vote, as it is just a special case. of N=2 and M=K=1.
┆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
Start by locating the proposal engine and its proposal execution code, then trace how binary decisions are represented and passed to execution. Define the supported ranked-alternative inputs and winner identifiers, including the stated N, M, and K constraints, and confirm binary voting remains representable as the special case. Done means the engine supports the requested decision forms and execution receives the winning identifiers.
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
- 25/100