[SC-01] Build backend Soroban bridge service — typed client for the AssetsUp contracts

[yusuftomilola]

Overview

AssetsUp ships extensive Soroban smart contracts (contracts/assetsup — registry, tokenization, dividends, voting, audit; plus maintenance and multisig contracts), but nothing connects to them. The Stellar SDK is installed in the backend and completely unused. This issue creates the single bridge service every other blockchain feature builds on.

What to Build

A StellarModule in backend/src/stellar/ exposing a SorobanService:

• Config from env: STELLAR_NETWORK (testnet/futurenet/mainnet), SOROBAN_RPC_URL, ASSETSUP_CONTRACT_ID, backend signing keypair (STELLAR_SECRET_KEY) for server-signed operations
• Core primitives: build → simulate → sign → send a contract invocation; read-only calls via simulation; decode XDR results into typed JS objects
• Typed wrappers for the first methods needed by [SC-02]: register_asset, asset getters, and the audit-log reads (contracts/assetsup/src/lib.rs / asset.rs / audit.rs define the entrypoints)
• Health: a startup check that logs contract reachability; graceful degradation — when Stellar env vars are absent, the module loads in "disabled" mode and dependents no-op (contributors without Stellar setup must be unaffected)
• Error mapping: contract errors (contracts/assetsup/src/error.rs) surfaced as typed exceptions

References

• Contract source: contracts/assetsup/src/
• Blocked by nothing on the web2 side; consumed by [SC-02], [SC-07], [SC-08]

Acceptance Criteria

• SorobanService invokes and reads the deployed testnet contract (document the deploy steps used for testing in the PR)
• Disabled mode: app boots and all features work with no Stellar env configured
• Contract errors map to typed, loggable exceptions
• At least register_asset and one read method wrapped and demonstrated

[eulami]

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

Hi. I'm very good at this. I will submit an efficient PR within 24 hours. Kindly assign it to me.

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

[Gyanee01]

@Gyanee01 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 closely aligns with my experience building role-based administrative workflows, form-heavy interfaces, validation logic, and state-driven frontend features. The combination of permission enforcement, server-validated financial values, mandatory reasoning, and immediate ledger updates makes this a particularly interesting workflow to implement carefully.

I have worked on similar frontend features where users with different roles have access to different actions and where sensitive operations require explicit confirmation before being submitted. I’m comfortable working with React/TypeScript applications, integrating forms with backend APIs, handling asynchronous mutations, and making sure the UI does not treat client-side values as authoritative. For this issue, I would first understand the existing permission and API patterns in the repository, then implement the waiver and adjustment forms around those conventions rather than introducing a separate approach.

I can cover both full and partial waivers, mandatory reason validation, review/confirmation before submission, server-side amount validation, and appropriate feedback for loading, success, and failure states. I would also make sure unauthorized users cannot reach or trigger the workflow through either the UI controls or routing. After a successful operation, the relevant ledger data should update immediately without requiring users to manually refresh the page.

I’m also comfortable adding automated tests around the most important interaction and permission boundaries, including authorized versus unauthorized users, invalid amounts, missing reasons, successful submissions, and failed requests. My goal would be to deliver the feature in a way that fits naturally into the existing ChainVerse frontend architecture while keeping the workflow predictable, accessible, responsive, and easy to maintain.

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

[authenticeasy-sys]

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

I'd like to work on this.

AssetsUp ships extensive Soroban smart contracts (contracts/assetsup — registry, tokenization, dividends, voting, audit; plus maintenance and multisig contracts), but nothing connects to them. The Stellar SDK is installed in the backend and completely unused.

I'll make sure each of these is covered:

• SorobanService invokes and reads the deployed testnet contract (document the deploy steps used for testing in the PR)
• Disabled mode: app boots and all features work with no Stellar env configured
• Contract errors map to typed, loggable exceptions
• At least register_asset and one read method wrapped and demonstrated

I'll keep the change focused and match the existing code conventions.

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

[drips-wave]

Congratulations, @authenticeasy-sys! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on August 31, 2026.

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

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox!

@authenticeasy-sys's PR #1364 was approved and merged by @yusuftomilola.

🏆 @authenticeasy-sys: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (675 total points). Track your full progress on GrantFox.

👏 Great work, @authenticeasy-sys! Keep contributing to DistinctCodes.

[drips-wave]

This issue has been completed by @authenticeasy-sys as part of the Stellar Wave Program's 8th Wave 🥳

😎 @authenticeasy-sys: 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.