Ethereum Foundation: How will the integration affect the Ethereum application layer?

Transition d'Ethereum vers PoS -suck- Coming soon: devnets (network development) has been established, special instructions have been completed and community expansion has started.The integration is designed for:To the rightethereumend users, smart contracts toou dappsfromLess impact. However, some subtle changes should be noted. Before we get into the details of these changes, here are a few links that give you an overview of the whole integration.

Evolution of the Ethereum roadmap:

https://tim.mirror.xyz/CHQtTJb1NDxCK41JpULL-zAJe7YOtw-m4UDw6KDju6c

Architecture client post-fusion :

https://tim.mirror.xyz/CHQtTJb1NDxCK41JpULL-zAJe7YOtw-m4UDw6KDju6c

The remainder of this article assumes the reader is familiar with the above terms. For a more in-depth understanding of all integration specifications, see:

Executive level:

https://github.com/ethereum/execution-specs/blob/master/network-upgrades/mainnet-upgrades/merge.md

Set of recommendations:

https://github.com/ethereum/consensus-specs/tree/dev/specs/merge

API Cav :

https://github.com/ethereum/execution-apis/tree/main/src/engine

01.block structure

After the integration, the PoW blocks will no longer be available on the Ethereum network. Instead, the old PoW elements will be part of the tag chain design block. In the meantime, the tag chain can be seen as a new PoS approval process in Ethereum that replaces the existing PoW approval process. Beacon chain blocks include:Support, which is the same as the current PoW chain block after integration. The images below illustrate this relationship.

For the end user and the application developer, theseSupportThis is where the interaction with Ethereum occurs. The trade in these processes is also carried out by process workers (Besu, Erigon, Geth, Nethermind, etc.). Fortunately, due to the stability of the process obtained, the integration will lead to small changes.

Ommer mines and boulder fields

After integration, many sites previously included in the PoW block header are obsolete because they do not interact with PoS. To minimize damage to equipment and facilities, these fields are not completely removed from the data model, but are set to 0 or their equivalent for the data model. All changes to the blockchain can be found in EIP-3675.

https://eips.ethereum.org/EIPS/eip-3675#block-structure

Since PoS does not generate ommers (also called uncle blocks) like PoW, these names (ommers) in each block are empty and the hash of the form (ommerHash) becomes the RLP code of the empty hash. . In the same way,difficultandyes in theAccording to the characteristics of PoW, it is set to 0 and at the same time specifies the value of the byte.

Other areas are related to miningmix the minceIt is not set to 0, but has the value RANDAO of the string tag. This is explained in more detail below.

After the merger,block hashThe opcode can still be used, but since it was not created by the PoW hashing process, the pseudo-random number provided by this opcode is less powerful.

In this regard,difficultThe opcode (0x44) has been changed and renamed to:Random. After integration, this opcode returns the output of the light provided by the beacon string. Thereforeblock hashIn contrast, this opcode would be a strong (but incredible) random character used by developers.

RandomThe citizen rate is stored in:Support, keep the affected PoW counts.mix the minceReasonable price. payloadmix the minceField names have also been changed to:Random.

belowdifficult&RandomThe diagram shows how the opcodes work before and after sharing:

Before joining us0 x44opcode returns the header of the block.difficultresponnse. After sharing, this opcode isRandom, and past inclusionmix the minceThe block header field now maintains the state of the tag chain.Randomthe price.

This change isPEB-4399It has been approved by, and it also provides the way for the application of chains to measure if there is integration. PEB-4399:

https://eips.ethereum.org/EIPS/eip-4399

The following is from EIP-4399.

02 ibblocking time

Mergers affect Ethereum's average time. In the current PoW mechanism, the block development time averages about 13 seconds, and the actual block development time can be very different. In the PoS mechanism, the block creation time is 12 seconds unless the validator is offline or a special location does not create a block because the block is not delivered on time. However, in practice this only happens in less than 1% of openings.

This is the average blocking time on the PoS network.1 second reduction. For smart contracts that feel there is a certain delay in their calculations, this should be taken into account.

03. security header block& block finished

PoW mechanisms always have the possibility of block configurations. Apps typically wait until a few blocks are checked out on top of the new header before doing so, as blocks are unlikely to be removed from the release chain. The blocks are "controlled". After the merger, there is the notion of "complete" and "security block". Compared to the “proof” blocks of the PoW mechanism, these PoS blocks are more reliable, but must be modified to understand how to use them correctly.

"Completed" blockIt refers to the blocking that more than 2/3 of PoS validators recognize as legal (regulatory). If the attacker wants to create a collision, the attacker must break 1/3 of the entire ETH contract. At the time of this writing, that means over $ 10 billion (or over $ 2.5 million) in ETH.

security header block(Secure Head Block) represents a block that must be placed in the correct chain according to network conditions. Assuming the network latency is less than 4 seconds, most validators are correct, and there is no resistance from the fork option, a secure header block is not a orphan block. The link below is a detailed description of how to calculate the security header block in various situations, and in a subsequent article we have developed and identified the theories and recognition of the header block. of security.

https://docs.google.com/presentation/d/1MUVaFyd9ce3hPQ5L-UhqVSfxf1ajMYFbkActkp5xNKI/edit#slide=id.gf1d0105ca5_0_147

After the merger,Runtime Layer API(eg JSON RPC) Available on request.recentlyThe (current) block returns a secure header block by default. Under normal network conditions, the top of the security header block and the blockchain are the same (the security header block is a few minutes later). Now with PoWrecentlyCompared to the (final) block, the security header block in PoS islessmay need updating. An addition to the JSON RPC to represent the top of the PoS chain.dangeroussymptoms.

The final block also goes through the new JASON RPC block.Of courseIndicator light (Completed). They can be used as an alternative to PoW analysis. The following table illustrates this point.

04 ibto follow

We hope this article will help developers prepare for the long-awaited PoS transition. The long-term partnership will be used for testing by communities throughout the next week. There will also be a community conference call for integration (link below) where construction companies, equipment and manufacturers can ask questions and hear the latest technology collaboratively. We are there or have:

https://github.com/ethereum/pm/issues/419