# Technical Docs

Navi's offering includes a decentralized liquidity protocol. It allows users to lend and borrow cryptocurrency assets without intermediaries, using a shared liquidity pool system.

Navi's liquidity pools are created for each supported asset, and users can deposit their assets into these pools. They receive Navi receipt tokens in return, which represent their share of the pool (i.e. nSUI). These tokens can be used as collateral to borrow other assets from the pool. The collateralization ratio determines the amount that can be borrowed, and it is adjusted dynamically based on supply and demand. More in-depth information can be found in [Technical Reference](broken://pages/5cDE25HF3GtAu5yJCbtW).

Navi has a governance system that allows Navi token holders to vote on proposals and changes to the protocol. This includes setting interest rates, adding new assets to the protocol, and changing the collateralization ratio. Check out the [Tokenomics](https://navi-protocols-organization.gitbook.io/navi-tokenomics/) page for an overview of the Tokenomics.&#x20;

Overall, Navi's architecture provides a decentralized and efficient way for users to lend and borrow assets, without the need for traditional financial intermediaries.

In the following pages, we'll go in depth into how the NAVI liquidity protocol works in all its aspects, from high-level mechanics to granular risk management features we've implemented


---

# 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.naviprotocol.io/technical/technical-docs.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.
