Optimizing multi-chain data fetching for an EVM wallet tracker without requiring wallet connection. How do you handle RPC and API latency?

Post original

Hey everyone, I’ve been working on a mobile companion app (HappyWick) and recently added a read-only EVM wallet tracker.. The core idea was to let users monitor their balances across multiple networks (Ethereum, Base, Arbitrum, Optimism, Polygon, Ink, Linea, zkSync) without forcing them to connect their wallets or expose private keys just pure public address scraping.. While the UX feels smooth, I'm hitting some technical crossroads regarding data aggregation and would love to get some feedback from fellow devs here: -Multi-chain Aggregation & API Infrastructure: Right now, I am leveraging the Blockscout API to aggregate and fetch these multi-chain balances. While it’s an amazing open-source tool, querying 9 different networks simultaneously can sometimes hit latency bottlenecks on the initial load. If you've used Blockscout for multi-chain setups, how do you handle caching, or did you have to transition to custom indexing (like The Graph protocol or commercial node clusters) as you scaled? -UI/UX for L2s: With so many Layer 2s coming out (just added Ink recently), the mobile UI can get cluttered quickly. How do you prefer to see multi-chain breakdowns? Aggregated total first, or strictly separated by networks? Looking forward to hearing how you guys handle multi-chain data aggregation and caching! https://preview.redd.it/c2f53upv3g5h1.png?width=463&format=png&auto=webp&s=9c10adec22b8766a4d4e101e48971632522a5f82   submitted by   /u/MedenicaDarko [link]   [comments]