<aside> đź’ˇ

Quick Facts

In its initial version, the Logos Blockchain is intended to support Sovereign Rollups - the most customisable, performant solutions for applications built on Logos. Sovereign Rollups have complete freedom to define their own state, only using the Logos Blockchain to ensure consensus and the availability of rollup data. This design allows applications built on Sovereign Rollups to have low fees and maximum scalability. While the Logos Blockchain is designed to eventually support permissionless and interoperable Zones with minimal setup required, this support remains a work in progress and is slated for inclusion in later versions of the protocol.

Overview

The idea behind Sovereign Rollups is to make performant applications with the freedom to define an execution environment to suit their needs, with the Logos Blockchain providing economic security and data availability guarantees that the rollup alone could not provide, helping to bootstrap rollups’ economic security. To ensure the correctness of the rollup state, Sovereign Rollups are left to their own devices instead of relying on a smart contract on the L1 as with Ethereum L2s. This could be done in any number of ways - including publishing ZK validity proofs to be verified by its validators, providing a challenge window for fraud proofs, or by requiring rollup nodes to re-execute the state transition function.

Bedrock does not attempt to interpret rollup data, only providing operations via Mantle to allow rollups to temporarily post data in the form of a LogosDA blob. This blob is distributed among DA nodes, allowing all Logos Light Nodes to verify its availability. The blob commitments are written on-chain, ensuring that the rollup state enjoys the benefits of Cryptarchia consensus.

One example of a Sovereign Rollup that uses validity proofs to verify its state.

One example of a Sovereign Rollup that uses validity proofs to verify its state.

The Sovereign Rollup depicted above has a sequencer that processes transactions from clients and sends the batched state data to LogosDA, while simultaneously creating ZK proofs for its state updates and distributing them off-chain. Rollup light nodes can then verify the proofs received from the sequencer and check the availability of the data via data availability sampling.

Use Cases

Sovereign Rollups can implement almost anything, ranging from applications to virtual machines that are home to many different applications. They are best suited for applications that require high performance and do not need strong interoperability. Some examples include: