Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Runtime: CRTs -- forced revenue splits #5141

Open
mochet opened this issue Apr 24, 2024 · 3 comments
Open

Runtime: CRTs -- forced revenue splits #5141

mochet opened this issue Apr 24, 2024 · 3 comments
Labels

Comments

@mochet
Copy link

mochet commented Apr 24, 2024

Problem

Some creators/users have expressed a curiosity/desire that revenue splits should be an event that is triggered by the system somehow. The rationale for this seems fairly obvious to basically ensure that a channel does actually activate a revenue split at some point in the future, even though the channel owner cannot claim their own revenue until a revenue split is active there is still some mistrust that a channel owner may be lazy. This seems like a fair argument in favor of allowing this.

Solution

  • I think due to scaling issues this is a very difficult one to tackle--even with some kind of punishment for the channel owner it still does not guarantee they would actually activate a channel split and there is probably some world in which lost accounts could cause issues. I can't envision how it would occur with runtime changes and still allow for the system to scale to significant levels.
  • Perhaps it is possible for the curator group to be given permission to do this somehow, but this does open doors to abuse due to it freezing market activity.
  • One other possible solution is to utilize the recently implemented proxy pallet within Atlas/CRT design flow and allow for a "trusted external party" to trigger a revenue split action on behalf of a channel owner. However, this does not ensure at a system level that this even would actually occur.
@bedeho bedeho added the project_token Project tokens label Apr 24, 2024
@bedeho
Copy link
Member

bedeho commented Apr 24, 2024

Simplest sollution is to allow anyone to trigger splits when channel balance goes above a certain amount. I don't know if I think this is a good idea though, best to at least wait until some real number of people feel a creator is not behaving prosocially.

@bedeho bedeho added the runtime label Apr 24, 2024
@mochet
Copy link
Author

mochet commented Apr 24, 2024

Simplest sollution is to allow anyone to trigger splits when channel balance goes above a certain amount. I don't know if I think this is a good idea though, best to at least wait until some real number of people feel a creator is not behaving prosocially.

That sounds like a very common sense solution, I wish I had thought of that! And agreed it is best to wait a while to see how things materialize with the feature first.

@mochet
Copy link
Author

mochet commented Apr 25, 2024

I suppose another potential solution may be for the $CRT holders to be able to stake their tokens to trigger a revenue split--and if n% of the CRT are staked then the revenue split is forced to begin.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants