Skip to main content

Mitosis L1 Chain

Overview​

overview The Mitosis L1 Chain provides:

  • An EVM-compatible execution environment for the Mitosis Protocol and its builders
  • Ethereum-level security leveraging EigenLayer
  • A Proof-of-Stake consensus mechanism with instant finality and rapid block times, powered by CometBFT and Cosmos SDK

The Mitosis L1 Chain is not just another L1 or L2 chain; it offers several technical advantages:

  • Separation of Execution and Consensus
  • Ethereum Security

Separation of Execution and Consensus​

The Mitosis L1 Chain consists of two layers:

  • Consensus Layer
  • Execution Layer

One of our primary objectives has been to support the EVM while harnessing the benefits of CometBFT. We've aimed to develop an approach that is EVM-compatible, high-performing, and easy to maintain.

We were inspired by Ethereum's modular architecture:

  • The execution client is responsible for transaction handling, transaction gossiping, state management, and supporting the EVM.
  • The consensus client handles block building, block gossiping, and consensus logic.

Based on these considerations, our key decisions are:

  • Adopt Ethereum's modular architecture
  • Utilize Ethereum execution clients without modification
  • Create a custom consensus client using Cosmos SDK (CometBFT)

Execution Layer​

execution clients

Developers can use the same execution clients employed for Ethereum with Mitosis without modifications. You can utilize Geth, Reth, Nethermind, or any other Ethereum execution client for Mitosis.

All execution clients are compatible as long as the consensus client communicates with them in accordance with the Engine API specifications.

The Mitosis Protocol and dApps on the Mitosis chain are implemented on top of the execution layer. This allows users and dApp developers to focus solely on this layer without worrying about the consensus layer.

The entire Mitosis ecosystem—including dApps, oracles, explorers, and development tools like Foundry—interacts exclusively with the execution layer. As a result, many existing EVM-based tools and applications can be seamlessly adopted with Mitosis.

Consensus Layer​

The consensus layer is built using the Cosmos SDK to leverage the benefits of CometBFT, including instant finality. It also utilizes Octane to communicate with the execution layer through the Engine API.
Additionally, we leverage Ethereum's security instead of relying on the traditional approach used by other Cosmos SDK-based applications.
See Ethereum Security for details.

Ethereum Security​

The more common approach for security in Cosmos SDK-based applications relies on their own native token. This method involves issuing a new token and encouraging users to stake it.

This approach presents several challenges:

  • Security Bootstrapping: Initially, there may not be enough staked tokens to adequately secure the network against attacks.
  • Price Volatility: The native token's price fluctuations can destabilize network security.
  • High Inflation Rate: To incentivize staking, a large number of tokens are minted and distributed as rewards. This high staking APR can negatively impact the token economy and create selling pressure.

In contrast, leveraging Ethereum security via EigenLayer offers significant advantages:

  • Immediate security bootstrapping from day one
  • Reduced price volatility

We integrate Ethereum's security into the Mitosis chain through Ethos AVS.
EigenLayer operators can opt into Ethos AVS on Ethereum and then join as validators of the Mitosis Chain.
The validator list stored in Ethos AVS is synchronized with the consensus layer of the Mitosis Chain. This synchronization is implemented in x/avsoracle by leveraging vote extensions.
Any evidence of misbehavior by a validator on the Mitosis Chain triggers slashing for that specific validator. This misbehavior is reported to Ethos AVS, which in turn initiates slashing for the corresponding operator in EigenLayer.