role eth1_data in looping blocks: underage
Transition Ethereum from Ethereum 1 (also existence as eth1) to Ethereum 2 (ETH2), also called the Mayakov’s chain, was an important milestone in the evolution of the network. One -in -law’s question is an ethereum declining, wherever the field of eth1_data in the block, the Nadyada from Execution_Payload. Well, this can be shown, Ponimania this concept can help you clear how eth1 and eth2 work together.
Conception of the false load
In Ethereum every block, it is presented as ExecutionPayload (EP), as well as the field load of the ETH1_DATA. The order for the rest is referred to the alleviation of the inteling counteract on the blockchain, then as the false load of the eth1_data assumes the metadanic about the block itself. EP includes a data that is not intended for the alignment of the concrete counteract or the functional call, such as the values ​​of the memory, arguments and operand of instruction.
Importance eth1_data
When you run the Ethereum program in the cape of the Mayakov, for the codening code, the code is used. However, if you want to check the blockchain or to mitten the network, you need to get the access to the base, which refer to the block. Here comes to the eth1_data.
eth1_data content information on all blockchain Ethereum 1 (ETH1) to the defined moment, the included state -of -the -art steel, the blocks and the other corresponding metadanic. Exp by these data, the deletions can be given to the introduction of the one, as the network developed with the techniques, help them to reinstate the history and the absence of their contract.
Why eth1_DATA will be in the blocks of the Mayakov
So, why are we all more visible eth1_data in blocks on the Mayakov? There are several ones for this:
* Historical content of data : Failure load eth1_data content Information of all blockchain Ethereum 1 in Dumped with the time of time. These historical data are cooked for subdrazhki audites and analysis of the past blockchain.
* Correspondence with the architectural ETH2 : ETH2 presents a new concept, called “hood”, which allows you to efficiently entertain the data on the hog. The topic does not, this is the sake of the wickedness of the false loads eth1_data, to cut the change into the architectures of the network.
conclusion
Such an image that eth1_data will be able to get up with the boot execution_pay, because he introduces the historical data of the Ethereum 1 blockchain to the Dumped moment. These are metadada unusual for the audit and analysis of the past states of the blockchain, which allows you to reflect the presentation of the history and the absence of its contacts on the cape of the lighthouses.
In addition to the ETH2, it continues to develop and incorporate your architectural, the field load eth1_data, verifiable, will be dispensed as to the change in this area. Tems does not less, Ponimania, as it works eth1_data, evolves a tedy contract for tech, who works with ethereum 1 or crossing from Eth2.