The problem Chainguard solves

DeFi participants face significant information asymmetry when evaluating protocol risks, with critical data dispersed across fragmented sources including GitHub repositories, governance forums, audit reports, and social platforms. This fragmentation creates substantial barriers to informed decision-making and exposes users to preventable financial risks.

Current Market Challenges:
Information Fragmentation - Risk assessment requires manual aggregation of data from numerous disparate sources, each with varying formats, update frequencies, and reliability standards. This process is resource-intensive and often incomplete.
System Obsolescence - Existing risk assessment tools fail when protocols migrate infrastructure, deprecate data endpoints, or modify technical architecture, leaving users with outdated intelligence during critical decision windows.
Technical Complexity Barriers - Comprehensive risk evaluation demands specialized expertise in smart contract security, governance structures, and economic models

What People Can Use It For
🏦 Institutional Users:

Treasury Risk Management: Assess protocols before deploying institutional capital
Portfolio Diversification: Understand correlation risks across DeFi positions
Compliance Reporting: Generate comprehensive risk assessments with natural language explanations

👤 Retail Investors:

Investment Due Diligence: Get clear, actionable risk insights before interacting with protocols
Portfolio Monitoring: Receive proactive alerts about emerging risks in existing positions
Educational Guidance: Learn about DeFi risks through conversational explanations

🔧 Developers & Protocols:

Competitive Analysis: Benchmark security and governance practices against peers
Risk Monitoring: Track community sentiment and governance health
Integration: Access real-time risk scores via APIs and on-chain oracles

Challenges we ran into

One of the main challenges I encountered was integrating Chainlink Functions to make reliable offchain data calls from within a smart contract. While the Chainlink Functions product abstracts much of the complexity, ensuring seamless communication between the onchain and offchain environments required:

Careful configuration of secrets and APIs: Passing authenticated headers or API keys securely using the Chainlink Functions secrets manager introduced a new layer of complexity.

Timeout and gas constraints: Some API responses were too large or slow, which led to function timeouts or excessive gas costs. I had to optimize both the off