> For the complete documentation index, see [llms.txt](https://docs.eclipse.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.eclipse.xyz/architecture/eclipse-architecture/architectural-overview/core-infrastructure/eclipses-celestia-publisher.md).

# Eclipse's Celestia Publisher

## Block Indexing and Data Availability Layer

Eclipse's Celestia Publisher takes blocks from the Eclipse sequencer, indexes them in a local database, compresses and batches them, and posts the resulting blobs to Celestia. To ensure verifiability, it anchors span sequence commitments to Ethereum via BatchHeaders.

This module decouples execution from data availability, allowing for cost-effective scalability without sacrificing verifiability. The Publisher acts as the first bridge between the execution layer and the DA layer. By anchoring BatchHeaders with Celestia span sequence data to Ethereum, the publisher gives Eclipse strong reconstructibility guarantees.

**Processing steps**

* The Eclipse sequencer continuously processes transactions and produces Eclipse blocks.
* The Celestia publisher first retrieves blocks from the sequencer, then compresses them using zstd (level 3), and then batches them.
* The publisher submits individual block blobs to Celestia, receiving span sequence data.
* For gateway sync: The publisher submits an index blob to Celestia for the batch range.
* Finally, it creates and posts BatchHeaders containing span sequence information to the Ethereum Gateway contract.

**Flow Diagram**

{% @mermaid/diagram content="flowchart LR
D\["CelestiaPublisher"] --> E\["Batch & Compress Blocks"]
E --> F\["Publish Block Blobs to Celestia"]
F --> G\["Submit Index Blob to Celestia"]
G --> H\["Create BatchHeader with span\_sequence"]
H --> I\["Post BatchHeader to Ethereum Gateway"]" fullWidth="false" %}

***

We refer the reader to this blog [post](https://www.eclipselabs.io/blogs/leveraging-celestia-blobstream-for-data-availability-proofs) for some extra details related to Blobstream and availablity proofs. 

***


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.eclipse.xyz/architecture/eclipse-architecture/architectural-overview/core-infrastructure/eclipses-celestia-publisher.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.