Skip to content
Blockchain LabTHE VENTURE STUDIO

LibraryConfidential compute2023Design paperCorpus record

Plonky3: a toolkit of proof-system components

Plonky3. Polygon Zero.

Plonky3 publishes components, fields, hashes, and AIR machinery, rather than one circuit. A project that says it uses Plonky3 has named a toolkit, not a statement.

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

Plonky3 publishes components, fields, hashes, and AIR machinery, rather than one circuit. A project that says it uses Plonky3 has named a toolkit, not a statement.
Evidence
Primary paper
Re-measured
No
Assumptions
3
Records linked
3

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 toolkit does not prove a rollup. The AIR or the circuit the project wrote is the statement. The toolkit is the engine.

  2. Claim 02 · Paper model

    The proposal

    Plonky3 publishes components, fields, hashes, and AIR machinery, rather than one circuit. A project that says it uses Plonky3 has named a toolkit, not a statement.

  3. Claim 03 · Paper model

    The mechanism

    Fields and hashes are parameters. Two projects on Plonky3 can still disagree about every constraint.

  4. Claim 04 · Paper model

    The bound

    This note does not quote a proving speed.

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 toolkit does not prove a rollup. The AIR or the circuit the project wrote is the statement. The toolkit is the engine.

    Model

    What has to hold

    You are reading the Plonky3 repository. Plonky2 is the separate study.

    Falsifier

    What would retire it

    Which statement is being proved: which AIR?

  2. 02 The proposal

    Observation

    What the study says

    Plonky3 publishes components, fields, hashes, and AIR machinery, rather than one circuit. A project that says it uses Plonky3 has named a toolkit, not a statement.

    Model

    What has to hold

    You are reading the Plonky3 repository. Plonky2 is the separate study.

    Falsifier

    What would retire it

    Which statement is being proved: which AIR?

  3. 03 The mechanism

    Observation

    What the study says

    Fields and hashes are parameters. Two projects on Plonky3 can still disagree about every constraint.

    Model

    What has to hold

    You are reading the Plonky3 repository. Plonky2 is the separate study.

    Falsifier

    What would retire it

    Is the verifier a Plonky3 verifier or a wrapper?

  4. 04 The bound

    Observation

    What the study says

    This note does not quote a proving speed.

    Model

    What has to hold

    You are reading the Plonky3 repository. Plonky2 is the separate study.

    Falsifier

    What would retire it

    Which statement is being proved: which AIR?

03 Sequence

One action, as an operating tape

  1. 01Fields and hashes are parameters. Two projects on Plonky3 can still disagree about every constraint.
  2. 02An AIR, an algebraic intermediate representation, is the program. It is not implied by depending on the repository.
  3. 03Plonky2 is the earlier system. Plonky3 is not a drop-in file format for Plonky2 proofs.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    Plonky3 publishes components, fields, hashes, and AIR machinery, rather than one circuit. A project that says it uses Plonky3 has named a toolkit, not a statement.

    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.

  2. What actually moves

    The cut

    An AIR, an algebraic intermediate representation, is the program. It is not implied by depending on the repository.

    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

    No rollup is endorsed because it imports this repository.

  3. What a later deployment may change

    The cut

    Plonky2 is the earlier system. Plonky3 is not a drop-in file format for Plonky2 proofs.

    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 component bug is a proof-system bug. A constraint bug is the application's.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading the Plonky3 repository. Plonky2 is the separate study.

  • 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

A component bug is a proof-system bug. A constraint bug is the application's.

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 toolkit does not prove a rollup. The AIR or the circuit the project wrote is the statement. The toolkit is the engine.

What the design proposes

  • Fields and hashes are parameters. Two projects on Plonky3 can still disagree about every constraint.
  • An AIR, an algebraic intermediate representation, is the program. It is not implied by depending on the repository.
  • Plonky2 is the earlier system. Plonky3 is not a drop-in file format for Plonky2 proofs.

How the mechanism is specified

  • Fields and hashes are parameters. Two projects on Plonky3 can still disagree about every constraint.
  • An AIR, an algebraic intermediate representation, is the program. It is not implied by depending on the repository.
  • Plonky2 is the earlier system. Plonky3 is not a drop-in file format for Plonky2 proofs.

What this page does not treat as proven

  • This note does not quote a proving speed.
  • No rollup is endorsed because it imports this repository.
  • A component bug is a proof-system bug. A constraint bug is the application's.

Why the desk still reads it

Plonky3 publishes components, fields, hashes, and AIR machinery, rather than one circuit. A project that says it uses Plonky3 has named a toolkit, not a statement.

09 Lexicon

Terms, opened into the record

AIR
The algebraic description of the computation. It is the application's statement.
Toolkit
Components for building a prover. Importing them is not a proof.

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.

Concepts

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.