We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Reference Issue: vacp2p/rfc#182 Author: kdeme
There might be ways to link a message to a specific application, or worse user, because of the way the message is formed.
One specific case is for example, always having a specific size. Others might/will apply, tbi.
Waku v1 envelope data format e.g. always adds padding so that the messages become a mutiple of 256 bytes.
This should be further investigated, started by looking at the current (best) practises in privacy focused transports (e.g. mixnets)
Sphinx format used by Nym and Lightning Network: https://cypherpunks.ca/~iang/pubs/Sphinx_Oakland09.pdf
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Reference Issue: vacp2p/rfc#182
Author: kdeme
Problem
There might be ways to link a message to a specific application, or worse user, because of the way the message is formed.
One specific case is for example, always having a specific size. Others might/will apply, tbi.
Waku v1 envelope data format e.g. always adds padding so that the messages become a mutiple of 256 bytes.
Acceptance criteria
Details
This should be further investigated, started by looking at the current (best) practises in privacy focused transports (e.g. mixnets)
Possible Solutions
Notes
Sphinx format used by Nym and Lightning Network: https://cypherpunks.ca/~iang/pubs/Sphinx_Oakland09.pdf
The text was updated successfully, but these errors were encountered: