ethereum/AllCoreDevs

Alex Beregszaszi

@axic

The last call deadline has passed for the Istanbul EIPs. It would be time to merge marking them as Final: ethereum/EIPs#2410

There is only one unaddressed comment for EIP-1884’s last call, @holiman and others, can you please respond here: ethereum/EIPs#2421

Yaz Khoury

@YazzyYaz

hey all, I made a PR for EIP-2424 for EIP Code of Conduct within the EIP process here: https://github.com/ethereum/EIPs/pull/2424/files

I've also started a Reddit post on this: https://www.reddit.com/r/ethereum/comments/e5wx9t/proposal_for_eip_2424_eip_for_code_of_conduct/

I'd love any feedback from the EIP participants on this. The scope of the CoC applies only to participants in the Github repository for EIPs and not anything outside it (like Medium, Twitter).

I won't be able to make the ACD call today as I'm currently traveling, but would love to feel out the sentiment of the Ethereum community regarding this. Best wishes.

Daft-Wullie

@Daft-Wullie

DOA
if it ain't broke don't fix it

Yaz Khoury

@YazzyYaz

an Ethereum Magicians discussions link since the Reddit post got removed for some odd reason: https://ethereum-magicians.org/t/eip-2424-eip-code-of-conduct/3824

James Hancock

@MadeofTin

Clients being ready as soon as possible is the priority. @shemnon

Hudson Jameson

@Souptacular

I moved the Istanbul Community Call stream: https://www.youtube.com/watch?v=zv5E9bq34j4&feature=youtu.be

Tomasz Kajetan Stańczak

@tkstanczak

sorry, it overlaps with eth2 call on networking

is there a zoom for that?

Hudson Jameson

@Souptacular

https://ethereumfoundation.zoom.us/j/456497243

Tomasz Kajetan Stańczak

@tkstanczak

@fjl

matrixbot

@matrixbot

Wei Tang Is the Google Docs shown in the meeting call public? Or do we have meeting notes?

Tomasz Kajetan Stańczak

@tkstanczak

EIP2384 tests passing in Nethermind

Edson Ayllon

@edsonayllon

@matrixbot Notes should be available for the Istanbul call soon.

Rough notes for the Eth2 networking call are here: https://hackmd.io/@benjaminion/BJ3YqrSTr

Danny Ryan

@djrtwo

eth2 call in 10 hours
agenda: ethereum/eth2.0-pm#108
livestream: https://www.youtube.com/watch?v=MxeEWmEdb5E
chatbox: https://www.youtube.com/live_chat?v=MxeEWmEdb5E&is_popout=1

Danny Ryan

@djrtwo

eth2 call in 8 minutes
agenda: ethereum/eth2.0-pm#108
livestream: https://www.youtube.com/watch?v=MxeEWmEdb5E
chatbox: https://www.youtube.com/live_chat?v=MxeEWmEdb5E&is_popout=1
zoom: https://ethereumfoundation.zoom.us/j/352229383

Phil

@phillux

URGENT RELEASE: Please download the latest releases, Parity Ethereum v2.5.11-stable and v2.6.6-beta to make sure you're ready for the Istanbul hard fork on December 7th, 2019. Alternatively, you can just download the updated chainspec and run your client as parity --chain foundation.json

Pooja Ranjan

@poojaranjan

F2pool just confirmed, they are ready for the Istanbul upgrade. @ethernodes might want to update the status.

Hudson Jameson

@Souptacular

@ppratscher see @poojaranjan's message above.

Peter Pratscher

@ppratscher

Thanks, updated!

Hudson Jameson

@Souptacular

@sorpaas @phillux Does Parity have their auto-update feature still or is it broken?

Wei Tang

@sorpaas

Our auto-update feature is still there. Note that it's opt-in. We did not mark it as "critical" auto-update this time.

Hudson Jameson

@Souptacular

Well.....isn't it critical?

Or rather, what is your criteria for it being critical or not.

Martin Holst Swende

@holiman

That message by @phillux was really not clear -- you could have been more clear that all previous version were broken!

David

@dvdplm

@Souptacular Critical: funds at risk or high likliehood of major breakage, but sure I hear you, it wasn’t an obvious call to make.

Hudson Jameson

