Render Offers and Requests

The JSON schemas for render offer documents and render request documents on this page are still under development and subject to change.

Render offers

Render offers define the hardware parameters, performance parameters and render prices that a render node offers on the hive. Each render node will store a render offer document on the IPFS, which contains all the information about the render node's terms of service, rendering abilities, and pricing. The node is free to change that document at any time. The JSON schema of this document looks as follows:

// JSON schema for the render offer document
render_offer = {
    ID: int              // a unique ID of the render offer
    render_power: int    // offered render power
    ...
}

Render requests

Client nodes can submit render requests at any time, which represent the request to render a specific Blender file for a specific maximum price. To submit the render job to the render hive, the client node stores both the Blender file and a render request document on the IPFS. The latter contains all the information about the render job (e.g., CID of the Blender file, render settings, render terms, maximum total price, maximum price per BBP, total render work estimate, requested render power, distribution strategy, etc.). This document will be a JSON file that adheres to the following schema:

// JSON schema for the render request document
render_request = {
    ID: int              // a unique ID of the render offer
    file: CID            // CID of the Blender file to render
    render_work: int     // requested render work
    client_render: bool  // True, if the client participates in rendering this job
    ...
}

Since the CIDs of both render offer documents and render request documents are unique identifiers representing the content of the file, it is also guaranteed that nodes cannot come to different conclusions about the job parameters, the pricing or other contract terms.