refactor: streamline advanced iApp documentation and remove deprecated sections

- Removed outdated references and sections from the advanced iApp guides, including the overview and SGX encrypted dataset.
- Updated sidebar to reflect the changes in the advanced section.
- Enhanced documentation with dynamic chain name integration for commands.
- Removed unused image assets and improved clarity in examples.

Author: Le-Caignec

.vitepress/sidebar.ts

@@ -202,10 +202,6 @@ export function getSidebar() {
             text: 'Advanced',
             collapsed: true,
             items: [
-              {
-                text: 'Overview',
-                link: '/guides/build-iapp/advanced/overview',
-              },
               {
                 text: 'Quick Start for Developers',
                 link: '/guides/build-iapp/advanced/quick-start-for-developers',
@@ -215,17 +211,13 @@ export function getSidebar() {
                 link: '/guides/build-iapp/advanced/your-first-app',
               },
               {
-                text: 'Build your first SGX app (SCONE)',
+                text: 'Build your first SGX app',
                 link: '/guides/build-iapp/advanced/create-your-first-sgx-app',
               },
               {
                 text: 'End-to-end Encryption',
                 link: '/guides/build-iapp/advanced/end-to-end-encryption',
               },
-              {
-                text: 'SGX Encrypted Dataset',
-                link: '/guides/build-iapp/advanced/sgx-encrypted-dataset',
-              },
               {
                 text: 'Access Confidential Assets',
                 link: '/guides/build-iapp/advanced/access-confidential-assets',

src/assets/explorer-dataset-example.png

@@ -31,21 +31,18 @@ The SMS currently supports 3 types of secrets:
    is not linked to any application. When a requester buys a task, the requester
    can declare which secrets can be accessed by the application. Doing so, a
    single requester secret can be shared with multiple applications.
-3. [Dataset secret](sgx-encrypted-dataset.md): A dataset secret is not directly
-   accessible from the application but its decrypted content is. If a dataset is
-   requested and authorized to be used in it, its content will be automatically
-   decrypted in the application enclave. To monetize such a dataset on iExec,
-   the original dataset must be encrypted using the iExec SDK, its encrypted
-   counterpart must be publicly available and its encryption key pushed into the
-   SMS.
+3. [Protected Data secret](/guides/manage-data/manage-access): A protected data
+   secret is not directly accessible from the application but its decrypted
+   content is. If a Protected Data is requested and authorized to be used in it,
+   its content will be automatically decrypted in the application enclave.
 
 Here is a general overview of how confidential assets are used on iExec:
 
 ```mermaid
 graph TD
     Req[Requester] -->|1.a. Push secret| SMS[SMS]
     AppDev[Application developer] -->|1.b. Push secret| SMS
-    DatasetOwn[Dataset owner] -->|1.c. Push secret| SMS
+    ProtectedDataOwn[ProtectedData owner] -->|1.c. Push secret| SMS
     Req --> |2 . Buy task| Chain
     Chain[Blockchain] --> |3 . Notify task to compute| Worker[Worker/Workerpool]
     Worker --> |4 . Launch TEE application| App[TEE application]
@@ -58,4 +55,4 @@ graph TD
 You now understand how these three kinds of confidential assets work on iExec,
 you can go one step further by learning how to manipulate them:
 
-- [Access a confidential dataset](sgx-encrypted-dataset.md)
+- [Access to a Protected Data](guides/build-iapp/inputs-and-outputs)

src/guides/build-iapp/advanced/access-confidential-assets.md

@@ -225,8 +225,8 @@ docker run --rm -e SCONE_HASH=1 <docker-hub-user>/tee-scone-hello-world:1.0.0-de
 
 Deploy the app with the standard command:
 
-```bash
-iexec app deploy
+```bash twoslash
+iexec app deploy --chain {{chainName}}
 ```
 
 ### Run the TEE app
@@ -239,18 +239,15 @@ a debug workerpool, use the debug workerpool
 
 You are now ready to run the app
 
-```bash
-iexec app run --tag tee,scone --workerpool debug-v8-learn.main.pools.iexec.eth --watch
+```bash twoslash
+iexec app run --chain {{chainName}} --tag tee,scone --workerpool debug-v8-learn.main.pools.iexec.eth --watch
 ```
 
 ::: info
 
 You noticed we used `debug-v8-learn.main.pools.iexec.eth` instead of an ethereum
 address, this is an ENS name.
 
-The [ENS (Ethereum Name Service)](https://ens.domains/) protocol enables
-associating decentralized naming to ethereum addresses.
-
 :::
 
 ::: info
@@ -269,3 +266,16 @@ may need to use some confidential data to get the full potential of the
 
 - [Access confidential assets from your app](access-confidential-assets.md)
 - [Protect the result](end-to-end-encryption.md)
+
+<script setup>
+import { computed } from 'vue';
+import useUserStore  from '@/stores/useUser.store';
+import {getChainById} from '@/utils/chain.utils';
+
+// Get current chain and compute explorer info
+const userStore = useUserStore();
+const selectedChain = computed(() => userStore.getCurrentChainId());
+
+const chainData = computed(() => getChainById(selectedChain.value));
+const chainName = computed(() => chainData.value.chainName);
+</script>

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

@@ -1,4 +1,4 @@
-# 🛡️ Build Intel TDX App (Experimental)
+# 🛡️ Build Intel TDX App (Experimental) <ChainNotSupportedBadge/>
 
 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
@@ -309,3 +309,7 @@ EXPERIMENTAL_TDX_APP=true iapp run <app-address>
   in TDX
 - **[Advanced iApp Building](/guides/build-iapp/advanced/overview)** - Advanced
   development techniques
+
+<script setup>
+import ChainNotSupportedBadge from '@/components/ChainNotSupportedBadge.vue'
+</script>

src/guides/build-iapp/advanced/create-your-first-tdx-app.md

@@ -64,21 +64,22 @@ private key in the file `<0x-your-wallet-address>_key`.
 
 Now, push the public key to the SMS:
 
-```bash
-iexec result push-encryption-key --tee-framework scone
+```bash twoslash
+iexec result push-encryption-key --tee-framework --chain {{chainName}} scone
 ```
 
 And check it using:
 
-```bash
-iexec result check-encryption-key --tee-framework scone
+```bash twoslash
+iexec result check-encryption-key --tee-framework --chain {{chainName}} scone
 ```
 
 Now to see that in action, you'd need to trigger a task and specify yourself as
 the beneficiary in the command:
 
-```bash
+```bash twoslash
 iexec app run <0x-your-app-address> \
+    --chain {{chainName}}
     --workerpool debug-v8-learn.main.pools.iexec.eth \
     --tag tee,scone \
     --encrypt-result \
@@ -87,8 +88,8 @@ iexec app run <0x-your-app-address> \
 
 Wait for the task to be `COMPLETED` and download the result:
 
-```bash
-iexec task show <0x-your-task-id> --download
+```bash twoslash
+iexec task show --chain {{chainName}} <0x-your-task-id> --download
 ```
 
 If you extract the obtained zip and try to read the content of the file
@@ -134,3 +135,16 @@ the dataset, and the result.
 
 You can go to the advanced section and learn more about managing orders on the
 iExec to effectively monetize your applications and datasets.
+
+<script setup>
+import { computed } from 'vue';
+import useUserStore  from '@/stores/useUser.store';
+import {getChainById} from '@/utils/chain.utils';
+
+// Get current chain and compute explorer info
+const userStore = useUserStore();
+const selectedChain = computed(() => userStore.getCurrentChainId());
+
+const chainData = computed(() => getChainById(selectedChain.value));
+const chainName = computed(() => chainData.value.chainName);
+</script>

src/guides/build-iapp/advanced/end-to-end-encryption.md

@@ -64,7 +64,7 @@ Ethereum wallet. See iExec SDK documentation
 
 Create a new folder for your iExec project and initialize the project:
 
-```text
+```bash
 mkdir ~/iexec-projects
 cd ~/iexec-projects
 iexec init --skip-wallet
@@ -87,7 +87,7 @@ for a full list.
 
 You can now check your wallet content:
 
-```text
+```bash
 iexec wallet show
 ```
 
@@ -102,7 +102,7 @@ Let's deploy an iExec app!
 
 Initialize a new application
 
-```text
+```bash
 iexec app init
 ```
 
@@ -134,22 +134,22 @@ iExec.
 You will now deploy your app on iExec, this will be your first transaction on
 the blockchain:
 
-```text
-iexec app deploy
+```bash twoslash
+iexec app deploy --chain {{chainName}}
 ```
 
 ::: tip
 
 While running `iexec app deploy` you sent your first transaction on the
-bellecour blockchain.
+{{chainName}} blockchain.
 
 :::
 
 You can check your deployed apps with their index, let's check your last
 deployed app:
 
-```text
-iexec app show
+```bash twoslash
+iexec app show --chain {{chainName}}
 ```
 
 ## Run your app on iExec
@@ -173,21 +173,21 @@ At any time you can:
 
 - view your balance
 
-```sh
-iexec account show
+```bash twoslash
+iexec account show --chain {{chainName}}
 ```
 
 - deposit RLC from your wallet to your iExec Account
 
-```sh
-iexec account deposit <amount>
+```bash twoslash
+iexec account deposit --chain {{chainName}} <amount>
 ```
 
 - withdraw RLC from your iExec account to your wallet \(only stake can be
   withdrawn\)
 
-```sh
-iexec account withdraw <amount>
+```bash twoslash
+iexec account withdraw --chain {{chainName}} <amount>
 ```
 
 :::
@@ -197,8 +197,8 @@ to pay for the computation.
 
 Everything is ready to run your application!
 
-```text
-iexec app run --args <your-name-here> --workerpool prod-v8-learn.main.pools.iexec.eth --watch
+```bash twoslash
+iexec app run --chain {{chainName}} --args <your-name-here> --workerpool prod-v8-learn.main.pools.iexec.eth --watch
 ```
 
 ::: info
@@ -253,14 +253,14 @@ is a 32Bytes hexadecimal string\).
 
 Download the result of your task
 
-```text
-iexec task show <taskid> --download my-result
+```bash twoslash
+iexec task show --chain {{chainName}} <taskid> --download my-result
 ```
 
 You can get your taskid with the command:
 
-```text
-iexec deal show <dealid>
+```bash twoslash
+iexec deal show --chain {{chainName}} <dealid>
 ```
 
 ::: info
@@ -274,7 +274,7 @@ produce an text file in `result.txt`.
 
 Let's discover the result of the computation.
 
-```text
+```bash
 unzip my-result.zip -d my-result
 cat my-result/result.txt
 ```
@@ -301,13 +301,13 @@ The conditions to use an app are defined in the **apporder**.
 
 Publish a new apporder for your application.
 
-```text
-iexec app publish
+```bash twoslash
+iexec app publish --chain {{chainName}}
 ```
 
 ::: info
 
-`iexec app publish` options allows to define custom access rules to the app
+`iexec app publish` command allows to define custom access rules to the app
 \(run `iexec app publish --help` to discover all the possibilities\).
 
 You will learn more about orders management later, keep the apporder default
@@ -320,18 +320,14 @@ conditions defined in apporder.
 
 You can check the published apporders for your app
 
-```text
-iexec orderbook app <your app address>
+```bash twoslash
+iexec orderbook app --chain {{chainName}} <your app address>
 ```
 
 Congratulation you just created a decentralized application! Anyone can now
 trigger an execution of your application on the iExec decentralized
 infrastructure.
 
-- With the iexec SDK CLI
-  `iexec app run <app address> --workerpool prod-v8-learn.main.pools.iexec.eth`
-- On iExec marketplace
-
 ## What's next?
 
 You are now familiar with the following key iExec concepts for developers:
@@ -346,3 +342,16 @@ You are now familiar with the following key iExec concepts for developers:
 Continue with these guides:
 
 - [Learn how to build your first application running on iExec](your-first-app.md)
+
+<script setup>
+import { computed } from 'vue';
+import useUserStore  from '@/stores/useUser.store';
+import {getChainById} from '@/utils/chain.utils';
+
+// Get current chain and compute explorer info
+const userStore = useUserStore();
+const selectedChain = computed(() => userStore.getCurrentChainId());
+
+const chainData = computed(() => getChainById(selectedChain.value));
+const chainName = computed(() => chainData.value.chainName);
+</script>