@Souptacular

Hey David! Would Parity reconsider marking it as critical?

@dvdplm

Martin Holst Swende

@holiman

@dvdplm your parity/parity:stable docker image is 23 days old

high likliehood of major breakage

Like, chain split...?

David

@dvdplm

@Souptacular general sentiment over here seems to be that we made the right call. May I ask what your argument is for making it critical?

@holiman Thanks for the heads-up, will check asap.

Hudson Jameson

@Souptacular

@dvdplm I'll give my personal opinion, but let @holiman take lead on the discussion since he is EF security lead for the chain.

Peter Pratscher

@ppratscher

half of all parity nodes that were previously istanbul ready did already upgrade to the newest version

Hudson Jameson

@Souptacular

@dvdplm According to @ppratscher's site ethernodes Parity represents about 23% of the network and is commonly used by major miners and exchanges. Since we are in a time where these service providers have a lot more coins to deal with they may not have checked 1 tweet that Parity sent out (the Ethereum Cat Herders are manually reaching out now that we realize the severity of the situation). I fear if 1-2 major exchanges stay on the old fork and 1-2 major mining pools mine the old chain it will cause confusion and in a more severe case double spends.

David

@dvdplm

@Souptacular I agree there’s a risk here and our internal discussion yesterday went along pretty much exactly those lines. In the end the counter argument won: we’re confident that we’ll be able to reach out to the biggest pools of miners and infra providers; other users will often be running with the auto-update mechanism on. But as I said, it was not an easy decision and one mostly based on the avversion to reboot people’s nodes remotely.

Martin Holst Swende

@holiman

but let @holiman take lead on the discussion since he is EF security lead for the chain.

Yeah well, it's their call to make, but I could definitely see the auto-update being very useful in this scenario, but I guess that depends on how it's been "marketed". If it's explicitly "we'll only ever use this to protect funds" then fair, but if people rely on the auto-updater to save them the trouble of updating the node when there's trouble, then it might be counter-productive

Hudson Jameson

@Souptacular

@dvdplm Understood, and I can see how you all came to that conclusion. What steps have been performed to reach out to the miners/infra providers?

David

@dvdplm

@holiman The people that wishes to run their Parity node “hands-free” (i.e. trust us to push out auto-updates) are likely to opt in to it I would think.

Martin Holst Swende

@holiman

Ah right, ok! Then I misunderstood you. So what you're saying is that you can push to non-opted-in, but only in emergencies? And that all opt-in will get it. Then yes, I'm with you totally

David

@dvdplm

Correct. :)

Martin Holst Swende

@holiman

Anyway, an idea to consider is to mark it as critical after the fork block. That way, if you happen to screw with and crash a non-updated miner, it's better turned off than on (both for the network and the node operator)

Anett Rolikova

@anettrolikova

sorry guys for jumping in, just curious which term you prefer to be called Muir glacier - is it an emergency fork or unplanned ? or any other word that’s describing this fork

Takuya Umeki

@umetaku5

@anettrolikova I've also got that information, and mind that.
Ref:https://twitter.com/peter_szilagyi/status/1202899531920216065
https://github.com/ethereum/go-ethereum/releases/tag/v1.9.9

David

@dvdplm

@holiman Stale docker image should be fixed now. Again, thanks for the heads-up.

Eth-Gitter-Bridge

@Eth-Gitter-Bridge

<M H Swende (holiman)> Np!

Anett Rolikova

@anettrolikova

@umetaku5 sorry, I didn’t get what you’re referring to

Pooja Ranjan

@poojaranjan

@ppratscher another confirmation received from Blockscout - Parity-Ethereum/v2.5.11-stable ready

Tim Beiko

@timbeiko

Slightly less urgent, but the Besu Muir Glacier release is 1.3.6: https://github.com/hyperledger/besu/releases/tag/1.3.6

GuthL

@GuthL

Just a bit of info I can share about mining client, we made some measurements @starkware a few weeks ago (context: we measured the network capacity to mine on top of big blocks, aka >32kb, for which Geth and Parity have different behaviours).
From our estimation, Parity must represent less than 15% of mining power and if behaviours did not change, valid blocks should still be propagated by old Parity clients.

Where communities thrive

People

Repo info

Activity