Joystream / Joystream/joystream

Distinct actors for distinct roles under one membership

Open
#1,444 0 comments 0 reactions 1 assignee View on GitHub

@shamil-gadelshin is already working on this.

Since Sep 22, 2020.

mainnet_review working-group-pallet
Dominant language
Rust
Stars
1.4k
Forks
116
PR merge metrics
No merged PRs in 30d

Description

A membership is a very valuable asset, as it becomes an entry point for highly rewarded roles as it accumulates social capital. We can make memberships even more robust assets if we enable complex divisions of labor behind a single membership, as it allows organizing ever-greater scope of economic activity under one stable identifier. An example would be where a single membership is controlled by a leader, and then this membership also has multiple roles like storage provisioning, curation, etc. which is occupied by distinct real world actors. The actor controlling the membership has overall control, which can be exercised by using the on-chain key hierarchy.

There is however a big obstacle to doing this in of the current approach. The role key is interpreted both as the way to manage the role, and to act within the role in some context, such as authetnicating for the forum or content directory. This means that a role actor gets the ability to perform abusive actions that go outside of just doing the work. One very salient example is changing the reward account.

An easy solution here is to not use the role key for any such sentistive actions, and instead require the member to do these. The role key is only used to "do the work", so to speak.

┆Issue is synchronized with this Asana task by Unito

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.