Lots of thoughts on the conversations this weekend, and while I think there is a charitable interpretation to some of the criticisms, let me start by saying it's pretty rich to criticize people for "jerking off and watching the burn" when well....
Obviously, narratives get distilled on Twitter, but, to say the least, i makes it harder to educate folks about the subtleties (e.g. willeip1559lowergasprices.org) when this is what's pushed.
Similarly, no one ever dropped the "1.x roadmap": it was literally the last Ethereum event that happened pre-COVID and work on its various aspects is progressing (not to mention 1559 was part of it...)
One of the big bits of 1.x was capping the amount of data nodes need to store. With The Merge happening, it's a good time to have this conversation, and we literally had it on the last AllCoreDevs, see:
The reason these things take time is that Ethereum supports billions (trillions?) in economic activity, and we can't break the chain. Similarly, we can't break all the applications that are built on it. Otherwise, we'd have done State Rent in 6 months.
It's 100x easier to fork geth, claim you've fixed something which isn't the actual bottleneck, launch your token and complain that Ethereum "isn't doing anything" while you never submit a single upstream PR.
That being said, I hear the concern that fees are too high, L2 adoption isn't as widespread as we'd like, and that the EVM isn't improving fast enough. A lot of smart people working on Ethereum are aware of this and spending their time trying to fix it.
We just *can't* have Ethereum go down to ship these changes, and that's 50%+ of the complexity of these things. Similarly, we want to keep node hardware requirements low enough for normal people to verify the chain, which makes a lot of "easy" solutions not possible for Ethereum.
And while there might be a better point along the gas limit/hardware requirement curve than we currently are at, a 20% increase just isn't going to cut it. We need multiple 10-100x increases, which aren't as simple to ship.
That being said, it's a free market, so if we fail at delivering this, of course users and applications will end up elsewhere!
The best we can do is to keep attracting the best people, aligning them on the largest challenges, and shipping solutions. I'm confident we have them today, and the vast majority of them aren't on Twitter arguing, but making sure Ethereum is gmi. Thank god. Rant over 🙏
One more thing, just stumbled upon this very accessible thread by @ChainLinkGod explaining the tradeoffs of blockchain scaling. Highly recommend it if you're trying to understand the different approaches:
@ChainLinkGod Other interesting thing for those interested, here are the "readiness checklists" we've used for 1559 and are now using for The Merge to gauge when a change is ready to deploy to mainnet:

1559: github.com/ethereum/pm/bl…
Merge: github.com/ethereum/pm/bl…

• • •

Missing some Tweet in this thread? You can try to force a refresh
 

Keep Current with Tim Beiko | timbeiko.eth 🍵

Tim Beiko | timbeiko.eth 🍵 Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @TimBeiko

15 Oct
We wrapped up @ethereum #AllCoreDevs 124 this morning, and, as promised, we've had several merge updates since the last call!

Agenda: github.com/ethereum/pm/is…
Stream:

Recap below 👇🏻
@ethereum First on the call, we recap'ed the #amphora🏺 interop from last week. Rather than rehashing the recap, here's the blog post covering the event 😁:
@ethereum A couple updates from the call that aren't in the blog post: Pithos, the new devnet which was launched yesterday, is now running with 3 consensus clients + geth. Besu + Nethermind will be added soon. Explorer: pithos-explorer.ethdevops.io

Build instructions: github.com/parithosh/cons…
Read 28 tweets
17 Sep
We wrapped up another @ethereum #AllCoreDevs this AM 🛠

Agenda: github.com/ethereum/pm/is…
Stream:

Recap below 👇🏻
@ethereum First up, @nethermindeth had an announcement urging people to upgrade to v1.11.2 to mitigate a potential PoW vulnerability. More details here:

Upgrade your nodes 🚨
@ethereum @nethermindeth Then, we discussed several things related to The Merge ⛓
Read 29 tweets
15 Sep
Exactly one year later, I'm happy to come back to this thread and say we're sending back the extra funds from the @gitcoin grant back to the CLR match pool 😁

Details below 👇🏻
@gitcoin When we started to work on EIP-1559, we raised a ~90,000$ Gitcoin grant which, at the time, was the largest ever in a single round on Gitcoin. gitcoin.co/grants/946/pro…
@gitcoin We always meant for those funds to be used for common goods, and from Day 1 committed to sending any excess funds back to CLR matching.
Read 9 tweets
3 Sep
We just wrapped up another @ethereum #AllCoreDevs.

Agenda: github.com/ethereum/pm/is…
Stream:

FYI, this one is a bit less "recap-able" because most of the call was going over merge docs ⛓. Recording strongly recommended if you care about the Merge!
@ethereum First up on the call, we went over @mkalinin2's Consensus <> Execution layer communication API doc, which you can find here: hackmd.io/@n0ble/consens…
@ethereum @mkalinin2 We had already covered part of it in a Merge call last week () and continued going over the details. Mikhail went over some of the comments on the doc and explained the most recent changes.
Read 30 tweets
20 Aug
First on the call, we had @mkalinin2 present a design document for the Merge Consensus APIs: hackmd.io/@n0ble/consens…

He went over it on the call and answered some questions from other attendees.
@mkalinin2 The document was inspired by what was done in the Rayonism hackathon (rayonism.io), the merge EIP (eips.ethereum.org/EIPS/eip-3675) and even opens the door to L2 interop, as proposed by @protolambda:
Read 30 tweets
9 Jul
We just wrapped up another @ethereum #AllCoreDevs 🤝

Agenda: github.com/ethereum/pm/is…
Stream:

Recap below 👇🏻
First on the call we discussed the London upgrade going live on Goerli and Ropsten. For Goerli, @vdWijden and Karim from @ConsenSysQuorum spammed the network before the fork block and after it to make sure things went smoothly, which they did 🎉
On Rinkeby, the @go_ethereum team found a small issue in their validator configs: the minimum gas price that miners/validators accept in Geth is 1 gwei, and post-London this is calculated with the priority fee instead.
Read 44 tweets

Did Thread Reader help you today?

Support us! We are indie developers!


This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal

Thank you for your support!

Follow Us on Twitter!

:(