-
Notifications
You must be signed in to change notification settings - Fork 66
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
block polling interval #388
Comments
Stop using Helius then. It's garbage anyway. |
Cheers, thanks for the suggestion! Sorry, if I got this backwards, but lite-rpc acts as a kind of optimization "proxy" between a full RPC service and the client, doesn't it? |
Do you have way to get geyser subscriptions , if you do not want to poll blocks ?? |
so the polling is mainly done as a confirmation strategy? So that you could use lite-rpc to send transaction, but just subscribe to the signature-status updates on the "original” rpc connection... 🤷♂️ |
What is wrong with Helius? @jordanamr |
When using lite-rpc to optimize some rather rarely occurring swap transactions,
would there a possibility to tone down the block polling interval in between transactions?
Or would that undermine the whole optimization strategy?
So in other words does lite-rpc have to continually poll the current slot and block that fast?
Asking mainly because, when using in conjunction with paid RPC services,
the getSlot & getBlock methods calls amount for a really large amount of credits...🤔
The text was updated successfully, but these errors were encountered: