Closed Souptacular closed 5 years ago
I would love to see some support from the core devs on the Tennagraph effort for measuring something besides coin votes for progpow :-D
https://tennagraph.com/eip/1057
They make signaling yea nay or abstain really easy... just tweet your opinion and put it on the site or hope someone else does ;-)
@griffgreen there's a couple double counts in the "influencer vote" on both Yay and Nay. I noticed a few other inconsistencies that I think may be misinterpretations as well (someone I think was being sarcastic in a Tweet)
I would like to discuss EIP 1344 (Chain ID opcode). Positive sentiment has been logged in EthMagicians, and I think we could propose moving this to Last Call after following up with some client implementors confirming a few small decisions with the implementation. If everything seems good, it could potentially be a candidate for Istanbul as it would be valuable to EIP-712 implementations.
I think it will be useful to also look into proposed process of selection of EIPs for future upgrade #1929 with regards to Agenda item 3(b).
I did the suggestion in 1929 for EIP-1344 here: https://github.com/ethereum/EIPs/pull/1934
@GriffGreen tennagraph is outside of scope for the core dev meetings. @fubuloubu will you be on the call to 1344 and 1929?
Just for 1344.
I used 1929 in order to make sense of the process, so I can attest to it's utility however! :smiley_cat:
@fubuloubu cool! Tim is running this meeting and should add your stuff to the end of the meeting.
It's early here on the West Coast. Will there be an approximate time?
Meeting time and duration are listed at the top of the issue. I don't have an ETA on when the meeting will end unfortunately. Could be 30 minutes if things go fast.
Unfortunately, I won't be able to join today. Updates:
Since last time, written the post about the estimation of contract storage sizes.
Regarding sync protocols, the latest version of Red Queen's doc is here. We are about to start Proof Of Concept implementation, while still trying to unify with Firehose (Trinity team's proposal).
On the stateless client prototype, gathered more data. The first version of the blog post had data up to 5.4m block, then I updated it to 5.8m block, currently gathered data up to 6.4m blocks. Hoping to update it further when I get data up to 7.1m. Will fix outstanding failures and move on to the slightly stateful clients, to see how much reduction in the block proof sizes it will get.
I have been thinking about storage hoarding a bit, and I am becoming more sceptical that the hoarding would actually be practical (I will likely write a post about it later). Therefore, I am going to explore the variant of the roadmap with EIP-1559 (fee market change for Eth1.0) + making SSTORE/SLOAD more expensive in the first hard fork, instead of introducing prepayments.
No updates on Turbo-Geth.
Aleth: two release candidates for 1.6.0. If nothing happens, the release will be done on Monday. Changelog: https://github.com/ethereum/aleth/blob/release/1.6/CHANGELOG.md#160---unreleased
Parity Ethereum updates:
For a full list of changes, refer to the changelogs on our releases page: https://github.com/paritytech/parity-ethereum/releases
Actual live-stream link: https://www.youtube.com/watch?v=gfC92gQKKnI
Actual live-stream link: https://www.youtube.com/watch?v=gfC92gQKKnI
@Souptacular the video is unlisted, couldn't find it directly on YouTube. Thanks @veox for sharing the link.
Closing in favor of #95
Ethereum Core Devs Meeting 59 Agenda
Agenda