Decentralized shared sequencer network built on CometBFT that orders transactions for many rollups in lockstep and posts them to Celestia for data availability, enabling cross-rollup composability without per-rollup sequencer bootstrapping.
- 01shared sequencing across EVM rollups
- 02cross-rollup atomic composability
- 03permissionless rollup launch
- 04Celestia-DA rollups
- 05credibly neutral ordering
| Variable | Scope | Description |
|---|---|---|
| ASTRIA_SEQUENCER_RPC_URL | Server | Astria sequencer RPC endpoint (CometBFT) for submitting and querying ordered txs. |
| ASTRIA_ROLLUP_ID | Client | 32-byte rollup ID (hex) registered on the Astria sequencer network for your rollup's namespace. |
| ASTRIA_COMPOSER_URL | Server | Astria composer endpoint that bundles rollup transactions into sequencer blocks. |
Use Astria as the shared sequencer for the rollup. Register a 32-byte rollup ID, then point the rollup's execution layer (e.g. astria-geth or a custom EVM) at the Astria conductor, which pulls ordered transactions from the sequencer network and posts compressed blocks to Celestia for DA. Submit transactions via the composer or directly to the sequencer RPC; finality follows CometBFT (~2s) with Celestia confirming availability shortly after. Settlement and proofs (if any) are handled by your execution layer, not Astria.
- ⚑Astria provides ordering and DA-relay only — your rollup still needs its own execution and (for validity/fraud proofs) settlement story.
- ⚑DA inclusion latency = CometBFT block (~2s) + Celestia inclusion (~12s); plan soft-finality UX around the Celestia confirmation, not the sequencer block.
- ⚑Rollup IDs are global — collisions or typos silently route your transactions to another rollup or get dropped.
- ⚑Trust assumption shifts from your own sequencer to the Astria validator set — review its stake distribution and slashing rules before launch.
- ⚑Fees on Astria are paid in the sequencer's native token (TIA passthrough on Celestia plus Astria fees) — fund batcher wallets accordingly.
- ⚑Forks of the sequencer chain follow CometBFT finality; rollup nodes must treat unfinalized sequencer blocks as soft and reorg if needed.