From c74d3aa47beb1ffbf9e469c2177929249a73f4a4 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Fri, 17 Oct 2025 10:35:16 +0200 Subject: [PATCH 01/13] Refresh TDX page; clarify experimental status --- .../advanced/build-your-first-tdx-iapp.md | 22 ++++--------------- 1 file changed, 4 insertions(+), 18 deletions(-) diff --git a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md index 796e85c9..ada94ef0 100644 --- a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md +++ b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md @@ -11,11 +11,11 @@ In this tutorial, you will learn how to build and run a Confidential Computing application with Intel TDX technology using both traditional deployment and the iApp Generator. -:::danger ⚠️ EXPERIMENTAL FEATURE +::: info **Experimental** -**TDX support is currently experimental and should NOT be used in production.** -This feature is provided for testing and development purposes only. Expect -instabilities, limited compatibility, and potential outages. +- Please don’t share sensitive data or secrets. +- Features and availability may change or be discontinued. +- Please share feedbacks, ideas, and suggestions on [Discord](https://discord.com/invite/pbt9m98wnU) or support bot. ::: @@ -24,20 +24,6 @@ differences between TEE technologies. Check out our **[Intel TDX Technology](/protocol/tee/intel-tdx)** guide for comprehensive explanations of TDX technology and its benefits. -::: info - -**Request access to the experimental feature** - -- The TDX-powered workerpool is currently in a development environment and not - intended for production use. -- Expect occasional instability or incomplete features. Service is subject to - change or discontinuation -- Development environment only - do not share sensitive data or secrets. -- Please share any bug reports, suggestions for improvement, or general feedback - on your experience. -- To request early access, please [contact us](https://discord.gg/9h25DQFSCU) - -::: ## Prerequisites From 2d24c30606a2344bb29712b04dd08f7a43f2a2e9 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Fri, 17 Oct 2025 10:55:46 +0200 Subject: [PATCH 02/13] format docs with Prettier --- src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md index ada94ef0..68a41534 100644 --- a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md +++ b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md @@ -15,7 +15,8 @@ iApp Generator. - Please don’t share sensitive data or secrets. - Features and availability may change or be discontinued. -- Please share feedbacks, ideas, and suggestions on [Discord](https://discord.com/invite/pbt9m98wnU) or support bot. +- Please share feedbacks, ideas, and suggestions on + [Discord](https://discord.com/invite/pbt9m98wnU) or support bot. ::: @@ -24,7 +25,6 @@ differences between TEE technologies. Check out our **[Intel TDX Technology](/protocol/tee/intel-tdx)** guide for comprehensive explanations of TDX technology and its benefits. - ## Prerequisites - [Docker](https://docs.docker.com/install/) 17.05 or higher on the daemon and From c1a0e32471a80377155b60078ff1497971fdb45f Mon Sep 17 00:00:00 2001 From: erirc6 Date: Fri, 17 Oct 2025 15:24:29 +0200 Subject: [PATCH 03/13] rephrase --- .../build-iapp/advanced/build-your-first-tdx-iapp.md | 9 +++++---- 1 file changed, 5 insertions(+), 4 deletions(-) diff --git a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md index 68a41534..cfee9624 100644 --- a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md +++ b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md @@ -13,10 +13,11 @@ iApp Generator. ::: info **Experimental** -- Please don’t share sensitive data or secrets. -- Features and availability may change or be discontinued. -- Please share feedbacks, ideas, and suggestions on - [Discord](https://discord.com/invite/pbt9m98wnU) or support bot. +TDX support is currently in experimental phase: + +- Stability and confidentiality features are still being tested and refined. +- Features may evolve based on user feedback, please share your experience on + [Discord](https://discord.com/invite/pbt9m98wnU). ::: From a6c18fbdef4d35eeba4ee55b5c443101080bb840 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Fri, 17 Oct 2025 15:25:31 +0200 Subject: [PATCH 04/13] typo --- src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md index cfee9624..57a38272 100644 --- a/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md +++ b/src/guides/build-iapp/advanced/build-your-first-tdx-iapp.md @@ -11,7 +11,7 @@ In this tutorial, you will learn how to build and run a Confidential Computing application with Intel TDX technology using both traditional deployment and the iApp Generator. -::: info **Experimental** +::: info **Experimental Feature** TDX support is currently in experimental phase: From 57d23085bae8ee86e6a3cafd9a3020052b55cd39 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Tue, 21 Oct 2025 12:00:54 +0200 Subject: [PATCH 05/13] clean the page, introduce quick guide --- src/protocol/pay-per-task.md | 57 +++++++++++++++++++++--------------- 1 file changed, 34 insertions(+), 23 deletions(-) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index 1834fa34..4197299b 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -1,20 +1,20 @@ ---- -title: Pay Per Task Model -description: - Pricing model and task categories for iExec protocol, including computing and - deal time limits. ---- -# Pay per task model +# Task size (Pay-Per-Task) -We are introducing a new method for pricing and we have defined several task -categories that describe the execution boundaries. We'll setup a test -infrastructure so that application developers can evaluate the category of their -submissions. Conversely, worker pools will be able to benchmark their -infrastructures against the reference machine. +Pay-per-task categories, time limits, and claim rules. -In the future, we'll redefine the categories, and provide more advanced tools -for helping developers to maximize the usage of the infrastructure + +## Pay-per-task model + +The pay-per-task model is based on task size categories. Each category defines +two limits: + +- Maximum Computing Time (C): per-task execution time on the worker. If the task + exceeds C, the task is stopped and failed. +- Maximum Deal Time (D): overall time window for a task in the deal. If the task + isn’t completed within D, the requester can claim (i.e., recover according to + protocol rules). On claim, the requester recovers the RLC escrowed for that + task, no payout is made to the worker and workerpool. **Categories Description:** @@ -23,12 +23,23 @@ for helping developers to maximize the usage of the infrastructure | 0 – XS | 5 min | 50 min | | 1 – S | 20 min | 200 min (3h20m) | | 2 – M | 1 hour | 10h | -| 3 – L | 3 hour | 30h (1d6h) | -| 4 – XL | 10 hour | 100h (4d4h) | - -- Each worker will allocate **C** minutes to compute the application. If the - computation is not completed within this **Maximum Computing Time**, the - running application will be stopped. -- From a buyer perspective, a requester will be able to claim a task of a deal - after **D** minutes if the task is not completed within the **Maximum Deal - Time**. +| 3 – L | 3 hours | 30h (1d6h) | +| 4 – XL | 10 hours | 100h (4d4h) | + +- Workers allocate up to C per task. Beyond C, the app is stopped. +- Requesters can claim after D if the task isn’t completed. + +## How to pick a category (quick guide) + +Use this decision table to choose a safe category for your workload. + +| **Typical workload** | **Suggested category** | +| ------------------------------------- | ---------------------- | +| Short scripts / small data processing | Cat 0–1 | +| Medium data processing (10-15min) | Cat 2 | +| Heavy ML inference / long simulations | Cat 3–4 | + +Use the iExec SDK (CLI/API) to **set the category** in app, request, or +workerpool orders. +For commands and examples, see the +[iExec SDK GitHub repository](https://github.com/iExecBlockchainComputing/iexec-sdk/blob/master/docs/README.md). From fe0d4b070d29e95bf0b33045e8cc46db352e3611 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Tue, 21 Oct 2025 12:04:27 +0200 Subject: [PATCH 06/13] typo in titile --- src/protocol/pay-per-task.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index 4197299b..f4775acb 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -1,5 +1,5 @@ -# Task size (Pay-Per-Task) +# Task Size: Pay-Per-Task Pay-per-task categories, time limits, and claim rules. From 47da5a0d56108c3bd551d2b73e46ee49f0043864 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Tue, 21 Oct 2025 12:10:14 +0200 Subject: [PATCH 07/13] prettier fixes --- src/protocol/pay-per-task.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index f4775acb..925e6827 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -1,9 +1,7 @@ - # Task Size: Pay-Per-Task Pay-per-task categories, time limits, and claim rules. - ## Pay-per-task model The pay-per-task model is based on task size categories. Each category defines From 9cdc2a35163ff1f5ab6f1f5b6bf5beef12a1cd2a Mon Sep 17 00:00:00 2001 From: erirc6 Date: Tue, 21 Oct 2025 15:09:09 +0200 Subject: [PATCH 08/13] minor fixes --- src/protocol/pay-per-task.md | 22 +++++++++++----------- 1 file changed, 11 insertions(+), 11 deletions(-) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index 925e6827..985fbe0c 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -1,18 +1,18 @@ -# Task Size: Pay-Per-Task +# Task size: pay-per-task Pay-per-task categories, time limits, and claim rules. ## Pay-per-task model -The pay-per-task model is based on task size categories. Each category defines +We base the pay-per-task model on task size categories. Each category defines two limits: - Maximum Computing Time (C): per-task execution time on the worker. If the task - exceeds C, the task is stopped and failed. + exceeds C, the worker stops the task and marks it as failed. - Maximum Deal Time (D): overall time window for a task in the deal. If the task - isn’t completed within D, the requester can claim (i.e., recover according to - protocol rules). On claim, the requester recovers the RLC escrowed for that - task, no payout is made to the worker and workerpool. + isn’t completed within D, the requester can claim the task. On claim, the + requester recovers the RLC held in escrow for this task, the protocol does not + pay the Workerpool. **Categories Description:** @@ -24,8 +24,8 @@ two limits: | 3 – L | 3 hours | 30h (1d6h) | | 4 – XL | 10 hours | 100h (4d4h) | -- Workers allocate up to C per task. Beyond C, the app is stopped. -- Requesters can claim after D if the task isn’t completed. +- Worker allocates up to C per task. Beyond C, the worker stops the task. +- Requesters can claim the task after D if the task isn’t completed. ## How to pick a category (quick guide) @@ -37,7 +37,7 @@ Use this decision table to choose a safe category for your workload. | Medium data processing (10-15min) | Cat 2 | | Heavy ML inference / long simulations | Cat 3–4 | -Use the iExec SDK (CLI/API) to **set the category** in app, request, or -workerpool orders. +Use the iExec SDK to **set the category** in app, request, or workerpool +orders. For commands and examples, see the -[iExec SDK GitHub repository](https://github.com/iExecBlockchainComputing/iexec-sdk/blob/master/docs/README.md). +[iExec SDK Github repository](https://github.com/iExecBlockchainComputing/iexec-sdk/blob/master/docs/README.md). From 0fd9fa9f1fcf9916ef8241a0d6cbd8004e2a6b8a Mon Sep 17 00:00:00 2001 From: erirc6 Date: Tue, 21 Oct 2025 15:15:03 +0200 Subject: [PATCH 09/13] better claim description --- src/protocol/pay-per-task.md | 3 +-- 1 file changed, 1 insertion(+), 2 deletions(-) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index 985fbe0c..1e598b3b 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -11,8 +11,7 @@ two limits: exceeds C, the worker stops the task and marks it as failed. - Maximum Deal Time (D): overall time window for a task in the deal. If the task isn’t completed within D, the requester can claim the task. On claim, the - requester recovers the RLC held in escrow for this task, the protocol does not - pay the Workerpool. + requester recovers the RLC engaged for this task. **Categories Description:** From 344f89d64d36e26aac863acfe965846da8cad001 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Tue, 21 Oct 2025 16:14:12 +0200 Subject: [PATCH 10/13] vale fixes --- src/protocol/pay-per-task.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index 1e598b3b..fa8c83b5 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -11,7 +11,7 @@ two limits: exceeds C, the worker stops the task and marks it as failed. - Maximum Deal Time (D): overall time window for a task in the deal. If the task isn’t completed within D, the requester can claim the task. On claim, the - requester recovers the RLC engaged for this task. + requester can recover the RLC engaged for this task. **Categories Description:** From 65ed9d8ece03306bb0056e4194fc853c3b9084e6 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Tue, 21 Oct 2025 16:14:41 +0200 Subject: [PATCH 11/13] vales fixes --- src/protocol/pay-per-task.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index fa8c83b5..2c8e79cb 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -18,22 +18,22 @@ two limits: | **Category** | **Maximum Computing Time (C)** | **Maximum Deal Time (D)** | | ------------ | ------------------------------ | ------------------------- | | 0 – XS | 5 min | 50 min | -| 1 – S | 20 min | 200 min (3h20m) | +| 1 – S | 20 min | 200 min | | 2 – M | 1 hour | 10h | -| 3 – L | 3 hours | 30h (1d6h) | -| 4 – XL | 10 hours | 100h (4d4h) | +| 3 – L | 3 hours | 30h | +| 4 – XL | 10 hours | 100h | - Worker allocates up to C per task. Beyond C, the worker stops the task. - Requesters can claim the task after D if the task isn’t completed. -## How to pick a category (quick guide) +## How to pick a category: quick guide Use this decision table to choose a safe category for your workload. | **Typical workload** | **Suggested category** | | ------------------------------------- | ---------------------- | | Short scripts / small data processing | Cat 0–1 | -| Medium data processing (10-15min) | Cat 2 | +| Medium data processing / 10-15min | Cat 2 | | Heavy ML inference / long simulations | Cat 3–4 | Use the iExec SDK to **set the category** in app, request, or workerpool From 859afc389df7914f1f59eb23dc344e634138d2d7 Mon Sep 17 00:00:00 2001 From: erirc6 Date: Wed, 22 Oct 2025 10:25:02 +0200 Subject: [PATCH 12/13] remove redondant "getting started" info in iapp description --- src/get-started/overview/privacy-iapp.md | 41 ------------------------ 1 file changed, 41 deletions(-) diff --git a/src/get-started/overview/privacy-iapp.md b/src/get-started/overview/privacy-iapp.md index ceedfedf..1fa65adc 100644 --- a/src/get-started/overview/privacy-iapp.md +++ b/src/get-started/overview/privacy-iapp.md @@ -125,47 +125,6 @@ Collaborative research on sensitive datasets across institutions -## Getting Started - - - -## Time to build! - -Let's build an iApp that can process protected data in a secure environment -using the [iExec iApp generator tool](/references/iapp-generator). This tool -helps you create, test and deploy iApp with just a few commands. - - - -### Quick Start Path - -1. **Protect your data** with [DataProtector](/references/dataProtector) -2. **Build your iApp** using the [iApp Generator](/references/iapp-generator) -3. **Deploy and test** your application -4. **Process protected data** securely - -### What You'll Learn - -- How to create a Docker container for your application -- How to handle inputs and outputs securely -- How to deploy to the iExec network -- How to process protected data in TEE environments - -::: tip - -These are just a few examples, the possibilities are endless. Want to explore -iApp Generator? Check out our [documentation](/references/iapp-generator) and -see what you can build! - -::: - -## Technical Requirements - -- **Docker**: Your application must be containerized -- **Input/Output**: Define clear input and output schemas -- **TEE Compatibility**: Ensure your code runs in secure enclaves -- **Network Access**: Configure any external API calls or dependencies - ## Next Steps Ready to build your first privacy-preserving application? Start with our From c2b1c5eea3584e39cc37096888b10c6816dc9a7d Mon Sep 17 00:00:00 2001 From: erirc6 Date: Wed, 22 Oct 2025 11:45:49 +0200 Subject: [PATCH 13/13] add "contact us" --- src/protocol/pay-per-task.md | 5 +++++ 1 file changed, 5 insertions(+) diff --git a/src/protocol/pay-per-task.md b/src/protocol/pay-per-task.md index 2c8e79cb..f504c9b3 100644 --- a/src/protocol/pay-per-task.md +++ b/src/protocol/pay-per-task.md @@ -40,3 +40,8 @@ Use the iExec SDK to **set the category** in app, request, or workerpool orders. For commands and examples, see the [iExec SDK Github repository](https://github.com/iExecBlockchainComputing/iexec-sdk/blob/master/docs/README.md). + +::: info Need help +Can’t find a workerpool order that fits your needs or unsure which category to choose? +[Contact us on Discord](https://discord.com/invite/pbt9m98wnU) and we will help you pick the right setup. +:::