27. [Decoder] Map WASM traps to readable messages

[dotandev]

Description
Implement specific decoding for WASM-level traps that occur during execution.

Requirements and Context

• Background: "Wasm Trap" is too vague. We need to know if it was an unreachable instruction, null pointer, etc.
• Success Criteria (Done):
  • Identify and report "Out of Bounds Access", "Integer Overflow", and "Stack Overflow".

Suggested Execution

• Fork/Branch: feature/decoder-wasm-traps
• Implementation:
  • Parse the error string returned by soroban-env-host.
  • Match common trap patterns.

Test and Commit

• Testing:
  • Trigger different traps in a test contract and verify they are correctly identified.
• PR Inclusions:
  • Trap identification logic.

Example Commit Message
feat(decoder): improve classification of wasm traps

Guidelines

• Must-haves: Differentiate between Host-initiated traps and VM-initiated traps.

---

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 150 Points.

🧑‍💻 Interested in contributing? Apply to work on this issue on Drips Wave, earn points, and receive rewards.

Warning

Only applications submitted via the apply link above will be considered. Please do not apply by commenting on the issue or opening a PR directly.

🤠 Repo maintainers: You can manage this issue's Points and Complexity on your Maintainer Dashboard here. Please keep an eye on applications and respond quickly 💙

ℹ️ Learn more about Drips Wave

[ALIPHATICHYD]

@ALIPHATICHYD has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I'd like to work on this because I enjoy improving CLI tools and this tackles a concrete pain point for developers working with rust

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

[afurious]

@afurious has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’m a good fit for this task because I understand how WASM traps manifest during contract execution and can distinguish between VM-initiated and host-initiated errors. I’m comfortable parsing soroban-env-host error strings and mapping them to specific trap types like “Out of Bounds Access,” “Integer Overflow,” and “Stack Overflow.”

I can implement precise trap classification logic and verify it with test contracts to ensure that errors are reported clearly and accurately during simulation.

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

[Divine-designs]

@Divine-designs has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

I’m Divine!
A skilled frontend developer and designer. I want to contribute to this project as I have worked on frontend gigs similar to implementing specific decoding for WASM level traps that occur during execution..
I would like to be assigned this issue.

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

[JerryIdoko]

@JerryIdoko has applied to work on this issue as part of the Stellar Wave Program's 1st wave.

Hi! I would like to work on this issue.

I understand the goal is to parse the generic "Wasm Trap" errors returned by soroban-env-host into specific, readable messages (e.g., Out of Bounds, Integer Overflow). I will ensure the solution differentiates between Host-initiated and VM-initiated traps as outlined in the guidelines.

I plan to implement the matching logic in a new branch feature/decoder-wasm-traps and verify it by triggering these specific traps in a test contract.

Could you please assign this to me?

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

[drips-wave]

Congratulations, @JerryIdoko! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on January 31, 2026.

🧑‍💻 @JerryIdoko: 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 issued 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 @JerryIdoko as part of the Stellar Wave Program's 1st Wave 🥳

😎 @JerryIdoko: You earned 150 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.

🧑‍💻 Repo maintainers: How'd the contributor do? If you like, you can reward them with additional points by making a compliment within seven days after the Wave Program's current wave ends.

[drips-wave]

@JerryIdoko received 3 compliments:

• Problem Solver: +50 points
• High-Quality Code: +50 points
• Fast & Easy: +50 points