Joystream / Joystream/joystream
Creator token issuance control
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.4k
- Forks
- 116
- PR merge metrics
- No merged PRs in 30d
Description
Background
We do not know how much abuse there ends up being in issuing creator tokens under false channel profiles, or perhaps how much the platform wants to make such issuing a scarce activity for operational reasons.
Proposal
Allow governance to switch between a normal permissive and arestrictive token issuance policy, as follows, by adding
- new configurable storage field
only_curator_approved_channels_can_issue_token: booleanin content pallet, which can be updated by content lead only. - new field
curators_granted_token_issuing: BooleantoChannelRecord, which can only be updated by curators. - issuing token extrinsic in content pallet checks: ensure
only_curator_approved_channels_can_issue_tokenis true orcurators_granted_token_issuingis true for the given channel.
and test + benchmarks.
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 in the content pallet and locate its configurable storage, ChannelRecord, and token-issuing extrinsic. Trace how content-lead and curator permissions are enforced, then review the pallet's tests and benchmarks. Done means the policy and channel approval state are persisted, authorization is enforced during issuance, and coverage includes tests and benchmarks.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- blockchain
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100