iExecBlockchainComputing · 64ix · Sep 8, 2025 · Sep 2, 2025 · Sep 2, 2025 · Sep 2, 2025
diff --git a/.github/styles/config/vocabularies/Technical/accept.txt b/.github/styles/config/vocabularies/Technical/accept.txt
@@ -173,7 +173,7 @@ presale
 presigned
 untrusted
 dev
-cryptocurrecny
+cryptocurrency
 Unmatching
 incentivized
 Whitepaper
@@ -190,3 +190,12 @@ chipset
 auditable
 Composable
 Activable
+RLC
+API
+dApp
+iApp
+IPFS
+TEE
+SGX
+TDX
+MCP
diff --git a/.vale.ini b/.vale.ini
@@ -11,3 +11,5 @@ md = markdown
 [*.md]
 BasedOnStyles = Vale, Google
 IgnorePatterns = README.md
+
+Google.Acronyms = NO
diff --git a/.vitepress/sidebar.ts b/.vitepress/sidebar.ts
@@ -64,8 +64,8 @@ export function getSidebar() {
             link: '/get-started/overview/protected-data',
           },
           {
-            text: 'iApp',
-            link: '/get-started/overview/iapp',
+            text: 'Privacy iApp',
+            link: '/get-started/overview/privacy-iapp',
           },
           {
             text: 'Workerpool',

diff --git a/README.md b/README.md
@@ -171,11 +171,8 @@ please see our [CONTRIBUTING.md](CONTRIBUTING.md) guide.**
 - Talk about ENS on Bellecour(it's not supported on arbitrum)
 - Talk about encrypting results in use-iapp
 - Refactor "advanced" section in build-iapp
-- Rework src\get-started\protocol\iexec-doracle.md (transfer to guide or
-  rewrite)
 - Talk about encrypting results in use-iapp (link in outputs, iapp generator...)
 - Rework src\get-started\protocol\oracle.md (transfer to guide or rewrite)
-- Talk about iApp secret
 - Improve Guide in build-iapp section - be more clear for builder ( how to
   process process protectedData, clarify input-output guide)
 - Add illustration in the different pages
diff --git a/src/assets/rlc/rlc.gif b/src/assets/rlc/rlc.gif
diff --git a/src/assets/rlc/rlc.webp b/src/assets/rlc/rlc.webp
diff --git a/src/assets/use-cases/mcp-server.png b/src/assets/use-cases/mcp-server.png
diff --git a/src/assets/use-cases/mpc-server.jpg b/src/assets/use-cases/mpc-server.jpg
diff --git a/src/assets/use-cases/private-image-generator.png b/src/assets/use-cases/private-image-generator.png
diff --git a/src/get-started/helloWorld/2-protectData.md b/src/get-started/helloWorld/2-protectData.md
@@ -161,7 +161,7 @@ bun add @iexec/dataprotector
 import { Address, IExecDataProtector } from '@iexec/dataprotector';
 ```
 
-Create a new instance and call the methods you need
+Create a new instance and call the methods you need.
 
   </div>
 </div>

diff --git a/src/get-started/overview/iapp.md → src/get-started/overview/privacy-iapp.md b/src/get-started/overview/iapp.md → src/get-started/overview/privacy-iapp.md
@@ -13,16 +13,18 @@
 import CardWithoutBorder from '@/components/CardWithoutBorder.vue';
 </script>
 
-# iApp
+# What is an iApp?
 
-An iExec Application (iApp) brings Turnkey Privacy to your regular application
-code. Your Python scripts, AI models, or data processors can securely process
-protected data inside a TEE (Trusted Execution Environment).
+An iExec Application (iApp) is an application that runs inside a confidential
+environment (TEEs) to process Protected Data (created with DataProtector).
 
-## Why iApp Matter ?
+Your Python scripts, AI models, or data processors can securely process
+protected data inside a TEE.
 
-iApp provide Turnkey Privacy capabilities. Process sensitive data while keeping
-it private and secure.
+## Why iApp Matters?
+
+iApp provide privacy capabilities, allowing you to process sensitive data while
+keeping it private and secure.
 
 Imagine you want to build:
 
@@ -36,15 +38,16 @@
 </CardWithoutBorder>
 
 Users have this data, but they won't trust your regular app with it. **With
-Turnkey Privacy iApp, they will.**
+Privacy iApp, they will.**
 
 **You gain their trust. They gain their privacy. Everyone wins.**
 
 ## Key Concepts
 
 <CardWithBorder>
-
-  ✅ **True Privacy:** Users never expose their raw data. Your app processes it privately inside secure enclaves
+
+✅ **True Privacy:** Users never expose their raw data. Your app processes it
+privately inside secure enclaves.
 
 ✅ **Trusted Execution:** iExec ensures your code runs inside a Trusted
 Execution Environment (TEE), guaranteeing only the specified Docker image
@@ -62,18 +65,19 @@
 ## How it Works
 
 Your code runs in a Trusted Execution Environment (TEE). This secure area exists
-inside specific processors (Intel Software Guard Extensions (SGX)/Trust Domain
-Extensions (TDX) chipset). Everything stays private and protected there, even
-from the operating system.
+inside specific processors (Intel Software Guard Extensions (SGX) or Trust
+Domain Extensions (TDX) chipsets). Everything stays private and protected there,
+even from the operating system.
 
-Authorized users trigger iApp that process protected data inside this private
-environment. Your iApp uses the data but never exposes it, not even to you.
+Authorized users trigger an iApp that processes protected data inside this
+private environment. Your iApp uses the data but never exposes it, not even to
+you.
 
 <CardWithBorder>
 
 1. User provides private data
 2. Data is protected with DataProtector
-3. User builds and deploys a confidential iApp that processes protected data
+3. You build and deploy a confidential iApp that processes protected data
 4. Run the iApp with the corresponding protected data, performing confidential
    computing
 
@@ -88,8 +92,8 @@
 
 <CardGrid>
   <CardWithoutBorder>
-  
-   ### Healthcare
+
+### Healthcare
 
 Process medical data for AI diagnosis without exposing patient information
 
@@ -108,14 +112,16 @@
 ### Media
 
 Content recommendation engines that don't track user behavior
-</CardWithoutBorder>
+
+  </CardWithoutBorder>
 
   <CardWithoutBorder>
 
 ### Research
 
 Collaborative research on sensitive datasets across institutions
-</CardWithoutBorder>
+
+  </CardWithoutBorder>
 
 </CardGrid>
 

diff --git a/src/get-started/overview/protected-data.md b/src/get-started/overview/protected-data.md
@@ -16,9 +16,12 @@
 # Protected Data
 
 Protected Data refers to any data encrypted using the **iExec Data Protector
-tool**. This Turnkey Privacy encryption solution enables users to protect,
+tool**. This Privacy Toolkit encryption solution enables users to protect,
 manage and monetize their data within the Web3 ecosystem effortlessly.
 
+This Protected Data can only be decrypted and used inside TEE enclaves, by
+authorized actors (Requester, iApp, Worker)
+
 ::: tip <i></i>
 
 Unlike standard datasets, Protected Data exposes its **data types on-chain**
@@ -53,7 +56,7 @@
 <CardWithBorder>
 
 1. **Protect:** Encrypt and register your data on the iExec network
-2. **Share:** Authorize specific users and iApps to access your data
+2. **Share:** Authorize specific users and iApp to access your data
 3. **Monitor:** Track usage and maintain control
 4. **Monetize:** Earn from your data while keeping it private
 5. **Compute:** Authorized users can compute on your data with authorized iApp

diff --git a/src/get-started/overview/rlc.md b/src/get-started/overview/rlc.md
@@ -1,35 +1,28 @@
 ---
 title: RLC Token
 description:
-  RLC (Run on Lots of Computers) is the cryptocurrency powering iExec's
-  confidential computing ecosystem. Learn about RLC tokenomics, utility, and how
-  it drives privacy-first Web3 apps.
+  RLC is the cryptocurrency powering iExec's confidential computing ecosystem.
+  Learn about RLC tokenomics, utility, and how it drives privacy-first Web3
+  apps.
 ---
 
-<img :src="rlcGif" alt="RLC Token Animation" class="size-80 -my-10 mx-auto" />
+<img :src="rlcWebp" alt="RLC Token" class="size-80 mx-auto mb-8" />
 
 # RLC Token
 
 The native cryptocurrency that powers the entire iExec decentralized
 confidential computing ecosystem
 
-RLC (Run on Lots of Computers) powers all privacy apps on iExec. Every
-confidential computation requires RLC. Every piece of protected data consumed
-requires RLC. Every app execution requires RLC. The more builders use iExec
-tools, the more utility RLC gains in real apps.
-
-::: tip Info
-
-On the iExec sidechain (Bellecour), the RLC token symbol becomes **xRLC**. xRLC
-is the native token of the Bellecour chain and is used for all transactions and
-payments on this network.
-
-:::
+RLC powers all privacy apps running on iExec. Every confidential computation
+requires RLC. Every piece of protected data consumed requires RLC. Every app
+execution requires RLC. The more builders use iExec tools, the more RLC has to
+be bought and used by builder leveraging iExec's technology.
 
 ## 🎯 Why RLC Matters
 
-**Stack adoption = token usage.** When developers build with iExec tools, RLC
-gets used. More privacy apps deployed means more RLC demand.
+**iExec's adoption is linearly correlated to the real-time usage of the RLC
+token** When developers build with iExec tools, RLC gets used. More privacy apps
+deployed means more RLC demand.
 
 ### For users
 
@@ -38,13 +31,13 @@
 
 ### For providers
 
-Build apps, provide data, or run workers. All earn RLC when people use your
-contributions.
+Build apps, provide data, or [run workers](/get-started/overview/workerpool).
+All stakeholders earn RLC when people use their contributions.
 
 ### For holders
 
-**Clear positioning:** More developers using iExec's privacy tools means more
-RLC utility in real dApps. iExec builds actionable privacy, not just protocols.
+More developers using iExec's privacy tools means more RLC utility in real
+dApps. iExec builds actionable privacy, not just protocols.
 
 ## 💰 Transparent Payment Flow
 
@@ -75,6 +68,14 @@
 
 ### 📊 Ecosystem Growth Metrics
 
+::: info
+
+Circulating Supply The entire circulating supply of RLC has already been minted.
+There are no pending token unlocks or private allocations that could impact the
+market. Since launch, iExec has been self-funded, without relying on VCs.
+
+:::
+
 **RLC operates** on a utility-driven economic model where demand for
 confidential computing services drives token value:
 
@@ -84,7 +85,7 @@
 **Network Effects**: As more users and providers join the iExec ecosystem, the
 demand for RLC increases, driving token value through network effects.
 
-**Utility-Driven Growth**: Every interaction in the **Turnkey Privacy**
+**Utility-Driven Growth**: Every interaction in the **Privacy Toolkit**
 ecosystem requires RLC:
 
 - iApp executions consume RLC for computation
@@ -148,5 +149,5 @@
 import FeatureCard from '@/components/FeatureCard.vue';
 
 // Assets
-import rlcGif from '@/assets/rlc/rlc.gif';
+import rlcWebp from '@/assets/rlc/rlc.webp';
 </script>
diff --git a/src/get-started/toolkit.md b/src/get-started/toolkit.md
@@ -5,7 +5,7 @@
 
 # iExec Toolkit
 
-Build faster and smarter with our turnkey toolkit designed to streamline your
+Build faster and smarter with our privacy toolkit designed to streamline your
 iExec development experience.
 
 ## iApp Generator
@@ -39,7 +39,7 @@
 - **Asset visualization** to easily view and explore protected asset types on
   the iExec protocol
 - **Content consumption** capabilities for accessing protected data through
-  confidential iExec applications (iApps)
+  confidential iExec applications (iApp)
 - **Governance management** to control who accesses your data, when, and at what
   price
 

diff --git a/src/get-started/use-cases.md b/src/get-started/use-cases.md
@@ -33,6 +33,31 @@
   githubUrl="https://github.com/iExecBlockchainComputing/web3-messaging-usecase-demo"
 />
 
+## iExec Confidential AI
+
+### At the crossroads of DePIN and AI
+
+iExec provides the confidential computing infrastructure for AI, enabling
+developers to protect and monetize the entire AI pipeline. With the Confidential
+AI framework, you can:
+
+- **Train models collaboratively.**
+- **Monetize and reward contributors.**
+- **Ensure integral, end-to-end encryption across the workflow.**
+
+### End-to-end confidential AI pipeline
+
+- **Trusted Execution Environments (TEEs):** Secure, tamper-proof enclaves for
+  AI training and inference.
+- **Models and data stay encrypted at all times—processed without being
+  exposed.**
+- **Execution and results are traced on-chain, ensuring verifiability and
+  accountability.**
+
+</div>
+
+<div class="space-y-8 mt-8">
+
 <UseCaseCard
     title="AI Agent"
     description="Execute ElizaOS AI agents with full confidentiality in iExec TDX Trusted Execution Environments (TEEs)"
@@ -45,7 +70,7 @@
 <UseCaseCard
     title="MCP Server"
     description="A Model Context Protocol (MCP) compatible server to interact with the iExec protocol — built for Claude, agents, and AI tooling"
-    :imageUrl="mpcServer"
+    :imageUrl="mcpServer"
     imageAlt="AI Applications Demo Screenshot"
     :features="['MCP Protocol', 'AI Integration', 'Claude Support']"
     githubUrl="https://github.com/iExecBlockchainComputing/iexec-mcp-server"
@@ -78,7 +103,7 @@
 import contentCreatorImage from '@/assets/use-cases/content-creator.png';
 import web3MessagingImage from '@/assets/use-cases/web3-messaging.png';
 import elizaosImage from '@/assets/use-cases/elizaos.png';
-import mpcServer from '@/assets/use-cases/mpc-server.jpg';
+import mcpServer from '@/assets/use-cases/mcp-server.png';
 import privateImageGenerator from '@/assets/use-cases/private-image-generator.png';
 import imageCaptionMatcher from '@/assets/use-cases/image-caption-matcher.png';
 </script>
-Original file line number
+Diff line change
@@ Expand Up / @@ -161,7 +161,7 @@ bun add @iexec/dataprotector @@
     import { Address, IExecDataProtector } from '@iexec/dataprotector';
     ```
-    Create a new instance and call the methods you need
+    Create a new instance and call the methods you need.
       </div>
     </div>
@@ Expand Down @@