simplex, 2 months ago

@jamesmarshall @alshafei

Thank you!

On groups, for most public, open-to-join groups e2e encryption is needed to protect participation, not content, so we don't need pairwise ratchets between members here - we're developing the new design based on super-peers that'll do broadcasting. e2e encryption between members can indeed be added later to that design.

For IP address protection, we are currently developing a two-hop message routing protocol: https://github.com/simplex-chat/simplexmq/blob/stable/rfcs/2023-09-12-second-relays.md