Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryStorage and networks2017Design paperCorpus record

Render: a marketplace for rendering jobs

Render Network. Render Network.

The Render Network publishes a marketplace where node operators perform rendering jobs and a proof-of-render, as the docs define it, is how a job is accepted.

A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.

The Render Network publishes a marketplace where node operators perform rendering jobs and a proof-of-render, as the docs define it, is how a job is accepted.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
1

01 Claim ledger

What the paper is allowed to say

Each row is a sentence already in the study. The status is the same on every row: a model claim, not a live measurement.

  1. Claim 01 · Paper model

    The defect

    A render proof is only the check the docs specify. It may be a spot check of frames, not a proof that every pixel was honest.

  2. Claim 02 · Paper model

    The proposal

    The Render Network publishes a marketplace where node operators perform rendering jobs and a proof-of-render, as the docs define it, is how a job is accepted.

  3. Claim 03 · Paper model

    The mechanism

    A job specifies a scene. A node renders it. Acceptance follows the verification step the knowledge base names.

  4. Claim 04 · Paper model

    The bound

    This note does not define the proof beyond pointing at the docs, and it states no job count.

02 Three cuts

Observation, model, falsifier

A desk does not stop at the summary. Each claim is cut three ways, using only this study's own assumptions and checks. Nothing here is a new figure.

  1. 01 The defect

    Observation

    What the study says

    A render proof is only the check the docs specify. It may be a spot check of frames, not a proof that every pixel was honest.

    Model

    What has to hold

    You are reading Render's knowledge base. A studio pipeline built on it is an application.

    Falsifier

    What would retire it

    What is checked before a job is paid?

  2. 02 The proposal

    Observation

    What the study says

    The Render Network publishes a marketplace where node operators perform rendering jobs and a proof-of-render, as the docs define it, is how a job is accepted.

    Model

    What has to hold

    You are reading Render's knowledge base. A studio pipeline built on it is an application.

    Falsifier

    What would retire it

    Who can submit a job?

  3. 03 The mechanism

    Observation

    What the study says

    A job specifies a scene. A node renders it. Acceptance follows the verification step the knowledge base names.

    Model

    What has to hold

    You are reading Render's knowledge base. A studio pipeline built on it is an application.

    Falsifier

    What would retire it

    What happens to a disputed frame?

  4. 04 The bound

    Observation

    What the study says

    This note does not define the proof beyond pointing at the docs, and it states no job count.

    Model

    What has to hold

    You are reading Render's knowledge base. A studio pipeline built on it is an application.

    Falsifier

    What would retire it

    What is checked before a job is paid?

03 Sequence

One action, as an operating tape

  1. 01A job specifies a scene. A node renders it. Acceptance follows the verification step the knowledge base names.
  2. 02Payment is for an accepted job. A failed verification should not pay. That sentence is the design only if the docs agree.
  3. 03The token is a payment rail. It is not the verification.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    The Render Network publishes a marketplace where node operators perform rendering jobs and a proof-of-render, as the docs define it, is how a job is accepted.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    This note does not define the proof beyond pointing at the docs, and it states no job count.

  2. What actually moves

    The cut

    Payment is for an accepted job. A failed verification should not pay. That sentence is the design only if the docs agree.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

  3. What a later deployment may change

    The cut

    The token is a payment rail. It is not the verification.

    Why it carries weight

    If this cut is skipped, the paper's name is being used without the mechanism that makes the name mean anything.

    Where it is dropped

    A later client, parameter or reward formula is a different object from this paragraph.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading Render's knowledge base. A studio pipeline built on it is an application.

  • Model · Not re-measured

    The document is the one at the source URL. A marketing page with the same brand is not this text.

  • Model · Not re-measured

    No price, supply, yield, or adoption figure is added by this desk.

06 Divergence

What happened after the paper

This is not Filecoin's proof of replication.

A later client, parameter set, or reward formula is a different object. Cite this paper for the mechanism. Cite a primary release for the network. This desk has not re-run the proof.

07 Pre-mortem

What to check before you use the idea

  4. 0 of 3 marked on this browser. A mark is a reading note, not a pass, a rating, or a recommendation.

08 Anatomy

The paper, in the order a builder needs

The problem it names

A render proof is only the check the docs specify. It may be a spot check of frames, not a proof that every pixel was honest.

What the design proposes

  • A job specifies a scene. A node renders it. Acceptance follows the verification step the knowledge base names.
  • Payment is for an accepted job. A failed verification should not pay. That sentence is the design only if the docs agree.
  • The token is a payment rail. It is not the verification.

How the mechanism is specified

  • A job specifies a scene. A node renders it. Acceptance follows the verification step the knowledge base names.
  • Payment is for an accepted job. A failed verification should not pay. That sentence is the design only if the docs agree.
  • The token is a payment rail. It is not the verification.

What this page does not treat as proven

  • This note does not define the proof beyond pointing at the docs, and it states no job count.
  • A reputation score is not a cryptographic proof.
  • This is not Filecoin's proof of replication.

Why the desk still reads it

The Render Network publishes a marketplace where node operators perform rendering jobs and a proof-of-render, as the docs define it, is how a job is accepted.

09 Lexicon

Terms, opened into the record

Proof of render
Whatever check the docs require before payment. Do not upgrade it to a SNARK unless they do.
Node operator
A provider of the render. They are a counterparty.

10 Repository

Every linked record on this page

Underlined words open a page that already exists: a concept, a protocol profile, a failure record, or another paper. If a word is not underlined, this desk does not have a record for it.

Protocols

This is Blockchain Lab's reading of a public design paper. It is not the paper, not a copy of it, and not an offer of tokens, equity, custody or a partnership. Later network behaviour can diverge from the text. Nothing here is investment, legal or technical advice.

Research status: Design paper. Last reviewed: 1 October 2026. This is a reading of a public paper, not investment, legal or security advice.