astria-primary-sources-2026-05-12

Astria primary sources

Reviewed: 2026-05-12 UTC

Core protocol framing

• https://docs.astria.org/overview/introduction
  • Best short official overview of the Astria stack.
  • Used to confirm Astria’s self-description as a decentralized sequencing layer for multiple rollups, the lazy-sequencer framing, use of opaque (rollup_id, tx_bytes) payloads, and the split between sequencer, Celestia publication, and Conductor-based rollup derivation.
• https://raw.githubusercontent.com/astriaorg/astria/main/README.md
  • Canonical monorepo README.
  • Used to confirm the repo-level component split between sequencer, conductor, relayer, and protobuf definitions.

Ordering, batching, and execution flow

• https://docs.astria.org/overview/transaction-flow
  • Most useful single page for end-to-end mechanism flow in this pass.
  • Used to confirm the write path from rollup mempool → Composer → Astria mempool → shared sequencer block → Relayer batching to Celestia, plus the read path where the Conductor filters namespace-specific data, passes it to the rollup, and later marks previously seen blocks finalized when Celestia batches arrive.
• https://docs.astria.org/overview/components/relayer
  • Used to confirm that the Relayer batches fast sequencer blocks into slower DA submissions and that DA-published batches are treated as firm commits while earlier sequencer-visible blocks function as soft commits.

Shared sequencing and verification surfaces

• https://docs.astria.org/overview/components/the-astria-sequencing-layer
  • Used to confirm CometBFT as the consensus layer, Astria’s execution of sequencer-native transactions only, validator-backed commitments to rollup data, and the combination of local validator data availability plus wider publication through Celestia.
• https://docs.astria.org/overview/components/conductor
  • Best source for the rollup-side verification path.
  • Used to confirm how the Conductor verifies sequenced data via validator-backed commitments, Merkle inclusion proofs, rollup-ID commitments, and the soft-versus-firm commitment distinction.

Orderflow abstraction and builder surface

• https://docs.astria.org/overview/components/composer
  • Used to confirm Composer’s role as a rollup-side gas station sidecar, its underwriting of sequencing costs for ordinary users, direct-submission paths for sophisticated users, and Astria’s explicit framing of the sequencing layer as supporting bundle-oriented MEV supply chains.

Main takeaways from this pass

• Astria’s key reusable primitive is not only shared sequencing, but a specific decomposition of rollup coordination into Composer-side orderflow intake, lazy shared ordering, DA batching to Celestia, per-rollup Conductor verification, and downstream rollup execution.
• The soft-commit / firm-commit split is central: fast UX comes from sequencer-fed soft commitments, but finality is anchored in DA-published batches that the Conductor explicitly verifies.
• Important control surfaces include Composer operation, Relayer batching policy, namespace / rollup-ID commitment handling, and the boundary between direct sophisticated orderflow and operator-mediated user flow.
• Astria is therefore a strong comparison class for Espresso, NFFL, SUAVE-adjacent shared-ordering systems, and preconfirmation stacks that claim to decentralize rollup coordination while potentially shifting power into new middleware layers.