We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
We shall align the errors to Ethereum's.
{ "jsonrpc": "2.0", "error": { "code": -32004, "message": "Method not supported" }, "id": 9 }
And here's what we return:
{ "jsonrpc": "2.0", "result": "METHOD NOT IMPLEMENTED", "id": 9 }
The text was updated successfully, but these errors were encountered:
think we should use these error codes:
https://ethereum-json-rpc.com/errors
which is linked to from the ethereum docs "code": -32042, is probably a custom error code from QuickNode/Infura ?
"code": -32042,
Sorry, something went wrong.
actually id be careful with the format - seems some RPC providers dont respect the RPC spec we should probably look what Viem will de-serialise
claytonneal
giuliamorg92
No branches or pull requests
Summary
We shall align the errors to Ethereum's.
Expected result is:
And here's what we return:
The text was updated successfully, but these errors were encountered: