We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
Why are we using a custom implementation of send_and_confirm_transaction_with_spinner?
I changed to it solana_rpc_client implementation of send_and_confirm and my RPC was much happier without throwing 429s all the time.
The text was updated successfully, but these errors were encountered:
Can be closed. With 2.0 submitting and confirming transactions is much better now.
Sorry, something went wrong.
No branches or pull requests
Why are we using a custom implementation of send_and_confirm_transaction_with_spinner?
I changed to it solana_rpc_client implementation of send_and_confirm and my RPC was much happier without throwing 429s all the time.
The text was updated successfully, but these errors were encountered: