docs: update links to point to Arbitrum mainnet and clarify network selection in documentation

Author: Le-Caignec

src/get-started/tooling-and-explorers/iexec-explorer.md

@@ -18,6 +18,12 @@ explore apps and protectedData—all in one powerful dashboard.
   caption="🔗 Explore the iExec Protocol"
 />
 
+::: tip
+
+Before searching or exploring, make sure to select your desired network. The Explorer displays data for the network you choose.
+
+:::
+
 ## 🎯 What you Can Explore
 
 <CardGrid>
@@ -72,7 +78,7 @@ explore apps and protectedData—all in one powerful dashboard.
 <ImageViewer
   :image-url-dark="dealViewImage"
   image-alt="Deal View"
-  link-url="https://explorer.iex.ec/bellecour/deals"
+  link-url="https://explorer.iex.ec/arbitrum-mainnet/deals"
   caption="🔗 Explore Deals"
 />
 
@@ -98,7 +104,7 @@ explore apps and protectedData—all in one powerful dashboard.
 <ImageViewer
   :image-url-dark="taskViewImage"
   image-alt="Task View"
-  link-url="https://explorer.iex.ec/bellecour/tasks"
+  link-url="https://explorer.iex.ec/arbitrum-mainnet/tasks"
   caption="🔗 Explore Tasks"
 />
 
@@ -114,14 +120,14 @@ Browse and analyze all tasks across the iExec network:
 <ImageViewer
     :image-url-dark="taskDetailsStartedImage"
     image-alt="Result Decryption"
-    link-url="https://explorer.iex.ec/bellecour/tasks"
+    link-url="https://explorer.iex.ec/arbitrum-mainnet/tasks"
     caption="🔗 Explore Tasks"
 />
 
 <ImageViewer
     :image-url-dark="taskDetailsCompletedImage"
     image-alt="Task Completed"
-    link-url="https://explorer.iex.ec/bellecour/tasks"
+    link-url="https://explorer.iex.ec/arbitrum-mainnet/tasks"
     caption="🔗 Explore Tasks"
 />
 
@@ -150,7 +156,7 @@ Browse and analyze all tasks across the iExec network:
 <ImageViewer
   :image-url-dark="appViewImage"
   image-alt="App View"
-  link-url="https://explorer.iex.ec/bellecour/apps"
+  link-url="https://explorer.iex.ec/arbitrum-mainnet/apps"
   caption="🔗 Explore iApp Marketplace"
 />
 
@@ -165,7 +171,7 @@ Explore the iExec application marketplace:
 <ImageViewer
   :image-url-dark="datasetViewImage"
   image-alt="Dataset View"
-  link-url="https://explorer.iex.ec/bellecour/datasets"
+  link-url="https://explorer.iex.ec/arbitrum-mainnet/datasets"
   caption="🔗 Explore Protected Datasets"
 />
 
@@ -182,7 +188,7 @@ Navigate the protected data landscape:
 <ImageViewer
   :image-url-dark="workerpoolViewImage"
   image-alt="Workerpool View"
-  link-url="https://explorer.iex.ec/bellecour/workerpools"
+  link-url="https://explorer.iex.ec/arbitrum-mainnet/workerpools"
   caption="🔗 Explore Workerpools Infrastructure"
 />
 

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

