Manage your datasetorders
Orders enable setting custom governance for resources.
Here you will learn how to manage your dataset's monetization rules.
Publish a custom datasetorder
Initialize a datasetorder:
Edit the datasetorder part in iexec.json to set the conditions to use your dataset:
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)
the restriction is disabled by default with 0x0000000000000000000000000000000000000000
The supported tags for dataset orders are:
0x0000000000000000000000000000000000000000000000000000000000000000
No specific feature. Beware, such orders can be matched in TEE workerpools orders.
0x0000000000000000000000000000000000000000000000000000000000000003
Encrypted dataset for TEE task with Scone framework.
0x0000000000000000000000000000000000000000000000000000000000000005
Encrypted dataset for TEE task with Gramine framework (reserved value, do not use)
TEE tasks with Gramine TEE framework are not supported yet. Do not publish orders with both tee and gramine tag bits enabled.
As soon as your datasetorder complies to your requirements, you must sign it and you may publish it.
Remove an order from iExec Marketplace
List the published orders for your dataset.
Copy the orderHash of the order you want to remove
Unpublish the datasetorder from the iExec Marketplace
An unpublished order is still valid on the blockchain, to invalidate it use the cancel command.
Last updated