-
Notifications
You must be signed in to change notification settings - Fork 828
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
Add detail messages to particular cases for INVALID_PARAMS #5098
Comments
Another instance - when transaction type is incorrect, eth_sendRawTransaction can respond with invalid params but it's not obvious what the problem is https://discord.com/channels/905194001349627914/938504958909747250/1108931495797727354 |
yes, invalid params don't indication where is wrong |
changed default to internal error not invalid params #5506 |
suggest to follow the pattern used here for peer disconnect reasons #6899 |
"invalid params" error code is used a lot, but always with the same message, which can hide a lot of detail.
eg for #4212 it's hard to get any clues as to the nature of the problem. Could add further values to the JsonRpcError enum with the same code -32062 but with different messages that might help the user diagnose or at least report issues
eg
missing param
wrong type for param
unable to decode param (eg RLP)
JsonRpcError
INVALID_PARAMS(-32602, "Invalid params"),
The text was updated successfully, but these errors were encountered: