Original title: "One article to understand the ecological construction of modular blockchain Celestia"
Original author: DODO Research Institute
On October 20th, after Celestia announced a new round of financing led by Bain Capital Crypto and Polychain Capital , the modular public chain has once again become one of the hot topics of discussion. This article takes readers through the projects being built in the Celestia ecosystem: Cevmos, Fuel, dYmension, Eclipse.

In short, the modular solution is to modularize the function stack of the single block chain function. The specific functions can be roughly divided into:
Execution: process state changes;
Settlement: verify the state of the execution layer and resolve disputes, and be responsible for the bridge of assets cross-chain;
Consensus: the full node is effective for state transitions In short, nodes at least agree on transactions and their ordering;
Data Availability (DA): To ensure that data can be stored, verified and available, that is, to ensure that transactions behind the rollup block header The data has been published and made available so that anyone can recreate the state.
Under the premise of ensuring sufficient throughput, the single block chain cannot simultaneously break the correlation between calculation and verification costs to keep the network Trust and decentralization, this bottleneck is also known as the "impossible triangle of blockchain".
In fact, there is no conflict between the two. In the past, the rollup we knew only existed as a "vertical expansion" at the execution layer, while the modular blockchain headed by Celestia The solution realizes the modularization of the settlement layer based on rollup, and makes it possible to break the "blockchain impossible triangle" by building a "horizontal expansion" of the modular stack.

Celestia's predecessor LazyLedger is a pluggable consensus and data The availability layer, which only verifies data availability and transaction ordering, provides great flexibility for the entire blockchain network modular architecture. Why is Celestia inseparable from rollup? Before modularization, the proposal of rollup has made how to verify the DA of Layer2 transaction data a big problem.

Specifically, when a block producer publishes a valid block header but intentionally hides or tampers with transaction data, light nodes can only rely on the block header to Validation, so it is easy to be fooled and accept invalid blocks. However, full nodes cannot generate DA and fraud proofs for light nodes, which means that light nodes have to verify DA themselves or assume that most data is trustworthy. So, that's why most nodes have to download full transaction data and verify block data availability. Doing so, however, introduces scalability constraints and problems to network extension solutions.
Celestia adopts an off-chain method to implement DA, that is, through Reed-Solomon erasure code and special Namespaced Merkle Trees structure to ensure the availability of data, so that DA becomes cheaper and done in a more efficient manner. The specific working method of Celestia DA is as follows:
The node receives the transaction submitted by the rollup
The node ensures that the appropriate fee is paid
The node sorts the transaction< /p>
Collectively verify the integrity of the data
Partition the data according to the DNS mapping corresponding to the specific rollup inserted into Celestia

Of course, Celestia's core competitiveness lies not only in its DA and consensus functions, but also uses rollups to provide a variety of options for the execution layer. Of course, Celestia's core competitiveness lies not only in its DA and consensus functions, but also in its use of rollups to provide a variety of options for the execution layer. Celestia also divides rollup into Ethereum native and Celestia native. Celestia native rollup can be inserted into Celestia in two ways:
Sovereign rollup (Sovereign rollups)
Forced settlement rollup (Settlement Enforced rollups like Cevmos, Celestiums, etc)

It is worth noting that the biggest difference between the two schemes is whether the consensus layer is Ethereum or Celestia, and Regarding the two rollup buildable schemes, different teams put forward different ideas.
Cevmos is the Cosmos EVM application chain jointly developed by Evmos and Celestia The rollup stack aims to be the best settlement layer built on top of EVM rollup on Celestia. And Cevmos is an abbreviation for Celestia, Evmos and Cosmos.

As one of the mandatory settlement rollup schemes, Cevmos tries to reduce costs and improve efficiency by providing a special settlement layer for rollup (influenced by limited EVM). Specifically, in this stack, Cevmos will serve as a settlement layer, which will be based on Evmos, and the recursive rollup of EVM (rollup in rollup) will be built on top of it.
Cevmos uses Optimint ( Optimistic Tendermint) instead of the Tendermint Core consensus engine used on the existing Cosmos to build Celestia rollup. Optimint is a replacement for Tendermint BFT that enables developers to deploy rollups using existing consensus and DAs such as Celestia.
Since the Cevmos settlement layer itself is a rollup, the rollups built on top of it are collectively referred to as settlement rollups. Each built rollup will have a two-way trust-minimized bridge with Cevmos rollup, which can redeploy existing rollup contracts and applications on Ethereum to reduce the workload of migration. This also means that all rollups built will use calldata on Cevmos rollups, while Cevmos uses Optimint to batch the data and publish it to Celestia.

