Skip to content
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

Some EVM nodes don't work in realtime mode #953

Open
droserasprout opened this issue Mar 3, 2024 · 3 comments
Open

Some EVM nodes don't work in realtime mode #953

droserasprout opened this issue Mar 3, 2024 · 3 comments
Labels
bug Something isn't working documentation Improvements or additions to documentation

Comments

@droserasprout
Copy link
Member

See EVM Networks page in docs.

@droserasprout droserasprout added the bug Something isn't working label Mar 3, 2024
@scottincrypto
Copy link

Workaround for this is to remove the ws_url from the node datasource config. It works OK with just the rpc URL configured.

@droserasprout
Copy link
Member Author

droserasprout commented May 30, 2024

Yeah, some node providers just don't expose the WS endpoint, I don't know why. Maybe there's no bug on our end. WebSocket connection is only needed to save some RPS and reduce latency a bit. I'll keep this ticket open until all this stuff is documented.

@droserasprout droserasprout added the documentation Improvements or additions to documentation label May 30, 2024
@scottincrypto
Copy link

Correct, some don't expose it. In my tests, I used Alchemy which does provide WS endpoints and found that I couldn't get any events to fire in real-time mode. Dipdup appears to be using the WS endpoints from what I can gather.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants