LibraryScaling2023Design paperCorpus record
Linea: a zkEVM rollup specification
Linea. Consensys.
Linea publishes a zkEVM rollup: execution is argued by proof to a settlement contract, and the sequencer's order is not itself the proof.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
Linea publishes a zkEVM rollup: execution is argued by proof to a settlement contract, and the sequencer's order is not itself the proof.
- Evidence
- Primary paper
- Re-measured
- No
- Assumptions
- 3
- Records linked
- 6
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.
Claim 01 · Paper model
The defect
A Consensys product name is not a specification. The specification is the object that says what the proof must show.
Claim 02 · Paper model
The proposal
Linea publishes a zkEVM rollup: execution is argued by proof to a settlement contract, and the sequencer's order is not itself the proof.
Claim 03 · Paper model
The mechanism
The proof is meant to attest an Ethereum-like execution. Differences in precompiles or gas are part of the spec, not footnotes you may ignore.
Claim 04 · Paper model
The bound
No equivalence score, fee, or finality time is stated here.
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.
01 The defect
Observation
What the study says
A Consensys product name is not a specification. The specification is the object that says what the proof must show.
Model
What has to hold
You are reading Linea's public technical docs, not a press release.
Falsifier
What would retire it
What does the proof statement include besides a new root?
02 The proposal
Observation
What the study says
Linea publishes a zkEVM rollup: execution is argued by proof to a settlement contract, and the sequencer's order is not itself the proof.
Model
What has to hold
You are reading Linea's public technical docs, not a press release.
Falsifier
What would retire it
Which differences from the EVM does Linea itself document?
03 The mechanism
Observation
What the study says
The proof is meant to attest an Ethereum-like execution. Differences in precompiles or gas are part of the spec, not footnotes you may ignore.
Model
What has to hold
No price, supply, yield, or adoption figure is added by this desk.
Falsifier
What would retire it
What does the proof statement include besides a new root?
04 The bound
Model
What has to hold
You are reading Linea's public technical docs, not a press release.
Falsifier
What would retire it
What does the proof statement include besides a new root?
03 Sequence
One action, as an operating tape
- 01The proof is meant to attest an Ethereum-like execution. Differences in precompiles or gas are part of the spec, not footnotes you may ignore.
- 02The bridge releases funds against the proven root, not against a blog post.
- 03A change of prover stack is allowed only if the settlement contract is changed to match. Otherwise the old statement is still the rule.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
Linea publishes a zkEVM rollup: execution is argued by proof to a settlement contract, and the sequencer's order is not itself the proof.
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.
What actually moves
The cut
The bridge releases funds against the proven root, not against a blog post.
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.
What a later deployment may change
The cut
A change of prover stack is allowed only if the settlement contract is changed to match. Otherwise the old statement is still the rule.
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
Operator keys, if the docs still name them, are a trust assumption and have to be read as one.
05 Register
What has to be true
Model · Not re-measured
You are reading Linea's public technical docs, not a press release.
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 an endorsement of any Consensys product.
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
- 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 Consensys product name is not a specification. The specification is the object that says what the proof must show.
What the design proposes
- The proof is meant to attest an Ethereum-like execution. Differences in precompiles or gas are part of the spec, not footnotes you may ignore.
- The bridge releases funds against the proven root, not against a blog post.
- A change of prover stack is allowed only if the settlement contract is changed to match. Otherwise the old statement is still the rule.
How the mechanism is specified
- The proof is meant to attest an Ethereum-like execution. Differences in precompiles or gas are part of the spec, not footnotes you may ignore.
- The bridge releases funds against the proven root, not against a blog post.
- A change of prover stack is allowed only if the settlement contract is changed to match. Otherwise the old statement is still the rule.
What this page does not treat as proven
- No equivalence score, fee, or finality time is stated here.
- Operator keys, if the docs still name them, are a trust assumption and have to be read as one.
- This is not an endorsement of any Consensys product.
Why the desk still reads it
Linea publishes a zkEVM rollup: execution is argued by proof to a settlement contract, and the sequencer's order is not itself the proof.
09 Lexicon
Terms, opened into the record
- Verifier contract
- The settlement contract that accepts or rejects a proof.
- Operator
- A party the docs may still trust for ordering or upgrades. Naming them is part of the design.
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.
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.