To implement a testnet with Merge and Sharding, with multiple clients we need a spec. Although the eth2.0-specs repo details many parts of the Merge and Sharding features today, it is not an appropriate place for hackathon specific changes, nor will the Merge specification necessarily stabilize during the hackathon implementation work. Instead, we maintain a meta-spec: Pin Merge features for implementation Quick iteration on new features or hackathon-specific modifications Merge into upstream spec as it stabilizes Notes + coordination point for implementers
4/26/2021Chain configuration Execution configuration (Eth1) Chain ID and Network ID Allocate pre-funded accounts At least 1 account with funds to distribute to new accounts later (faucet etc.) Deposit contract
4/19/2021Thu April 15. Summary notes by @protolambda. Note: Simultaneous OpenEthereum Berlin problem, not as many eth1 devs on call. Terminology Consensus (eth2), Execution (eth1), Application (dapps) Engine or Sub-system, not layer RPC
4/15/2021Draft by @protolambda. Special thanks to Karl Floersch for help with v1. Simple Summary Defines a new call opcode which enables virtualization within EVM. Abstract Add VIRTUALCALL which behaves similarly to the other call opcodes like delegate call & static call. It accepts a virtualizerAddress and virtual-memory input and output, in addition to the 6 fields that are normally supplied to STATICCALL. Once the call is executed, all stateful opcodes are execute as calls to the contract located at virtualizerAddress. Specification
4/9/2021