Spire

• Name: Spire / Based Stack
• URL: https://docs.spire.dev/
• Tags: ethereum-ecosystem
• Category: based-rollup stack / sequencer-election design / preconfirmation routing middleware
• Summary: Spire is best understood as a configurable based-rollup control plane. What matters is the split between the ticket market that allocates sequencing rights, the eligibility rules that decide which L1 proposers or sequencers can use those rights, the optional censorship-resistance gadgets that can constrain block contents, and the Preconf Router that can become the practical wallet-facing chokepoint for fast commitments.
• What it does:
  • Builds and maintains the open-source Based Stack for deploying Ethereum-based rollups and appchains
  • Uses a Dutch-auction ticket system to allocate sequencing rights ahead of the Ethereum proposer lookahead
  • Elects eligible based sequencers from the lookahead using configurable rules around ticket ownership and optional minimum preconfirmation collateral
  • Supports optional forward-sequencer and CR-committee layers that can constrain block contents for censorship-resistance or policy reasons
  • Positions preconfirmations as a separate but integrated layer and runs a general-purpose Preconf Router that routes transactions to one of multiple preconf providers
  • Frames the stack as open-source and “credibly neutral,” specifically claiming no required token and no mandatory dependence on one provider or one sequencing-revenue extractor
• Key claims:
  • The Based Stack repository describes itself as an open-source framework for deploying based rollups that outsource block production to Ethereum and aim for decentralization, neutrality, and shared security rather than a centralized sequencer model.
  • Spire’s based-sequencing docs make the sequencing market explicit: an L1 election contract runs a Dutch auction that distributes tickets, and those tickets plus Ethereum’s proposer lookahead determine who gets sequencing rights for appchain blocks.
  • The same docs say the elected based sequencer has the exclusive ability to sequence and propose appchain blocks and therefore to give preconfirmations and other proposer commitments, which makes sequencer election a direct preconfirmation-power allocation mechanism rather than merely a block-ordering detail.
  • Spire’s preconfirmation docs say the Based Stack itself is preconf-protocol agnostic, while still intentionally preferring sequencer-election configurations where elected proposers have posted preconfirmation collateral; this makes Spire analytically useful as a distribution and routing layer above specific commitment protocols.
  • The docs also expose optional forward-sequencer and CR-committee roles that can constrain the next block’s contents, which is important because it shows the stack is not only about auctioning a sequencer slot but also about defining who can shape censorship-resistance and inclusion policy.
  • Spire’s Preconf Router page says it is a general-purpose Ethereum RPC that adds preconfirmations by routing transactions to one of a number of preconf providers, which means the practical chokepoint may sit in wallet/app routing rather than in any single downstream commitment protocol.
  • The “open source and credibly neutral” page explicitly claims the Based Stack does not depend on a token, rely on a specific service provider, or extract sequencing revenue by default; even if that neutrality remains partly aspirational, it is a useful declared design target for comparison against more vertically integrated stacks.
  • The sequencing-revenue docs make clear that Spire is also trying to price sequencing rights so some MEV flows back to the application, which makes it a useful comparison point against both pure based sequencing and more explicit fast-lane / orderflow-auction systems.
• Whitepaper: No standalone Spire or Based Stack whitepaper surfaced in this pass. The strongest primary materials were the official docs, the public Based Stack repository, and the Preconf Router documentation collected in ../whitepapers/spire-primary-sources-2026-05-11.md.
• Sources:
  • https://docs.spire.dev/
  • https://docs.spire.dev/based-stack/based-sequencing
  • https://docs.spire.dev/based-stack/preconfirmations
  • https://docs.spire.dev/based-stack/open-source-and-credibly-neutral
  • https://docs.spire.dev/based-stack/sequencing-revenue-mev-retention
  • https://docs.spire.dev/preconf-rpc
  • https://github.com/spire-labs/based-stack

Internal linkages

• Strongest comparison points: puffer-preconf, bolt, and espresso.

Control / trust posture

• Spire is useful because it makes the hidden authority surfaces fairly plain: ticket ownership, eligibility rules, router defaults, and optional forward-sequencer or CR-committee policy.

• That is a better frame than the neutral-marketing version. The question is who buys, routes, and constrains the right to issue fast commitments.

• Last reviewed: 2026-05-27 UTC