Tree-shaking audit + bundle size budget for Stellar entry

[truthixify]

Tier: M (2-4 days) Type: perf / audit

Context

The chains/stellar subpath export should let consumers bundle only the Stellar code without pulling in shared utility files or unused exports. Today we have no measurements.

Scope

• Measure the Stellar entry's bundle size against both Vite and esbuild
• Visualize the dependency graph via rollup-plugin-visualizer
• Set a Stellar bundle size budget in package.json using size-limit
• CI gate fails on budget overage
• Identify and fix any accidental imports that pull non-Stellar code into the Stellar entry

Acceptance criteria

• BUNDLE_SIZE.md baseline for the Stellar entry
• size-limit config with Stellar budget
• CI gate
• At least one identified optimization landed (or documented as already-tight)

Files to start with

• sdk/package.json
• tsup.config.ts
• src/chains/stellar/index.ts

[Theraxia]

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

hi, i would like to work on this issue, thanks

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

[Timrossid]

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

Hi, I just reviewed the issue description and I will like to work on this issue. I’m a full-stack developer and Smart contract expert, I have previously contributed to multiple open-source projects. Please assign this issue to me! I can have a PR ready for review in a few hours.

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

[drips-wave]

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

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

[truthixify]

@Theraxia Assigned. Welcome to wave 6.

Quick expectations to make this smooth for both sides:

1. Branch from develop (not main). PRs target develop.
2. Open a draft PR within ~3 days of pickup so we can see direction early.
3. Update at least every 5 days. If you get stuck or context changes, just say so on the PR — silence is the only thing that costs you the assignment.
4. Read the issue body's acceptance criteria carefully. Hitting those is the merge bar.

If anything is ambiguous, ask before building. Looking forward to the PR.