Thanks Shymaa! Appreciate your respectful answer and the resources you condensed for me to be brought up to speed.
Since we are discussing Prague inclusion, Iāll point out that the associated EIP is EIP-6800.
I wanted to note that unlike the original hackmd the EIP doesnāt seem explicitly to define WITNESS_BRANCH_COST and WITNESS_CHUNK_COST.
Furthermore it would be nice if the EIP clarified whether or not itās changing the code size limit. The wording under the Gas Reform section ā200 gas charged per 31 byte chunk of codeā makes it sound like or at least forgets to mention the added branch cost that would be charged once when accessing code beyond the first 3868 bytes (31 * 128). Since a full 32-bytes is allocated to the code size and code is only ever accessed in metered chunks it might make sense to lift the code size limit entirely and explicitly specify that in the EIP.
Wrote an ELI5 explainer on Verkle trees: Verkle Trees For The Rest Of Us: Part 1
1 Like
https://research.2077.xyz/the-verge-making-ethereum-verifiable-and-sustainable
An article on paths towards adopting Verkle trees on Ethereum and improving state management on the L1 by 2077 Research. A thread summarizing the articleās main takeaways is available here: https://x.com/2077Research/status/1868745665372885118