remove change from branch

Author: aimen-djari

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

@@ -67,275 +67,6 @@ Ethereum wallet. See iExec SDK documentation
 
 :::
 
-## Initialize your iExec project
-
-Create a new folder for your iExec project and initialize the project:
-
-```bash
-mkdir ~/iexec-projects
-cd ~/iexec-projects
-iexec init --skip-wallet
-```
-
-::: info
-
-The iExec SDK creates the minimum configuration files:
-
-- `iexec.json` contains the project configuration
-- `chain.json` contains the blockchain connection configuration
-- use `--skip-wallet` to skip wallet creation as we already created it
-
-:::
-
-You can now connect to the desired supported blockchain. In the following steps,
-the tutorial uses 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:
-
-```bash
-iexec wallet show
-```
-
-## Deploy your app on iExec
-
-iExec enables decentralized deployment of dockerized applications. The
-applications deployed on iExec are Smart Contracts identified by their Ethereum
-address and referencing a public docker image. Each iExec app has an owner who
-can set the execution permissions on iExec platform.
-
-Let's deploy an iExec app!
-
-Initialize a new app
-
-```bash
-iexec app init
-```
-
-The iExec SDK writes the minimum app configuration in `iexec.json`
-
-| **key**   | **description**                                                             |
-| --------- | --------------------------------------------------------------------------- |
-| owner     | app owner ethereum address \(default your wallet address\)                  |
-| name      | name of the app                                                             |
-| type      | type of app \("DOCKER" for docker container\)                               |
-| multiaddr | download URI of the app \(a public docker registry\)                        |
-| checksum  | checksum of the app \("0x" + docker image digest\)                          |
-| mrenclave | app fingerprint used for confidential computing use cases \(default empty\) |
-
-::: info
-
-The default app is the public docker image
-[iexechub/python-hello-world](https://hub.docker.com/repository/docker/iexechub/python-hello-world).
-
-Given an input string, the app generates an ASCII art greeting.
-
-:::
-
-You can deploy this app on iExec, it will run out of the box. When you are
-confident with iExec concept, you can read
-[Build and Test an iApp](../build-&-test) and learn how to setup your own app on
-iExec.
-
-You will now deploy your app on iExec, this will be your first transaction on
-the blockchain:
-
-```bash twoslash
-iexec app deploy --chain arbitrum-mainnet
-```
-
-::: tip
-
-While running `iexec app deploy` you sent your first transaction on the
-arbitrum-mainnet blockchain.
-
-:::
-
-You can check your deployed apps with their index, let's check your last
-deployed app:
-
-```bash twoslash
-iexec app show --chain arbitrum-mainnet
-```
-
-## Run your app on iExec
-
-iExec allows you to run applications on a decentralized infrastructure with
-payment in **RLC** tokens \(the native cryptocurrency of iExec\).
-
-::: info
-
-To run an app you must have enough RLC staked on your iExec account to pay for
-the computing resources.
-
-Your iExec account is managed by smart contracts \(and not owned by iExec\).
-
-When you request an execution the price for the task is locked from your
-account's stake then transferred to accounts of the workers contributing to the
-task \(read more about [Proof of Contribution](/protocol/proof-of-contribution)
-protocol\).
-
-At any time you can:
-
-- view your balance
-
-```bash twoslash
-iexec account show --chain arbitrum-mainnet
-```
-
-- deposit RLC from your wallet to your iExec Account
-
-```bash twoslash
-iexec account deposit --chain arbitrum-mainnet <amount>
-```
-
-- withdraw RLC from your iExec account to your wallet \(only stake can be
-  withdrawn\)
-
-```bash twoslash
-iexec account withdraw --chain arbitrum-mainnet <amount>
-```
-
-:::
-
-Currently, iExec sponsors applications running on Bellecour, and you won't have
-to pay for the computation.
-
-Everything is ready to run your app!
-
-```bash twoslash
-iexec app run --chain arbitrum-mainnet --args <your-name-here> --workerpool {{workerpoolAddress}} --watch
-```
-
-::: info
-
-`iexec app run` allows to run an application on iExec at the market price.
-
-Useful options:
-
-- `--args <args>` specify the app execution arguments
-- `--watch` watch execution status changes
-- `--workerpool <address>` specify the workerpool to use (for example:
-  `--workerpool {{workerpoolAddress}}`)
-
-Discover more option with `iexec app run --help`
-
-:::
-
-::: tip Congratulation you requested the execution of
-[iexechub/python-hello-world](https://hub.docker.com/repository/docker/iexechub/python-hello-world).
-
-This will generate an ASCII art greeting with your name.
-
-:::
-
-The execution of tasks on the iExec network is asynchronous by design.
-
-```mermaid
-graph TD
-    Requester["Requester (or anyone)"] --> |"1 . Match compatible orders \n(request, application, dataset & workerpool orders) \n & Wait result" | Blockchain
-    Blockchain --> |2 . Notify new deal with tasks to compute| Scheduler
-    Worker --> |3 . Request new task to compute| Scheduler
-    Worker --> |4 . Run application| Application[Application image]
-    Worker --> |5.a. Push result| ResultStorage["Result Storage"]
-    Worker --> |5.b. Commit result proof| Blockchain
-    Workerpool --> |6 . Publish result link or callback| Blockchain
-
-    subgraph Workerpool
-        Scheduler
-        Worker
-        Application
-    end
-```
-
-Guaranties about completion times (fast/slow) are available in the
-[category section](/protocol/pay-per-task):
-
-- maximum deal/task time
-- maximum computing time
-
-Once the task is completed copy the taskid from `iexec app run` output \(taskid
-is a 32Bytes hexadecimal string\).
-
-Download the result of your task
-
-```bash twoslash
-iexec task show --chain arbitrum-mainnet <taskid> --download my-result
-```
-
-You can get your taskid with the command:
-
-```bash twoslash
-iexec deal show --chain arbitrum-mainnet <dealid>
-```
-
-::: info
-
-A task result is a zip file containing the output files of the application.
-
-:::
-
-[iexechub/python-hello-world](https://hub.docker.com/repository/docker/iexechub/python-hello-world)
-produce an text file in `result.txt`.
-
-Let's discover the result of the computation.
-
-```bash
-unzip my-result.zip -d my-result
-cat my-result/result.txt
-```
-
-Congratulations! You successfully executed your application on iExec!
-
-## Publish your app on the iExec Marketplace
-
-You deployed your app on iExec and completed an execution on iExec. For now,
-only you can request an execution of your application. The next step is to
-publish it on the iExec Marketplace, making it available for anyone to use.
-
-As the owner of this application, you can define the conditions under which it
-can be used
-
-::: info
-
-iExec uses orders signed by the resource owner's wallet to ensure resources
-governance.
-
-The conditions to use an app are defined in the **apporder**.
-
-:::
-
-Publish a new apporder for your application.
-
-```bash twoslash
-iexec app publish --chain arbitrum-mainnet
-```
-
-::: info
-
-`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
-values for now.
-
-:::
-
-Your application is now available for everyone on iExec marketplace on the
-conditions defined in apporder.
-
-You can check the published apporders for your app
-
-```bash twoslash
-iexec orderbook app --chain arbitrum-mainnet <your app address>
-```
-
-Congratulation you just created a decentralized application! Anyone can now
-trigger an execution of your application on the iExec decentralized
-infrastructure.
-
 ## What's next?
 
 You are now familiar with the following key iExec concepts for developers: