zkEVM Node version: v0.6.4
OS & Version: Linux
Network: Cardona
Expected behaviour
eth_call takes as a parameter the blockNumber as a parameter in order to execute the payload on a specific blockNumber.
Tx being executed in the blockNumber provided
Actual behaviour
Looks like this is not happening in the node since transaction is always being executed in the latest block number
Steps to reproduce the behaviour
SC deployed:
// SPDX-License-Identifier: MIT
pragma solidity 0.8.18;
contract GetBlockHash {
function getBlockTimestamp() public view returns (uint) {
return block.timestamp;
}
}
System information
zkEVM Node version:
v0.6.4
OS & Version:Linux
Network:Cardona
Expected behaviour
eth_call
takes as a parameter theblockNumber
as a parameter in order to execute the payload on a specific blockNumber. Tx being executed in the blockNumber providedActual behaviour
Looks like this is not happening in the node since transaction is always being executed in the latest block number
Steps to reproduce the behaviour
SC deployed:
eth_call
usingcast
:The above command should return always the same timestmap, but instead it returns always the latest one
returns always the same timestamp, which is the timestamp of the specified
blockNumber