A _lot_ has happened on 1559 in the past few weeks. I've just finished summarizing it in the latest update: 006 out now πŸ”₯

TL;DR below πŸ‘‡πŸ»

hackmd.io/@timbeiko/1559…
First, the 1559 resources page is now linked right at the top πŸ‘€ Image
Second: we found a few bugs in our large state testnet. We're in the process of fixing them and restarting the network 🐞⏳
Third: now that EIP-2718 is confirmed for Berlin, we're updating the 1559 spec to work with it. We've also drafted an EIP to add a BASE FEE opcode to 1559, which will make a bunch of smart contract use cases smoother πŸ’…
Fourth, @VitalikButerin shared his thoughts on the DoS risks of 1559, and why they may not be as bad as they seem 🀞🏻
Fifth, @adietrichs has basically solved out transaction pool issues πŸŠβœ…
Sixth, some more R&D simulations by @barnabemonnot and the @nethermindeth folks, looking at the transition from legacy to 1559-style transactions and potential BASE FEE manipulation πŸ“‘πŸ‘€
And, last but not least, some updates on the recent pushback from miners' we've seen with regards to 1559 ⛏
And, right as I pressed Publish, @ralexstokes shared a great article about mining incentives alignment under 1559:

Added to the update :-)
Also fixed a bad copy/paste typo πŸ˜…

β€’ β€’ β€’

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

22 Jan
First up is the YoloV3/Berlin update. We now have a proper spec for Berlin: github.com/ethereum/eth1.…

This is the equivalent of the previous "Hardfork Meta" EIPs that we had for previous hard forks.
Where we're at right now is that we need one more PR merged into Geth for EIP-2718/2930, then we can set up YOLOv3 and start looking at blocks for testnets.
Read 18 tweets
14 Jan
We had our 9th EIP-1559 Implementers' call this AM πŸ”₯

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

Summary below πŸ‘‡πŸ»
First on the call, @adietrichs gave an update on his work about transaction pool management. His latest writeup is available here: hackmd.io/@adietrichs/15…
The document is quite short, and worth reading, but here are the main takeaways with regards to mining ⛏
Read 45 tweets
8 Jan
Starting the call with YOLOv3 updates!

Nethermind going first: EIP-2929 now passes all tests, and they are waiting for some final specification decisions for EIP-2930 & 2718. Everything is ready πŸ‘πŸ»

Besu: everything is implemented, and the team is working on testing for 2930 βœ…
OpenEthereum: everything should be ready πŸŽ‰

Geth: EIP-2930/2718 is still remaining, and then there are still a few small issues to fix. @lightclients is leading the implementation, and says it should be up to spec. Going into the details on the call now about the final tweaks πŸ“Ί
Read 29 tweets
8 Aug 20
Here's an attempt at explaining the ETH supply discrepancy that @pierre_rochard & others have pointed out.

TL;DR: because Ethereum doesn't just have ETH (it also has contracts), instead of tracking supply each block, both the tokens and contracts are tracked, a.k.a. the "state"
Obviously, because this state is large, it's not literally part of each block, instead we store it in a tree and just keep the root node ("state root"). Every time an account or contract, which is stored in a leaf of that tree, changes, it change its entire branch, incl. the root
Here's a write up by @PegaSysEng about what data is stored exactly where and what it represents: pegasys.tech/ethereum-expla…
Read 12 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 Become our Patreon

Thank you for your support!

Follow Us on Twitter!