Charts
DataOn-chain
VIP
Market Cap
API
Rankings
CoinOSNew
CoinClaw🦞
Language
  • 简体中文
  • 繁体中文
  • English
Leader in global market data applications, committed to providing valuable information more efficiently.

Features

  • Real-time Data
  • Special Features
  • AI Grid

Services

  • News
  • Open Data(API)
  • Institutional Services

Downloads

  • Desktop
  • Android
  • iOS

Contact Us

  • Chat Room
  • Business Email
  • Official Email
  • Official Verification

Join Community

  • Telegram
  • Twitter
  • Discord

© Copyright 2013-2026. All rights reserved.

简体繁體English
|Legacy
BTCBTC
💲70336.45
+
1.76%
ETHETH
💲2058.85
+
1.99%
SOLSOL
💲86.95
+
2.77%
USDCUSDC
💲0.9999
-
0.01%
HYPEHYPE
💲37.36
+
6.77%
XRPXRP
💲1.39
+
1.46%

蓝狐
蓝狐|3月 12, 2026 05:47
The developers of the Ethereum ecosystem have just released a proof of concept for 'Native Rollups'. This is led by the Ethrex execution client team, in collaboration with researchers from the Ethereum Foundation and contributors to L2BEAT. Specifically, what does this' Native Rollups' do? For ease of understanding, let me make a simple analogy: Ethereum L1 is similar to the most secure 'big bank', while L2 is equivalent to many small branches opened outside the 'big bank'. These small branches want to process business faster and cheaper, but they still need to prove that they have not cheated and that their accounts are correct, and they also need to establish a "proof system". There are two types of "proof systems" now, one is the fraud proof system (Optimistic type, mostly with a 7-day challenge period, quite troublesome); One is the ZK proof system (complex, difficult to write circuits, difficult to upgrade, and unable to keep up with the main chain). The result is, The security of small branches needs to be maintained by their own team or "security committee", and upgrades require meetings and voting, making it difficult to achieve true decentralization. Even if bugs occur, they have to be fixed by themselves. In this context, Native Rollups emerged. Its meaning is to directly let Ethereum, the 'big bank', help L2 and these small branches verify the ledger. How to do it? Through a precompile called EXECUTE (EIP-8079 proposal), the small branch throws a bunch of transaction data to the main chain, and the main chain directly "re executes" these transactions to confirm whether they are correct or not. Just like the main chain recalculates its accounts to ensure accuracy. What are the benefits? L2 implementation is equivalent to L1 security, and verification is done using Ethereum's own engine. Any bugs that occur are also Ethereum's bugs, not the fault of small branches. Inheriting all the security of the main chain, there is no need to engage in "semi centralized" things such as security committees and multi signature bridges, achieving true decentralization; Upgrades also automatically follow: If L1 hard forks and upgrades EVM (such as some new opcodes), Native Rollup will be automatically compatible, and the L2 team does not have to chase after changing the code; The L2 team no longer needs to maintain the proof system, which is much simpler than the ZK circuit. In fact, for ETH holders of Ethereum, the most concerning issue is value capture. With Native Rollup, L2 relies more on Ethereum DA for higher security, which is beneficial for capturing Ethereum value, burning more ETH, and increasing ETH value. L2 and L1 have a more synergistic relationship rather than a parasitic relationship. At present, the developers have completed the PoC (Proof of Concept) and implemented EXECUTE using the Ethrex client, which can run the complete deposit, contract deployment, cross chain calling, and withdrawal processes. The code is open sourced on GitHub, and some people can already try it out locally. Will L2 support it? It is likely to be widely adopted, especially for projects that truly want to obtain Ethereum level security. At present, the founders of Arbitrarum, Optimism, and Base have expressed their support or interest. In the future, the ultimate solution may be formed by combining "based rollup" (a decentralized sorter that uses main chain validators for sorting). The adoption time is still uncertain, perhaps it will take 1-2 years. What are the drawbacks? If running pure heavy, the throughput is limited due to the main chain gas limitation. However, After integrating ZK proofs in the future, it will be possible to "infinitely" expand gas (validators only look at the proof and do not need to rerun), solving the problem. Summary in one sentence: Native Rollups=turning L2 into a "direct branch" of the main chain, relying solely on the main chain for security, upgrades, and simplicity, without having to do it alone. For users: more reassuring. For the L2 team: more convenient. For ETH: More valuable. If L2 is truly adopted, then Ethereum's L1 and L2 can achieve true synergy, no longer a situation of "feudal separatism".
+6
Mentioned
|
APP
Windows
Mac
Share To

X

Telegram

Facebook

Reddit

CopyLink

|
APP
Windows
Mac
Share To

X

Telegram

Facebook

Reddit

CopyLink

Timeline

3月 11, 12:55edgeX_exchange uses Chainlink as cross-chain infrastructure
3月 11, 10:36Ethereum researchers showcase 'native rollup' prototype
3月 11, 02:56Two key factors driving the flywheel effect in the crypto industry
3月 09, 23:15The Ethereum Foundation uses DVT-lite to stake 72,000 ETH
3月 09, 02:00Orderly launches Orderly Skills, supporting AI agents
3月 08, 20:30Create a dedicated database for code to support developers' use.
3月 06, 02:21Bitwise donated $100,000 to Ethereum open-source developers
3月 06, 01:58Bitwise donates $100,000 to the Ethereum open-source development organization
3月 05, 15:31Ethereum's banking stack
3月 05, 12:47BNB Chain promotes the development and open-sourcing of the first batch of delegated skills

HotFlash

|
APP
Windows
Mac
Share To

X

Telegram

Facebook

Reddit

CopyLink

APP
Windows
Mac

X

Telegram

Facebook

Reddit

CopyLink

Hot Reads