Eliminate deprecated RPC methods
The following deprecated methods are being removed in Agave 2.0:
- confirmTransaction
- getSignatureStatus
- getSignatureConfirmation
- getTotalSupply
- getConfirmedSignaturesForAddress
- getConfirmedBlock
- getConfirmedBlocks
- getConfirmedBlocksWithLimit
- getConfirmedTransaction
- getConfirmedSignaturesForAddress2
- getRecentBlockhash
- getFees
- getFeeCalculatorForBlockhash
- getFeeRateGovernor
- getSnapshotSlot
Clean all references and code for these from web3.js.
I've started to have a few second thoughts here.
- Responsibly removing these methods would require a major version bump, which would take legacy web3.js to 2.0.
- The new library that we actually intend on releasing as web3.js 2.0 already has these methods gone.
I think maybe we just cut our losses for legacy, and close #2859 by releasing the new library. Two birds, one stone.
I've started to have a few second thoughts here.
- Responsibly removing these methods would require a major version bump, which would take legacy web3.js to 2.0.
- The new library that we actually intend on releasing as web3.js 2.0 already has these methods gone.
I think maybe we just cut our losses for legacy, and close #2859 by releasing the new library. Two birds, one stone.
Hi Steve,
Is there an estimate on when the new library will be released? Or, if it is already released, can you help me with a link?
Hey @sekaieth; you can follow along with the Release Candidates here. It's looking like the final will come shortly after Solana Breakpoint this year.
Thanks!
I'm on a wallet team. Will the Agave 2.0 fork break my application if we don't upgrade this sdk immediately?
The versions aren't related. @solana/web3.js 2.0 breaks all APIs from the application perspective, not the network perspective. There are no RPC API changes between the network at 1.18 or 2.0, except that some long-deprecated methods have been permanently removed.
Thanks!
This is done in 2.0. We're not going to remove them in the 1.x line.
Because there has been no activity on this issue for 7 days since it was closed, it has been automatically locked. Please open a new issue if it requires a follow up.