ethereum/pm

Ethereum Core Devs Meeting 44 Agenda

lrettig opened this issue · 12 comments

lrettig commented

Ethereum Core Devs Meeting 44 Agenda

Meeting Date/Time: Friday 10 August 2018 at 14:00 UTC

Meeting Duration 1.5 hours

YouTube Live Stream Link

Livepeer Stream Link

Constantinople Progress

Agenda

  1. Testing
  2. Client Updates
  3. Research Updates
  4. Three competing EIPs to delay the difficulty bomb and/or reduce the block reward:
    a. EIP-858 - Reduce block reward to 1 ETH per block.
    b. EIP-1227 - Delay bomb and change rewards to 5 ETH.
    c. EIP-1234 - Delay bomb and change rewards to 2 ETH.
  5. Constantinople
    a. EIP 1014 Issues
    b. EIP 1218: Simpler blockhash refactoring. We are looking for a reason to implement this or anyone who will champion this. Otherwise we will drop it.
    c. EIP 1283/EIP 1087: Net gas metering for SSTORE operations: 1283 is an alternative to 1087 created due to issues Parity was having implementing 1087. Read 1283's motivation seciton of the EIP.
    d. EIP-1109: Remove call costs for precompiled contracts.
  6. Fellowship of Ethereum Magicians Update (didn't get to this on the last call)
Deleted user commented

Please consider adding EIP-1276 as a part of discussion!

jbaylina commented

Could you consider EIP-1108 and EIP-1109 ?

sorpaas commented

Please consider adding EIP-1283 to the discussion as well. This is an alternative for EIP-1087. For parity-ethereum, we are having some issues implementing EIP-1087 as is, and we think EIP-1087 may be a potential optimization blocker. You can read more on this in EIP-1283's Motivation section.

Souptacular commented

@eosclassicteam disabling the difficulty bomb was rejected at the last core dev call so there is no reason to bring it up again at this time.

@jbaylina we discussed 1108 last meeting. See notes here.
Would you like to be on the next call to discuss 1109?

@sorpaas Added.

  • 👍1
jbaylina commented

Thank you @Souptacular ! Good discussion for EIP1108. And yes, I'll be glad to join the call!

winsvega commented

Writing an update here.
I suggest to drop blockhash refactoring if this is the case, because we already have a lot of changes.

extocodehash tests list: https://docs.google.com/spreadsheets/d/1xat7UI8GtB4ZGVdlK5_XQSHJZaMThi4SrlcL8XMZb5Q/edit?pli=1#gid=1811198384

create2 tests list:
https://docs.google.com/spreadsheets/d/1xat7UI8GtB4ZGVdlK5_XQSHJZaMThi4SrlcL8XMZb5Q/edit?pli=1#gid=1872446916

please add your ideas as a comments to the list. (right button -> comment)

Please confirm the implementation of this EIP
https://eips.ethereum.org/EIPS/eip-1014
the hash will affect contract creation address. which will affect all the tests.

Retesteth update:
Retesteth now support client configurations. You could set configs and bash script that retesteth will use to manage the RPC socket. Or you could set TCP socket and external ip address. retesteth could execute tests on all provided clients from command option like

retesteth -t RPCTests -- --clients="eth, parity, geth"
  • 👍1
chfast commented

Partial net sstore tests: ethereum/tests#483.

gumb0 commented

Decision on the formula for CREATE2 address is needed - option 1 vs option 2 vs RLP-encoding each component ethereum/EIPs#1014

holiman commented

@gumb0 re that address, two questions to resolve, as I understand it:

  • Use initcode VS hash of initcode
  • Prepend with 0xff VS use an RLP-schema to ensure that preimages don't collide with 'classic' address creation
lrettig commented

Closing in favor of #54