BuidlZone-Labs/zicket-web

Wallet SDK Caches First Transaction Hash Indefinitely

Closed

#175 opened on Jul 29, 2026

View on GitHub
 (8 comments) (0 reactions) (1 assignee)TypeScript (43 forks)auto 404
Stellar Wavebugfrontendhelp wantedweb3

Repository metrics

Stars
 (4 stars)
PR merge metrics
 (PR metrics pending)

Description

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

Contributor guide

Research direction
Inspect the caching logic in `lib/walletSdk.ts` to see how `loadPromise` stores the transaction hash. Identify how to separate SDK module loading from per transaction signing, so each request generates a unique hash.
Tech stack
typescript
Domain
frontend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitTypeScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75