-
Notifications
You must be signed in to change notification settings - Fork 115
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
Comments
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. |
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. |
This could actually be feasibly triggered by smart contracts |
Smart contracts do not solve anything here. You need some trigger to cause the split, this can either be a user transaction, in which case whether its a smart contract or native runtime transaction is of no distinction. Alternatively one could do some sort of on-chain hook, like |
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
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 notensure
at a system level that this even would actually occur.The text was updated successfully, but these errors were encountered: