Author: Donovan Choy, Blockworks; Compiled by Baishuei, Jinse Finance

The Ethereum Foundation is experiencing some internal turmoil, but the development of the world computer continues.

Ethereum researcher Justin Drake published a compilation article on the ethresearch forum yesterday about a new aggregation design called "Native Aggregation".

If you're like me and not technically inclined, keeping up with Ethereum's constantly evolving aggregation design landscape is tedious - let alone keeping up with its entire infrastructure stack.

But the simplest way to think about Native Aggregation is that it relies on Ethereum L1 validators to perform the proof, i.e. the state transition function and verification.

This contrasts with Optimism Rollup (e.g. Optimism, Arbitrum) or zk Rollup (e.g. Starknet, ZKsync), which offload the computational burden to L2, then rely on fraud or zk proof systems to generate the state root and proof, and then feed it back to the mainnet.

These proof systems have complex code, are prone to errors and other vulnerabilities, which is why Rollup sequencers (the entities that order transactions on L2) have historically been centralized. The complaints about sequencer centralization, in turn, have spurred "base" Rollup designs like Taiko, which rely on Ethereum L1 validators to perform the ordering.

But back to Native Aggregation. Drake's proposal suggests introducing an "execution" precompile (a hardcoded function in the EVM) that will verify the EVM state transition of user transactions. This achieves a few breakthroughs:

• Native rollup no longer needs to invest in and maintain an expensive miner prover network, as the proof will be handled and executed by the L1 validators.

• Native rollup no longer needs to maintain a complex governance structure, including a trusted security council to approve contract upgrades to achieve EVM equivalence.

Both of these unlocks actually make native rollup "trustless" by inheriting the security of Ethereum L1.

Finally, like rollup-based rollups, native rollup will enjoy "synchronous composability", which refers to on-chain transactions being able to be composed across different rollup chains, rather than being siloed. Restoring the seamless interchangeability of assets across L1 and L2 chains will solve the long-standing UX problem of cross-chain persistent bridging.

However, unlike rollup-based rollups, the execution of native rollup will not be constrained by the 12-second block time. Due to the "execution" precompile, L1 validators only need to verify the zk proof, without having to execute the computation themselves.

Can Native Aggregation help alleviate the ETH value accrual problem? Maybe.

As I understand it, validators will use the new precompile to enforce, which will make ETH a required settlement asset for transactions.

Secondly, the elimination of L2 governance (and its tokens) can redirect value back to ETH as the primary value source.

Native Aggregation represents a gradual but critical step towards strengthening Ethereum's value proposition and the role of ETH as the foundation of the decentralized ecosystem.