Since Cevmos rollup itself is a restricted EVM environment, they will also try to complete the extreme challenge setting through a single round (single round) fraud proof.
Cevmos not only tries not to design and maintain a complex consensus mechanism, but also brings the efficiency of rollup and the interoperability of EVM to the entire Cosmos ecosystem, providing modules The popularization and use of globalization solutions and Cosmos ecology provide practical solutions.
Fuel and Celestia are twin sisters. The difference is that Celestia is optimized for DA and sorting and only deals with data availability and consensus, while Fuel is positioned as a modular execution layer.

The biggest difference from today's Optimistic rollups is that Fuel runs a brand new virtual machine architecture, namely FuelVM and its tool chain and Sway language.
Fuel VM is a custom virtual machine built entirely for the execution of smart contracts, to process transactions in parallel. Fuel VM was designed from the ground up to be easily fraud-proof and can be used by the transaction execution layer of Optimistic rollup.
In addition, FuelVM has the characteristics of SeaLevel from WASM, EVM and Solana , but the difference is that Fuel uses the UTXO model , not the account model. Specifically, Fuel VM forces each transaction to explicitly define the UTXOs it will touch, and since the execution engine can identify exactly which states each transaction touches, it can easily find undisputed transactions and parallelize them.
dYmension is a sovereign rollup built on top of Cosmos, designed to Chain (settlement layer), RDK (RollApp Development Kit), and IRC (inter-rollup communication) make the development of rollApp (customized application-focused rollup) extremely convenient.

The settlement layer built by dYmension is called dYmension hub, which is a PoS chain with Tendermint Core state replication model for networking and consensus. The RollApp built on dYmension hub inherits the security of the hub, and the RDK and the dedicated module group supported by the hub ensure mutual communication.
RollApps consists of two cores: a client and a server. The server is the application side designated for the RollApp deployer to implement custom business logic and build prepackaged modules of the RollApp Development Kit RDK. The client component, called dymint, derived from Celestia's Optimint, is a drop-in replacement for Tendermint and is responsible for block production, peer-to-peer message propagation, and interlayer communication. Since RollApp itself has no consensus tasks, dymint can provide the low latency requirements required by modern applications.

Similar to Cosmos, dYmension RollApps aims to create application-specific blockchains to reduce consensus overhead. The RDK builds on the Cosmos-SDK by adding new modules and modifying existing ones to ensure RollApp is compatible with the dYmension protocol while still being compatible with other Cosmos ecosystem tools. RollApps are able to interact with any IBC-capable chain using the dYmension Hub and are therefore part of the Cosmos ecosystem.
Eclipse is also a sovereign rollup based on the Cosmos ecology, allowing it to be used on any chain Solana VM builds a customizable and modular rollup settlement layer.
Eclipse will use Celestia as the consensus layer and DA in the early stage, and Solana VM as the environment for settlement and execution, and its ultimate vision is to be any Layer1 heterogeneous area The blockchain builds a customizable rollup execution layer that connects all blockchains in a modular manner. In addition, the settlement layer rollup based on Solana VM will also be iterated into Optimistic rollup and zk rollup in the future.

It is worth noting that the construction of the above modular schemes all use Celestia to provide data and Cosmos IBC to ensure inter-chain communication. Just like the free ecology of Ethereum, a modular ecology based on Cosmos has been built, and the interoperability usage scenarios of Cosmos will also usher in an explosion.

It is foreseeable that with the launch of the Celestia Fellowships project, more and more modular solutions will emerge. The final solution of the "impossible triangle" is getting closer and closer, and perhaps the narrative of blockchain modularity has also been opened.
Reference:
https://docs.celestia.org/concepts/ how-celestia-works/>https://forum.celestia.org/t/an-open-modular-stack-for-evm-based-applications-using-celestia- evmos-and-cosmos/89
https://fuel-labs.ghost.io/beyond-monolithic-the-modular-blockchain-paradigm/
https://medium.com/alliancedao/the-case-for-parallel-processing-chains-90bac38a6ba4 blockquote>https://docs.dymension.xyz/learn/dymension-hubhttps://mirror.xyz/neelsalami.eth/rvhK5mEcFTOjyu_DFsqS2cYR7U6Fj vbw3nf8tI-pr-Q?ref=twitterhttps:/ /polygon.technology/solutions/polygon-avail/https://rainandcoffee.substack.com/p/ the-modular-world
Original link
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia