[Backend] Drop unused 'stellar-sdk' dependency — code only imports '@stellar/stellar-sdk'

[ogazboiz]

Join the discussion on Telegram

Why this matters

backend/package.json declares two Stellar SDK packages:

\"@stellar/stellar-sdk\": \"^14.5.0\",
...
\"stellar-sdk\": \"^13.3.0\",

But no source file under backend/src imports from stellar-sdk — every import uses @stellar/stellar-sdk. Confirmed by grep -rn \"from 'stellar-sdk'\" backend/src returning nothing.

This is a stale 30+ MB dependency that bloats install time and CI.

Acceptance criteria

• Remove stellar-sdk from backend/package.json (npm uninstall stellar-sdk)
• Confirm npm run build and npm test still pass

Files to touch

• backend/package.json
• package-lock.json (regenerated)

Out of scope

• Bumping @stellar/stellar-sdk itself

[Frontman-Code]

@Frontman-Code has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

I will love to work on this issue

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

[Godfrey-Delight]

@Godfrey-Delight has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer! I’d love to work on this issue if it’s still available. I have a good understanding of the requirements and would be happy to implement the solution. Thanks for considering my request!

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

[DeePrincipal-dev-lang]

@DeePrincipal-dev-lang has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Let me quickly take a look at the issue and fix what's to be fixed
I'm a professional prompt engineer and detailed oriented analyst

ℹ️ Repo Maintainers: To accept this application, review their application or assign @DeePrincipal-dev-lang to this issue.

[Banx17]

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

Please assign this issue to me, thanks.

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

[veemakama]

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

Hi, I would love to work on this

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

[CHASE3020]

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

I would love to work on the issue

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

[attyolu]

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

Good evening Maintainer. I would love to work on this issue quickly. Please assign to me. Thank you

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

[uche102]

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

Hi maintainer I would love to work on this

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

[NickiM84]

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

Hello, I'm a fullStack developer with years of experience, I have worked on several projects, can I please work on this

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

[Fury03]

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

Kindly assign boss

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

[Glam26]

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

I'd like to work on this issue.

I'm a returning contributor and have previously helped with dependency cleanup and backend maintenance tasks. This looks like a straightforward optimization that reduces install size and CI overhead without affecting runtime behavior.

My plan is to:

• Verify there are no remaining imports of stellar-sdk under backend/src (and check for any indirect usage outside the source tree if needed).
• Remove the unused stellar-sdk dependency from backend/package.json using the project's package manager.
• Regenerate the lockfile so package-lock.json stays in sync.
• Verify that only @stellar/stellar-sdk remains as the supported SDK dependency.
• Run the backend build and test suite (npm run build and npm test) to ensure there are no regressions after removing the package.
• Include the validation results and dependency diff in the PR for reviewers.

The scope will remain limited to dependency cleanup—I won't upgrade @stellar/stellar-sdk or make unrelated dependency changes.

If the issue is available, I'd be happy to take it. Thanks!

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