Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file modified src/assets/tooling-&-explorers/iexec-explorer/dataset-view.png
Loading
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.
Binary file not shown.
51 changes: 35 additions & 16 deletions src/get-started/tooling-and-explorers/iexec-explorer.md
Original file line number Diff line number Diff line change
Expand Up @@ -114,13 +114,6 @@

### Task Execution Monitoring

<ImageViewer
:image-url-dark="taskDetailsStartedImage"
image-alt="Result Decryption"
:link-url="`${explorerUrl}/tasks`"
caption="Explore Tasks"
/>

<ImageViewer
:image-url-dark="taskDetailsCompletedImage"
image-alt="Task Completed"
Expand Down Expand Up @@ -154,7 +147,7 @@
:image-url-dark="appViewImage"
image-alt="App View"
:link-url="`${explorerUrl}/apps`"
caption="Explore iApp Marketplace"
caption="Explore iApp"
/>

Explore the iExec application marketplace:
Expand All @@ -169,24 +162,50 @@
:image-url-dark="datasetViewImage"
image-alt="Dataset View"
:link-url="`${explorerUrl}/datasets`"
caption="Explore Protected Datasets"
caption="Explore Protected Data"
/>

Navigate the protected data landscape:

- **Data Catalog**: Discover available datasets with their metadata and asset
type
- **Usage Patterns**: Analyze dataset popularity and user adoption
- **Schema Validation**: Ensure data structure compatibility with your
applications
- **Data Catalog**: Discover available protected data with their metadata and
asset types
- **Usage Analytics**: Analyze protected data popularity and adoption trends
across the network
- **Schema Discovery**: Find protected data that matches your requirements using
advanced filtering

The explorer provides a powerful filtering system that lets you search for
protected data based on their schema structure, making it easy to find datasets
compatible with your iApp.

<ImageViewer
:image-url-dark="assetTypesAdvanceFilterViewImage"
image-alt="asset Types Advance Filter View"
:link-url="`${explorerUrl}/datasets`"
caption="Explore Asset Types Filter"
/>

**How to use the asset type filter:**

1. **Select asset type criteria** - Choose from predefined types and enter the
field names
2. **Apply multiple filters** - Combine asset type filters with other criteria
like date range, owner, or tags
3. **Browse matching datasets** - View only the protected data that matches your
schema requirements

This filtering capability is essential when building iApps that need specific

Check failure on line 197 in src/get-started/tooling-and-explorers/iexec-explorer.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/get-started/tooling-and-explorers/iexec-explorer.md#L197

[Vale.Spelling] Did you really mean 'iApps'?
Raw output
{"message": "[Vale.Spelling] Did you really mean 'iApps'?", "location": {"path": "src/get-started/tooling-and-explorers/iexec-explorer.md", "range": {"start": {"line": 197, "column": 54}}}, "severity": "ERROR"}
data structures. For example, if your iApp processes user profiles, you can
filter for datasets containing `email: string` and `age: f64` fields to ensure
compatibility.

## Workerpools

<ImageViewer
:image-url-dark="workerpoolViewImage"
image-alt="Workerpool View"
:link-url="`${explorerUrl}/workerpools`"
caption="Explore Workerpools Infrastructure"
caption="Explore Workerpools"
/>

Explore the decentralized computing infrastructure:
Expand Down Expand Up @@ -216,9 +235,9 @@
import explorerGlobalImage from '@/assets/tooling-&-explorers/iexec-explorer/explorer-global.png';
import dealViewImage from '@/assets/tooling-&-explorers/iexec-explorer/deal-view.png';
import taskViewImage from '@/assets/tooling-&-explorers/iexec-explorer/task-view.png';
import taskDetailsStartedImage from '@/assets/tooling-&-explorers/iexec-explorer/task-details-started.png';
import taskDetailsCompletedImage from '@/assets/tooling-&-explorers/iexec-explorer/task-details-completed.png';
import appViewImage from '@/assets/tooling-&-explorers/iexec-explorer/app-view.png';
import datasetViewImage from '@/assets/tooling-&-explorers/iexec-explorer/dataset-view.png';
import workerpoolViewImage from '@/assets/tooling-&-explorers/iexec-explorer/workerpool-view.png';
import assetTypesAdvanceFilterViewImage from '@/assets/tooling-&-explorers/iexec-explorer/asset-types-advance-filter.png';
</script>
3 changes: 2 additions & 1 deletion src/guides/build-iapp/inputs.md
Original file line number Diff line number Diff line change
Expand Up @@ -413,7 +413,8 @@

