Tree-shaking audit + per-chain bundle size budget

[truthixify]

Labels: Stellar Wave, stellar, perf, audit, drips, help-wanted
Tier: M (2–4 days)
Type: perf / audit

Context

The SDK ships subpath exports per chain so consumers can import only what they need. In theory, a consumer who only uses @wraith-protocol/sdk/chains/stellar should not pay the bundle cost of EVM, Solana, or CKB code. In practice, we've never verified this. Shared utility files, accidental cross-imports between chains, and noble-curves' multi-curve bundles could be silently leaking unused code into every consumer's bundle.

Scope

1. Measure per-entry bundle sizes — for each of index, chains/evm, chains/stellar, chains/solana, chains/ckb, build a minimal consumer (one import { something } from '@wraith-protocol/sdk/chains/X') and measure the resulting bundle with both Vite and esbuild.
2. Visualize the dependency graph — run rollup-plugin-visualizer or esbuild-analyzer and identify any non-obvious crossover (e.g., Stellar code being pulled into a CKB-only consumer).
3. Set per-entry budgets in package.json:

   {
     "size-limit": [
       { "path": "dist/chains/stellar/*", "limit": "40 KB" },
       { "path": "dist/chains/evm/*", "limit": "35 KB" },
       ...
     ]
   }

4. CI gate — fail the PR if any entry exceeds budget.
5. Optimization pass — fix any unintended crossovers; document the ones that are necessary (e.g., Solana legitimately re-exports Stellar's scalar math).

Where crossover is expected

• chains/solana re-uses chains/stellar crypto. That's intentional and should be measured + budgeted accordingly.
• chains/ckb re-uses chains/evm keys. Same story.

Crossover that is NOT expected:

• chains/evm accidentally importing from chains/stellar.
• A shared utils/ module that pulls in chain-specific code via import * as.

Acceptance criteria

• Bundle sizes per entry measured and committed in BUNDLE_SIZE.md.
• Per-entry budgets in CI via size-limit or equivalent.
• Visualizer output committed (PNG or HTML) so future contributors can see the breakdown.
• At least one identified optimization landed.
• PR description includes a before/after table.

Why this matters

Frontend consumers (the demo, the console, any third-party integrator's web app) directly feel SDK bundle size. A 50 KB savings on the Stellar entry is a measurable LCP improvement for every user of every Wraith-powered site.

Resources

• size-limit package: https://github.com/ai/size-limit
• Rollup visualizer: https://github.com/btd/rollup-plugin-visualizer

[JafetCHVDev]

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

Hello Team,

My Background

My name is Cristian, and I’m a passionate full-stack developer from Costa Rica 🇨🇷💻. I’m excited about the opportunity to contribute to your Stellar-based project during Drips Wave! 🌊
I enjoy building web applications that combine clean user interfaces with solid back-end logic and reliable databases.

Experience

I have experience developing web applications using technologies such as React, .NET Core, SQL Server, and Firebase. I’ve worked on projects that include role-based systems, CRUD platforms, booking systems, and data-driven web apps.
While I’m still growing in Web3 and blockchain, I’m highly motivated to learn and apply these technologies, especially within the Stellar ecosystem.

I’m driven by the opportunity to improve my skills, collaborate with a talented team, and make a meaningful contribution to your project.

Links

You can find my profiles and links here:

GitHub: https://github.com/JafetCHVDev

Thank you for considering my candidacy. I am excited about the opportunity to contribute to this project and create a positive impact. Please let me know if you have any questions or need additional information.

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

[israelolrunfemi]

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

Hi, I’d like to work on this issue.

My approach would be to treat this as a reproducible bundle-audit + optimization task instead of changing imports blindly.

I’ll first create minimal consumer fixtures for each SDK entrypoint (index, chains/evm, chains/stellar, chains/solana, chains/ckb) and measure bundle output using both Vite and esbuild. This should verify whether importing a single chain subpath accidentally pulls unrelated chain code into the consumer bundle.

I’ll add bundle analysis tooling using size-limit, rollup-plugin-visualizer, and/or esbuild-analyzer depending on the repo’s current tooling conventions. The generated visualizer output (HTML/PNG) will be committed so future contributors can inspect dependency crossover easily.

I’ll document all measurements in BUNDLE_SIZE.md with a before/after table and notes explaining intentional reuse paths such as:

chains/solana reusing Stellar crypto
chains/ckb reusing EVM keys

I’ll specifically audit for unintended crossover such as:

• chains/evm importing Stellar code
• shared utility modules accidentally importing chain-specific implementations
• import * as patterns preventing tree-shaking
• noble-curves imports pulling unnecessary curves

I’ll then add per-entry size budgets via size-limit and wire them into CI so PRs fail on regressions.

After generating the dependency graphs, I’ll land at least one concrete optimization if unnecessary bundle crossover exists, while keeping the changes conservative and aligned with the existing file structure, build system, lint rules, and export conventions.

Before opening the PR I’ll validate with build, typecheck, lint, test, and bundle-size analysis runs to ensure the implementation is stable and reviewable.

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

[drips-wave]

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

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