Extract the Error from a Failed Transaction's Raw XDR Result

[Emrys02]

Implement the constructor that takes a decoded TransactionResult XDR, navigates into the operation results, finds the InvokeHostFunctionResult, extracts the ScError type and code, and maps them to the correct HostError variant. This is the entry point the CLI's prism decode command calls.

Implementation Guidelines

• Navigate: TransactionResult → results → OperationResult → InvokeHostFunctionResult::Err → extract ScErrorType + ScErrorCode
• Return PrismError::NotSorobanTransaction or PrismError::TransactionSucceeded for invalid inputs

Expectations

• What done looks like: Given any failed Soroban TX result, returns the correct HostError variant. Given a success or non-Soroban TX, returns a descriptive error.

[Michealshodipo56]

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

I would like to work on this issue kindly assign me

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

[cybermax4200]

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

I’d like to work on this issue because it involves low-level transaction/result parsing and precise error mapping, which are important for good developer tooling and debugging workflows. Improving how raw XDR errors are decoded makes the CLI more useful and easier to trust when diagnosing failed Soroban transactions.

I have experience working with Rust, structured error handling, enum mapping, and navigating nested serialized data formats. I’m comfortable tracing through transaction result structures, handling edge cases cleanly, and implementing fail-safe parsing logic that matches the expected PrismError behavior.

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

[Johnjnr1]

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

Hi, I'd like to work on this issue! because I am very conversant with solving problems like this!

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

[Akinyemi04]

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

I would like to work on this issue

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

[drips-wave]

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

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