header-langage
简体中文
繁體中文
English
Tiếng Việt
Scan to Download the APP
Partnered With:

A new stateless roadmap for Ethereum

Read this article in 5 Minutes
It's been some time since the last stateless Ethereum comprehensive "roadmap" was released, and a lot has changed.
Original title:"An updated roadmap for Stateless Ethereum"
Original source: Pipermerriam
Ethereum aficionados




It's been some time since the last stateless Ethereum comprehensive "roadmap" was released, and a lot has changed. It seems it's time to "write it all down" again.  


What are we not doing


We're not solving the problem of stateless mining.


We're not working it out.DSA (Dynamic State Access)Nor is it prepared to attach Witness data to the transaction for execution purposes.


The critical path


It is difficult to determine exactly what our goal is. But I think as long as we look at the needs, there will be a target gradient.


Implement stateless verifier through block witness


We want/need validators to validate blocks without having to keep the complete state. One proposal is to require additional blocks in the protocolblockwitnessTo allow the client to use the block witness data to validate the status root from the execution of the block.


To do this, we need:


A: Significant reduction in witness size (up to 100 MB for the current hexadecimal Patricia tree)


B: This allows the verifier to obtain reliable testimony along with the block


We use  Verkle Trie To address demand A, reduce the proof expense to A constant size (theoretically, based on the current gas cap of 12.5 million, the upper limit of the proof size is about 800K and the average is about 200K). See also"For Ethereum state applications  Verkle Trie's proposal". It is also worth mentioning that the unification of Verkle Trie needs to be revised. SELFDESTRUCT  The act of an opcode, or the complete deletion of the opcode.


We address requirement B by witnessing the message as part of the protocol's operation (most likely as an access list in the block header) so that the person receiving the certificate confirms that it is the correct proof for the corresponding block. Responsibility for generating and witnessing through Gossip has not yet been determined.


Why is statelessness so important to ETH 2.0?


State Expiry is used to suppress State growth


Block proposers (or miners) still need to generate blocks. We do not recommend addressing the problem of stateless block mining, as this would shift our goal to reducing the increasing burden of state maintenance.


Our goal is to impose economic limits on the size of the total state. We plan to achieve this through a "Status Shelf Period", please refer to:Resurrection-conflict-minimized state bounding, take 2 - #17 by vbuterin.


Roughly speaking, a state shelf life is when a state is "inactivated" after a certain period of time (about 12 months). The inactivation state is no longer managed by the protocol. Any interaction with the deactivated state needs to be accompanied by a proof that the deactivated state is reactivated. This solution does not introduce any complex "lease" mechanism into EVM, but it does in effect enforce "state lease." The result is a strict upper limit on the overall state size.


Subcritical path


Implement a stateless client architecture through the Portal Client


Further reading:Complete revamp of the "Stateless Ethereum" roadmap - #2 by dankrad 


The current DEVP2P Ethereum protocol does not support stateless clients very well. Even if the protocol is modified to support stateless clients, this is not easy. That is, relying on the "critical path" alone, we could build a client that would work for the Eth1+Eth2 merge infrastructure, but these clients would be useless to most people who use the client in order to use the JSON-RPC API.


Another initiative under way is to build the network infrastructure necessary to support the widespread deployment of ultra-lightweight "portal clients." By "portal," a client can view the network and associated data, but does not have to participate in the protocol in any meaningful way.


The Portal Client will participate in a specialized peer-to-peer network designed to meet the following requirements:


1. Retrieve any on demandstate.

State Network DHT - Development Update #2 - #5 by pipermerriam


2. Search arbitrary on demandHistory of Blockchain.

Alexandria - HackMD(obsolete, but conceptually representative)


3. Participate inTrading gossip, but there is no need to access the state.

Scalable Transaction Gossip - #3 by pipermerriam


4. Participate inBlock gossip, but do not have to meet the implicit requirements of the DEVP2P Ethereum protocol.


Any "stateless client" that wants to attract users of the JSon-RPC API will participate in this type of network. We hope that existing clients will take advantage of such networks to make themselves even more lightweight.


This is not a critical path to achieve the primary goal of Eth1 + Eth2 merging, but it helps extend the stateless client to use cases other than verifiers.


Regenesis (Probably Not Clearing State)


In the past, Regenesis had two different meanings:


Use a new creation block to restart the blockchain and agree on the status of creation.

To "deactivate" a state, proof must be provided to "reactivate" the state.


The activity/inactivation mechanism is now classified as a "state validity" scheme.


There are many benefits to restarting the blockchain with a new creation block. The main one is to make the client simpler by freeing all clients from the hidden requirements of the history fork rule. This can also help the node reduce the synchronization time required to get a full copy of the state.


Content that is removed from the critical path


  Binary Trie


Originally the main mechanism used to reduce witness size has been replaced by Verkle Trie.


Reference reading:EIP-3102: Binary trie structure


Merkelization of code


A secondary mechanism that was originally intended to reduce witness size has been replaced by Verkle Trie.


Reference reading:EIP-2926: Chunk-Based Code Merkleization


The original link


Welcome to join the official BlockBeats community:

Telegram Subscription Group: https://t.me/theblockbeats

Telegram Discussion Group: https://t.me/BlockBeats_App

Official Twitter Account: https://twitter.com/BlockBeatsAsia

举报 Correction/Report
Choose Library
Add Library
Cancel
Finish
Add Library
Visible to myself only
Public
Save
Correction/Report
Submit