Stellar transaction simulator usage guide

[truthixify]

Tier: S (½-1 day) Type: writing

Context

Soroban simulateTransaction is powerful but underused. Document how to wire it for safe pre-flight in stealth payment flows.

Scope

Write docs/guides/stellar-tx-simulation.mdx:

• What simulation is (resource estimation, output preview, error decoding)
• When to use (always for Soroban contract calls, especially before signing)
• SDK helpers + raw RPC patterns
• Decoding simulation results (events, return values, fees)
• Handling sim failures (decode contract errors, show actionable user feedback)
• Demo's reference implementation walkthrough

Acceptance criteria

• Page committed
• Working code snippet end-to-end
• Linked from SDK Stellar and demo

Files to start with

• New: docs/guides/stellar-tx-simulation.mdx

[baedboibidex-cmyk]

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

I would love to take on this issue and write the definitive guide for Soroban transaction simulation. Integrating pre-flight simulations (simulateTransaction) is an absolute requirement for robust Stellar smart contract development, particularly when calculating resource footprints and debugging stealth payment pipelines before committing gas fees on-chain.

To deliver an exceptional, highly practical resource, I will structure docs/guides/stellar-tx-simulation.mdx around:

1. The Core Simulation Lifecycle: Providing a crisp breakdown of what happens during a Soroban pre-flight check—focusing on CPU/memory resource estimation, storage footprint declarations, and transaction cost previews.
2. Implementation Blueprints: Writing clean, copy-pasteable code blocks that illustrate how to use the SDK helpers alongside raw RPC patterns to execute simulations right before a signature prompt.
3. Parsing and Error Decoding: Detailing exactly how to intercept and read the simulation payload—including parsing emitted contract events, mapping return values, and extracting underlying contract panics or revert reasons to surface actionable UI feedback.
4. Reference Walkthrough: Documenting a production-style implementation based on the demo application to show a real-world, end-to-end simulation flow.

I can have this guide fully drafted and formatted within 24 hours of being assigned. Let's make Soroban pre-flights a standard pattern across the ecosystem!

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

[truthixify]

@baedboibidex-cmyk Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. Silence is the only thing that costs you the assignment; if you get stuck or context changes, just say so on the PR.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building.

[drips-wave]

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

🧑‍💻 @baedboibidex-cmyk: 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 🌊