Cowrie Research

based-op

4 min read

Based OP

  • Name: Based OP
  • URL: https://gattaca-com.github.io/based-op/
  • Tags: ethereum-ecosystem
  • Category: based-rollup reference stack / gateway sequencing overlay
  • Summary: Based OP is a useful reference implementation for gateway-mediated based sequencing on the OP Stack. The real mechanism is the split between the portal sidecar that intercepts Engine API calls, the gateway that sequences on behalf of L1 proposers and gossips partial blocks as frags, the modified follower stack that can replay those frags before sealing, and the rollout policy that decides whether this is still one operator with a fast sidecar or something closer to delegated based sequencing.
  • What it does:
    • Provides an open-source reference stack for deploying a Phase 1 based OP rollup that remains backwards compatible with existing OP Stack components
    • Inserts a portal sidecar between the OP node and the execution layer so Engine API calls can be multiplexed to gateways plus a fallback EL
    • Runs a specialized gateway sequencer that continuously builds blocks, breaks them into frags, and broadcasts partial block state before final sealing
    • Upgrades follower nodes and execution clients so they can replay streamed frags, serve partial-block RPC state, and reduce the latency between sequencing and user-visible confirmation
    • Starts from a phased rollout path where a centralized gateway can later expand to whitelisted and then permissionless delegated gateways with slashing
    • Gives L1 proposers or their delegates a way to participate in based sequencing without every proposer needing to run a full high-throughput specialized stack themselves
  • Key claims:
    • The docs describe Based OP as a reference implementation of a Phase 1 based OP stack that overlays high-performance components onto the existing OP stack while remaining backwards compatible.
    • The overview page makes the decentralization path explicit: first a single centralized gateway, then whitelisted gateways, and eventually permissionless gateways with proposer delegation and slashing, which is analytically useful because it surfaces rollout policy as a first-class control surface rather than a footnote.
    • The portal docs show that the portal is the immediate sequencing chokepoint in this design: it intercepts Engine API calls, selects the active gateway, forwards payload-building requests, and falls back to a conventional EL if the gateway does not deliver a valid payload.
    • The gateway docs make clear that Based OP is not simply outsourcing sequencing to an unchanged node; the gateway is a purpose-built high-performance sequencer with its own actor model, transaction sorting pipeline, simulator workers, and partial-block frag gossip path.
    • The scaling docs explain the central performance claim: instead of waiting for end-of-slot sealing, the sequencer pipelines production throughout the block interval and shares frags early so follower nodes can pre-process blocks and serve near-real-time partial state.
    • The project README reinforces that a running gateway self-registers behind the portal and sequences transactions into frags that are broadcast over p2p to follower nodes, which makes gateway discovery and registry policy another practical control surface.
    • The strongest comparison frame is not generic “faster OP Stack.” It is “external block production plus gateway election plus frag-based partial-state distribution,” which makes Based OP a useful reference point for Puffer Preconf, Spire, Rollup Boost-style sidecars, and other based-rollup sequencing designs.
  • Whitepaper: No standalone Based OP whitepaper surfaced in this pass. The strongest materials were the official docs, the public repository README, and the linked Ethereum Research design post collected in ../whitepapers/based-op-primary-sources-2026-05-11.md.
  • Sources:

Internal linkages

Control / trust posture

  • The practical authority sits in the portal, gateway selection and registration policy, fallback EL behavior, and the rollout path from one trusted gateway toward delegated or permissionless gateways.

  • So the real question is not whether Based OP is based; it is who controls the gateway set and failure handling when the fast path breaks.

  • Last reviewed: 2026-05-28 UTC

Graph View

Backlinks