You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: src/use-iapp/getting-started.md
+30-14Lines changed: 30 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,31 +1,39 @@
1
1
---
2
2
title: Getting Started with iApps
3
-
description: Learn the basics of finding and executing iApps on the iExec network
3
+
description:
4
+
Learn the basics of finding and executing iApps on the iExec network
4
5
---
5
6
6
7
# 🚀 Getting Started with iApps
7
8
8
-
Welcome to the world of secure, privacy-preserving computation! This guide will walk you through the essential steps to start using iApps on the iExec network.
9
+
Welcome to the world of secure, privacy-preserving computation! This guide will
10
+
walk you through the essential steps to start using iApps on the iExec network.
9
11
10
12
## Prerequisites
11
13
12
14
Before you begin, make sure you have:
13
15
14
16
- A Web3 wallet (MetaMask, WalletConnect, etc.)
15
-
- Some RLC tokens for paying computation fees (or access to free vouchers through learning programs)
17
+
- Some RLC tokens for paying computation fees (or access to free vouchers
18
+
through learning programs)
16
19
- Basic understanding of blockchain transactions
17
20
18
21
### 🆓 Use Our Stack for Free!
19
22
20
-
Good news! You can start using iApps **completely free** through our learning programs:
23
+
Good news! You can start using iApps **completely free** through our learning
24
+
programs:
21
25
22
-
-**Learn Web3 Program**: Get free access to our entire stack, including vouchers for iApp executions
23
-
-**Free Vouchers**: Pre-funded computation credits provided through learning initiatives
24
-
-**No RLC Required**: Start experimenting and building without any upfront costs
26
+
-**Learn Web3 Program**: Get free access to our entire stack, including
27
+
vouchers for iApp executions
28
+
-**Free Vouchers**: Pre-funded computation credits provided through learning
29
+
initiatives
30
+
-**No RLC Required**: Start experimenting and building without any upfront
31
+
costs
25
32
26
33
### 💰 Getting Started Without RLC
27
34
28
-
Don't have RLC tokens yet? No problem! Our learning programs provide everything you need:
35
+
Don't have RLC tokens yet? No problem! Our learning programs provide everything
36
+
you need:
29
37
30
38
-**Free Vouchers**: Access to pre-funded computation credits
31
39
-**Full Stack Access**: Use all iExec tools and infrastructure at no cost
@@ -35,7 +43,8 @@ Ready to dive in? Let's get started with finding and executing your first iApp!
35
43
36
44
## Step 1: Find Available iApps
37
45
38
-
The first step is discovering what iApps are available for your use case. You can find iApps through several methods:
46
+
The first step is discovering what iApps are available for your use case. You
47
+
can find iApps through several methods:
39
48
40
49
1. Visit the [iExec Explorer](https://explorer.iex.ec)
41
50
2. Navigate to the "Apps" section
@@ -55,8 +64,12 @@ Before executing an iApp, understand what it needs:
55
64
56
65
If the iApp requires protected data:
57
66
58
-
1.**Protect Your Data**: Use the [Data Protector](/manage-data/dataProtector/dataProtectorCore/protectData) to encrypt your sensitive information
59
-
2.**Grant Access**: Ensure the iApp has permission to access your protected data using [grantAccess](/manage-data/dataProtector/dataProtectorCore/grantAccess)
67
+
1.**Protect Your Data**: Use the
68
+
[Data Protector](/manage-data/dataProtector/dataProtectorCore/protectData) to
69
+
encrypt your sensitive information
70
+
2.**Grant Access**: Ensure the iApp has permission to access your protected
Copy file name to clipboardExpand all lines: src/use-iapp/guides/add-inputs-to-execution.md
+71-41Lines changed: 71 additions & 41 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,17 +1,24 @@
1
1
---
2
2
title: Add Inputs to iApp Execution
3
-
description: Learn how to provide arguments, files, secrets, and other inputs to iApp executions
3
+
description:
4
+
Learn how to provide arguments, files, secrets, and other inputs to iApp
5
+
executions
4
6
---
5
7
6
8
# 📥 Add Inputs to iApp Execution
7
9
8
-
iApps can accept various types of inputs to customize their behavior and provide necessary data for processing. This guide covers all the different ways to add inputs to your iApp executions using various iExec tools and SDKs.
10
+
iApps can accept various types of inputs to customize their behavior and provide
11
+
necessary data for processing. This guide covers all the different ways to add
12
+
inputs to your iApp executions using various iExec tools and SDKs.
9
13
10
-
::: tip ENS Addresses
11
-
**ENS (Ethereum Name Service)** is a naming system for Ethereum addresses that allows you to use human-readable names instead of long hexadecimal addresses. For example, instead of using `0x1234567890abcdef...`, you can use `debug-v8-learn.main.pools.iexec.eth`.
14
+
::: tip ENS Addresses **ENS (Ethereum Name Service)** is a naming system for
15
+
Ethereum addresses that allows you to use human-readable names instead of long
16
+
hexadecimal addresses. For example, instead of using `0x1234567890abcdef...`,
17
+
you can use `debug-v8-learn.main.pools.iexec.eth`.
12
18
13
-
In the examples below, we use `debug-v8-learn.main.pools.iexec.eth` which is iExec's official debug workerpool ENS address. This workerpool is specifically designed for testing and development purposes on the Bellecour testnet.
14
-
:::
19
+
In the examples below, we use `debug-v8-learn.main.pools.iexec.eth` which is
20
+
iExec's official debug workerpool ENS address. This workerpool is specifically
21
+
designed for testing and development purposes on the Bellecour testnet. :::
15
22
16
23
## Types of Inputs
17
24
@@ -24,12 +31,17 @@ iExec supports several types of inputs for iApp executions:
24
31
25
32
## Method 1: Adding Command-Line Arguments
26
33
27
-
Command-line arguments are passed as a string to the iApp and are visible on the blockchain.
34
+
Command-line arguments are passed as a string to the iApp and are visible on the
0 commit comments