Skip to main content

Configuration

In order to use Super Protocol CLI tool, you need to create config.json file in the same directory where you put spctl file. You can obtain the sample of config.json file from the repository. Alternatively, you can make use of the CLI commands and the tool will automatically create an empty config.json file for you.

Open config.json file and fill in the parameters in accordance with the instructions below.

backend

This section contains parameters needed to connect to Super Protocol backend. The backend significantly optimizes the reading of data from the blockchain, for example, offers and orders.

ParameterDescription
urlhttps://bff.testnet.superprotocol.com/graphql
accessTokenYour personal access token from the Testnet invitation email

blockchain

This section contains parameters needed to establish a connection to the blockchain.

ParameterDescription
rpcUrlhttps://mumbai.polygon.superprotocol.com/hesoyam

Note. You can use a different node, but the Super Protocol team will not be able to provide any support associated with it.
smartContractAddress0xf96266Ec42f8D7ccf5831eBCaD3f4851967e9D45
accountPrivateKeyYour personal private key from the Testnet invitation email
authorityAccountPrivateKeyRequired for offer creation. Leave this field blank if you are not a provider.

storage

Before you can deploy your own solutions or use your own data on Super Protocol, you need to encrypt and upload them to some storage that TEE providers could have access to. See these guides for information on the supported storages and how to configure them.

ParameterDescription
typeSTORJ

Note. More storage types will be supported in the future.
bucketSTORJ bucket. Your encrypted solutions and data are uploaded to this bucket.
writeAccessTokenSTORJ access grant with write permission for the specified bucket. This token is used by CLI to upload your encrypted solutions and data to the specified bucket.
readAccessTokenSTORJ access grant with read permission for the specified bucket. This token is used by TEE providers to access your encrypted solutions and data.

workflow

This section contains parameters related to the creation of new orders.

resultEncryption

TEE providers always encrypt results before uploading them to the storage. The parameters below are related to this encryption.

ParameterDescription
algoECIES

Note. More algorithms will be supported in the future.
keyPrivate key for order results encryption. Public key derived from it is used by TEE providers to encrypt order results. Use workflows generate-key command to generate this key.
encodingbase64

Note. More types will be supported in the future.