v6 to v7 migration

iExec v7 comes with some breaking changes, follow this guide to migrate from v6 to v7.
​CLI users​
​Application migration​
​Dataset migration​
​Requester migration​
​JS library​
CLI users
Application migration
Application developers need to publish their application sell order to the v7 marketplace in order to make it available for requesters.
Upgrade iExec SDK CLI to v7:
1
npm i -g [email protected]
2
​
3
iexec -V
4
# 7.0.0
Copied!
Publish your application to the v7 marketplace:
1
iexec app publish <app-address> [options]
Copied!
Dataset migration
Dataset developers need to push their dataset secret to the v7 SMS and publish their dataset sell order to the v7 marketplace in order to make it available for requesters.
Upgrade iExec SDK CLI to v7:
1
npm i -g [email protected]
2
​
3
iexec -V
4
# 7.0.0
Copied!
Push your dataset secret to the v7 SMS:
1
iexec dataset push-secret <dataset-address> --secret-path <secret-path> [options]
Copied!
Publish your dataset to the v7 marketplace:
1
iexec dataset publish <dataset-address> [options]
Copied!
Requester migration
Requesters need to login to the Result proxy v7 to store their results and must push their encryption public key to the v7 SMS to use result encryption feature.
Upgrade iExec SDK CLI to v7:
1
npm i -g [email protected]
2
​
3
iexec -V
4
# 7.0.0
Copied!
Login to the v7 Result proxy:
1
iexec storage init
Copied!
Push your encryption key to the v7 SMS:
1
iexec result push-encryption-key [options]
Copied!
JS library
Upgrade iExec SDK CLI to v7 in your project's dependencies to use the v7 stack.
1
npm i [email protected]
Copied!

Key Concepts - Previous

Pay per task model

Next - Help

Glossary

Last modified 29d ago

Copy link

Contents

CLI users

Application migration

Dataset migration

Requester migration

JS library