Very productive week at the geth offsite. A few decisions impact verkle: - While data will never be deleted from the verkle tree in normal operation, our deep reorg code needs support for it, as it relies on reverse-diffs to reorg past the 128-depth limit.
Nouveau podcast! Barnabe et moi-meme parlons des retraits! - Spotify: https://open.spotify.com/episode/6Vmquudlk93saK7xKFJQNg - Amazon: https://music.amazon.com/podcasts/f60ed3ed-f11b-4d8f-b522-05f775e121eb/episodes/0842752c-2489-44ba-97b2-94e260066203/ethplorateurs-les-retraits
* @gballet.bsky.social is Geth core dev at the Ethereum Foundation. He focuses on evolutions to the protocol and bringing research ideas to fruition. His talk provides a high-level introduction to verkle sync and proposes a separation between attesters and block proposers.
What's up with verkle trees? We've been busy working on the conversion from the current merkle tree to a verkle tree. This is a challenging problem, because the amount of data is huge. This means it doesn't find in RAM, and needs at least a day for the translation to complete on a beefy machine.