From 1a9394c041e7b1a626406f5fc79674205f97800d Mon Sep 17 00:00:00 2001
From: alelpoan <155192176+alelpoan@users.noreply.github.com>
Date: Sun, 7 Jun 2026 12:23:19 +0300
Subject: [PATCH] docs: add From FHE to CoFHE bridge section in fhenix.mdx

---
 get-started/introduction/fhenix.mdx | 19 +++++++++++++++++++
 1 file changed, 19 insertions(+)

diff --git a/get-started/introduction/fhenix.mdx b/get-started/introduction/fhenix.mdx
index 38044ef..5afca84 100644
--- a/get-started/introduction/fhenix.mdx
+++ b/get-started/introduction/fhenix.mdx
@@ -60,4 +60,23 @@ These challenges can all be mitigated by using FHE in your smart contracts.
 * Users control their data without relying on trusted third parties.
 
 
+---
+
+## From FHE to CoFHE
+
+FHE establishes that computation on encrypted data is possible — but
+possibility alone doesn't make it practical. Implementing FHE from
+scratch requires deep cryptographic expertise and migrating to an
+entirely different chain. Fhenix solves this by taking a different
+approach: instead of asking developers to migrate, bring encrypted
+computation to the chains they already use.
+
+The result is CoFHE — an FHE coprocessor that attaches to any EVM
+chain. The heavy cryptographic work runs offchain; your contract only
+ever sees lightweight handles to encrypted values. Same Solidity, same
+chains — confidentiality becomes just another feature.
+
+→ See how CoFHE works in practice: [What is CoFHE?](/get-started/introduction/what-is-cofhe)
+
+