# Why NODO?

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXdlOdsK_zPcVWZTsqHjnxtX33o5tB8SuGEi-LwLGbKdCnPu16FTPRaJB8e0VM8hwhVlkKwWhdDpZeONhF8wkCJtk56eOwHw-tg8n45b4ViyX6nWjU30cx_a_vHkhi_jfVU8RrAKVg?key=7-HNZ3Di6QYq9DVX1rUt1w" alt=""><figcaption></figcaption></figure>

#### The Problem

#### Decentralised finance has made remarkable strides, but liquidity provisioning remains plagued by inefficiencies. Most vaults operate on static strategies, leaving users exposed to impermanent loss, volatility, and low capital efficiency. Market making is still largely manual and reactive, failing to keep up with real-time market shifts. Meanwhile, token projects struggle to bootstrap liquidity without resorting to unsustainable token emissions, and market makers lack access to scalable, risk-mitigated infrastructure.

#### The NODO Advantage

NODO differentiates itself from competitors through its fully integrated, AI-driven liquidity management solution. Unlike many competing vaults that provide isolated or limited AI functionality, NODO combines sophisticated real-time rebalancing, intelligent automated exit strategies, multi-collateral flexibility, and comprehensive risk management within a single product.

Notably, NODO uniquely offers:

* Integrated impermanent loss (IL) protection for volatile pairs involving USDC.
* Customizable cooldown periods for optimal and risk-sensitive exits.
* Stable BTC pair coverage for conservative, yet profitable, LP positions.<br>

Supported by over $2 million in live LP commitments, NODO is a proven, market-tested yield engine tailored explicitly for volatile, dynamic market environments.


---

# 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.nodo.xyz/public/introduction-and-overview/why-nodo.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.