# Litepaper

**Introduction**

Solido is building a modular, AI-powered DeFi engine that turns passive crypto assets into productive capital. Whether you are staking, borrowing, or farming, Solido replaces active management with intelligent, automated financial flows driven by code and real-time market signals.

Over time, Solido will become the base layer of liquidity automation on Supra, powering both protocol- and user-level activity. Through a network of interconnected strategies, vaults, and stable primitives, Solido will serve as the backbone of Supra’s AutoFi stack, delivering composable infrastructure for the next generation of apps, DAOs, and institutions.

**Architectural Pillar**

<details>

<summary>Always-On Liquidity</summary>

Solido aims to create perpetual liquidity loops where users can stake, borrow, and reallocate capital across Supra’s ecosystem without ever having to exit the system. Think: mint $CASH, earn in Grow, auto-loop yield into Flow, and repeat — all with built-in risk parameters and real-time rebalancing.

</details>

<details>

<summary>AI-Native Automation</summary>

Solido vaults will operate as intelligent liquidity engines, reacting to volatility, liquidation signals, and yield differentials across the network. Over time, these AI-driven vaults will act as **DeFi co-pilots,** deploying funds based on optimal strategy profiles without requiring user input.

</details>

<details>

<summary>Modular DeFi Infrastructure</summary>

Every primitive in Solido (Flow, Cash, or Grow) is designed to be a Lego block. Developers, protocols, and DAOs can use Solido as middleware to plug in native yield, collateral management, and stablecoin access, turning Solido into the liquidity API of Supra.

</details>

<details>

<summary>Credit-Native DeFi Economy</summary>

With $CASH as the native stablecoin, Solido isn't just enabling borrowing — it's building a credit layer where users and protocols can access liquidity with algorithmic risk pricing, yield-optimized repayments, and modular collateral types. $CASH becomes the default unit of account on Supra.

</details>

<details>

<summary>Decentralized Liquidity Intelligence</summary>

Long-term, Solido will evolve into a decentralized financial brain — learning from on-chain data, adjusting vault strategies in real time, and even enabling DAOs and communities to set preferences (e.g., risk appetite, duration, target returns).

</details>

**The Heart of AutoFi**

<details>

<summary>Flow = Plug-and-Play Liquid Staking</summary>

Liquid staking becomes the first step in AutoFi, transforming idle tokens into productive collateral. With native integration into Supra’s staking mechanisms, Solido Flow sets the foundation for trustless yield and capital efficiency across the chain.

</details>

<details>

<summary>Cash = Credit as a Primitive</summary>

Solido Cash enables anyone to mint $CASH — a decentralized stablecoin — against SUPRA, BTC, and other collaterals. This is the **credit engine of AutoFi**, where real-time borrowing, loop strategies, and automated debt management replace legacy CDP systems.

</details>

<details>

<summary>Grow = Intelligence-Driven Yield Layer</summary>

Grow is where AutoFi truly shines. Vaults dynamically move user liquidity to wherever it earns the most — lending pools, stable pairs, or Stability Vaults — based on price action, liquidation needs, and protocol demand. It's DeFi with a brain.

</details>

<details>

<summary>Bytes, Blocks, and Beyond</summary>

Solido’s on-chain activity feeds back into Supra’s AutoFi data loop, turning real-time user behavior into signals for smarter liquidity routing, governance, and vault optimization.

</details>


---

# 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://solido-money.gitbook.io/solido/litepaper.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.