Celestia’s SP1 Blobstream Deployments Are No Longer Maintained — Some Rollups Need a New Verification Path

Add TechGaged as your preferred source on Google

See more TechGaged stories across Google News and Discover.

Add

Celestia has quietly moved Blobstream into legacy status, and the change has a practical consequence for rollups that depended on the Succinct-operated SP1 deployments for dispute verification.

According to Celestia’s current documentation, those SP1 Blobstream deployments are no longer maintained and no longer receive new commitments as of September 2026. Celenium has also stopped providing its Blobstream explorer.

This does not mean Celestia data availability itself is offline. It means one specific verification bridge between Celestia and EVM environments is no longer being operated as a maintained service.

Latest Stories

2 min read • 5 minutes ago

Polkadot Adds New Emergency and Technical Governance Tracks in Runtime v2.5.0

2 min read • 5 minutes ago

Scroll Completes OpenVM 2.0 Upgrade With New SWIRL Proof System

2 min read • 5 minutes ago

Cosmos Community Weighs Return of 1.227 Million ATOM Recovered After Neutron Exploit

Read all latest stories →

The distinction matters for rollup security

Blobstream was designed to let EVM chains verify that data had been published to Celestia. It relayed commitments to Celestia data roots into contracts on another chain, where rollups could prove that their transaction data was actually available.

That mechanism is especially relevant for integrations such as Arbitrum Nitro with Celestia DA. Celestia’s own Nitro integration documentation now warns operators not to rely on the old SP1 Blobstream deployment for new commitments.

Teams using that architecture must establish another working Blobstream verification path if they want dispute proofs to remain dependable.

Data availability and verification are separate dependencies

The episode is a useful reminder that modular blockchain stacks contain multiple layers of trust and operations. A rollup may successfully post data to Celestia while still depending on another service to prove that publication inside a dispute system.

If the verification layer stops receiving new commitments, the underlying data can still exist while the rollup’s fraud-proof pathway becomes incomplete.

Celestia has retained legacy proof-query documentation, meaning operators can still query inclusion proofs directly from consensus full nodes. But infrastructure teams now need to own or source the verification pathway rather than assuming the old hosted deployment will continue indefinitely.

For modular rollups, that is not a cosmetic documentation change. It is an operational dependency that needs to be reviewed.