Eth1 -> Eth2 Merge Requirements Overview
Closed this issue ยท 4 comments
mkalinin commented
The material to facilitate discussion around the Merge planned for ACD 106.
Spec drafts
Eth1 client modifications
- eth1-eth2 communication protocol
- state and chain sync
- new opcodes (
RANDOM
,BEACONBLOCKROOT
, etc) - block storage (block number, block hash, fork choice)
- consensus part (ethash, difficulty, timestamp, rewards)
Breaking changes
BLOCKHASH
opcode (either randomness or verification)DIFFICULTY
opcode- guarantee of storing entire block history by full nodes
mkalinin commented
Eth1 side changes
UPD:
Client modifications
- eth1-eth2 communication protocol
- state and chain sync
- new opcodes (
RANDOM
,BEACONBLOCKROOT
, etc) - block storage (block number, block hash, fork choice)
- consensus part (ethash, difficulty, timestamp, rewards)
Breaking changes
BLOCKHASH
opcode (either randomness or verification)DIFFICULTY
opcode- guarantee of storing entire block history by full nodes
djrtwo commented
Recent workshop presentations by @mkalinin and @gballet on eth1/eth2 merge
https://www.youtube.com/watch?v=uGeIDNEwHjs&t=7450s
holgerd77 commented
Argh, argh. Sorry for writing the same message over and over: but - also here - actually loved the fact that we finally had some dedicated issues on these things (HF timing, merge,...), would find it very valuable to keep this open (or - again - is there another go-to place here?). ๐