READ THIS: The Complete Guide to Based and Native Rollups

The image I used as a banner for this article was created by beautiful people in Spire Labs. It provides a good overall visual -decision on how different layer 2 solutions use Ethereum infrastructure. In this article, I will be expanded to native and based on rollups to give you a complete picture of how these architectures work together.

The Rollup Landscape: Four Key Components

Any layer 2 solution has four critical components, as shown in the left image column:

1. Remote – where the final state is recorded and that -Secure

2. Having data (DA) – where transaction data is stored

3. Follow -up – Who decides to adopt -following transactions

4. Implementation – Who is processing transactions

Traditional L2 may use Ethereum for regulating and DA, but handling the compliance and implementation independently. “Based” and “native” aims to use more of Ethereum infrastructure for increasing security.

Based on rollups: the order that Ethereum activates

What are the rollups based on?

Based on the rollups use Ethereum not only for regulating and the availability of data, but also for transaction compliance. This means that the adherence of transactions on a rollup based on a rollup is determined directly by Ethereum validators rather than through a separate sequencer.

How rollups work

1. Transaction Submit: Users submit transactions directly to Ethereum L1

2. Ethereum's adherence to Ethereum: Ethereum miners/validators refer to the transaction -following

3. Data Storing: Transaction data can be stored in Ethereum (in Calldata or Blobs)

4. Off-chain implementation: Transactions are still killed in the Rollup chain

5. State Promise: Results have been posted back to Ethereum for regulating

Benefits of Based on Rollups

• Resistance to Censorship: No separate sequencer means no one point of control for ordering transaction

• MEV protection: Leveages Ethereum's MEV (maximum extractable value) protection

• Fast Confirmies Fast: Transactions get some security once it appears at Ethereum Mempool

• No Permission: Anyone can submit transactions without going through a controlled sequencer

Challenges of Based on Rollups

• Higher latency: Transactions must wait for Ethereum block times

• Higher Cost: Each transaction pays for Ethereum gas directly

• Limited throughput: dependent by the capacity of the Ethereum transaction

Native Rollup: The implementation of Ethereum-Powered

What are native rollups?

Native rollups use Ethereum not only for regulating and gaining data, but for Implementation The verification by the proposed precompile implementation. This means that the processing of transactions is directly proven by Ethereum validators.

How native rollups work

1. Off-chain order: Transactions can be seized -following a separate creature

2. Data storage: Transaction data will be stored in Ethereum

3. The verification of native implementation: The implementation of precompile confirms state transfers

4. Remote: Results are that -Secure of Agreement by Ethereum

Benefits of native rollups

• Full security legacy: Rollup security is equivalent to Ethereum's

• No security councils: Eliminates the need for trusted operators or multisigs

• EVM automatic compatibility: Native rollups automatically remain compatible with Ethereum upgrades

• Simplified: Simpler to develop and maintain

Challenges of native rollups

• Requires changes in Ethereum's protocol: Precompile implementation must be added to Ethereum

• Potentially higher cost: Native validation may be more expensive than that -Pimize custom solutions

• Potentially limited customization: Ethereum's implementation policies should be followed

Ultra Sound Rollups: Based + native

Ideally, what we wanted was the so -called Ethereum researcher Justin Drake “Ultra Sound Rollups”. These are L2 solutions that are both based on and native. It will use Ethereum for all four critical substances:

It represents maximum security and decentralization, even as likely in tradeoff to performance and cost. However, they are closer to mirror the architecture of Ethereum L1 in terms of security and decentralization than other options.

The spectrum of trust

What appeals to this method is how it creates a spectrum of trust:

• Traditional L2S: Trust in the sequences, mechanisms of implementation, and security councils

• Based on rollups: Trust in implementation, but the adoption is that Ethereum is -secure

• Native rollup: Trust in order -next, but the implementation is that Ethereum's

• Ultra Sound Rollups: Both enemies and implementation that Ethereum's

Practical implications

For users

• Security option: Can select L2 with proper security balance compared to performance

• Same -EXPERIENCE: Native rollups act exactly like Ethereum

• MEV protection: Offers based on rollups of better protection against transaction manipulation

For developers

• Simplified stack: Native rollups are noticeably -Providing the tech stack required to run an L2

• Following Options -Reviews: May choose between resistance of censorship of the based on the following -the performance of the dedicated sequencers

• Transfer path: Existing rollups can gradually adopt a based or native substance

The future scene

As you can see from the Spire Labs diagram, there is a clear development to “more Ethereum” – with rollups that use more Ethereum infrastructure for increasing security guarantees. This evolution describes what the Ethereum L2-centrian roadmap endgame will look like. A future where layers 2 are not separate systems, but instead of Ethereum extensions itself, with different adjustments to which the ingredients are based on the infrastructure of the Ethereum. If choosing a rollup based, native, or both are likely to depend on the specific case of its use:

• High-Security Applications: Can choose ultra sound rollups (both based on + native)

• Applications dedicated to performance: May use selectively based or native substance

• Custom applications: Can use traditional rollup architecture with specialized substances

By understanding these architectural options, users and developers can make smarter decisions about which L2 solutions best meet their needs for security, decentralization, cost, and performance.

Hope you find it useful.