submitBatch dryRun option

[Jaydbrown]

Add { dryRun: true } that simulates every transaction and returns the would-be outcomes without submitting, for pre-flight UIs.

[ZacLou]

I'd like to work on this issue. I have relevant experience with this tech stack and can deliver a clean, well-tested PR. I can submit within 1-2 days.

[Ranjeet2063]

Hi maintainers, I would love to take up this issue.

I am a senior Web3 frontend engineer (#1 contributor on Mova Store with 28 successfully merged PRs), specializing in Next.js, React, TypeScript, Tailwind CSS, and Freighter/Stellar wallet integrations.

🎯 Technical Execution Plan for submitBatch dryRun option:

1. Component Design & UI State: Implement submitBatch dryRun option with clean component decoupling, responsive layouts, accessible forms/modals, and robust loading/skeleton/error boundaries.
2. Web3 & Client Logic: Wire real-time state streams, optimistic UI updates, and seamless Freighter wallet transaction signatures with user-friendly error alerts for rejections/timeouts.
3. Comprehensive Test Suite: Add component and unit tests (Vitest / Jest + React Testing Library) verifying state changes, input sanitization, and edge-case rendering.
4. Production Verification: Confirm zero TypeScript errors (noImplicitAny), zero ESLint/Prettier warnings, and clean production build (pnpm build).

💡 Why Assigning Me Directly Benefits You:

• Zero Maintenance Burden: Pixel-perfect UI with strict typing and responsive states that work out of the box.
• Rapid Turnaround: Ready to deliver a production-ready PR within 12–24 hours, clearing this task quickly.
• Track Record: 28 merged Web3 PRs — zero review ping-pong and immediate alignment with your conventions.

[Ranjeet2063]

Hi maintainers,

I have resolved this issue by adding the dryRun: true pre-flight simulation option to submitBatch in PR #687:
#687

Highlights:

• Added dryRun?: boolean to BatchSubmitOptions in src/batch-tx.ts
• Simulates transactions via server.simulateTransaction(tx) without calling sendTransaction
• Returns structured would-be outcomes (SUCCESS, FAILED, SKIPPED) for pre-flight UIs
• Added comprehensive unit tests in src/tests/batch-submit.test.ts (all 22 tests green)
• Verified full build

[Fading-Dev]

Hello! I’d be glad to work on this. The issue presents a good opportunity to improve the project, and I’m confident I can deliver the requested functionality while keeping the existing behavior intact. I’ll validate everything before opening the PR.