Comment on page
Manage your datasetorders
Orders enable setting custom governance for resources.
Here you will learn how to manage your dataset's monetization rules.
Initialize a
datasetorder:iexec order init --dataset
Edit the
datasetorder part in iexec.json to set the conditions to use your dataset:key | description |
|---|---|
dataset | dataset address |
datasetprice | price to charge the requester for each use of the dataset (in nRLC) |
volume | number of authorized uses, each use decreases this number |
tag | restrict usage to a specific runtime such as Scone or Gramine TEE frameworks |
apprestrict | restrict to use the dataset with a specific app (1) |
workerpoolrestrict | restrict to use the dataset on a specific workerpool (1) |
requesterrestrict | restrict the dataset usage to a specific requester (1) |
- 1.the restriction is disabled by default with 0x0000000000000000000000000000000000000000
The supported tags for dataset orders are:
Tag value | Description |
|---|---|
0x0000000000000000000000000000000000000000000000000000000000000000 | No specific feature. Beware, such orders can be matched in TEE workerpools orders. |
0x0000000000000000000000000000000000000000000000000000000000000003 | Encrypted dataset for TEE task with Scone framework |
TEE tasks with Gramine framework do not support datasets. Do not publish dataset orders with the `tee` and `gramine` tag bits enabled.
As soon as your
datasetorder complies to your requirements, you must sign it and you may publish it.iexec order sign --dataset && iexec order publish --dataset
List the published orders for your dataset.
iexec orderbook dataset <your dataset address>
Copy the
orderHash of the order you want to removeUnpublish the
datasetorder from the iExec Marketplaceiexec order unpublish --dataset <orderHash>
An unpublished order is still valid on the blockchain, to invalidate it use the cancel command.
iexec order cancel --dataset <orderHash>
Last modified 3mo ago