diff --git a/opsec/i2ptorrents/0.png b/opsec/i2ptorrents/0.0.png
similarity index 100%
rename from opsec/i2ptorrents/0.png
rename to opsec/i2ptorrents/0.0.png
diff --git a/opsec/i2ptorrents/0.1.png b/opsec/i2ptorrents/0.1.png
new file mode 100644
index 0000000..1907ede
Binary files /dev/null and b/opsec/i2ptorrents/0.1.png differ
diff --git a/opsec/i2ptorrents/index.html b/opsec/i2ptorrents/index.html
index 4d926aa..327ec7c 100644
--- a/opsec/i2ptorrents/index.html
+++ b/opsec/i2ptorrents/index.html
@@ -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>oxeo0 - 2025 / 03 / 14</ba></p>
 <h1>Peer-to-Peer Large File Sharing (Torrents over I2P)</h1>
-<img src="0.png" style="width:250px">
+<img src="0.0.png" style="width:250px">
 <p> </p>
           
 	       </div>
@@ -150,6 +150,15 @@
   It's assumed Alice and Bob have a working internet connection, a Debian 12 with a desktop environment and root access to their computers.<br>
   They can have firewall or NAT (I2P can do <a href="https://en.wikipedia.org/wiki/NAT_traversal">NAT traversal</a>) but it would be ideal to have the ability to open one UDP port on the router.
   It's also possible to run I2P on a separate machine in your LAN (like a NAS or Raspberry PI running Debian). I2P greatly benefits from running constantly since it can discover faster tunnels over time.
+</p>
+
+<p>
+Here's a simplified graph showcasing how the file will be sent over I2P network:<br><br>
+
+<img src="0.1.png" class="imgRz">
+<br>
+<br>
+
 </p>
 
       </div>