-
Notifications
You must be signed in to change notification settings - Fork 53
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
rpc.walletconnect error "method not supported eth_uninstallFilter" #698
Comments
We load balance across multiple RPC providers, looks like for We recommend using your own RPC provider for predictable functionality if you need this method. |
We are considering an improvement that would avoid this issue: #702 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Describe the bug
Sometimes I get error message in my dapp using viem
method not supported eth_uninstallFilter
when calling URLhttps://rpc.walletconnect.com/v1/?chainId=eip155:137&projectId=***************
(my project id) so the app crashes. I've investigated and it looks like rpc.walletconnect.com/ sometimes gives -32004 error.SDK Version (if relevant)
No
To Reproduce
Steps to reproduce the behavior:
Open Postman.
Send request to
https://rpc.walletconnect.com/v1/?chainId=eip155:137&projectId=***************
(use your project id) with the payload{"jsonrpc":"2.0","method":"eth_uninstallFilter","params": ["0x996f29fe3a5a4cb7eb8ee831b77e1ce7"],"id":1}
Send it multiple times. I am getting error
{ "jsonrpc": "2.0", "id": 1, "error": { "code": -32004, "message": "method not supported eth_uninstallFilter" } }
Expected behavior
Always result like this
{ "jsonrpc": "2.0", "id": 1, "result": false }
Screenshots
Not applicable
Desktop (please complete the following information):
Any OS, curl, Postman.
Smartphone (please complete the following information):
Not applicable.
Additional context
I guess it can be related to throttling (when I send this to JSON RPC too frequently), but the error msg must be obviously better.
The text was updated successfully, but these errors were encountered: