Minimal Merge roadmap

[tersec]

M0 through M5 milestones defined at https://hackmd.io/@tvanepps/amphora-milestones

• guide add merge SSZ consensus object tests #2858 into unstable, creating base from which multiple people can work
• implement other beacon chain merge functions, largely back-end computational logic (including upgrade_to_merge)
• add tests as they pass to the tested part of the EF test suite, taking advantage of support for running with/without execution client to do so without devops changes initially
• audit all ALTAIR_FORK_EPOCH references to ensure they behave properly with respect to MERGE_FORK_EPOCH
• add merge block/state database support, including immutable-state support, along with tests
• add merge hardfork usage to block_sim
• implement modified BeaconBlocksByRange v2 / BeaconBlocksByRoot v2
• subscribe/unsubscribe to/from merge topics
• recreate or port over initial quick merge #2477 from quick-merge-v1 branch the RPC mechanisms such that they target current (similar, but tweaked) protocol
• M0 milestone
• M1 milestone
• create working launch_local_testnet support for at least post-merge world and ideally merge itself
• document, along the lines of https://github.com/status-im/nimbus-eth2/blob/stable/docs/rayonism_merge.md, how to run this testnet with geth or other execution client- [ ] implement modified beacon_block gossip validation (https://github.com/ethereum/consensus-specs/blob/v1.1.0/specs/merge/p2p-interface.md#beacon_block)- [ ] M2 milestone
• M2 milestone
• M3 milestone
• M4 milestone
• M5 milestone

[tersec]

M5 is effectively separate -- it's a whole-ecosystem effort more intrinsically.