Skip to content

Commit 27c505a

Browse files
committed
speedrun iexec content
replaced what we do by "speedrun iexec" and added some content. Goal of the content : introduce the protocol, but simply. Add some important keywords and explain them Also introduces the devtools and link to them
1 parent 185888e commit 27c505a

File tree

5 files changed

+125
-47
lines changed

5 files changed

+125
-47
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,7 @@
88
node_modules
99
auto-imports.d.ts
1010
components.d.ts
11+
.cursor
1112

1213
#mac
1314
.DS_Store

.vitepress/config.mts

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,7 @@ export default defineConfig({
7777
// https://vitepress.dev/reference/default-theme-config
7878
nav: [
7979
{ text: 'Home', link: '/' },
80-
{ text: 'Overview', link: '/overview/what-we-do' },
80+
{ text: 'Overview', link: '/overview/speedrun-iexec' },
8181
{ text: 'Protect Data', link: '/manage_data/guides' },
8282
{ text: 'Build iApp', link: '/build_iapp/iapp-generator/what-is-iapp' },
8383
{ text: 'Use iApp', link: '/use_iapp/introduction' },

.vitepress/sidebar.ts

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -6,7 +6,10 @@ export function getSidebar() {
66
{
77
text: 'OVERVIEW',
88
items: [
9-
{ text: '💡  What We Do', link: '/overview/what-we-do' },
9+
{
10+
text: '⚡  Speedrun iExec',
11+
link: '/overview/speedrun-iexec',
12+
},
1013
{
1114
text: '👋   Hello World',
1215
link: '/overview/helloWorld',

overview/speedrun-iexec.md

Lines changed: 119 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,119 @@
1+
---
2+
title: Speedrun iExec
3+
description:
4+
Understand iExec protocol in 3 minutes - privacy-first computing for Web3
5+
---
6+
7+
# ⚡ Speedrun iExec
8+
9+
**Privacy-first computing protocol.** Your data stays protected, your code runs
10+
in secure enclaves, results come back encrypted. Here's how it works.
11+
12+
## The Protocol (Simple Version)
13+
14+
### 🔒 Step 1: Protect Data
15+
16+
Your sensitive data gets encrypted and stored online. Only you control who can
17+
access it.
18+
19+
**Devtool**: [DataProtector](/manage_data/dataProtector) handles this for you
20+
21+
### ⚙️ Step 2: Secure Computing (Workers)
22+
23+
Code runs inside **secure enclaves** (TEEs) on iExec workers. The worker can
24+
access your data to process it, but only within the privacy-safe TEE
25+
environment - your data never leaves the secure bubble.
26+
27+
### 🚀 Step 3: Run iApps
28+
29+
You submit a **Task** = "Run this iApp on this protected data". The protocol
30+
finds available workers and executes everything confidentially.
31+
32+
**Devtool**: [iApp Generator](/build_iapp/iapp-generator) helps you create and
33+
deploy iApps
34+
35+
### 📦 Step 4: Get Results
36+
37+
Results come back **encrypted to you**. Workers never see raw data, you never
38+
lose control.
39+
40+
```
41+
Protected Data + iApp + Worker = Task → Encrypted Result
42+
```
43+
44+
## What Each Piece Does
45+
46+
### 🛡️ **Protected Data**
47+
48+
Your data, encrypted. You set the rules: "Only these apps can use it, only for
49+
these purposes."
50+
51+
### 🚀 **iApps**
52+
53+
Your code, packaged to run on workers. Can be AI models, data processing
54+
scripts, any computation.
55+
56+
### 🏭 **Workers (Secure Enclaves)**
57+
58+
Computers that process your data inside privacy-safe TEE environments. They can
59+
access your data to work with it, but the TEE ensures it stays confidential and
60+
tamper-proof.
61+
62+
### **Deals**
63+
64+
A job request: "Execute iApp X on protected data Y, send results to Z." The
65+
protocol handles the rest.
66+
67+
## Real Example Walkthrough
68+
69+
**AI Model Training (Private)**
70+
71+
1. **Protect**: Medical researchers upload patient data → becomes Protected Data
72+
2. **Deploy**: AI company packages their model → becomes iApp
73+
3. **Execute**: Someone submits Task → "Train model on this data"
74+
4. **Result**: Model gets trained, researcher gets insights, raw data never
75+
leaves enclave
76+
77+
**Web3 Email**
78+
79+
1. **Protect**: Users upload email contacts → Protected Data
80+
2. **Execute**: App submits Task → "Send email via Web3Mail iApp"
81+
3. **Result**: Email sent, addresses stay private, sender/receiver authenticated
82+
83+
## Why This Architecture Rocks
84+
85+
### **True Privacy**
86+
87+
Data processing happens in secure enclaves. Workers can't peek, hackers can't
88+
break in.
89+
90+
### **User Ownership**
91+
92+
Data owners control access programmatically. Revoke permissions anytime.
93+
94+
### **Composable**
95+
96+
Any iApp can use any Protected Data (if authorized). Build once, use everywhere.
97+
98+
### **Monetizable**
99+
100+
Data owners get paid automatically when their data gets used in tasks.
101+
102+
## Start Building
103+
104+
Now that you get the protocol, pick your devtools:
105+
106+
- **📧 Quick Win**: Add [Web3Mail](/use_iapp/web3mail) or
107+
[Web3Telegram](/use_iapp/web3telegram.md) to your project ! (uses the protocol
108+
under the hood)
109+
- **🛡️ Protect Data**: Try [DataProtector](/manage_data/dataProtector) to
110+
encrypt your first dataset
111+
- **🚀 Build iApps**: Create confidential compute with
112+
[iApp Generator](/build_iapp/iapp-generator)
113+
- **👋 Hands-On**: Follow our [Hello World](/overview/helloWorld) to see all
114+
devtools working together
115+
116+
---
117+
118+
**TL;DR**: iExec = Encrypted data + Secure computing + Your code → Private
119+
results. Privacy made easy.

overview/what-we-do.md

Lines changed: 0 additions & 45 deletions
This file was deleted.

0 commit comments

Comments
 (0)