Map All Storage Error Codes to Names, Descriptions, and Severity Levels

[Emrys02]

Implement the complete mapping of all Storage category error subcodes. Storage errors occur when contracts read or write ledger data and hit missing entries, access violations, size limits, or the notoriously unhelpful InternalError that tells developers almost nothing.

Implementation Guidelines

• Create crates/core/src/decode/mappings/storage.rs
• Map all known subcodes (ExceededLimit, EntryNotFound, AccessDenied, InternalError, etc.)
• For InternalError specifically, guide the developer toward diagnostic events since the code alone reveals nothing

Expectations

• What done looks like: Every Storage subcode has a clear explanation. The InternalError mapping explicitly tells developers how to get more signal.

[Praxhant97]

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

Greetings, i would like to work on your Prism project! Storage errors can stall developers for hours when they encounter vague host failures while reading or writing ledger entries, and I have the specific Soroban internals and Rust data-structure mapping skills this project needs to expose clear diagnostic paths. I am highly comfortable with Rust module design, mapping low-level error subcodes to structured meta-objects, and interpreting Soroban storage constraints, which will allow me to cleanly implement storage.rs, map every subcode (like ExceededLimit, EntryNotFound, and AccessDenied) to granular descriptions and severity rankings, and write explicit guidance for InternalError to point developers directly toward capturing diagnostic events for maximum debugging signal.

Timeframe: 24 hours

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

[dotmantissa]

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

I can fix this.
ETA: 1 - 2 hours.

Kindly assign it to me.

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

[mansory-01]

@mansory-01 has applied to work on this issue as part of the Stellar Wave Program's 5th wave.

I will like to work on this. I will create storage.rs and map all known Storage subcodes with clear explanations, with special attention to InternalError, guiding developers toward diagnostic events to get actionable signal beyond the code alone.

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

[drips-wave]

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

🧑‍💻 @mansory-01: 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 @mansory-01 as part of the Stellar Wave Program's 5th Wave 🥳

😎 @mansory-01: 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.