CRTs: block revenue split if CRT is newly created or channel account contains no tokens

[mochet]

Problem

I am pretty sure that I have seen now multiple creators issue a CRT and then immediately begin a revenue share--I think this is partly because the tutorial implies that the user should start a revenue split as the 3rd and final step of the CRT tutorial.

Note in the above screenshot in step 4 it is implied that I should start a revenue split to "complete" the tutorial/progress

In this particular example: https://gleev.xyz/channel/25946?tab=Token

• It appears the user issued a creator token in block 7536073
• It appears the user then issued a revenue split in block 7536089 for a month
• It appears the user who created the CRT then participated in the split: https://joystream.subscan.io/block/7536139 but it is very unclear whether they actually got anything out of it--they possibly got 0.00644 $JOY which makes the entire process totally unviable economically: https://joystream.subscan.io/account/j4SjWEMujQVg9ZyzrbSKM74od8g65VNFTv9JXPpTRuEUV53cz?tab=transfer
• It appears the "current revenue" of the account was zero

This basically means the creator shot themselves in the foot:

• No one bought or can buy their CRT for an entire month
• Their channel account has a balance of zero which makes the revenue split pointless

Note: I am fairly certain I have seen this same thing happen multiple times now

Solution

1. Change the tutorial slightly and perhaps make more visible how many tokens are actually in the revenue split--it should somehow be implied that if the current revenue is below some amount then it isn't really worth starting the revenue split just yet.
2. Add some sort of warning specifically for newly created creator tokens (<7 days)
3. Add some very specific warning for channels that currently have zero balance in their channel account or some very small balance.
4. Perhaps issue a specific warning about 30 day long revenue splits that is more obvious to the end user--this is a very long revenue split and I am not sure that users are fully aware of the implications