### How to Access App Secrets

App secrets are exposed as environment variables following the `IEXEC_APP_DEVELOPER_SECRET` naming pattern.
App secrets are exposed as environment variables following the

Check notice on line 416 in src/guides/build-iapp/inputs.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/guides/build-iapp/inputs.md#L416

[Google.Passive] In general, use active voice instead of passive voice ('are exposed').
Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('are exposed').", "location": {"path": "src/guides/build-iapp/inputs.md", "range": {"start": {"line": 416, "column": 13}}}, "severity": "INFO"}
`IEXEC_APP_DEVELOPER_SECRET` naming pattern.

::: code-group

Expand Down
23 changes: 23 additions & 0 deletions src/guides/manage-data/handle-schemas-dataset-types.md
Original file line number Diff line number Diff line change
Expand Up @@ -16,6 +16,11 @@
contains an email address and a phone number" without revealing the actual
values.

Use the
<a :href="`${explorerUrl}/datasets`" target="_blank" rel="noopener">iExec
explorer</a> to browse protected data and see their asset types. Make filtered
searches based on schema to find data that fits your needs.

## How schemas work

When you protect data with DataProtector, the SDK automatically analyzes your
Expand Down Expand Up @@ -131,6 +136,10 @@

## Real examples

For real-world applications built by developers using various asset types, check
out the [iExec case studies](https://www.iex.ec/case-studies) to see how schemas
are used in production environments.

Check notice on line 141 in src/guides/manage-data/handle-schemas-dataset-types.md

View workflow job for this annotation

GitHub Actions / vale

[vale] src/guides/manage-data/handle-schemas-dataset-types.md#L141

[Google.Passive] In general, use active voice instead of passive voice ('are used').
Raw output
{"message": "[Google.Passive] In general, use active voice instead of passive voice ('are used').", "location": {"path": "src/guides/manage-data/handle-schemas-dataset-types.md", "range": {"start": {"line": 141, "column": 1}}}, "severity": "INFO"}

### Simple User Profile

```ts twoslash
Expand Down Expand Up @@ -269,3 +278,17 @@
for running computations
- **See it in action**: Try our [Hello World tutorial](/get-started/helloWorld)
for a complete example

<script setup>
import { computed } from 'vue';
import useUserStore from '@/stores/useUser.store';
import {getChainById} from '@/utils/chain.utils';
import ImageViewer from '@/components/ImageViewer.vue';

// Get current chain info
const userStore = useUserStore();
const selectedChain = computed(() => userStore.getCurrentChainId());

const chainData = computed(() => getChainById(selectedChain.value));
const explorerUrl = computed(() => chainData.value.iexecExplorerUrl);
</script>
Original file line number Diff line number Diff line change
Expand Up @@ -208,8 +208,7 @@ const processProtectedDataResponse =

Do not use this to provide any sensitive information to the application. All
arguments passed this way are visible in plain text using the
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
explorer</a> .
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .

:::

Expand Down Expand Up @@ -448,8 +447,7 @@ import { type ProcessProtectedDataResponse } from '@iexec/dataprotector';

The ID of the transaction that happened on iExec's side chain. You may view
details on the transaction using the
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
explorer</a> .
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .

### dealId

Expand All @@ -463,8 +461,7 @@ Identifies the specific deal associated with this transaction.

A unique identifier associated with a task currently running on the iExec
protocol. You can monitor task execution using the
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
explorer</a> .
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .

::: tip

Expand Down
3 changes: 1 addition & 2 deletions src/references/web3mail/methods/sendEmail.md
Original file line number Diff line number Diff line change
Expand Up @@ -313,8 +313,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
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
explorer</a> .
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .

## Error Handling

Expand Down
3 changes: 1 addition & 2 deletions src/references/web3telegram/methods/sendTelegram.md
Original file line number Diff line number Diff line change
Expand Up @@ -281,8 +281,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
<a :href="explorerUrl" target="_blank" rel="noopener">iExec blockchain
explorer</a> .
<a :href="explorerUrl" target="_blank" rel="noopener">iExec explorer</a> .

<script setup>
import { computed } from 'vue';
Expand Down