22 | This can happen when your request is malformed. Additionally, some
23 | of the provides use this code to signal that a particular method is
24 | not available or requires switching to a paid tier.
25 |
26 |
27 |
28 |
-32601
29 |
Method not found
30 |
31 | This usually happens when the method is not available with a given
32 | provider. If you need to use a specific method that's not supported
33 | by the provider, try changing the provider or consider switching to
34 | a more expensive tier.
35 |
36 |
37 |
38 |
-32602
39 |
Invalid params
40 |
41 | This happens when the request parameters are invalid. To fix, double
42 | check the parameters that you pass with the request and make sure
43 | they comply with the spec.
44 |
45 |
46 |
47 |
-32603
48 |
Internal error
49 |
50 | This might happen when the node reverts during the request
51 | execution. This can also happen if the request is malformed or
52 | invalid.
53 |
54 |
55 |
56 |
-32000
57 |
Invalid input
58 |
Missing or invalid parameters
59 |
60 |
61 |
-32001
62 |
Resource not found
63 |
64 | This usually happens when calling a method that's not supported. Try
65 | using a different method or switch providers.
66 |
67 |
68 |
69 |
-32002
70 |
Resource unavailable
71 |
Requested resource not available
72 |
73 |
74 |
-32003
75 |
Transaction rejected
76 |
Transaction creation failed
77 |
78 |
79 |
-32004
80 |
Method not supported
81 |
Method is not implemented
82 |
83 |
84 |
-32005
85 |
Limit exceeded
86 |
Request exceeds defined limit
87 |
88 |
89 |
-32006
90 |
JSON-RPC version not supported
91 |
92 | Version of JSON-RPC protocol is not supported
93 |