Joystream / Joystream/joystream

Verified status for channels

Open
#2,586 4 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

crt-v2 metaprotocol post-mainnet project_token qn-hydra-board query-node SP:2
Dominant language
Rust
Stars
1.4k
Forks
116
PR merge metrics
No merged PRs in 30d

Description

Extend metadata standard for channels, importantly, this may require introducing metadata submission extrinsic that only curators can use, as only curators can manage this status. The semantics are entirely social, but they mean something to the effect of this account is real. There should probably be a rationale payload whenever this status is updated.

Also this constraint is probably a wise idea:
https://twitter.com/danrobinson/status/1494210892883398657

Design >
-https://github.com/Joystream/atlas/issues/2091

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.

Research direction

Start by reading the linked design issue, Joystream/atlas#2091, then review how channel metadata and curator-managed status are currently represented. Define the scope for a curator-only metadata submission, its rationale payload, and the linked constraint before implementation; done requires an agreed design rather than an obvious isolated edit.

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.