Ethereum core developers meeting #24, (September 8, 2017) as posted by Souptacular.
Reminder: Metropolis is now split into 2 hard forks: "Byzantium" first and then "Constantinople".
1. Metropolis updates/EIPs.
a. Any "subtleties" or questions we need to work out.**
• Topic: EIP96 = PR210 contains three different hex code for the BLOCKHASH contract, but there should be at most two (runtime code and initcode).
• Resolution: Figured out on the call. Issue resolved.
•EIP #603: Add ECADD and ECMUL precompiles for secp256k1. See this comment for details and request to add to Constantinople.
• Resolution: Sounds like a good idea. Easy to add to all clients. Needs more feedback on the EIP PR and for editors to make sure it is correctly written. The change would be added to Constantinople if it is accepted. We will discuss official acceptance in future meetings.
b. Updates to testing.
• 9:23 On Hive multi-client cross-compatibility testing we are seeing better numbers wrt passing tests. geth has < 10 failing tests. cpp-ethereum has 700 errors, but because we cannot locally reproduce them there may be another unrelated issue causing it to fail. Many people pointed out mistakes in tests this week and that helped a lot.
c. Details and implementations of EIPs.
1. Implementation Updates
• geth - Basically done besides some testing. peter spots a cat around 12:38.
• Parity - Basically done besides some state tests failing and implementing blockchain tests. Should be ready in 2-3 days. Parity team will work with Martin H.S to resolve issue of Parity not working in hive. Arkidiy is sending branch information to Martin..
• cpp-ethereum - Progress made. Several minor fixes occurred.
• ethereumJ - Implemented all EIPs. Passing all blockchain, state, and transition tests, but still needs to implement/update compatibility with the new test format and with Hive.
• ethereumJS - As of this morning the elleptic pairing pre-compiles have been merged and all of the state tests are passing. About a dozen tests to debug. Expect to be passing blockchain tests soon.
• yellowpaper - Needs to add EIP 649, pointed out by /u/5chdn..
• pyethapp No progress since last core dev call.
• Other clients - No others in attendance. Afaik Ruby is deprecated and Haskell client (ethereumH) may no longer be actively maintained, not sure.
2. Determining gas prices for new opcodes & pre-compiles.
•Meeting occurred earlier in the week to discuss gas prices for Metropolis. Gas price benchmarks are complete and we are ready to confirm the suggestions created based on analysis of the benchmarks. This is will be discussed further in Gitter chat. More technical details discussed in the call.
•Cat plays with squeaky mouse toy.
d. Review time estimate for testing/release of Byzantium.
• The testing team has determined that we are at a place where we can launch the testnet within two weeks, pending the resolution of the Hive consensus issues in CPP we are currently having.
•Projected block times for mainnet:
30 second block times on September 22nd
39 seconds October 22nd
• We set a target date for the Ropsten testnet hard fork for 10 days from now - September 18th.
If testnet variables remain as they are now, that block number will likely be block number 1.7 million on Ropsten.
We will pick a block time that is around September 18th. This block number will be decided at 14:00 UTC Wednesday September 13th in the core developers chat.
We are picking the block number 5 days from now so we can account for difficulty adjustments on testnet that may occur between now and then. This allows us to pick a more accurate block number and adjust for mining changes on testnet.
These dates can be changed if we determine that we need more time for testing or major issues are found.
*A mainnet fork block number will be decided around or after the testnet hard fork launches.
The testnet will run for at least 3 weeks, which would put a tentative main net hard fork date at October 9th.
These dates are very unofficial and can be changed if we determine that we need more time for testing or major issues are found. October 9th is a tentative date assuming that the testnet fork goes smoothly and no major issues are found.
2. EIP 706: Snappy compression for devp2p - "very simple change yet reduces sync bandwidth by 60-80%."
• Active EIP PR discussion on-going. Most clients are in favor of implementing this change besides Parity.
•Arkidiy from Parity suggests that this be made as an optional subprotocol.
•Peter responds to Arkidiy.
•We will bring up this item in future core dev meetings. This change would affect the Ethereum network layer and not require a hard fork, just client agreement.
For more updates, technical blogs and general discussion on Blockchain Technology and Ethereum, please join us at our Website, reddit, Facebook, Medium, steemit and follow us at Twitter. Please feel free to share this post, email us with your suggestions and connect at LinkedIn.
#ethereum #blockchain #cryptocurrency #eip #metropolis #byzantium