The JSON-RPC methods in this section were removed in Agave v2.0 and are not available on current RPC nodes. Migrate calls instead of detecting a validator version and falling back to these method names.
An SDK may still expose a similarly named convenience function. For example, a
client-side confirmTransaction helper can use getSignatureStatuses and
subscriptions internally. That helper is different from the removed
confirmTransaction JSON-RPC method documented here.
Migration Summary
| Removed method | Supported replacement |
|---|---|
confirmTransaction | getSignatureStatuses; compare confirmationStatus and err |
getConfirmedBlock | getBlock with commitment: "confirmed" |
getConfirmedBlocks | getBlocks with commitment: "confirmed" |
getConfirmedBlocksWithLimit | getBlocksWithLimit with commitment: "confirmed" |
getConfirmedSignaturesForAddress2 | getSignaturesForAddress |
getConfirmedTransaction | getTransaction with commitment: "confirmed" |
getFeeCalculatorForBlockhash | isBlockhashValid for validity; getFeeForMessage for cost |
getFeeRateGovernor | No direct replacement; use getFeeForMessage for a transaction message |
getFees | getLatestBlockhash plus getFeeForMessage |
getRecentBlockhash | getLatestBlockhash plus getFeeForMessage when a fee is needed |
getSignatureConfirmation | getSignatureStatuses; read confirmations and err |
getSignatureStatus | getSignatureStatuses; read the first result's err |
getSnapshotSlot | getHighestSnapshotSlot |
getStakeActivation | Decode the stake account and derive activation from epoch data |
The replacement signature-status method does not accept a commitment parameter.
When migrating a legacy call that did, compare the returned confirmationStatus
with the commitment your application requires. Treat the levels as ordered:
processed < confirmed < finalized.
Is this page helpful?