-
Notifications
You must be signed in to change notification settings - Fork 126
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
Usage of depreacted RPC calls that will soon be removed #465
Comments
These are the occasion of the calls in the SDK:
|
Thanks for the heads up! I will push an update later today to remove all the deprecated functions and have it mimic the rust/js lib |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hey, there are bunch of RPC calls that are deprecated and will be removed very soon.
You can find the deprecated calls here:
https://github.com/anza-xyz/agave/wiki/Agave-v2.0-Transition-Guide
I searched your SDK for usage of these calls and looks like you are using
confirmTransaction
getConfirmedBlock
getConfirmedBlocks
getConfirmedBlocksWithLimit
getConfirmedTransaction
getConfirmedSignaturesForAddress2
getRecentBlockhash
getFees
getFeeCalculatorForBlockhash
getFeeRateGovernor
getSnapshotSlot
getStakeActivation
These calls will not be usable anymore soon after breakpoint when Agave 2.0 goes live.
You can find the all the usages in the code using this bash script:
https://gist.githubusercontent.com/cloakd/2366d9c5d415c27a1f26f10de0b8be93/raw/d0d3a25dda23586ba9704f7985fb06093032ec72/check_words.sh
Here you can find a replacement implementation for rust and JS client side for get stake activation:
https://github.com/solana-developers/solana-rpc-get-stake-activation
All other calls have replacement calls here:
https://github.com/anza-xyz/agave/wiki/Agave-v2.0-Transition-Guide
If you know users of the SDK would also be great if you could inform them about the deprecated calls so nothing breaks when the calls actually get removed on mainnet.
The text was updated successfully, but these errors were encountered: