Retry Logic for Transaction Submission

[Pidoko257]

Description:
Stellar transaction submissions can fail with transient errors (sequence number mismatch, fee bump needed, network congestion). The transaction submission service should implement intelligent retry logic: refresh sequence number on tx_bad_seq, bump fee on tx_insufficient_fee, and use exponential backoff for network timeouts.

Acceptance Criteria:

• tx_bad_seq error triggers sequence number refresh and rebuild before retry
• tx_insufficient_fee error bumps the fee by 20% and retries up to 3 times
• Network timeouts retry with exponential backoff up to 5 attempts
• Other errors are not retried and are returned immediately with the Stellar error code

Skills Required:

• Node.js / TypeScript
• Stellar SDK (transaction submission)

[dev-RAM11]

@dev-RAM11 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi, I'd love to be assigned this issue. I've been actively contributing across Stellar Wave 4 and Wave 5 projects, working across smart contracts on Stellar/Soroban, Rust backends, NestJS APIs, Next.js frontends, and DevOps infrastructure — and I'm well-positioned to tackle this effectively.
I've reviewed the issue and have a clear implementation plan. I'll follow the project's contribution guidelines, write tests alongside the implementation, and keep the PR focused and reviewable.
Looking forward to contributing!

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dev-RAM11 to this issue.