Skip to content
New issue

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

14/WAKU2-MESSAGE: Investigate the use of a message format with better features regarding unlinkability #60

Open
jimstir opened this issue Jun 13, 2024 · 0 comments

Comments

@jimstir
Copy link
Collaborator

jimstir commented Jun 13, 2024

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

  • Review existing solutions, suggest what is applicable.

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant