Multi-Chain Debt Position Aggregator-and-Health-Monitor

WHAT IT DOES This tool connects to your EVM wallet and scans multiple lending protocols—including Aave, Compound, MakerDAO, and others—across different EVM chains. For each protocol you configure, it reads your collateral balances, borrowed amounts, liquidation thresholds, loan-to-value ratios, and health factors. The tool aggregates this data into a unified dashboard showing your total collateral, total debt, and overall health across all positions. Each position is displayed with a visual health bar and risk indicators (green for safe, amber for caution, red for risk of liquidation). HOW TO USE Connect your Web3 wallet using the Connect button. The tool will automatically detect your connected wallet address and pre-fill the address field, but you can also enter any address to monitor. In the Protocol Configurations textarea, enter each lending protocol you want to scan in the format name:contract_address:chain_id—one per line. For example, "Aave:0x7d2768dE32b0b80b7a3454c06BdAc94A69DDc7A9:1" for Aave on Ethereum mainnet or "Compound:0x3d9819210A31b4961b30EF54bE2aeD79B9c9Cd3B:1" for Compound. Click "Scan Positions" to fetch all debt positions. Results appear in the Results card with a summary of total collateral, total debt, overall health factor, and a detailed list of each position with individual risk indicators. TECHNICAL MECHANISM: ADAPTIVE PROTOCOL ABI DETECTION The tool uses ethers.js to interact with lending protocol contracts. It attempts multiple standard ABI patterns common across DeFi protocols. First, it calls getUserAccountData(address) which returns total collateral, total debt, available borrows, liquidation threshold, LTV, and health factor—used by Aave and similar protocols. If that fails, it falls back to getAccountLiquidity(address) used by Compound and forks. As a third fallback, it tries getCollateralBalance and getBorrowBalance for simpler implementations. Each protocol configuration specifies the contract address and chain ID, allowing the tool to query positions across multiple chains using the same connected provider. Health factors are parsed as BigNumber and converted to human-readable values, with thresholds applied: >1.5 is safe, 1.05–1.5 is cautious, and