# RiskDAO

We’re excited to announce the launch of [RiskDAO](https://riskdao.org/) — a service DAO spearheaded by [B.Protocol](https://www.bprotocol.org/) and [1kx](https://twitter.com/1kxnetwork) that will focus on providing a new, open-source risk assessment framework and associated audits to DeFi lending and borrowing protocols as well as L1 networks.

## Why RiskDAO? <a href="#id-930a" id="id-930a"></a>

Lending, borrowing, and CDP protocols account for over 30% of DeFi’s $110B total value locked. As a dominant sector in a rapidly growing industry, it’s important that we build open-source tools and resources to make protocols safer and the risks more clear for users. Risk DAO will aim to do just that.

Tens to hundreds of millions of dollars have been wiped out or put at risk due to economic exploits and/or mismanagement of borrowing protocols, further highlighting the need for objective third-party risk assessments and frequent monitoring.

Our new methodology takes into account real-world liquidation data of popular assets from centralized exchanges, along with the price trajectory of the assets in question. We extrapolate the liquidation sizes and price trajectory to the asset we wish to analyze, and simulate the outcome based on the asset’s available DeFi liquidity. This approach eliminates most of the assumptions that are usually made in risk assessments in the DeFi ecosystem regarding user behavior during market crashes and makes it more feasible to analyze the risk of a platform, including for multichain lending platforms, where the data for user behavior is even more sparse.

## Our Services <a href="#ebf6" id="ebf6"></a>

Here’s a summary of the services we’ll offer to DeFi protocols and L1s, all of which are rendered as one-time audits, with the potential for ongoing collaboration:

* Stress tests (e.g. bad debt likelihood, liquidation performance)
* Parameter optimization (e.g. collateral factor (MCR), liquidation penalty)
* Survey of collateral risks (e.g. price oracle strength, liquidity)
* Chain-specific analysis (e.g. liquidity propagation time, block time, and gas costs)

These various aspects of a borrowing system are analyzed through an in-house risk assessment model built by B. Protocol that’s outlined in depth [here](https://medium.com/b-protocol/data-extrapolation-framework-for-risk-assessment-of-defi-lending-platforms-290945d11cb7).

## Work With Us <a href="#id-29ee" id="id-29ee"></a>

Building a new project? Looking to make your protocol more robust? Reach out on [Twitter](https://twitter.com/Risk_DAO), [Telegram](https://t.me/koltenb), or [Discord](https://discord.gg/NYyeDQDDvM) and we’ll handle the rest!

If you’re still unsure, explore what we’ve built further by reading [*Data Extrapolation Framework for Risk Assessment of DeFi Lending Platforms*](https://medium.com/b-protocol/data-extrapolation-framework-for-risk-assessment-of-defi-lending-platforms-290945d11cb7) or the full report outlining our risk analysis framework [here](https://github.com/backstop-protocol/whitepaper/blob/master/Risk%20Analysis%20Framework.pdf).

## Join Us <a href="#id-4923" id="id-4923"></a>

Last, but not least, like any new DAO **we’re looking for talented individuals**. If you’re interested in math, risk analysis, data analytics, or becoming a researcher, [**join our Discord and fill out a membership request**](https://discord.gg/NYyeDQDDvM). Specifically, we’re looking for those with skills in:

• Technical Writing (academic experience is a plus)

• Designing and implementing mathematical models

• DeFi Security

• DeFi Research and Writing

• Data Analytics

<br>


---

# Agent Instructions: 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:

```
GET https://docs.bprotocol.org/riskdao.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
