From 332f05db856421d447421a335dde719a92663645 Mon Sep 17 00:00:00 2001 From: alelpoan <155192176+alelpoan@users.noreply.github.com> Date: Mon, 18 May 2026 13:06:28 +0300 Subject: [PATCH 1/2] docs: fix incorrect symbols for problem statements in fhenix.mdx --- get-started/introduction/fhenix.mdx | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/get-started/introduction/fhenix.mdx b/get-started/introduction/fhenix.mdx index 38044ef..b1b901e 100644 --- a/get-started/introduction/fhenix.mdx +++ b/get-started/introduction/fhenix.mdx @@ -28,9 +28,9 @@ Blockchain is often praised for its **decentralization, immutability, and transp In public blockchains like Ethereum, every transaction, smart contract interaction, and account balance is **completely visible** to anyone. This radical transparency, while crucial for establishing trust and enabling verification, creates significant privacy challenges. FHE solves this fundamental tradeoff by allowing data to remain **fully encrypted** while still maintaining the network's ability to verify its accuracy and authenticity. This means sensitive information can be processed and validated without ever being exposed, combining the best of both worlds - **bulletproof privacy with trustless verification**. **Real-world consequences of blockchain transparency:** \ - ✅ **Front-running & MEV** – Traders can analyze mempools and exploit pending transactions before they are executed. \ - ✅ **Confidentiality leaks** – Sensitive financial transactions, payroll information, or business logic are exposed. \ - ✅ **Enterprise adoption hurdles** – Companies are reluctant to use public blockchains if competitors can access proprietary data. + 🔴 **Front-running & MEV** – Traders can analyze mempools and exploit pending transactions before they are executed. \ + 🔴 **Confidentiality leaks** – Sensitive financial transactions, payroll information, or business logic are exposed. \ + 🔴 **Enterprise adoption hurdles** – Companies are reluctant to use public blockchains if competitors can access proprietary data. These challenges can all be mitigated by using FHE in your smart contracts. From 7411adc4ff345588d3b1974142ffd76b74c6ae69 Mon Sep 17 00:00:00 2001 From: alelpoan <155192176+alelpoan@users.noreply.github.com> Date: Mon, 18 May 2026 13:07:04 +0300 Subject: [PATCH 2/2] docs: fix typo "experince" in compatibility.mdx --- get-started/introduction/compatibility.mdx | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/get-started/introduction/compatibility.mdx b/get-started/introduction/compatibility.mdx index 2b039ad..3da074d 100644 --- a/get-started/introduction/compatibility.mdx +++ b/get-started/introduction/compatibility.mdx @@ -43,7 +43,7 @@ When working with CoFHE components: - **Check release notes**: Review breaking changes and migration guides when upgrading -For the best development experince, use the latest versions of all components. They are designed to work together seamlessly and include the latest features and security improvements. +For the best development experience, use the latest versions of all components. They are designed to work together seamlessly and include the latest features and security improvements. ## Network Compatibility