> For the complete documentation index, see [llms.txt](https://riskguard-1.gitbook.io/riskguard-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://riskguard-1.gitbook.io/riskguard-docs/whitepaper/01-the-problem.md).

# 1. The Problem

> Every DeFi investor knows where their money is. Almost none of them know how dangerous it is.

Decentralized finance has matured into a multi-chain landscape holding tens of billions of dollars in user assets. Yet the tooling available to the everyday investor has not kept pace with the risks. Portfolio trackers like DeBank, Zerion, and Zapper answer a single question well: *where are my assets?* They render balances, positions, and token lists across protocols. But they remain silent on the question that actually determines whether an investor keeps their money: **how much risk am I carrying, and what should I do about it?**

This gap is not academic. In 2025, DeFi protocols lost more than three billion dollars to exploits, hacks, and economic attacks — a figure that rose roughly forty percent year over year. The first quarter of 2025 alone was the worst three-month period in the industry's history. Behind each of these headline numbers are thousands of individual investors who held positions in affected protocols and had no warning, no risk signal, and no clear sense of their exposure until it was too late.

## Three structural failures in current tooling

### 1. Balances are not risk

Knowing that a wallet holds a position in a lending protocol says nothing about the smart-contract risk of that protocol, the liquidity depth backing the position, the degree of admin-key centralization, or the market conditions that could unwind it. A portfolio that looks healthy by dollar value can be acutely fragile. Existing dashboards display the dollar value and stop there.

### 2. Solana is underserved

The dominant risk and analytics tools were built EVM-first. Solana — now one of the most active DeFi ecosystems — is either unsupported or treated as an afterthought. The protocols where Solana users actually deploy capital, such as Kamino, Jupiter, Raydium, and Orca, use position architectures that off-the-shelf trackers fail to detect at all. An investor cannot assess risk on positions a tool cannot even see.

### 3. Risk intelligence is locked behind institutional pricing

Where sophisticated risk analytics do exist, they are priced for funds and institutions. Platforms aimed at professional analysts begin at tens of dollars per month and climb into four figures, with interfaces designed for full-time analysts rather than the retail investor managing their own capital. The investor who most needs an accessible risk signal is the one least served by the market.

{% hint style="info" %}
**The core insight.** The DeFi market has comprehensive tools for *tracking* assets and institutional-grade tools for *analyzing* them — but nothing that gives the everyday multi-chain investor an honest, actionable risk signal across their entire portfolio, including the Solana positions other tools cannot detect.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://riskguard-1.gitbook.io/riskguard-docs/whitepaper/01-the-problem.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.