Alvin Lang
Feb 24, 2026 15:12
Stellar (XLM)’s Freighter browser wallet cuts initial load time to 1.27 seconds through aggressive caching, batch fetching, and smarter asset icon loading.
Stellar (XLM)’s Freighter browser extension wallet now loads in 1.27 seconds after a multi-week optimization effort that cut startup times by 63%, according to a technical breakdown published by the development team on February 23.
The improvements target a persistent pain point for crypto wallet users: waiting for balances and transaction history to appear. For traders who need quick access during volatile market conditions, every second matters.
What Actually Changed
The Freighter team identified external API calls as the primary bottleneck. The wallet was previously fetching account balances, transaction history, asset icons, and multiple data streams simultaneously at startup—forcing users to wait for everything before seeing anything.
The fix? Load only account balances initially, then fetch everything else in the background. Transaction history, asset lists, and icons now load asynchronously after the main interface renders. This data gets cached, so navigating to the History tab pulls from local storage rather than triggering fresh API calls.
The Asset Icon Problem
One particularly inefficient process involved loading asset icons. The old method required three separate network roundtrips per asset: first fetching the issuer’s account from Horizon, then loading the associated TOML file, then finally grabbing the icon URL. Multiply that by every token in a user’s wallet.
The new approach checks asset lists first—since popular Stellar tokens are already catalogued—and only falls back to the multi-step process when necessary. Even then, the team switched to Stellar RPC’s ledger entries endpoint, which returns multiple asset issuers in a single call instead of iterating through them individually.
Aggressive Caching Strategy
The wallet now caches essentially everything until the user closes it, with a three-minute staleness threshold triggering automatic refreshes. Actions that obviously invalidate cached data—sending payments, adding trustlines—trigger immediate re-fetches rather than waiting for the timer.
For transaction history specifically, the team implemented batch fetching to avoid redundant lookups. Users frequently interact with the same Soroban contracts multiple times; caching contract data during the first encounter eliminates duplicate API calls when processing subsequent transactions.
Why This Matters
Browser extension performance remains a competitive differentiator as wallet options multiply. Research into extension optimization through 2026 emphasizes that content scripts running unnecessary code directly impact perceived speed—exactly what Freighter addressed by deferring non-critical loads.
The 1.27-second target puts Freighter in reasonable territory for browser extensions, though users on slower connections or with extensive transaction histories may still experience longer waits. The caching improvements should compound over time as more data gets stored locally.
Stellar’s native token XLM continues trading amid broader market conditions, with the wallet improvements potentially reducing friction for users actively managing positions on the network.
Image source: Shutterstock
Credit: Source link
