[Backend] sorobanService: drop second TransactionBuilder/Account/Networks import inside simulateContractCall

[ogazboiz]

Join the discussion on Telegram

Why this matters

backend/src/services/sorobanService.ts line 52 does a dynamic await import('@stellar/stellar-sdk') to destructure TransactionBuilder, Account, Networks:

const { TransactionBuilder, Account, Networks } = await import('@stellar/stellar-sdk');

But all three names are already statically imported at the top of the file (line 1):

import { rpc, xdr, StrKey, Contract, nativeToScVal, Keypair, TransactionBuilder, Account, Networks } from '@stellar/stellar-sdk';

The dynamic import is dead and shadows the static names. Every call to simulateContractCall pays the cost of a redundant import resolution.

Acceptance criteria

• Delete line 52
• Confirm the function still type-checks (it uses the top-level imports already)
• No behavior change

Files to touch

• backend/src/services/sorobanService.ts (line 52)

Out of scope

• Refactoring pauseStream/resumeStream/withdraw which also dynamic-import Address (separate issue would be to do the same cleanup there if Address were already statically imported — it currently isn't)

[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.

[samjay8]

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

Hello Chief, please can I handle this for you?

ℹ️ Repo Maintainers: To accept this application, review their application or assign @samjay8 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 🌊