LibraryScaling2023Design paperCorpus record
OP Stack protocol specification
OP Stack. OP Labs.
The OP Stack separates the rollup configuration from the fault-proof programme. A chain that says it is an OP Stack chain is naming a spec, not a guarantee that the fault proof is live.
A reading of the project's public design document. Not a copy, not a benchmark, and not an offer.
The OP Stack separates the rollup configuration from the fault-proof programme. A chain that says it is an OP Stack chain is naming a spec, not a guarantee that the fault proof is live.
- 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.
Claim 01 · Paper model
The defect
Calling a chain optimistic without saying who may challenge, and on what instruction trace, leaves the bridge as an admin key.
Claim 02 · Paper model
The proposal
The OP Stack separates the rollup configuration from the fault-proof programme. A chain that says it is an OP Stack chain is naming a spec, not a guarantee that the fault proof is live.
Claim 03 · Paper model
The mechanism
Deposits and withdrawals are messages to a settlement contract. The derivation rule says how those messages become a chain.
Claim 04 · Paper model
The bound
This is not a claim that any named deployment has an open, permissionless fault proof today.
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
Calling a chain optimistic without saying who may challenge, and on what instruction trace, leaves the bridge as an admin key.
Model
What has to hold
You are reading the OP Stack specification, not a single chain's status page.
02 The proposal
Observation
What the study says
The OP Stack separates the rollup configuration from the fault-proof programme. A chain that says it is an OP Stack chain is naming a spec, not a guarantee that the fault proof is live.
Model
What has to hold
You are reading the OP Stack specification, not a single chain's status page.
Falsifier
What would retire it
Is the fault-proof programme the authority, or is a key set still the authority?
03 The mechanism
Observation
What the study says
Deposits and withdrawals are messages to a settlement contract. The derivation rule says how those messages become a chain.
Model
What has to hold
You are reading the OP Stack specification, not a single chain's status page.
04 The bound
Observation
What the study says
This is not a claim that any named deployment has an open, permissionless fault proof today.
Model
What has to hold
You are reading the OP Stack specification, not a single chain's status page.
Falsifier
What would retire it
Is the fault-proof programme the authority, or is a key set still the authority?
03 Sequence
One action, as an operating tape
- 01Deposits and withdrawals are messages to a settlement contract. The derivation rule says how those messages become a chain.
- 02A fault proof disputes an instruction trace. Until that programme is the thing the bridge trusts, the bridge trusts something else, usually a set of keys.
- 03An OP Stack deployment can change its proof system without changing its brand. The spec you cite has to name which one.
04 Load-bearing
The argument, and where a pitch drops it
What the name has to mean
The cut
The OP Stack separates the rollup configuration from the fault-proof programme. A chain that says it is an OP Stack chain is naming a spec, not a guarantee that the fault proof is live.
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 is not a claim that any named deployment has an open, permissionless fault proof today.
What actually moves
The cut
A fault proof disputes an instruction trace. Until that programme is the thing the bridge trusts, the bridge trusts something else, usually a set of keys.
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 is not a claim that any named deployment has an open, permissionless fault proof today.
What a later deployment may change
The cut
An OP Stack deployment can change its proof system without changing its brand. The spec you cite has to name which one.
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 is not a claim that any named deployment has an open, permissionless fault proof today.
05 Register
What has to be true
Model · Not re-measured
You are reading the OP Stack specification, not a single chain's status page.
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
Base, Mode, and other deployments are configurations. They are not this document by default.
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
Calling a chain optimistic without saying who may challenge, and on what instruction trace, leaves the bridge as an admin key.
What the design proposes
- Deposits and withdrawals are messages to a settlement contract. The derivation rule says how those messages become a chain.
- A fault proof disputes an instruction trace. Until that programme is the thing the bridge trusts, the bridge trusts something else, usually a set of keys.
- An OP Stack deployment can change its proof system without changing its brand. The spec you cite has to name which one.
How the mechanism is specified
- Deposits and withdrawals are messages to a settlement contract. The derivation rule says how those messages become a chain.
- A fault proof disputes an instruction trace. Until that programme is the thing the bridge trusts, the bridge trusts something else, usually a set of keys.
- An OP Stack deployment can change its proof system without changing its brand. The spec you cite has to name which one.
What this page does not treat as proven
- This is not a claim that any named deployment has an open, permissionless fault proof today.
- It does not quote a fee, a throughput number, or a withdrawal delay.
- Base, Mode, and other deployments are configurations. They are not this document by default.
Why the desk still reads it
The OP Stack separates the rollup configuration from the fault-proof programme. A chain that says it is an OP Stack chain is naming a spec, not a guarantee that the fault proof is live.
09 Lexicon
Terms, opened into the record
- Output root
- The commitment the settlement bridge stores for a rollup state.
- Fault proof
- A dispute about an execution trace. It is not a mood and not a logo.
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.