ximcity/blog-contributions
1
0
Fork 0
forked from nihilist/blog-contributions
Code Pull Requests Activity

updated

Browse Source
This commit is contained in:
nihilist 2024-09-07 12:25:32 +02:00
parent 3ca1e6650e
commit fb51de43eb
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
opsec/chainalysisattempts/index.html
View File

@ -62,7 +62,7 @@
<div class="col-lg-8 col-lg-offset-2">
<a href="../index.html">Previous Page</a></br></br><p><img src="../../assets/img/user.png" width="50px" height="50px"> <ba>nihilist@mainpc - 2024-09-07</ba></p>
<h1>Why can't I trust Centralised Exchanges, and random Monero nodes ?</h1>
<p> As of September 5, 2024 the sech1 posted on monero.town the following <a href="https://monero.town/post/4220893">post</a>, which was a repost of the following <a href="https://redlib.nowhere.moe/r/Monero/comments/1f8jv6w/comment/llnyemp/?context=3">reddit post</a> 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.</p>
<p> As of September 5, 2024 sech1 posted on monero.town the following <a href="https://monero.town/post/4220893">post</a>, which was a repost of the following <a href="https://redlib.nowhere.moe/r/Monero/comments/1f8jv6w/comment/llnyemp/?context=3">reddit post</a> 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.</p>
</div>
</div><!-- /row -->
@ -89,9 +89,9 @@
<div class="col-lg-8 col-lg-offset-2">
<h2><b>Chainalysis targets IP addresses and behavior anomalies (such as non-default fees)</b></h2> </br> </br>
<img src="1.5.png" class="imgRz">
<p>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 :</p>
<p>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:</p>
<ol>
<li><p>the timestamp of each transaction</p></li>
<li><p>The timestamp of each transaction</p></li>
<li><p>The transaction behavioral characteristics (the number of inputs, outputs, the fee structure (1x, 10x, 100x, etc)</p></li>
<li><p>Which IP address is connecting there (clear attack on dandelion++), and it's latency.</p></li>
</ol>