-
Notifications
You must be signed in to change notification settings - Fork 75
Eth2.0 Implementers Call 10 Agenda #23
Comments
I would like to discuss the details of moving Ether from PoW chain to PoS chain, because it affects impact analysis for for the change of PoW. There are 3 main things:
an idea on the simply way to make censoring of deposits much harder by PoW miners. The beacon chain needs needs to allow counterfactual deposits. It means that I have an address A with some ETH on it on PoW chain. I choose a salt, and generate a CREATE2 contract address based on that salt, some fixed factory address, and some standard init_code, which creates a contract that can only self-destruct and burn (properly burn, by self-destructing to itself) ETH. I send 32 ETH to that address, that to everybody who does not know my salt looks just like any other address. Once the acceptance threshold is reached (i waited for 1024 or 2048 blocks), I reveal my salt to the beacon chain. It simply checks that CREATE2 address == sha3(0xff | factory_address | salt | sha3(init_code)) and accepts my deposit, without requiring me to actually instantiate the contract and burn my ETH - because nothing else can be done with it anyway |
Thanks for raising this. If we assume a Serenity mainnet is ready for launch in (early?) 2020, we have to discuss transition details on both sides. I would also add this to the Eth 1.x agenda once we are done with Constantinople upgrade and the ProgPoW debate. |
Eth2.0 Implementers Call 10 Agenda
Meeting Date/Time: Thursday 2018/1/17 at 14:00 GMT
Meeting Duration 1.5 hours
YouTube Live Stream Link
Agenda
The text was updated successfully, but these errors were encountered: