Repository navigation
Ethereum Core Devs Meeting 125 Agenda #401
Description
Activity
If anyone wants to read up for the verkle trie update, please read up here to get a summary for the suggested statelessness roadmap: https://notes.ethereum.org/Yn_mwNa2SeeQHnKsRgekKg
If there is time, I would like to briefly discuss the base fee calculation EIP I just published: #406
Reacted by Tim Beiko@adietrichs I saw a write-up a few weeks ago, I think written by Vitalik, where he proposed a basefee modification + explainer with concrete examples about how it would work with regards to transactions in the pool. I don't know if you know what write-up I'm talking about, but if you do -- do you know where it is? And is it about the same thing as you describe in that EIP?
ArrowGlacier fork id:
0x20c327fc(please double-check)Other resources on Verkle Tries
- PEEPanEIP - Verkle tries for Ethereum state with Dankrad Feist
- Stateless Meeting - Verkle Tries
@adietrichs I saw a write-up a few weeks ago, I think written by Vitalik, where he proposed a basefee modification + explainer with concrete examples about how it would work with regards to transactions in the pool. I don't know if you know what write-up I'm talking about, but if you do -- do you know where it is? And is it about the same thing as you describe in that EIP?
I assume you might be thinking of the "Make EIP 1559 more like an AMM curve" proposal? Or maybe some similar proposal.
I'd argue those are orthogonal to this EIP: The EIP modifies the signal used for the base fee update (how full was the last block? how full should it have been?), whereas these proposals by Vitalik & co deal with how to update the base fee given a specific signal. I also have some thoughts on the latter, but decided to keep them out of the EIP to really make it single-purpose.
Closed in favor of #407
- addedACDType: All Core Dev calls - execution & consensusType: All Core Dev calls - execution & consensusExecutionLayer: Issues that affect the execution layerLayer: Issues that affect the execution layer
on Feb 4, 2025
Meeting Info
Agenda