everstake.eth (๐Ÿ’™,๐Ÿ’›) pfp
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 (๐Ÿ’™,๐Ÿ’›) pfp
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 (๐Ÿ’™,๐Ÿ’›) pfp
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 (๐Ÿ’™,๐Ÿ’›) pfp
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