Joystream / Joystream/joystream

Content directory imposed CRT constraints

Open
#4,151 10 comments 0 reactions 1 assignee Claimed by @dobertRowneySr View on GitHub
content-pallet crt-v2 project_token runtime
Dominant language
Rust
Stars
1.4k
Forks
116
PR merge metrics
No merged PRs in 30d

Description

# Background
One of the main issues with CRTs on DeSo was lack of long term alignment between issuer and buyers. Unfortunately for them, they did not have vesting, which we do, but we can do even better: governance.

# Proposal
Allow lead, or council, to set global constraints on CRTs that can be issued, e.g.

* max daily number
* only channels that are verified (is this in state?) and/or some how at a given tier (permission levele?)
* min vesting schedule for issuer
* whether permission less demonstrability is ok
* max patronage
* etc.

This is not a spec, it's an idea, implementer should come up with concrete design before starting.

Probably also constraints on [sale terms](https://github.com/Joystream/joystream/issues/2362#issuecomment-1059012676) and other parameters is also sensible. Implementer should provide exhaustive list of constraints.

┆Issue is synchronized with this [Asana task](https://app.asana.com/0/1201958687417145/1202777295294353) by [Unito](https://www.unito.io)

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.