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.
The Besu team has been working with Geth on setting up proper testing for this EIP. The reason why this is complicated is that 2930 is a new transaction type, which requires a whole new suite of tests.
@JHancock asks if it would be possible to start looking at setting testnet fork blocks in parallel to launching YOLOv3.
It seems like that _could_ be possible, but it's hard to estimate exactly when that could be because we don't have an ETA for when the work will be completed. We _hope_ we can get YOLOv3 running in the next week or so 🤞🏻
Next up on the agenda is the Ice Age ❄️
It seems like the Ice Age will be kicking in again in July 2021
There's discussion about whether to update it now, or wait.
It seems like there is general consensus to not update it in Berlin, and wait to change it later.
Also a lot of comments in the chat about the fact that we're close to Eth2 shipping and that was the Ice Age's original purpose, so we should keep it (but delay it again) 😅
A final comment by @peter_szilagyi was that the Ice Age can be useful in resolving conflicts for contentious EIPs, so we should probably keep it around.
Next up is an update on EIP-2937 (eips.ethereum.org/EIPS/eip-2937). There were some outstanding questions on the EthMagicians thread: ethereum-magicians.org/t/eip-2937-set…
.@lightclients is giving some updates about it on the call. Worth watching the livestream for the details. Some of the latest changes to the spec are here, but not merged yet: github.com/ethereum/EIPs/…
Also, quick shoutout to @trueblocks for their difficulty calculator scripts were used to double check the difficulty bomb projections: github.com/TrueBlocks/tok… 💣
Last topic on the call: as part of moving to facilitate AllCoreDevs, I've been reaching out to folks involved with the process to hear their general feedback about the calls and how they could be improved.
I've talked with most client teams at this point, and am looking to chat with more people who have been involved in the process and want to share their thoughts. If that's you, please reach out here (DMs open!) or via discord (still @timbeiko) 😁
And that was it! Short call today, as everyone is focused on getting Berlin out, and we hope to make good progress on that async over the next week or two. See you all on the next on, Feb 5th 14:00 UTC 👋🏻

• • •

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

18 Jan
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 🐞⏳
Read 10 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!