Runtime: CRTs -- forced revenue splits

[mochet]

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.