blobstream-x-primary-sources-2026-05-11

Blobstream X primary sources

Collected: 2026-05-11 UTC

Primary sources reviewed

• https://docs.celestia.org/operate/blobstream/install-binary/
  • Official Celestia operator docs for Blobstream.
  • Used to confirm the orchestrator / relayer split, the separate Blobstream P2P network, and the practical operator story for posting commitments to EVM chains.
• https://github.com/celestiaorg/orchestrator-relayer
  • Official historical operator repository.
  • Used to locate the older Blobstream operational stack and the deprecation note pointing operators toward BlobstreamX.
• https://raw.githubusercontent.com/celestiaorg/orchestrator-relayer/main/README.md
  • Historical operator README.
  • Used to confirm that the vanilla Blobstream implementation has been decommissioned and that BlobstreamX is the production successor.
• https://github.com/celestiaorg/blobstream-contracts
  • Official historical contract repository.
  • Used to confirm the older contract-level mechanism and audit trail.
• https://raw.githubusercontent.com/celestiaorg/blobstream-contracts/master/README.md
  • Historical contract README.
  • Used to confirm the older validator-signature trust model, the one-way Celestia-to-EVM message-relay framing, and the explicit deprecation notice pointing production users to SP1 Blobstream and blobstream0.
• https://github.com/succinctlabs/blobstreamx
  • Official Blobstream X repository.
  • Used to anchor the current production-oriented implementation.
• https://raw.githubusercontent.com/succinctlabs/blobstreamx/main/README.md
  • Blobstream X README.
  • Used to confirm the core contract role, verifyAttestation, the proof-request / relay workflow, genesis-parameter initialization flow, and the existence of a prover-whitelist control.
• https://github.com/succinctlabs/sp1-blobstream
  • Official SP1 Blobstream repository.
  • Used to anchor the current zkVM implementation path.
• https://raw.githubusercontent.com/succinctlabs/sp1-blobstream/main/README.md
  • SP1 Blobstream README.
  • Used to confirm that SP1 Blobstream is the SP1 zkVM implementation of Blobstream.
• https://succinctlabs.github.io/sp1-blobstream/
  • Generated documentation site for SP1 Blobstream.
  • Used to confirm the current architecture split across SP1Blobstream contract, SP1Verifier contract, SP1 program, and operator.
• https://github.com/celestiaorg/nitro-das-celestia
  • Official downstream integration repository for Celestia-backed Nitro DA.
  • Used to anchor Blobstream’s role inside rollup data-availability verification.
• https://raw.githubusercontent.com/celestiaorg/nitro-das-celestia/main/README.md
  • Downstream integration README.
  • Used to confirm that downstream validators and DA servers depend on Blobstream contract addresses and parent-chain RPC configuration to validate Celestia certificates, which makes Blobstream a practical middleware dependency rather than only an abstract bridge.

Notes

• Blobstream X cleared the bar because it is not just another bridge label; it separates Celestia data-root production, proof generation, verifier contracts, operator relaying, and downstream certificate validation into a legible DA-attestation stack.
• The older Blobstream implementation is still useful as a baseline because it shows the pre-zk trust model: validator-set tracking plus >2/3 voting-power signatures over validator-set updates and data-root tuple roots.
• The production story now shifts trust and operational dependence toward proof systems, verifier deployments, and operators or proving services. That makes Blobstream X a strong comparison class for other DA bridges, light clients, and proof middleware.
• The prover-whitelist and in-place-upgrade details are especially worth carrying forward. They make explicit that deployment and proving policy can become the new control plane once a bridge moves away from direct validator signatures.
• This entry should later be compared against Hyperlane / Wormhole-style message verification, optimistic DA attestation paths, and any other Celestia-light-client or data-root bridge systems so data availability, proof verification, and message bridging do not get flattened together.