Earlier The following year, rayonism hackathon The first prototype of the architecture was created. Ethereum’s Change to proof of stake The Transition is often referred to simply as The Merge, will keep existing clients of the beacon chains (eth2) & execution layer (eth1), “merge” Both chains, having the beacon-chain drive execution layer consensus This approach is the latest in an ongoing series of iterations on the Ethereum Roadmap (more about that) Here).

While Rayonism While this architecture was solid, there were many other things to design and implement. This included the transition from proofs-of-work to proofs-of-stake. To do so, customer groups met face-to face last week (analogous). Eth2 interoperability as of 2019) for a workshop called Ánfora 🏺.

Here’s Here’s a summary of the key points that were covered during the workshop, and how to get there. The Merge.

Reaching the Amphora Milestones

The This event had the purpose of achieving consensus between execution layer clients teams in order to resolve open issues in specification and to achieve a set development milestones. Each Customers reached milestone to be closer to a fully functional devnet merger that transformed from PoW into PoS. Representatives Starting at Besu, Erigon, EthereumJS, Geth, Nethermind, Nimbus, Lighthouse, Lodestar, QuiltAnd Teku The workshop was attended in person. The Prysm Together with other members of the above teams, they participated remotely.

The Customers only had to implement the fusion specification for M1 as their first milestone. It Almost all of the teams had completed the task before the workshop began! To Customers can validate their implementation. Several – Tests – Suites They These were available.

Then Customers set up networks of development with increasing technical complexity and greater node diversity during the M2, M3, M4 milestones. M2 was created Execution Layer (EL) Consensus Layer (CL) Teams pair up one-on-1 and launch a post merger development network. This Both layers were able to communicate with each other over the Engine API In a point-of-sale context.

M3 stands for Amphora’s Workshop went beyond rayonism to help customers establish ephemeral networks for development that would last through the transition from PoW into PoS.

The PoW difficulty is the basis of transition: Once a block has difficulty equals or exceeds an arbitrary value, it is called TERMINAL_TOTAL_DIFFICULTYEither DTTIt is the last PoW block. The The execution layer starts listening to PoS consensus layers for new blocks. To To ensure that each team’s implementation was strong, EL teams needed to connect with two CL clients and vice versa in order to pass M3.

M4 was the ultimate goal of the event. It was to get multiple EL & CL customers into a network that could go through the whole transition from PoW and PoS. In In other words, M3 was all about one-to-1 developments, but M4 was all about many-tos many.

We This was achieved for a small subset of teams, but we still had to reach our ultimate goal of M5.