Performance: Implement Lazy Loading for Contract ABIs and Chain Data

[Smartdevs17]

Context

The frontend bundle includes ABI definitions for all deployed contracts, even those rarely used. This inflates bundle size and increases load time.

Current Limitation/Problem

All contract ABIs (Soroban + EVM) are bundled eagerly. For a merchant using only Stellar, EVM ABIs are unnecessary payload. Similarly, chain configuration data is loaded upfront.

Expected Outcome

Dynamic lazy loading of contract ABIs and chain metadata based on user context (connected chains, active features). ABIs are fetched only when needed.

Acceptance Criteria

• Split ABI files into per-chain, per-contract chunks
• Lazy-load ABIs when user interacts with a specific chain
• Cache loaded ABIs in IndexedDB for repeat visits
• Chain configuration data (RPC URLs, explorer URLs, token lists) loaded on demand
• Loading states for ABI-dependent operations
• Fallback: static ABI bundle for offline use
• Bundle size: conditionally loaded ABIs reduce initial JS by 200KB+
• Network: ABI chunks are cacheable with long max-age

Technical Scope

• frontend/src/lib/contracts/abi-loader.ts - dynamic ABI loader
• Code splitting: per-chain ABI entry points
• IndexedDB caching for ABIs
• frontend/src/hooks/useContract.ts - lazy ABI loading hook
• Webpack chunk configuration for ABI files
• Edge cases: ABI version mismatch, loading failures, concurrent chain switching

[opepraise]

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

Hello Maintainer, I can work on this issue.

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

[drips-wave]

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

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

[drips-wave]

This issue has been completed by @opepraise as part of the Stellar Wave Program's 6th Wave 🥳

😎 @opepraise: You earned 200 Points for completing this issue! After the current Wave ends, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here. You can also Leave a review to share your experience working on this issue.

🧑‍💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.