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

Message originator can be identified #120

Open
fed-franz opened this issue Feb 28, 2023 · 0 comments
Open

Message originator can be identified #120

fed-franz opened this issue Feb 28, 2023 · 0 comments
Labels
fix:bug Something isn't working

Comments

@fed-franz
Copy link
Contributor

Description
Since broadcast messages include a maximum height, nodes receiving a message during the first relay know that the sender created the message.

Expected behaviour
When receiving a message, nodes should not be able to determine if the sender is its originator or simply a relayer.
In particular,

Possible solutions

  • Seppia trick: when receiving a message with height=MAX, this is relayed with the same height to at least another peer.
  • Dandelion style solution: use an "anonymity phase" in which the message is relayed linearly through a path of nodes, using an initial height chosen at random, but bigger than MAX. At each step, the node probabilistically decides whether to continue the anonymity phase or to switch to the standard behavior.
@fed-franz fed-franz added the fix:bug Something isn't working label Feb 28, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fix:bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant