Part of the Linea stack responsible for extracting data from the execution of an EVM client in order to construct large matrices called execution traces.
The spec says that one should keep warmths for TX_SKIP as they are. I wonder what that would mean e.g. if
sender is a precompile (does our testing environment even allow this ? or would we need to produce a signature for the (unknown) private key of a precompile) ?
coinbase is a precompile (those are warm by default)
TX_SKIPmessage callsThe spec says that one should keep warmths for
TX_SKIPas they are. I wonder what that would mean e.g. ifN.B. Recipients may not be precompiles.
source https://github.com/Consensys/linea-tracer/pull/1510#issuecomment-2491185905
TX_SKIPdeployment transactionsIf we don't have them yet we should add tests for TX_SKIP with trivial deployments. We can play the same games of
source https://github.com/Consensys/linea-tracer/pull/1510#discussion_r1852065538