From 126b3b412d8d1e4145b7aa3093c10bc14752edf0 Mon Sep 17 00:00:00 2001 From: Mathis Debuire <68806646+64ix@users.noreply.github.com> Date: Thu, 14 Aug 2025 16:54:57 +0200 Subject: [PATCH 1/5] Refactor iApp, Protected Data, and Workerpool docs Renamed and updated overview pages for iApps, Protected Data, and Workerpools for clarity and consistency. Updated sidebar, internal links, and references to match new filenames and titles. Added detailed content for the Workerpools page and removed the placeholder Workerpool doc. Reworked the What is iExec page for a better tech explanation --- .vitepress/sidebar.ts | 12 +- README.md | 1 + .../overview/{what-is-iapp.md => iapps.md} | 4 +- ...is-protected-data.md => protected-data.md} | 10 +- src/get-started/overview/what-is-iexec.md | 104 +++++++---- .../overview/what-is-workerpool.md | 11 -- src/get-started/overview/workerpools.md | 166 ++++++++++++++++++ src/guides/build-iapp/index.md | 3 +- src/guides/use-iapp/getting-started.md | 2 +- src/index.md | 4 +- src/references/iapp-generator.md | 3 +- 11 files changed, 257 insertions(+), 63 deletions(-) rename src/get-started/overview/{what-is-iapp.md => iapps.md} (99%) rename src/get-started/overview/{what-is-protected-data.md => protected-data.md} (97%) delete mode 100644 src/get-started/overview/what-is-workerpool.md create mode 100644 src/get-started/overview/workerpools.md diff --git a/.vitepress/sidebar.ts b/.vitepress/sidebar.ts index e77aac5f..646b3445 100644 --- a/.vitepress/sidebar.ts +++ b/.vitepress/sidebar.ts @@ -60,16 +60,16 @@ export function getSidebar() { link: '/get-started/overview/what-is-iexec', }, { - text: '❓ What is Protected Data ?', - link: '/get-started/overview/what-is-protected-data', + text: '🔐 Protected Data', + link: '/get-started/overview/protected-data', }, { - text: '❓ What is an iApp ?', - link: '/get-started/overview/what-is-iapp', + text: '🚀 iApps', + link: '/get-started/overview/iapps', }, { - text: '❓ What is a Workerpool ?', - link: '/get-started/overview/what-is-workerpool', + text: '⚡ Workerpools', + link: '/get-started/overview/workerpools', }, { text: '🪙 RLC Token', diff --git a/README.md b/README.md index cedd359a..5f876f3c 100644 --- a/README.md +++ b/README.md @@ -192,3 +192,4 @@ for input parameters: - migrate github SDK doc here - migrate pay-per-task page into a guide - check pages (introduction & getting-started) for use-iapp guide +- Schema what is iexec to do and implement diff --git a/src/get-started/overview/what-is-iapp.md b/src/get-started/overview/iapps.md similarity index 99% rename from src/get-started/overview/what-is-iapp.md rename to src/get-started/overview/iapps.md index 06f051fe..00ff06fc 100644 --- a/src/get-started/overview/what-is-iapp.md +++ b/src/get-started/overview/iapps.md @@ -1,9 +1,9 @@ --- -title: What is an iApp? +title: iApps description: Privacy-first applications that run on decentralized infrastructure --- -# 🚀 What is an iApp? +# iApps An iExec Application (iApp) is your regular application code (Python script, AI model, data processor, ...) that can securely process protected data (created by diff --git a/src/get-started/overview/what-is-protected-data.md b/src/get-started/overview/protected-data.md similarity index 97% rename from src/get-started/overview/what-is-protected-data.md rename to src/get-started/overview/protected-data.md index b77571da..632ca453 100644 --- a/src/get-started/overview/what-is-protected-data.md +++ b/src/get-started/overview/protected-data.md @@ -1,9 +1,9 @@ --- -title: What is Protected Data? +title: Protected Data description: Understanding iExec's data protection mechanisms --- -# ❓ What is Protected Data? +# Protected Data Protected Data refers to any data encrypted using the **iExec Data Protector tool**. This end-to-end encryption solution enables users to protect, manage and @@ -15,7 +15,7 @@ monetize their data within the Web3 ecosystem. ## Key Concepts -### 👑 Data Governance +### Data Governance
@@ -42,7 +42,7 @@ monetize their data within the Web3 ecosystem. -### 🔒 Privacy-preserving Computation +### Privacy-preserving Computation @@ -69,7 +69,7 @@ monetize their data within the Web3 ecosystem. -### 💰 Monetization +### Monetization diff --git a/src/get-started/overview/what-is-iexec.md b/src/get-started/overview/what-is-iexec.md index 11f43eb5..3a230dce 100644 --- a/src/get-started/overview/what-is-iexec.md +++ b/src/get-started/overview/what-is-iexec.md @@ -11,47 +11,87 @@ iExec is a **decentralized computing platform** that enables developers to build and deploy privacy-preserving applications using confidential computing technology. -## 🎯 **Mission** +## The Protocol (Simple Version) -iExec's mission is to democratize access to **confidential computing** by -providing a decentralized infrastructure that combines: +### Step 1: Protect Data -- **🔐 Privacy Protection** - Data remains encrypted during computation -- **⚡ Scalable Computing** - Access to distributed computing resources -- **💰 Monetization** - Fair compensation for computing providers -- **🌐 Decentralization** - No single point of failure or control +Your sensitive data gets encrypted and stored online. Only you control who can +access it. -## 🏗️ **Core Architecture** +→ **Devtool**: [DataProtector](/references/dataProtector) handles this for you -### **Three Main Components:** +### Step 2: Secure Computing (Workers) -1. **🤖 iApps (iExec Applications)** - - Confidential computing applications - - Run in secure enclaves (TEEs) - - Process encrypted data without exposing it +Code runs inside **secure enclaves** (TEEs) on iExec workers. The worker can +access your data to process it, but only within the privacy-safe TEE +environment - your data never leaves the secure bubble. -2. **🔐 DataProtector** - - End-to-end encryption solution - - Manage data access and sharing - - Monetize protected datasets +### Step 3: Run iApps -3. **⚙️ Worker Network** - - Distributed computing providers - - Execute iApps securely - - Earn RLC tokens for contributions +You submit a **Task** = "Run this iApp on this protected data". The protocol +finds available workers and executes everything confidentially. -## 🚀 **Key Features** +→ **Devtool**: [iApp Generator](/references/iapp-generator) helps you create and +deploy iApps -- **TEE (Trusted Execution Environment)** support -- **Zero-knowledge computation** -- **Decentralized marketplace** for computing resources -- **RLC token** for payments and governance -- **Cross-chain compatibility** +### 📦 Step 4: Get Results -## 🔗 **Get Started** +Results come back **encrypted to you**. Workers never see raw data, you never +lose control. -Ready to explore iExec? Check out: +``` +Protected Data + iApp + Worker = Task → Encrypted Result +``` -- [What is Protected Data?](/get-started/overview/what-is-protected-data) -- [What is an iApp?](/get-started/overview/what-is-iapp) -- [Hello World Tutorial](/get-started/helloWorld) +## What Each Piece Does + +### **Protected Data** + +Your data, encrypted. You set the rules: "Only these apps can use it, only for +these purposes." + +### **iApps** + +Your code, packaged to run on workers. Can be AI models, data processing +scripts, any computation. + +### **Workers (Secure Enclaves)** + +Computers that process your data inside privacy-safe TEE environments. They can +access your data to work with it, but the TEE ensures it stays confidential and +tamper-proof. + +### **Deals** + +A job request: "Execute iApp X on protected data Y, send results to Z." The +protocol handles the rest. + +## Real Example Walkthrough + +**AI Model Training (Private)** + +1. **Protect**: Medical researchers upload patient data → becomes Protected Data +2. **Deploy**: AI company packages their model → becomes iApp +3. **Execute**: Someone submits Task → "Train model on this data" +4. **Result**: Model gets trained, researcher gets insights, raw data never + leaves enclave + +**Web3 Email** + +1. **Protect**: Users upload email contacts → Protected Data +2. **Execute**: App submits Task → "Send email via Web3Mail iApp" +3. **Result**: Email sent, addresses stay private, sender/receiver authenticated + +## Start Building + +Now that you get the protocol, pick your devtools: + +- **📧 Quick Win**: Add [Web3Mail](/references/web3mail) or + [Web3Telegram](/references/web3telegram) to your project ! (uses the protocol + under the hood) +- **🛡️ Protect Data**: Try [DataProtector](/references/dataProtector) to encrypt + your first dataset +- **🚀 Build iApps**: Create confidential compute with + [iApp Generator](/references/iapp-generator) +- **👋 Hands-On**: Follow our [Hello World](/get-started/helloWorld) to see all + devtools working together diff --git a/src/get-started/overview/what-is-workerpool.md b/src/get-started/overview/what-is-workerpool.md deleted file mode 100644 index 3ef69aa9..00000000 --- a/src/get-started/overview/what-is-workerpool.md +++ /dev/null @@ -1,11 +0,0 @@ ---- -title: What is a Workerpool? -description: - Learn about workerpools in iExec - the computing resources that execute iApps ---- - -# What is a Workerpool? - -This page is under development. - - diff --git a/src/get-started/overview/workerpools.md b/src/get-started/overview/workerpools.md new file mode 100644 index 00000000..3cfb3209 --- /dev/null +++ b/src/get-started/overview/workerpools.md @@ -0,0 +1,166 @@ +--- +title: Workerpools +description: + Learn about workerpools in iExec - the computing resources that execute iApps +--- + +# Workerpools + +A **Workerpool** is a group of computing machines (workers) managed by a +**Workerpool Manager** that provides computational resources to execute iApps in +secure environments on the iExec network. + +Think of workerpools as computing clusters where your iApps run. Each workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.
+Want to use workerpools? Start building iApps and the protocol will handle workerpool selection automatically. Want to operate a workerpool? Check our deployment guides.
+Process medical data for AI diagnosis without exposing patient information
Analyze financial data for credit scoring while maintaining privacy
Content recommendation engines that don't track user behavior
Collaborative research on sensitive datasets across institutions
Think of workerpools as computing clusters where your iApps run. Each workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.
+Think of workerpools as computing clusters where your iApp run. Each workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.
Want to use workerpools? Start building iApps and the protocol will handle workerpool selection automatically. Want to operate a workerpool? Check our deployment guides.
+Want to use workerpools? Start building iApp and the protocol will handle workerpool selection automatically. Want to operate a workerpool? Check our deployment guides.
Think of workerpools as computing clusters where your iApp run. Each workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.
+Think of a workerpool as a computing cluster where your iApp runs. Each workerpool consists of multiple workers (machines) coordinated by a manager who ensures tasks are executed efficiently and securely.
Want to use workerpools? Start building iApp and the protocol will handle workerpool selection automatically. Want to operate a workerpool? Check our deployment guides.
+Want to use workerpool? Start building iApp and the protocol will handle workerpool selection automatically.