Dependency Health Monitor (Oracle, Bridge, Price Feed)

WHAT IT DOES Dependency Health Monitor (Oracle, Bridge, Price Feed) helps you track the health of critical DeFi dependencies. It checks oracles, bridge contracts, and price feed aggregators by calling their view functions and validating the responses. For each dependency you add, the tool fetches the current state, evaluates it against custom conditions you define, and reports whether the dependency is healthy or unhealthy. This is essential for DeFi protocols that rely on Chainlink price feeds, cross-chain bridges like LayerZero or Axelar, or any external contract that your application depends on. The tool displays a health score, shows detailed results for each check, and helps you quickly identify which dependencies are failing or returning unexpected values. It's designed for protocol operators, DeFi developers, and security researchers who need to ensure their application's critical external contracts are operational. HOW TO USE Connect your wallet to access the EVM network. For each dependency you want to monitor, enter the contract address, a description, select the dependency type (Oracle, Bridge, or Other), and enter the function signature to check—for example, "latestRoundData()" for Chainlink or "getPrice()" for a custom oracle. Optionally, add an expected condition like "> 1000000" or "!= 0" to validate the return value. Click "Add Dependency" for each contract, then click "Run Health Monitor." The tool sequentially processes each check by calling the function, evaluating the condition if provided, and reporting the result. Results are displayed in a summary dashboard showing total dependencies, healthy/unhealthy counts, and an overall health score. Each individual check shows the address, function signature, return value, health status, and response time in milliseconds. You can remove dependencies at any time and re-run checks as needed. THE REAL MECHANISM The tool uses direct eth_call RPC requests to the connected EVM node. For each dependency, it first calls eth_getCode to verify that a contract exists at the address. It then builds an ethers.js Interface from the function signature and encodes the call using encodeFunctionData. The tool sends an eth_call, which executes the function in the context of the current block without modifying state. If the call succeeds, the tool decodes the return value using decodeFunctionResult. If a condition is specified, the tool parses it—supporting operators like >, =,