Skip to content

Breaking Change to eth_call Behaviour In 1.10.7 #23408

@nlordell

Description

@nlordell

System information

Geth version: 1.10.7
OS & Version: Windows/Linux/OSX

Expected behaviour

With the release of 1.10.7 which includes #23303, the behaviour of eth_call has changed in non-backwards compatible ways.

Specifically, it was previously possible to use eth_call with a from address that was an account with code. This was useful to simulate a transaction sent from that contract, for example simulating a transaction from a SC wallet. This appears to no longer be possible.

Steps to reproduce the behaviour

Perform an eth_call where the from address is an account with code:

{"jsonrpc":"2.0","method":"eth_call","params":[{"from":"$CONTRACT_ADDRESS","other":"parameters..."},"latest"],"id":0}

And receive an error response:

{"jsonrpc":"2.0","id":0,"error":{"code":-32000,"message":"err: sender not an eoa: address $CONTRACT_ADDRESS, codehash: ... (supplied gas ...)"}}

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions