-
Notifications
You must be signed in to change notification settings - Fork 20.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Breaking Change to eth_call
Behaviour In 1.10.7
#23408
Comments
Same limitation started to apply to the |
Yes, this is due to EIP-3607 which makes sending transactions from accounts with contract code illegal |
Makes sense. edit: It looks like this was already thought of:
In general the issue was not really a comment about the change in itself, and more that it was included from |
A. 3607 is still in dForraft, not final. |
Yes, we'll fix |
Geth does not follow semver. |
Fixed in #23424. |
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 ofeth_call
has changed in non-backwards compatible ways.Specifically, it was previously possible to use
eth_call
with afrom
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 thefrom
address is an account with code:And receive an error response:
The text was updated successfully, but these errors were encountered: