Smart Contracts

Data Registry

Data refinement (encrypted, normalized, queryable) content IDs (CIDs) for individual files are now also stored in the data registry. This allows for later retrieval and re-indexing by the Query Engine in the data access layer.

Job Registry (New)

The job registry contract manages Compute Engine job executions, meaning

• defining which pre-configured jobs can be run through the Compute Engine (such as a basic data query job)
• submitting new jobs to run for application builders with pre-deposited payment amounts in $VANA to be consumed by the Compute Engine as job runs are successfully completed
• cancelling or retrieving the status of existing jobs

Query Engine (New)

The query engine contract primarily serves as the gateway for permissioning data access with pricing transparency. This is where:

• DataDAOs submit & approve new general permission requests on behalf of application builders with generalized pricing for all potential data consumers
• DataDAOs approve, reject, revoke, or check permission requests

Data Refiner Registry (New)

The data refiner registry contract holds the list of all known data refiner types and instructions utilized in the data refinement process of a DataDAO's Proof-Of-Contribution (PoC) step.

Data refiners store references to

• off-chain schema definitions that clearly denote the normalized structure of data refined with the type
• off-chain refinement instructions in the form of the container url used to refine the data
• onchain owner information such as the relevant DataDAO