sdk: add retry with exponential backoff to RPC read methods#3099
Merged
sdk: add retry with exponential backoff to RPC read methods#3099
Conversation
Wrap all read-only RPC calls in DZClient with backon retry (3 retries, 500ms-5s exponential backoff) to handle transient RPC timeouts gracefully. Write methods and subscription loops are intentionally not retried.
Add a .when() filter to all retry sites so that only transient network errors (IO, Reqwest, Middleware) are retried. Permanent errors like AccountNotFound (RpcError::ForUser) now fail immediately instead of retrying 3 times with backoff, which was causing activation delays in the activator and e2e test timeouts.
snormore
force-pushed
the
snor/sdk-rpc-retry
branch
from
c740ac3 to
a3dbe8d
Compare
Replace "latest" with "^1" for @types/bun in all TypeScript SDK packages to avoid forced npm registry lookups that can hang indefinitely when the registry is unreachable. Also add timeout-minutes: 10 to the sdk-test CI job, and remove redundant per-package bun lockfiles in favor of the workspace-level lockfile.
snormore
requested review from
elitegreg,
juan-malbeclabs and
martinsander00
elitegreg
approved these changes
Feb 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary of Changes
DZClientusing the existingbackondependencyAccountNotFoundfail immediately via a.when()filter, avoiding wasted backoff delays in the activator and CLIDZClientinherent methods and theDoubleZeroClienttrait impl:get_balance,get_epoch,get_account,get_all,gets,get,get_program_accounts,get_transactions, andget_logsexecute_transaction) and subscription loops (subscribe,gets_and_subscribe) are intentionally not retriedDiff Breakdown
Core logic change in a single file — retry wrappers with transient-error filtering on all RPC read calls.
Key files (click to expand)
smartcontract/sdk/rs/src/client.rs— addedrpc_retry_builder(),is_retryable_rpc_error()helpers and wrapped all read-only RPC calls with filtered retryCHANGELOG.md— added unreleased entryTesting Verification
cargo test -p doublezero_sdk)-Dclippy::all -DwarningsRpcError::ForUser("AccountNotFound")— returned by Solana'sget_account()for non-existent accounts — is correctly classified as non-retryable, preventing the activator from wasting ~3.5s of backoff per missing account lookup