Wallet SDK Caches First Transaction Hash Indefinitely

[DioChuks]

Category

Bug

Priority

High

Description

In lib/walletSdk.ts, loadPromise stores the resolved dynamic import promise globally in a module variable. Once loadWalletSDK() resolves, subsequent purchases or wallet connection triggers return the exact same cached mock transaction hash string forever.

Evidence from lib/walletSdk.ts#L30-L57:

let loadPromise: Promise<string> | null = null;
export async function loadWalletSDK(): Promise<string> {
  if (!loadPromise) {
    loadPromise = new Promise<string>(...);
  }
  return loadPromise;
}

Proposed Solution

1. Separate SDK module loading from transaction execution.
2. Cache the SDK instance, but execute transaction signing dynamically per payment request so each transaction receives a unique hash.

Acceptance Criteria

• Wallet SDK package dynamically loads once.
• Every transaction signing request generates a unique transaction hash.
• Failed transactions can be retried without stale hash collisions.

Files

• lib/walletSdk.ts

[EstherIkechukwu]

I have gone through the description expect a pr in less than 24hrs

[Leemxiey]

@Leemxiey has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Maintainer sir, its left to your final decision. I am ready for work.

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

[Aycode01]

@Aycode01 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi can I work on this

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

[jbeloved700]

@jbeloved700 has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer please I will like to work on this issue

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

[zeemscript]

@zeemscript has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi, I'd like to work on this issue. I've gone through the description and acceptance criteria and I'm confident I can deliver it. I'll make sure every acceptance criterion is met and submit a clean, tested PR. Please assign it to me.

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

[sanctus-mvp]

@sanctus-mvp has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hi Maintainer, I’d be happy to work on this issue. I have experience with similar implementations and can ensure the work is completed efficiently and to a high standard.

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

[Otfrugger]

@Otfrugger has applied to work on this issue as part of the Stellar Wave Program's 7th wave.

Hello can i work on this quickly

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

[drips-wave]

Congratulations, @sanctus-mvp! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on July 30, 2026.

🧑‍💻 @sanctus-mvp: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