End user spam prevention
When we talk about messaging there is always three different types of messages users send: public, group and private.
Tribute-to-talk would be required to message a user which does not have you in their contact list. I see it as “please, add me as contact, I pay your fee.”.
When someone sends a valid payment and other user accept payment (or we could just add automatically?) then the messages from that contact would appear in the messages list.
The smart contract we have ready accepts some captcha or some sort of challange from the receiver to be accepted, e.g. the same captcha would be shown to both users but the requester would solve it first.
Spam in group chats can be easily mitigated if administrator removes them. But the Spam feature can actually be used to spam against users by joining them in groups.
Tribute-to-talk can prevent it as it would do for private messaging, and the group invitation would be considered a private message.
We could discuss how to make the moderation of group chats a democratic process based on any type of token. It’s possible to create “Public Private Groups”, where joining requires the payment to the democracy (or a single individual).
Spam in chats can be prevented with a visibility stake, which user needs to lock some amount of SNT for some time to users/nodes consider the message valid. A moderation using democracy could be implemented to slash deposit of “bad behavior, such as scammers”, but is not necessary.
Would be possible to allow PoW messages without stake. The PoW should be accounting for the message size, so big messages would require a bigger PoW.
This preventions are “end user”, however status-nodes should not relay invalid messages, and delete messages as they become invalid (user removed deposit)
Transport layer incentivize
This ideas can work together with a incentivize on the transport layer, as
which prevents spam in a lower level and provide incentives in the protocol that would guarantee the availability and continuity of the decentralized service.
I see that all this ideas together would provide a very robust spam protection, better then competitor’s solutions, and accidentally provide income to famous people that use Status…