RLN roll out in Status

[fryorcraken]

@haelius

Is this necessarily the case? If we deploy paymasters or a stealth commitment scheme in the interim, I imagine it would be possible to hide the entire RLN membership registration and distribution mechanism from end users.

Interesting approach. Should definitely be put on the table.

@haelius

Communities suggestion for 1:1 chats that will minimise the impact of the change in the same way? RLN-controlled chats can be rolled out as a new type of DoS-protected chat only available to users that have updated the app. It would be logically & visually separate from your “legacy chats”.

Totally valid approach. But it’s inherently more work as there are more UX/UI work and decision around handling legacy vs new.

Whereas it would be straightforward for communities (it’s just a new community) and less dependency on UI/UX work.

@haelius

Since we already have a solution for Communities that provide decent levels of DoS protection and scalability (assuming statically-sharded communities), my inclination is to stick with the current roadmap of providing minimum viable scalability/DoS protection for 1:1 chats with RLN first.

Good point.