feat: move encryption guide to use-iapp

.vitepress/sidebar.ts

@@ -161,10 +161,6 @@ export function getSidebar() {
                 text: 'Build your first SGX app',
                 link: '/guides/build-iapp/advanced/build-your-first-sgx-iapp',
               },
-              {
-                text: 'End-to-end Encryption',
-                link: '/guides/build-iapp/advanced/protect-the-result',
-              },
               {
                 text: 'Access Confidential Assets',
                 link: '/guides/build-iapp/advanced/access-confidential-assets',

README.md

@@ -173,7 +173,6 @@ please see our [CONTRIBUTING.md](CONTRIBUTING.md) guide.**
 - 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

src/guides/build-iapp/advanced/build-your-first-sgx-iapp.md

@@ -560,7 +560,6 @@ to use some confidential data to get the full potential of the **Confidential
 Computing** paradigm. Check out next chapters to see how:
 
 - [Access confidential assets from your iApp](access-confidential-assets.md)
-- [Protect the result](/guides/build-iapp/advanced/protect-the-result.md)
 
 <script setup>
 import { computed } from 'vue';

src/guides/build-iapp/outputs.md

@@ -145,5 +145,3 @@ Continue building with these guides:
   Control who can use your iApp
 - **[Debugging Your iApp](/guides/build-iapp/debugging)** - Troubleshoot
   execution issues
-- **[How to Get and Decrypt Results](/guides/use-iapp/getting-started)** -
-  User-side result handling

src/guides/use-iapp/run-iapp-without-ProtectedData.md

@@ -200,3 +200,140 @@
   workerpoolorder: workerpoolOrders.orders[0].order,
 });
 ```
+
+## 🔐 Encrypt Results (Advanced)
+
+::: info
+
+DataProtector handles encryption automatically If you're using DataProtector,
+result encryption is handled automatically. This section is only needed for
+manual encryption when not using DataProtector.
+
+:::
+
+Secure your outputs with end‑to‑end encryption so only you (the beneficiary) can
+read them. Results leave the enclave and may traverse untrusted storage and
+networks; encryption ensures nobody else (operators, storage providers,
+intermediaries) can access the content.
+
+### 1) Generate your encryption key pair
+
+The beneficiary key pair is the root of trust for result confidentiality. The
+public key will be used inside the TEE to encrypt results for the beneficiary;
+the private key stays with the beneficiary to decrypt them locally.
+
+Run from your iExec project directory:
+
+```bash
+iexec result generate-encryption-keypair
+```
+
+This creates two files in `.secrets/beneficiary/`:
+
+```
+.secrets/
+└─ beneficiary/
+   ├─ <0x-your-wallet-address>_key       # PRIVATE KEY (keep safe)
+   └─ <0x-your-wallet-address>_key.pub   # PUBLIC KEY
+```
+
+Back up the private key securely. You will only need it locally to decrypt
+results.
+
+### 2) Push your public key to the SMS
+
+The Secret Management Service securely delivers your public key, at runtime, to
+the enclave running your iApp. Without this, the iApp cannot encrypt outputs for
+you.
+
+Make the public key available to TEEs at runtime:
+
+```bash
+iexec result push-encryption-key --tee-framework scone
+```
+
+Verify it:
+
+```bash
+iexec result check-encryption-key --tee-framework scone
+```
+
+### 3) Run the iApp with encrypted results
+
+The --encrypt-result flag instructs the platform to perform envelope encryption
+inside the enclave using your public key, so the archive that leaves the TEE is
+unreadable to others.
+
+Trigger a task and request encrypted outputs:
+
+```bash
+iexec app run <0x-app-address> \
+  --workerpool <0x-workerpool-address> \
+  --tag tee,scone \
+  --encrypt-result \
+  --watch
+```
+
+When completed, download the results archive:
+
+```bash
+iexec task show <0x-task-id> --download
+```
+
+Inside the archive, `iexec_out/result.zip.aes` is encrypted.
+
+Note: Results are encrypted for the task beneficiary. Ensure the beneficiary
+address is yours to be able to decrypt the archive.
+
+If you extract the archive and try to read the encrypted file, you'll see
+unreadable content:
+
+```bash
+mkdir /tmp/trash && \
+    unzip <0x-your-task-id>.zip -d /tmp/trash && \
+    cat /tmp/trash/iexec_out/result.zip.aes
+```
+
+The output will look like:
+
+```bash
+)3XqYvzEfRu<\ݵmm疞rc(a{{'ܼ͛q/[{hgD$g\.kj"s?"hJ_Q41_[{XԚa蘟vEr肽
+Յ]9WTL*tdzO`!e&snoL3K6L9%
+```
+
+This confirms the results are properly encrypted and unreadable without the
+private key.
+
+### 4) Decrypt results locally
+
+Results are encrypted end‑to‑end; only your private key can decrypt them. This
+step restores the plaintext so you can use the output files.
+
+Use your private key generated in step 1:
+
+```bash
+iexec result decrypt iexec_out/result.zip.aes
+```
+
+This produces `results.zip`. Extract it to view plaintext outputs:
+
+```bash
+unzip results.zip -d my-decrypted-result
+```
+
+And you can see the content of your result file:
+
+```bash
+$ cat my-decrypted-result/result.txt
+Hello, world!
+```
+
+Your results are now decrypted and ready to use.
+
+### Notes and tips
+
+- Keep the private key offline and backed up.
+- You can rotate keys by re-running generation and push steps; old tasks remain
+  decryptable with the old private key.
+- iApp code does not need changes to enable result encryption; it is enforced by
+  the TEE using the public key from SMS.