Replace All unwrap() Calls with Proper Error Handling

[Timi16]

Description

The codebase contains several unwrap() and expect() calls that can cause unexpected panics in production. Replace them all with proper ? propagation or meaningful error types.

Requirements

• Run grep -rn "\.unwrap()" src/ to find all instances
• Replace each with ?, ok_or(...), or a handled match
• For expect() calls: either remove or convert to a real error with context
• Add context strings to errors using .context() from anyhow
• All existing tests must still pass

Suggested Execution

1. Branch: git checkout -b fix/remove-unwraps
2. Find all unwrap() and expect() calls
3. Replace each with proper error propagation
4. Run cargo test to verify
5. Commit: fix: replace unwrap() calls with proper error handling

Acceptance Criteria

• Zero unwrap() calls in src/ (excluding tests)
• All errors propagate with meaningful context
• No new panics introduced
• All existing tests pass

[drips-wave]

This issue has been added to the Stellar Wave Program and is worth 200 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

[midenotch]

@midenotch has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Based on your request I will Replace All unwrap() Calls with Proper Error Handling accroding to the issues description to match the acceptance requirement

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

[EbukaMoses]

@EbukaMoses has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hello Maintainer,

I’d like to apply to work on this issue.

I’m Ebuka Moses, a full-stack and blockchain developer with experience building, testing, and maintaining smart contracts, particularly using Rust and blockchain-based architectures. I’m comfortable working with contract logic, validation, access control, persistent storage, and event handling, and I always pay close attention to correctness, security, and edge cases.

I take time to fully understand the issue requirements before implementing a solution, and I ensure my work follows the project’s coding standards. I also write clear, well-tested code and submit clean pull requests with meaningful commits.

I’m confident I can deliver a solid solution that meets the acceptance criteria and adds value to the project.

Thank you for your consideration, and I look forward to contributing.

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

[Mmesolove]

@Mmesolove has applied to work on this issue as part of the Stellar Wave Program's 2nd wave.

Hi maintain I have read through the description and I can solve it, please assign to me.

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