Log emmission events for anonymity analysis #48
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
@AlejandroCabeza can take care of the analisys part. |
danielSanchezQ
approved these changes
Nov 9, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I devised a simpler way to measure the anonymity.
We log every emission (forward) events. There are two big types of emissions. One is the immediate forwarding, and the other is emitting messages released from the Tier 1: Persistent Transmission.
For only the anonymity analysis, the logs of immediate forwarding can probably be ignored. But I’m logging all emissions with a type tag, just in case.
Unlike the logging for latency analysis, here we print logs "right before" sending messages to peers, because the outsider observers can only see the network traffic between nodes, not inside logic of nodes.
In the analysis tool, we can draw a chart (e.g. scatter plot) to see the distribution of emission events across nodes over time. The goal of the blend protocol is having several nodes who emit "some" messages while a certain node is emitting a data message in a certain time frame, in order to hide who is the data message sender. In our protocol, each node sends not only cover messages, but also unpacked messages. These two can obfuscate the observation of outsider. For example, if there are 20 nodes emitting a cover message while a node is emitting a data message, it's not easy for the outside observer to guess who is the data message sender.