Skip to content

LibraryScaling2023Design paperCorpus record

Base: an OP Stack rollup operated as a product

Base rollup. Coinbase.

Base publishes itself as an OP Stack chain with an operator. The fault-proof and bridge rules are the OP Stack's, plus whatever operator role Base's own docs add.

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

Base publishes itself as an OP Stack chain with an operator. The fault-proof and bridge rules are the OP Stack's, plus whatever operator role Base's own docs add.
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 product chain is not a new proof system. If the docs add a sequencer role or a pause, that addition is the part that is Base's.

  2. Claim 02 · Paper model

    The proposal

    Base publishes itself as an OP Stack chain with an operator. The fault-proof and bridge rules are the OP Stack's, plus whatever operator role Base's own docs add.

  3. Claim 03 · Paper model

    The mechanism

    Derivation and deposits follow the OP Stack specification unless Base's docs override them. An override is the interesting sentence.

  4. Claim 04 · Paper model

    The bound

    This note does not say the fault proof is permissionless. Read the current bridge roles.

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 product chain is not a new proof system. If the docs add a sequencer role or a pause, that addition is the part that is Base's.

    Model

    What has to hold

    You are reading Base's docs beside the OP Stack spec. The spec is the other study.

    Falsifier

    What would retire it

    Who can pause or upgrade the bridge?

  2. 02 The proposal

    Observation

    What the study says

    Base publishes itself as an OP Stack chain with an operator. The fault-proof and bridge rules are the OP Stack's, plus whatever operator role Base's own docs add.

    Model

    What has to hold

    You are reading Base's docs beside the OP Stack spec. The spec is the other study.

    Falsifier

    What would retire it

    Which OP Stack version does the page claim?

  3. 03 The mechanism

    Observation

    What the study says

    Derivation and deposits follow the OP Stack specification unless Base's docs override them. An override is the interesting sentence.

    Model

    What has to hold

    You are reading Base's docs beside the OP Stack spec. The spec is the other study.

    Falsifier

    What would retire it

    Which OP Stack version does the page claim?

  4. 04 The bound

    Observation

    What the study says

    This note does not say the fault proof is permissionless. Read the current bridge roles.

    Model

    What has to hold

    You are reading Base's docs beside the OP Stack spec. The spec is the other study.

    Falsifier

    What would retire it

    Who can pause or upgrade the bridge?

03 Sequence

One action, as an operating tape

  1. 01Derivation and deposits follow the OP Stack specification unless Base's docs override them. An override is the interesting sentence.
  2. 02The sequencer orders transactions. Ordering is not the fault proof.
  3. 03An operator controlled by a company is a censorship and liveness assumption. The docs either name it or they are incomplete.

04 Load-bearing

The argument, and where a pitch drops it

  1. What the name has to mean

    The cut

    Base publishes itself as an OP Stack chain with an operator. The fault-proof and bridge rules are the OP Stack's, plus whatever operator role Base's own docs add.

    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 say the fault proof is permissionless. Read the current bridge roles.

  2. What actually moves

    The cut

    The sequencer orders transactions. Ordering is not the fault 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

    This note does not say the fault proof is permissionless. Read the current bridge roles.

  3. What a later deployment may change

    The cut

    An operator controlled by a company is a censorship and liveness assumption. The docs either name it or they are incomplete.

    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

    Coinbase the company is not the OP Stack specification.

05 Register

What has to be true

  • Model · Not re-measured

    You are reading Base's docs beside the OP Stack spec. The spec is the other 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

Coinbase the company is not the OP Stack specification.

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

  1. 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 product chain is not a new proof system. If the docs add a sequencer role or a pause, that addition is the part that is Base's.

What the design proposes

  • Derivation and deposits follow the OP Stack specification unless Base's docs override them. An override is the interesting sentence.
  • The sequencer orders transactions. Ordering is not the fault proof.
  • An operator controlled by a company is a censorship and liveness assumption. The docs either name it or they are incomplete.

How the mechanism is specified

  • Derivation and deposits follow the OP Stack specification unless Base's docs override them. An override is the interesting sentence.
  • The sequencer orders transactions. Ordering is not the fault proof.
  • An operator controlled by a company is a censorship and liveness assumption. The docs either name it or they are incomplete.

What this page does not treat as proven

  • This note does not say the fault proof is permissionless. Read the current bridge roles.
  • It states no fee and no sequencer uptime.
  • Coinbase the company is not the OP Stack specification.

Why the desk still reads it

Base publishes itself as an OP Stack chain with an operator. The fault-proof and bridge rules are the OP Stack's, plus whatever operator role Base's own docs add.

09 Lexicon

Terms, opened into the record

Product rollup
A named deployment of a stack, with an operator. It is not the stack's specification.
Override
A place where the deployment's docs differ from the stack. That place is the deployment's 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.