[Backend] sorobanService.decodeAddress uses 'addr.contractId() as any' cast

[ogazboiz]

Join the discussion on Telegram

Why this matters

backend/src/services/sorobanService.ts line 36:

return StrKey.encodeContract(Buffer.from(addr.contractId() as any));

And the identical pattern in backend/src/workers/soroban-event-worker.ts line 55. The as any cast hides a real type mismatch between the SDK's Hash opaque and Node's Buffer. The SDK exposes proper helpers — StrKey.encodeContract accepts the hash buffer directly in recent SDK versions, or the buffer can be obtained without any via Buffer.from(hash.value as Uint8Array) or hash.value as Uint8Array.

Acceptance criteria

• Remove the as any in both files and use the correct typed source for the contract hash bytes
• Build passes; runtime decoding still produces a valid C... address (the existing decode test should cover this)

Files to touch

• backend/src/services/sorobanService.ts (line 36)
• backend/src/workers/soroban-event-worker.ts (line 55)

Out of scope

• Replacing the manual decoders with the SDK's higher-level scValToNative

[EbukaMoses]

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

[drips-wave]

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

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