Content
@
https://ethereum.org
0 reply
0 recast
0 reaction
ArtDemocrat
@artdemocrat.eth
Were we sitting on a zero day chain-killing Geth vulnerability discovered on Feb 6th for which no PR could be pushed (would've made it public), and which had to be kept secret until Mar 21st once Geth was likely below 66% thanks to secret coordination among key ecosystem folks and a fix was in place with Dencun? 1/5
1 reply
0 recast
0 reaction
ArtDemocrat
@artdemocrat.eth
- Tinfoil hat on - 1) earlier this year a client bug without "real" effects on the chain triggers a large group of influential ethereum people to make a big fuzz about it (while in last year's finality loss episode not even remotely was it considered such a big issue) 2/5
1 reply
0 recast
0 reaction
ArtDemocrat
@artdemocrat.eth
2) @coinbase, after years of not doing so, wakes up to influential people screaming about this issue 3) geth goes under super majority in a matter of weeks after years of status quo just accepting it as "not ideal" 3/5
1 reply
0 recast
0 reaction
ArtDemocrat
@artdemocrat.eth
4) a Geth chain-killing bug discovered on Feb 6th is kept secret until 21st of March (https://x.com/vdWijden/status/1770719230469542078?s=20), when the supermajority issue is likely no longer an issue and a fix already went into through "Dencun-ready" clients. I.e. we could hide the forest among the trees. 4/5
1 reply
0 recast
0 reaction
ArtDemocrat
@artdemocrat.eth
If this is anyhow remotely true, hats off to the coordination effort that took place. Keeping such a coordination effort confidential when a $0,5B asset class is at stake is a huge achievement. The "fixing the 737 while flying part" is, needless to say, worthy of the highest recognition. Ethereum 🩶.
0 reply
0 recast
0 reaction
