everstake.eth (๐,๐)
@eth-everstake
1/ Although we are marching towards the #Dencun upgrade and all posts are filled with its mentions, a basic understanding of the changes coming with it can still be challenging for the community. Today is the time for an explicit thread explaining all EIPs which is going to be implemented on the Execution Layer.
1 reply
0 recast
0 reaction
everstake.eth (๐,๐)
@eth-everstake
2/ EIP-1153: Transient storage opcodes ๐ย eips.ethereum.org/EIPS/eip-1153 ๐ฅ Authors: Alexey Akhunov, Moody Salemย ๐ In a nutshell: Running a transaction in #Ethereum can generate multiple frames of execution, each created byย CALLย (or similar) instructions.
1 reply
0 recast
0 reaction
everstake.eth (๐,๐)
@eth-everstake
3/ EIP-4788: Beacon block root in the EVM ๐ย eips.ethereum.org/EIPS/eip-4788 ๐ฅ@ralexstokes, @adiet88, @holiman, @dannyryan, @lightclient ๐It will force the commitment of a hash tree root of each parent beacon block in the corresponding execution block header, and store each of these roots in a smart contract.
1 reply
0 recast
0 reaction
everstake.eth (๐,๐)
@eth-everstake
4/ EIP-4844: Shard Blob Transactions ๐ย eips.ethereum.org/EIPS/eip-4844 ๐ฅ Authors: @vitalik.eth, @dankrad, @proto.eth, @asn-d6, @lightclient, @Inphi, @adiet88 ๐ For a detailed explanation, check out my previous cast: https://warpcast.com/eth-everstake/0x212a27ab
1 reply
0 recast
0 reaction