feat: fixed images (#133)

rlog/2023-11-07-rln-relay.mdx

@@ -144,13 +144,13 @@ This simulation was conducted by @alrevuelta, and is described in more detail [h
 The simulation included 100 waku nodes running in parallel.
 
 Proof generation times - 
-![img](https://user-images.githubusercontent.com/8811422/268019958-c2392954-ea42-4c0e-ae25-0d2b965dc9bf.png)
+![img](/img/rln-relay-2023-update//proof_generation_time.png)
 
 Proof verification times -
-![img](https://user-images.githubusercontent.com/8811422/267959342-e4481f2d-1e21-41e3-a693-f277594d8073.png)
+![img](/img/rln-relay-2023-update/proof_verification_time.png)
 
 A spammer node publishes 3000 msg/epoch, which is detected by all connected nodes, and subsequently disconnect to prevent further spam -
-![img](https://user-images.githubusercontent.com/8811422/268024411-2af9e330-1e80-49fa-892d-ebcf0ede9d9c.png)
+![img](/img/rln-relay-2023-update/spam_prevention_in_action.png)
 
 
 ## Security analysis
@@ -207,7 +207,7 @@ which provides step-by-step instructions on how to run Waku-RLN-Relay.
 
 Following is a diagram that will help understand the dependency tree -
 
-![rln-dep-tree](https://hackmd.io/_uploads/B1DgIbCin.jpg)
+![rln-dep-tree](/img/rln-relay-2023-update/rln_dep_tree.jpg)
 
 ## Future work