feat: build iapp by martin

src/build-iapp/guides/debugging-your-iapp.md

@@ -112,6 +112,12 @@ with open(f"{os.environ['IEXEC_OUT']}/computed.json", 'w') as f:
     json.dump(computed, f)
 ```
 
+### ⚠️ **Dataset type unmatching**
+
+- **Cause**: The dataset type specified in the frontend (protectData) does not
+  match with the dataset type specified in the iApp
+- **Solution**: Check both dataset types
+
 ## Best Practices
 
 ### 🔍 **Input Validation**

src/build-iapp/guides/inputs-and-outputs.md

@@ -275,23 +275,6 @@ environment.
 **When to use:** Processing user's sensitive information like personal data,
 financial records, health data.
 
-### How Users Provide Protected Data
-
-Users specify the protected data address when executing your iApp:
-
-```ts twoslash
-import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
-
-const web3Provider = getWeb3Provider('PRIVATE_KEY');
-const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
-// ---cut---
-// User provides their protected data for processing
-const response = await dataProtectorCore.processProtectedData({
-  protectedData: '0x123abc...', // Address of their protected data
-  app: '0x456def...', // Your iApp address
-});
-```
-
 ### How to Access Protected Data
 
 Protected data is available in the `IEXEC_IN` directory as decrypted files:
@@ -345,6 +328,23 @@ try {
 
 :::
 
+### How Users Provide Protected Data
+
+Users specify the protected data address when executing your iApp:
+
+```ts twoslash
+import { IExecDataProtectorCore, getWeb3Provider } from '@iexec/dataprotector';
+
+const web3Provider = getWeb3Provider('PRIVATE_KEY');
+const dataProtectorCore = new IExecDataProtectorCore(web3Provider);
+// ---cut---
+// User provides their protected data for processing
+const response = await dataProtectorCore.processProtectedData({
+  protectedData: '0x123abc...', // Address of their protected data
+  app: '0x456def...', // Your iApp address
+});
+```
+
 ### Working with Multiple Protected Datasets
 
 When multiple datasets are provided, they're available as separate files:

src/build-iapp/guides/using-tdx-experimental.md

@@ -38,6 +38,15 @@ technology, different from the default SGX implementation.
 - ❌ **Limited worker availability**
 - ❌ **Not production ready**
 
+| Feature                  | Intel SGX                                                                           | Intel TDX                                    |
+| ------------------------ | ----------------------------------------------------------------------------------- | -------------------------------------------- |
+| Release Year             | 2015                                                                                | 2023                                         |
+| Enclave Scope            | Application level                                                                   | Virtual machine level                        |
+| Code Adaptation Required | Yes - needs redesign of app's logic                                                 | No - supports lift-and-shift of full systems |
+| Memory Size              | Limited                                                                             | Extensive (multi-GB+)                        |
+| Integration Complexity   | Higher (more dev work)                                                              | Lower (VM legacy code)                       |
+| Best Fit For             | Lightweight, high-assurance modules (e.g. wallets, crypto key ops, small AI models) | Heavier AI workloads, legacy apps, databases |
+
 ## Enabling TDX in iApp Generator
 
 ### Environment Variable Method
@@ -53,6 +62,15 @@ iapp deploy
 iapp run <app-address>
 ```
 
+:::warning Environment Variable Declaration
+
+The syntax for setting environment variables differs between operating systems:
+
+- **Mac/Linux**: `export EXPERIMENTAL_TDX_APP=true`
+- **Windows**: `set EXPERIMENTAL_TDX_APP=true`
+
+:::
+
 ### Per-Command Method
 
 **Enable TDX for specific commands**:
@@ -77,6 +95,30 @@ EXPERIMENTAL_TDX_APP=true iapp debug <taskId>
 iexec app show <app-address>
 ```
 
+###
+
+⚠️ **To use** the iExec DataProtector SDK with TDX support, you must configure
+the SDK with the right SMS endpoint.
+
+```jsx
+const dataProtector = new IExecDataProtector(web3Provider, {
+  iexecOptions: {
+    smsURL: 'https://sms.labs.iex.ec',
+  },
+});
+```
+
+⚠️**You need** to change the default worker pool in your protected Data
+declaration
+
+```jsx
+await dataProtector.core.processProtectedData({
+  protectedData: protectedData.address,
+  workerpool: 'tdx-labs.pools.iexec.eth',
+  app: '0x1919ceb0c6e60f3B497936308B58F9a6aDf071eC',
+});
+```
+
 ## Protected Data Compatibility
 
 :::warning Protected Data Requirements

src/build-iapp/iapp-generator/getting-started.md

@@ -6,7 +6,7 @@ Before using the iApp Generator, make sure you have:
 
 \- [**Node.js**](https://nodejs.org/en/) version 20 or higher
 
-\- **Docker**
+\- **Docker / Docker hub account**
 
 \- **Docker Buildx** _(for macOS users, check AMD64 compatibility)_