On Demand Feeds

In On Demand feeds, the requestor can submit data feeds which will be triggered on any condition specified while placing the request for data feed. The conditions are programmable and can be as complex as the requestor needs. Generally on demand feeds are more expensive as multiple providers compete to submit the feed as there is no assignment involved. This leads to higher wastage of resources as only one data feed submission per run will be accepted and all the work done by other providers will be wasted. This might lead to the providers expecting to be compensated higher to account for the losses they might have to pay to compensate for the data feed submission. On the other hand on demand feeds might lead to faster data feeds compared to the insured feeds(explained in next section) which involves assignment thus might introduce delays if the assigned provider doesn’t submit feed in a specified interval.

Flow

1. Requestor submits the data feed request to the assignment contract and specifies the type of feed to be on demand along with details like enclave image to use, reward for the feed and conditions to be satisfied for the feed to be accepted.

2. Any provider can pick up the request and run the enclave image to generate the data feed.

3. Provider can submit the data feed to the Data Feed contract

4. If the data feed meets the specified conditions in the feed request reward as specified will be given to the provider who submitted the feed.

Step 01: Build a Job

Clients can create their own jobs – generated either via our drag-n-drop GUI interface or dropping their own custom code image along with rewards for successfully updating oracle data.

Step 02: Submit Job

The job, once submitted, is associated to the Assignment Contract, ready for execution. This job is published onto the marketplace.

Step 03: On-Demand Jobs

On-Demand jobs are more general purpose and can accommodate a much wider variety of job requests – including extremely complex or proprietary algorithms.

These jobs are made available to the entire pool of agents to compete and provide a response. The first agent to process and publish the response on-chain, earns the rewards.

Since multiple agents are actively trying to earn the rewards, there is much higher resource wastage, demanding the rewards to be equally proportionate.

Also, as there are no prerequisites or onboarding requirements to qualify to participate in executing on-demand jobs, there is no barrier-to-entry for anyone to participate and earn.

Step 04: Rewards Allocation

Once the jobs are executed, and the data is published on-chain (either from Insured feeds or On-Demand feeds) the final Data Feed Contract verifies the conditions set by the client and allocates the corresponding job rewards to the beneficiary/s.