@@ -65,41 +65,6 @@ touch sconify.sh
 chmod +x sconify.sh
 ```
 
-### Update chain json
-
-Make sure your `chain.json` content is as follows:
-
-```json
-{
-  "default": "bellecour",
-  "chains": {
-    "bellecour": {
-      "sms": { "scone": "https://sms.scone-debug.v8-bellecour.iex.ec" }
-    }
-  }
-}
-```
-
-If you start from a new directory tree, you will need to replay the following
-steps from [Build your first application](./your-first-app):
-
-- [Write the app](./your-first-app.md#write-the-app) Javascript or Python source
-  code in `src/`
-- [Dockerize your app](./your-first-app.md#dockerize-your-app)
-- [Push your app to Dockerhub](./your-first-app.md#push-your-app-to-dockerhub)
-
-As we mentioned earlier, the advantage of using **SCONE** is the ability to make
-the application **Intel® SGX-enabled** without changing the source code. The
-only thing we are going to do is rebuilding the app using the
-Trusted-Execution-Environment tooling provided by **SCONE**.
-
-::: info
-
-SCONE provides TEE conversion tooling (Python, Java, ..) plus eventually TEE
-base images for other languages (NodeJs).
-
-:::
-
 ## Build the TEE docker image
 
 We will use the following script to wrap the sconification process, copy the

src/guides/build-iapp/advanced/quick-start-for-developers.md

@@ -80,8 +80,9 @@ The iExec SDK creates the minimum configuration files:
 
 :::
 
-You can now connect to the blockchain. In the following steps, we will use the
-[iExec sidechain (also called Bellecour)](/get-started/tooling-and-explorers/blockchain-explorer#bellecour)
+You can now connect to the desired supported blockchain. In the following steps, we will use the chosen
+blockchain to deploy and run your iExec app. See the
+[supported blockchains](/get-started/tooling-and-explorers/blockchain-explorer) for a full list.
 
 You can now check your wallet content:
 

src/guides/use-iapp/how-to-pay-executions.md

@@ -28,7 +28,7 @@ your wallet to pay for executions.
 For detailed information on how to obtain RLC tokens, see our
 [RLC guide](/get-started/overview/rlc.md).
 
-### Step 2: Transfer to iExec Sidechain
+### Step 2: Stake RLC to Power Your iExec Tasks
 
 RLC tokens need to be staked on the iExec protocol to allow task payment. To do
 this, you should use the [iExec SDK](/references/sdk.md).
@@ -49,7 +49,7 @@ const balance = await iexec.account.checkBalance('0xa0c15e...');
 console.log('Nano RLC staked:', balance.stake.toString());
 console.log('Nano RLC locked:', balance.locked.toString());
 
-// Deposit RLC to the sidechain
+// Lock RLC in your account in the iExec protocol
 await iexec.account.deposit(1_000_000_000); // Deposit 1 RLC
 ```
 

src/references/dataProtector/dataProtectorCore/processProtectedData.md

@@ -464,8 +464,8 @@ Identifies the specific deal associated with this transaction.
 `string`
 
 A unique identifier associated with a task currently running on the iExec
-Bellecour side chain. You can monitor task execution using the
-[iExec blockchain explorer](https://explorer.iex.ec).
+protocol. You can monitor task execution using the
+[iExec blockchain explorer](https://explorer.iex.ec/arbitrum-mainnet).
 
 ::: tip
 

src/references/glossary.md

@@ -22,7 +22,7 @@ iExec’s product sidechain. It is linked to Ethereum Mainnet with a bridge
 allowing for the transfer of assets between networks. It allows iExec to be used
 without paying Ethereum gas fees.
 
-See “Sidechain and xRLC” for more information.
+See "Sidechain" and "xRLC" for more information.
 
 ### Beneficiary
 

src/references/web3mail/methods/sendEmail.md

@@ -321,7 +321,7 @@ import { type SendEmailResponse } from '@iexec/web3mail';
 
 This uniquely identifies the email task on the iExec side chain. You can view
 the status of the `sendEmail` method by monitoring the task on the
-[iExec Explorer](https://explorer.iex.ec/bellecour).
+[iExec Explorer](https://explorer.iex.ec/arbitrum-mainnet).
 
 ## Error Handling
 

src/references/web3telegram/methods/sendTelegram.md

@@ -292,7 +292,7 @@ import { type SendTelegramResponse } from '@iexec/web3telegram';
 
 This uniquely identifies the telegram task on the iExec side chain. You can view
 the status of the `sendTelegram` method by monitoring the task on the
-[iExec Explorer](https://explorer.iex.ec/bellecour).
+[iExec Explorer](https://explorer.iex.ec/arbitrum-mainnet).
 
 <script setup>
 import OptionalBadge from '@/components/OptionalBadge.vue'