[SC-79] assetsup's error.rs completeness vs. contrib's error.rs needs a cross-check

[yusuftomilola]

Overview

assetsup and contrib maintain separate Error enums (per contrib's own doc comment: "Several module names appear in both... but the implementations have diverged and are not interchangeable") — worth a direct audit that assetsup's error enum has equivalent coverage to what [SC-58]/[SC-59]/[SC-60] are about to require of the other three crates, so this cleanup doesn't leave assetsup as the one crate that was never checked.

Tasks

• Run the same .unwrap()/.expect() audit already done for multisig-wallet/contrib/asset-maintenance ([SC-58]/[SC-59]/[SC-60]) against assetsup/src/*.rs (excluding tests/) — the earlier repo-wide grep found only 2 hits there, but confirm those 2 are legitimately safe (e.g. genuinely-unreachable Options) rather than another real gap.
• Document the finding either way so this crate isn't silently skipped while its siblings get fixed.

Acceptance Criteria

• assetsup's remaining .unwrap()/.expect() call sites (if any) are explicitly reviewed and either justified or fixed, not just assumed fine because the count is low.

Dependencies

Companion audit to [SC-58]/[SC-59]/[SC-60].

Notes for Contributors

Requires Rust + Soroban. Workspace: contracts/ (soroban-sdk 23, members: assetsup, contrib, multisig-wallet, multisig-transfer, asset-maintenance). Run cargo test --all, cargo fmt --all -- --check, and cargo clippy --all-targets --all-features -- -D warnings before opening a PR — CI enforces all three. Comment below to be assigned.

[cyberdocs120]

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

I’d like to work on this issue because it addresses an important area of the project and presents a great opportunity to make a meaningful contribution. I’m particularly interested in delivering a solution that is reliable, maintainable, and aligned with the project’s existing architecture and development standards.

I have experience working across software development, including backend and frontend development, APIs, databases, testing, DevOps, and blockchain-based applications. I’m comfortable understanding existing codebases, identifying the root cause of issues, implementing clean and scalable solutions, and writing thorough tests to prevent regressions.

My approach would be to first understand the existing implementation and project conventions, then develop the solution in a focused and incremental way. I’ll ensure the changes are well-tested, documented where necessary, and do not introduce unnecessary complexity or break existing functionality. I’m also committed to clear communication, responding to review feedback, and delivering a polished contribution that provides real value to the project.

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

[Trusty08]

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

Hi maintainer, please I'll love to work on this issue please assign it to me.

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

[biggold10]

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

I’d be happy to take this issue. I’ve looked through the requirements and have a plan for approaching the implementation. I’ll investigate the existing code and dependencies, make the required changes, verify the behaviour with tests, and provide a concise PR explaining what was changed. I can start immediately and will communicate any blockers during development.

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

[Johnjnr1]

@Johnjnr1 has applied to work on this issue as part of the Stellar Wave Program's 8th 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.

[Tekh134]

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

Hi maintainer! Good to be back
I’ve contributed here before with merged PRs.
Can I take up issue ? please assign me. thank you .

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

[NeduTheDev1]

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

Please assign to me maintainer I can handle with ease

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

[retkatmun]

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

Hi Maintainer,

I’m a smart contract and full-stack developer and would love to contribute to this issue. I’m an experienced contributor with hands-on expertise in Rust, Soroban, Cairo, and TypeScript.

I’m passionate about building secure, scalable blockchain solutions, with a strong emphasis on writing clean and maintainable code. Based on the scope of this issue, I’m confident I can deliver a complete solution within 24 hours of assignment.

I’d greatly appreciate the opportunity to contribute and help move this forward.

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

[Dhivine-stack]

@Dhivine-stack has applied to work on this issue as part of the Stellar Wave Program's 8th wave.

Hello Maintainer, I've reviewed the issue and understand what's required. I have a clear approach for implementing the change while keeping it consistent with the existing codebase. I'd be glad to take this on.

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

[blurbeast]

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

hello my Boss, can i work on this please ??

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

[akansmafengadamu]

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

Hello maintainer
I would love to contribute to this Issue and I assure you the best result which matches your expectation

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