You are reading an excerpt from our free but shortened abridged report! While still packed with incredible research and data, for just $40/month you can upgrade to our FULL library of 60+ reports (including this one) and complete industry-leading analysis on the top crypto assets. 

Becoming a Premium member means enjoying all the perks of a Basic membership PLUS:

• Full-length CORE Reports: More technical, in-depth research, actionable insights, and potential market alpha for serious crypto users
• Early access to future CORE ratings: Being early is sometimes just as important as being right!
• Premium Member CORE+ Reports: Coverage on the top issues pertaining to crypto users like bridge security, layer two solutions, DeFi plays, and more
• CORE report Audio playback: Don’t want to read? No problem! Listen on the go.

Celestia: Bridging the Scalability Gap

At its core, Celestia serves as an auxiliary framework to Ethereum, providing a decentralized platform for publishing and accessing transaction data. This capability is instrumental in alleviating data congestion by facilitating an efficient data verification process for light nodes. 

Celestia asks the question, "What is the minimal role a blockchain must play to provide shared security for other blockchains, such as rollups?" This query leads us to distinguish between the concepts of consensus and execution, which are traditionally seen as inseparable in blockchain architectures.

Distinct Functions: Consensus and Validity

In standard blockchain models, the terms "consensus" and "validity" often overlap. However, these can be understood as distinct functions. Validity rules determine which transactions are valid, while consensus protocols enable nodes to agree on the sequence of these valid transactions. Celestia adopts the Tendermint consensus protocol to order transactions but does not engage in assessing their validity or executing them. Instead, it treats all transactions that pay the necessary fees equally—accepting, ordering, and replicating them without bias.

The Modular Approach

Celestia's architectural innovation lies in its modular design, which distinctly separates the consensus layer from the data availability and execution layers. This separation enables Celestia to specialize in the ordering and availability of data, thereby significantly enhancing its efficiency and scalability. By focusing solely on data availability, Celestia can seamlessly integrate with various execution layers (rollups), supporting them in processing transactions and executing smart contracts with the data provided by Celestia.

Role of Rollup Nodes

The execution of transactions and the enforcement of validity rules are delegated to rollup nodes. These nodes monitor Celestia to download transactions pertinent to their operations and execute them to update their state—for example, calculating account balances. Transactions deemed invalid by these nodes are simply ignored. This system ensures that as long as Celestia's transaction history remains unchanged, nodes operating under consistent validity rules can synchronize their state calculations.

Implications for Rollups

This approach has significant implications for rollups, which are essentially layered blockchains that operate atop a base chain like Celestia. Rollups do not require the base chain to perform any execution to maintain shared security; they only need to agree on a shared history of ordered transactions. This consensus on transaction history alone is sufficient to ensure security without execution.

Consensus Mechanism and Data Availability

A crucial aspect of this system is the data availability problem. In fraud or validity proof systems, it is vital that all transaction data is fully published and accessible. If data is withheld, light nodes might continue following a potentially compromised chain because they do not detect the missing data, leading to security risks.

Celestia uniquely addresses this problem by ensuring that block producers fully publish the underlying data of block headers. This enforcement allows even resource-limited light nodes to independently verify data availability, enhancing the scalability and security of the network.

The protocol's consensus mechanism is engineered for minimal interference with network throughput, attributing to its lightweight and efficient design. This efficiency is achieved through two primary technologies: block sampling and Data Availability Sampling (DAS).

Block Sampling

Block sampling is a process whereby light nodes download only the block headers, which contain commitments to the block data. This method enables light nodes to verify the availability of data without the need to download the entire block, thus reducing the bandwidth requirement and enhancing the network's scalability.

Data Availability Sampling (DAS)

DAS further refines the efficiency of Celestia by allowing light nodes to verify the availability of an entire block by examining only a small, randomly selected portion of it. This technique ensures that the necessary data for verifying transactions is accessible without necessitating its storage or processing on the main blockchain. While DAS and block sampling are closely related, they serve distinct functions within the protocol's architecture, collectively ensuring the integrity and scalability of the network.

Enhancing Security with Fraud Proofs

Celestia leverages fraud proofs to augment its security and scalability. These proofs serve as cryptographic evidence that can be submitted to the blockchain to contest the validity of a transaction. By facilitating the exchange of fraud proofs with other networks, Celestia enhances its ability to detect and reject invalid transactions, thereby safeguarding the network against malicious activities.

Celestia addresses these challenges with innovations like fraud and validity proofs. These proofs allow nodes, especially those with limited resources (light nodes), to verify the validity of transactions without executing them. By utilizing data structures like Merkle Trees, nodes can efficiently verify whether a transaction is included in a block without needing to download the entire block.