diff --git a/opsec/chainalysisattempts/index.html b/opsec/chainalysisattempts/index.html index 39e863a..821373e 100644 --- a/opsec/chainalysisattempts/index.html +++ b/opsec/chainalysisattempts/index.html @@ -62,7 +62,7 @@
As of September 5, 2024 the sech1 posted on monero.town the following post, which was a repost of the following reddit post talking about a leaked Chainalysis meeting video about what was their progress on tracing monero transactions back in August 2023. This is a great opportunity to highlight the opsec weaknesses they are targeting so let's dive into it.
+As of September 5, 2024 sech1 posted on monero.town the following post, which was a repost of the following reddit post talking about a leaked Chainalysis meeting video about what was their progress on tracing monero transactions back in August 2023. This is a great opportunity to highlight the opsec weaknesses they are targeting so let's dive into it.
Now, if you decide to trust a random remote node that is not yours, and let's say you decide to trust one of their malicious nodes, you need to be aware that they can :
+Now, if you decide to trust a random remote node that is not yours, and let's say you decide to trust one of their malicious nodes, you need to be aware that they can see:
the timestamp of each transaction
The timestamp of each transaction
The transaction behavioral characteristics (the number of inputs, outputs, the fee structure (1x, 10x, 100x, etc)
Which IP address is connecting there (clear attack on dandelion++), and it's latency.