To increase user's anonymity, we suggest users securely communicating over Waku to use a secret in order to frequently and deterministically change contentTopic - ideally, at every round trip communication.
However, this might have different drawbacks, since, for example:
users need to listen to all message received on the corresponding gossipsub topic to pick the ones with the contentTopic of their interest;
can use filter queries to retrieve messages in their interests, but this might affect their anonymity since the filter node will match the user requesting the filter to the one communicating (in encrypted form) over that contentTopic.
For such reasons, possible trade-offs should be investigated, especially if target lightweight devices.
Possible future directions
In the future, we might address this problem by implementing private filter queries using techniques such us oblivious transfer and private information retrieval. With these, a filter node becomes able to answer users' filter queries without learning the contents of the filter request made.
Acceptance criteria
[ ] Perform an anonymity/performance/resources impact analysis for (frequent) contentTopic changes as per 37/WAKU2-NOISE-SESSIONS.
Problem
To increase user's anonymity, we suggest users securely communicating over Waku to use a secret in order to frequently and deterministically change
contentTopic- ideally, at every round trip communication.However, this might have different drawbacks, since, for example:
contentTopicof their interest;contentTopic.For such reasons, possible trade-offs should be investigated, especially if target lightweight devices.
Possible future directions
In the future, we might address this problem by implementing private filter queries using techniques such us oblivious transfer and private information retrieval. With these, a filter node becomes able to answer users' filter queries without learning the contents of the filter request made.
Acceptance criteria
contentTopicchanges as per 37/WAKU2-NOISE-SESSIONS.