Timeline for How can I tell if the node I am using is exposing the Parity trace methods?
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 23, 2020 at 18:59 | comment | added | haxsyn |
afaik all three providers mentioned here utilize some middle api layer, which allows for custom error messages. if one were to query a node directly, they'd see {"jsonrpc":"2.0","error":{"code":-32601,"message":"Method not found"},"id":1}
|
|
| Apr 23, 2020 at 3:38 | vote | accept | Shane Fontaine | ||
| Apr 23, 2020 at 3:38 | comment | added | Shane Fontaine |
Great! Thanks for the update. Finally, I see here that there is not really a specific, defined error code for these kind of things. github.com/ethereum/wiki/wiki/… Why, in this case, would you choose -32601? Is there a canonical list of error codes?
|
|
| Apr 23, 2020 at 3:27 | comment | added | haxsyn |
quiknode now returns "code":-32601 as well 👍
|
|
| Apr 22, 2020 at 18:08 | comment | added | Shane Fontaine |
Great response. I tried that call with Quiknode, Infura, and Alchemy. The error message for each was different for every one of them, and the error code was the same for Infura and Alchemy (-32601) but different for Quiknode (-32000). Do you know of a more standardized way of collecting this data without a bunch oof (if...else) statements?
|
|
| Apr 22, 2020 at 17:47 | history | answered | haxsyn | CC BY-SA 4.0 |