# Amphora Merge Technical plans [toc] ## High level This event is for problem-solving and hands-on engineering related to Ethereum Merge implementations. The Merge has many problems to tackle. To help us utilize our time well, we have some discrete [engineering goals](#Engineering-goals) outlined along with some related [specification goals](#Spec-goals). These are sorted to help you prioritize your targets, but we fully expect plenty of parallelization going on. **Teams are expected to create (relatively) stable implementations of the current Merge specs *prior to the event*.** Client progress as well as concrete milestones for an iterative approach to testing and devnets can be [found here](https://hackmd.io/@q8X_WM2nTfu6nuvAzqXiTQ/B1XhPxfVt). ### A note on pre-event preparations This event will be 10x more successful if most teams tackle the core of their implementations before our time together. This will ensure that: 1. everyone has grok'd the difficult problems at hand to allow for a deep level of in-person discourse 2. we can hit the ground running on the engineering goals If you do not have core implementations ready to interop with other teams on day 1, you'll likely be hacking alone in a corner for the first few days, and *the fomo of not being on a group devnet will be massive.* ***Prior to the event teams should implement the [interop specs](https://hackmd.io/@n0ble/merge-interop-spec) to the fullest of their capabilities*** ## Goals and preparations Client progress as well as concrete milestones for an iterative approach to testing and devnets can be [found here](https://hackmd.io/@q8X_WM2nTfu6nuvAzqXiTQ/B1XhPxfVt). ### Engineering goals 1. Functional devnets of latest merge specs 2. Live merge transition process from pow devnet to pos 3. State sync under new paradigm 4. Failure recovery, consensus<>execution synchronization, hive integration, etc 5. [bonus] Metrics, load, and scenario testing ### Spec goals 1. Iron out how to use engine-API generically during execution-layer sync (generically for any sync) 2. Propose any changes and extensions to existing merge specs 3. Identify and work through any critical issues that are identified at the event ### Freeze specs 10 days ahead for unified target at event *The [merge interop specs](https://hackmd.io/@n0ble/merge-interop-spec) are now available. See [here](https://hackmd.io/@n0ble/merge-interop-spec) for target releases* Tests for consensus-specs will be released prior to the event. Reach goal to create engine-API tests and/or provision hive to handle Merge clients.