-
Notifications
You must be signed in to change notification settings - Fork 870
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
"Invalid params" response to eth_call #2251
Comments
This should definitely work. Here is what I get:
My besu version:
Do other methods work? Can you call this method to get enabled RPCs:
|
This is not fixed. We still get this intermittently when trying to send transactions. |
@samsondav can you be more specific - that would help us a lot! |
I got the same results @macfarla did, and am unable to reproduce the issue without more information. |
closing this one - let us know more information (as requested above) if you're still having a problem @samsondav |
I am always getting "Invalid params" as response to eth_call - even for the example stated in the besu documentation (https://besu.hyperledger.org/en/stable/Reference/API-Methods/#eth_call)
the same call to a geth node works:
The text was updated successfully, but these errors were encountered: