Case Study: KYVE Safeguarding The Historical Data of Celestia & Its Modular Rollups

This modular March, KYVE is thrilled to share its support for Celestia and its ecosystem, providing a custom data rollup to manage the chain’s historical data in a decentralized, immutable way.

Overall, this integration advances modular scalability and data validity for all. Let’s quickly break this down…

?? Who Keeps Track of Celestia’s Historical Data If No One’s Incentivized To Do So?

With Celestia witnessing exponential growth, vast amounts of data is being produced. To ensure scalability, pruned nodes will prune all of that data every 30 days.

Due to this, it’s obvious that accessing historical Celestia events can be very hard with public endpoints, and will just get harder with time. Not to mention, very few RPCs have event storing enabled, and those who do usually have strong pruning, so no one is really even keeping a copy of the data.

Keeping a full archival node of a blockchain is extremely resource-heavy/costly, and with no incentivization, very few take on the task.

But now, with KYVE validating each and every block and state snapshot on the Celestia chain and permanently archiving it all onto Arweave via its DPoS validator network, Celestia can keep its historical data whilst achieving optimal scalability.

In fact, Celestia doesn’t have to worry about their historical data management period, since KYVE handles it all.?

?? Why Celestia’s Historical Data Is So Important

Historical data is a lot more important than one might think…?

Via KYVE’s node tool KSYNC, node operators can sync to any historic Celestia block, state, or even height in a fast, reliable way. This streamlines the process of syncing with the chain to catch up to any certain height, or even for analysis of previous events or for accounting purposes.

Via KYVE’s Data Pipeline, developers can also easily import KYVE’s trustless backup of Celestia’s historical data into any preferred data backend and transform the raw data into any format they need for easy implementation into their builds. Developers can also leverage this for debugging.

?? Awesome, So What’s Next?

With a full permanent archive of Celestia in the works, next on KYVE’s list is an integration that includes all data from the PayForBlob TXs. This would allow the full archiving of all blobs on Celestia, meaning…

All rollups built on Celestia wouldn't need to worry about managing their historical data management and archiving, KYVE would handle it all! To further streamline the user experience, KYVE’s development team aims to also work on a trustless RPC to more easily query the validated blobs.?

Who’s ready to see rollups built with Celestia underneath; archived and validated by KYVE? ?? Build whatever, trustlessly.