I have a small cryptocurrency app that reads live Ethereum transactions and renders them in a web interface. The core functionality is there, but I’m stuck on persistent connection issues—messages such as “provider not found”, dropped WebSocket sessions, and intermittent time-outs when I call getTransaction and getBlock via Web3.js/ethers.js. Your first task is a clean bug-fix pass: trace the exact cause of the connection failures, stabilise the RPC/WebSocket flow (I’m using an Infura endpoint but can swap to Alchemy or a self-hosted node if needed), and confirm that transactions stream reliably to the front end without manual refreshes. Once the connection layer is rock-solid, I’d like a quick review of the way the data is parsed and displayed so blocks, hashes, gas and timestamps appear in the right order. No new features are required right now—just make the existing code run flawlessly on Ethereum mainnet and, as a bonus, Ropsten or Goerli. Deliverables • Fixed source code with clear comments highlighting each change • A short README telling me how to start the project, set environment variables, and switch endpoints • Proof it works: screen-capture or log output showing at least 50 consecutive blocks streaming with zero disconnects If you’ve debugged Web3 connection woes before, this should be straightforward. Let me know your estimated turnaround and the tools you prefer (Hardhat, Truffle, plain Node, etc.).