feat(demo/stellar): Soroban RPC retry + exponential backoff (#59)#90
Merged
truthixify merged 1 commit intoJun 26, 2026
Merged
Conversation
|
Someone is attempting to deploy a commit to the truthixify's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
@KaruG1999 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits. You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀 |
Contributor
|
Clean merge. RPC retry + exponential backoff ( |
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
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.
Description
This PR introduces a centralized resilience primitive (
withRetry) to wrap network interactions with Horizon and Soroban RPC nodes, mitigating transient failures (408, 429, 502, 503, 504) and generic network drops (TypeError).The core implementation leverages an exponential backoff algorithm coupled with a full random jitter formula to prevent stampeding or herd effects on infrastructure endpoints under load.
Technical Changes
Core Architecture (
src/lib/stellar/retry.ts)withRetry<T>(fn, opts)using the exponential backoff calculation:RETRYABLE_STATUSset and nativeTypeErrorboundaries. All other 4xx errors abort immediately.AbortSignallisteners to clear active timeouts and short-circuit thread execution instantly during component unmounts.Component Integration & Idempotency Guardrails
POST /transactionssubmission endpoints from the retry loop acrossStellarSend.tsxandStellarReceive.tsxto prevent non-idempotent submission hazards (double-spending/collisions).fetchWithRetrycheck inside an isolatedtry/catch/finallyblock inStellarSend.tsx. Persistent node degradation falls back tostealthExists = falseinstead of breaking the payment thread, preserving the originalcreateAccountrouting logic.finallyblock to the best-effort Soroban propagation context to prevent the"Retrying (3/3)…"string from freezing on successful payment rendering screens.AbortSignaldirectly into the debounce simulation effect withinStellarSend.tsxto kill up to 6 orphan RPC queries on rapid input mutation.Verification Results
Unit Testing (
src/lib/stellar/retry.test.ts)Compilation
tsc --noEmit. Zero errors introduced in modified file paths.closes #59
Any feedback is welcome, thankss!!