Skip to main content

Job Creation

Use the Acurast Console to specify a job and post it on Acurast to be executed by Processors.

Protocol and Templates Selection

Select the protocol / chain the job should fulfill on and select a job template as a starting point. Alternatively it is possible to just start with a blank template.

Job Script

Adapt the job script so that it performs the task you need. The above images show the template for publishing a price on Ethereum.

Job Schedule

Specify if the job should be matched to the available public processors or if it should run on a specific ones.

Additionally, specify start and end times for the job, the execution interval and the duration.

It is recommended to not have a start time sooner than 10 minutes from the present.

Job Environment Variables

It is possible to specify environment variables that the script can access at runtime. This is useful when the script needs to use data that should be secret, for example an API key allowing permissioned access to the API.

If an environment variable is specified like in pictured above, it will be accessible from the script with:

const myApiKey = _STD_.env["MY_API_KEY"];

The environment variables will be encrypted and only the Processor assigned to the job will be able to use them. Not even the owner of the device will be able to access this variable as it can only be encrypted within the Trusted Execution Environment of the devices.

Using environment variables will require a processor with the DataEncryption module enabled which wille be activated automatically in your job when adding one or more environment variables.

Job Reward and Publish

Specify the number of processors that should be assigned to run the job, the minimum reputation each processor needs to have and the reward per job execution, then publish the job.

Job Creation Progress

After publishing the job, a job creation progress screen is displayed, showing the various initial stage of the job creation:

  • Job is registered on chain
  • Job is matched to one or more processors
  • Job is acknowledged by the matched processors
    • At this point, if environment variables were specified, then the Set or Set All buttons should be pressed to encrypt and publish those variables on chain.

Go to Job will open the job details page where all the job's details are displayed and the environment variables can be updated.

In the Assigned Processors section, the list of assigned processors is displayed.

Each processor will use a dedicated account for the user creating the job, thus here you can see the various addresses the processor will use when interacting with the various chains (selected from the drop down menus).

If you see the Transaction Fees Required warning, it means that the chain has a Level 1 integration with Acurast and the user is responsible for those accounts to have enough balance to pay for the transaction fees.