BLOBBASEFEE
opcode (EIP-7516).TSTORE
and TLOAD
.
Having no transient storage contributed to extra gas consumption quirks in Ethereum; the most well known one being users charged extra for interacting with the contracts implementing OpenZeppelin’s Reentrancy Guard.
In practice, you will pay less on the execution level when interacting with the contracts that have functions that add no state change, like, again Reentrancy Guard.
Check out this nice deep dive into EIP-1153.
parentBeaconBlockRoot
in the block details:
5475939
to get the block’s parentBeaconBlockRoot
as discussed previously:
parentBeaconBlockRoot
to identify that it’s slot 4548475 on the consensus layer. Since it’s parent, we need the next slot: slot 4548476.
Use the slot number in a Retrieve blob sidecar call to the consensus layer:
MSTORE
& MLOAD
, the same thing can now be done with MCOPY
. This depends on the smart contract developer implementation however.
SELFDESTRUCT
, originally introduced as an understandable house cleaning opcode for developers — to remove the no longer needed code from the Ethereum state, actually made metamorphic contracts possible through the use of CREATE2
& SELFDESTRUCT
. You can deploy a contract, destroy the code, and then deploy a different contract to the same address. Example implementation.
Vitalik’s thoughts on the issue.
This EIP makes the use of SELFDESTRUCT
much more limited:
BLOBBASEFEE
allows contracts to manage data costs dynamically, especially for rollups. BLOBBASEFEE
only costs 2 gas to execute and provides the value of the blob base-fee directly from the block header.
Track the eth_blobBaseFee implementation in Go Ethereum.