spire-primary-sources-2026-05-11

Spire primary sources

Collected: 2026-05-11 UTC

Primary sources reviewed

• https://docs.spire.dev/
  • Official documentation home
  • Used to confirm product surface and documentation structure
• https://docs.spire.dev/based-stack/based-sequencing
  • Official sequencing design documentation
  • Used to confirm the Dutch-auction ticket model, lookahead-based sequencer election, eligible-proposer rules, forward-sequencer layer, and CR-committee layer
• https://docs.spire.dev/based-stack/preconfirmations
  • Official preconfirmation design notes
  • Used to confirm Spire’s protocol-agnostic preconfirmation framing, the role of minimum collateral in sequencer eligibility, and the claim that the stack is designed to be friendly to downstream preconf protocols
• https://docs.spire.dev/based-stack/open-source-and-credibly-neutral
  • Official positioning page
  • Used to confirm the explicit no-token / no-required-provider / no-default-revenue-extraction neutrality claim
• https://docs.spire.dev/based-stack/sequencing-revenue-mev-retention
  • Official economic-positioning page
  • Used to confirm that Spire explicitly treats sequencing rights as a way to return some MEV value to the application
• https://docs.spire.dev/preconf-rpc
  • Official Preconf Router page
  • Used to confirm the router/RPC surface that routes transactions across multiple preconfirmation providers
• https://github.com/spire-labs/based-stack
  • Public Based Stack repository
  • Used to confirm open-source status, current alpha framing, and the stack’s high-level product definition

Notes

• Spire’s key mechanism is not merely “based rollups.” It is the decomposition of based rollup operation into several distinct policy layers: ticket distribution, proposer eligibility, block-content constraints, collateral-gated commitment power, and wallet/app routing into preconf providers.
• The Dutch-auction ticket design matters because it makes sequencing rights an explicit market rather than a simple byproduct of whoever happens to control the next L1 proposer slot.
• The forward-sequencer and CR-committee sections matter because they reveal a second control plane beyond sequencer election: who gets to constrain inclusion or censorship-resistance for the next block.
• The Preconf Router matters because it suggests a practical chokepoint may sit above individual preconfirmation protocols, in the routing layer that wallets and apps actually integrate.
• This entry belongs in the active corpus because it helps compare based-sequencing rhetoric against concrete control surfaces: who pays, who qualifies, who routes, who constrains, and who captures value.