~/iexec-projects
- created previously, during the quick start tutorial.datasets/encrypted
, datasets/original
and .secrets/datasets
. A new section "dataset"
will be added to the iexec.json
file as well."Hello, world!"
as content inside datasets/original
. Alternatively, you can put your own dataset file.iexec dataset encrypt
will output a checksum, keep this value for a later use.datasets/encrypted/my-first-dataset.txt.enc
. That file is the encrypted version of your dataset, you should push it somewhere accessible because the worker will download it during the execution process. You will enter this file's URI in the iexec.json
file (multiaddr
attribute) when you will deploy your dataset. Make sure that the URI is a DIRECT download link (not a link to a web page for example)..secrets/datasets/my-first-dataset.txt.key
is the encryption key, make sure to back it up securely. The file .secrets/datasets/dataset.key
is just an "alias" in the sense that it is the key of the last encrypted dataset.iexec.json
file. Choose a name
for your dataset, put the encrypted file's URI in multiaddr
(the URI you got after publishing the file), and add the checksum
(you can get it by running sha256sum datasets/encrypted/my-first-dataset.txt.enc
)sed
commands will do the trick:~/iexec-projects/
.src/
create the file app.js
or app.py
then copy this code inside:sconify.sh
script to build the TEE-debug app.iexec.json
and fill in the standard keys and the mrenclave
object:SCONE_HASH=1
to get the enclave fingerprint (mrenclave):--tag tee
and the dataset to use --dataset <datasetAddress>
in iexec app run
command to run a tee app with a dataset.0xe6806E69BA8650AF23264702ddD43C4DCe35CcCe
(see deployed workerpools on https://v7.pools.iex.ec).