diff --git a/articles/introducing-trinity.md b/articles/introducing-trinity.md
index e60240e..5e3a3d7 100644
--- a/articles/introducing-trinity.md
+++ b/articles/introducing-trinity.md
@@ -1,7 +1,7 @@
 ---
 authors: ["Yanis Meziane"]
 title: "Introducing Trinity"
-image: "/articles/introducing-trinity/trinity.webp"
+image: "/articles/introducing-trinity/trinity.png"
 tldr: "Two-Party Computation for the ZK Era"
 date: "2025-04-28"
 tags: ["zk", "mpc"]
@@ -18,7 +18,7 @@ The core mechanism unifying these concepts is the KZG polynomial commitment sche
 
 Trinity redefines the role of ZK credentials, extending their use beyond traditional settings (e.g., authentication) to serve as verified private inputs within secure two-party computations (2PC).
 
-We've just added it as a new template in [mpc-hello](https://github.com/voltrevo/mpc-hello/tree/main/trinity), and it's time to show what it brings to the table.
+We've just added it as a new template in [mpc-hello](https://github.com/privacy-scaling-explorations/mpc-hello), and it's time to show what it brings to the table.
 
 To understand Trinity's novelty, let's first revisit how traditional secure two-party computation (2PC) works.
 
diff --git a/public/articles/introducing-trinity/trinity.png b/public/articles/introducing-trinity/trinity.png
new file mode 100644
index 0000000..6ccd61c
Binary files /dev/null and b/public/articles/introducing-trinity/trinity.png differ