bug: batchTransaction confirmation logic races simulation branches

[nanaf6203-bit]

Summary

src/lib/batchTransaction.ts fabricates confirmation data with Math.random and races between real and fake states, leading to false positives in demos.

Affected area

src/lib/batchTransaction.ts

Steps to reproduce / impact

Inconsistent success/failure branching on confirmation lookup; the transaction can appear confirmed in the UI while the underlying promise hasn't resolved, or vice versa.

Expected behaviour

Use a single awaiting function (e.g. waitForTransaction from viem/ethers) and avoid hand-rolled simulation in production code paths. Move the demo data behind a feature flag.

Acceptance criteria

• Replace simulated confirmation logic with real provider reads.
• Add tests verifying success/failure propagation.
• Add a feature flag NEXT_PUBLIC_DEMO_TX enabling the simulated branch only in dev.

[Priyanshu1-62]

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

Hi sir,
Please assign this issue to me, thanks.

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

[iexwr]

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

I'd like to work on this issue. I will replace the simulated confirmation flow with real transaction confirmation handling, isolate the demo behavior behind the NEXT_PUBLIC_DEMO_TX feature flag, and add tests to verify correct success and failure propagation.

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

[danieloche635-bit]

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

i would love to work on this issue sir

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

[drips-wave]

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

🧑‍💻 @danieloche635-bit: 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 🌊

[drips-wave]

This issue has been completed by @danieloche635-bit as part of the Stellar Wave Program's 6th Wave 🥳

😎 @danieloche635-bit: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.