Amphora: key points of Ethereum integration

In the coming months, Ethereum will begin trading PoW to PoS approvals. In Ethereum's announcement in December 2021, the hard rocket that Arrow Glacier was scheduled to complete was extended until 2022. The hard rocket means that the difficulty of the PoW chain has increased and the approval of PoW has taken. end.

However, paying attention to the word Amphora in terms of performance at work can give you a full understanding of Ethereum merger.

The amphora is very interesting. Why it was born or after the Ethereum hackathon, Ethereum developers discussed the number of users participating in the joint venture. A time issue has been closed with Amphora for this meeting. The participants at this time were Besu, Erigon, EthereumJS, Geth, Nethermind, Nimbus, Lighthouse, Lodestar, Quilt, Teku, Prysm, etc.

However, Amphora was named after the new network experience because the names had to be broadened during the onboarding process and many processes with which the network became an integral part were also possible. tsim. Indeed, the multi-user sharing experience was achieved through this experience called Amphora.

First, we have divided the integration into five stages, M1-M5, to achieve the importance of consumer integration.

M1: The user is using the joint. Most groups complete this before the meeting begins.

M2: Let your team develop a seamless connection that makes sense for different processes and variations. Network development should be one-to-one network development. There is an Execution Layer (EL) and an Authorization Layer (CL), which allow two layers to communicate effectively through the PoS API engine.

M3: Establish a temporary upgrade and complete the PoW to PoS conversion. In a PoW network, if the hardness of a block is greater than the value, it is called TERMINAL_TOTAL_DIFFICULTY (TTD) and is considered the end of the PoW block. The completion process starts looking for new blocks in the PoS layer approval process. For each group to work well, the EL group must be connected to two CL users.

M4: Complete some EL and CL client devices in the network setup during the transition. M3 is a one-to-one development network and M4 is multi-for-many.

M5: Transform the Amphora from a short-term event to long-term community use. M5 wants the User Pool to start a network upgrade that will work throughout the transition for all logged in users.

This is why Amphora was born. By the end of the conference, M5 was complete and a PoS network of 10,000 validators with 100 nodes had been created. Under PoW, multiple users can reach TTD status and switch to PoS.

The success of the Amphora clan has given Merge tremendous power. Since then, the consumer team has had a clear list of tasks.

After the meeting, the M5 Amphora development network reiterated with a stable version of Pithos. Now, the team of consumers and scientists continues to appeal through collaborations to improve issues encountered in Amphora and respond to community feedback. Once the specialization is completed, a new stable testnet is available.