Radius
Search
K

Motivations

Radius is driven by three key motivations: rollup sustainability, interoperability, and ensuring the order with data availability.
Sustainability
While rollups enhance blockchain scalability, they challenges such as harmful MEV (Maximal Extractable Value), such as frontrunning and sandwiching, and censorship from centralized sequencers. These issues not only lead to financial losses but also undermine trust in the overall ecosystem. Decentralizing sequencers can mitigate some risks, but it often sacrifices scalability and increases operational costs. Radius establishes a sustainable rollup ecosystem by eliminating harmful MEV and censorship with encrypted mempools, ensuring a fair blockchain environment by removing centralizing powers.
Interoperability
Interoperability is crucial in the rollup world. Today, each rollup operates independently, creating fragmented ecosystems and bad user experiences when interacting with multiple rollups. The current structure undermines the benefits of composable blockchains.
Radius proposes a solution using the shared sequencing layer to enhance interoperability, enabling data synchronization and achieving the consistency of states across different rollups.
The diagram below illustrates one potential solution to address the issue of rollup silos.
Atomic composability will ensure the transactions from different rollups are combined into a single transaction, eliminating risks like minting tokens in one rollup before burning in another.
Ensuring Data Availability
In Layer 1, transaction flow begins with transaction generation, block production, and finalization. In L2s, transaction flow begins with the sequencer, rollup, then data availability layer (DA). In these examples, the data availability ensured depends on the trusted layer.
When the rollup is the trusted layer, users can only trust and use data once it's executed by the rollup, making data availability dependent on the rollup's execution. On the other hand, if the sequencing layer is trusted, transaction order becomes known shortly after it's submitted, allowing faster confirmations, state updates, and ensuring data availability with minimized delays, even before finalization on Layer 1.