- #SCRIPTCASE CALENDAR REMOVE AGENDA BUTTON SOFTWARE#
- #SCRIPTCASE CALENDAR REMOVE AGENDA BUTTON FREE#
Trying to have a single place where we can highlight changes to APIs.We want a wrap of all consensus changes prior to having a mainnet blocks. Delay between having consensus changes finalised and the community enacting them (eg JSON RPC changes were being made whilst the London blocks were being set).
We should have been pinged automatically.
Eg ropsten issue took 4-5 hours to detect.
Be good to have automated alerts to alert for testnet issues. Eg forkmon, ethstats, transations that are ready to send which test edge cases. We need a common set of requirements for testnet forks. To help with this we should set timeframes and expectations up front for when things go wrong, that this is the clear path that will be taken. People felt that there was a lot of pressure not to speak up when things went wrong. As such it would be good to be able to point to a default timing path so that all are clear. It was felt there was lots of community pressure to launch London and this is expected to continue for the merge. There was a desire to see criteria on how long we wanted to see testnets running smoothly, how long testnets needed to run for post-bug fixing etc. Main takeaway: wasnt really clear what we wanted to see on testnets before we set a mainnet block. Last 2 weeks have been speaking with the client teams on how London went, and the upcoming roadmap heading into the merge. there's a Merge channel in the Eth R&D discord which people can feed back to if any comments on the doc. Geth's synchronisation feedback will be particularly valuable. Will aim to finish ahead of Thursday call. We at Geth have reviewed the doc internally. Feel free to comment in Github or in Discord on the doc if anyone has feedback. Would be useful for Cat Herders to host/record call. Some of these methods map to black box testing in EIP-3675. L1 is priority but if we can re-use these for L2 we reduce complexity. There is an idea from Protolamda to reuse the core set of methods for Layer 2 communication. Any input on this doc is very much appreciated, before and after next week's call. 
'Execution payload cache' section and some thoughts on the 'Shared execution client'.
Also there are sections on 'Asynchrony' and 'Consistency checkpoints' (ie what is critical for the transition process and also useful for recovery after software failures). Next is 'Extended set of features' section. These methods and processes will be deprecated after the merge, unfortunately (is a lot of effort only to be deprecated). Next section is the 'Transition process'. Looking at the doc, firstly there is the 'Minimal set of methods' for node operation post-merge. It would be good to get feedback from Geth focus group re: state sync post-merge. There may be things missed in this doc. Pan is for a call next Thursday, before the Eth2 Dev call, engaging as many client devs as possible. We will start iterating the consensus API via this doc and the doc intends to be a starter for discussion. This builds on previous work from Rayonism as well as other conversations eg EIP 3675 discussion. This doc is not a proposal, it is the Design Space. Mikhail has put together a spec for the consensus API for the merge. Wed like at least one approval for each client. This is whatever the clients are comfortable with. Wed like volunteers from each client to be responsive to the issues raised. Re: json rpc spec, we need reviews from clients before we can complete this. Would be useful for Ethereum Cat Herders to host/record next Thursday's Merge callĦ4 bit integer has been chosen to be the nonce limit Any wider input on this doc is very much appreciated, before and after next week's call. All Core Devs Meeting 120 Meeting Date/Time: Friday August 20, 2021, 14:00 UTC Meeting Duration: 1 hour 30 min Github Agenda Video of the meeting Moderator: Tim Beiko Notes: Shane Lightowler Decisions Made / Action items Decision Item
0 kommentar(er)
