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

# Introduction

## Abstract

DeFunds Finance is a decentralized investment and credit infrastructure that bridges traditional hedge fund practices with on‑chain asset management and undercollateralized real‑world lending. Built on Solana, it provides two integrated layers:

1. DeFi Strategy Vaults: 100% on-chain, auditable smart contract vaults operated by managers, fee logic (including performance/high-water mark fees), and real-time analytics.
2. RWA Credit Pools: Tokenized, undercollateralized lending pools that channel on-chain capital to real-world use cases (e.g., cash flow, construction). With a reputation system, investors will choose to invest in people and receive yields from it.

&#x20;

Defunds enables:

* Retail and professional investors to allocate across diversified yield sources (on-chain strategies + real-economy).
* Traditional Web2 fund managers to migrate to Web3 using familiar fee structures and governance transparency.
* Shift from copy trading to unified model :  every pool participant enters and exits the same trades—wins and losses are shared proportionally.

·         Facilitates capital formation where on-chain liquidity meets off-chain real-world opportunities.

&#x20;

Audit will be made between Q4 2025 and Q1 2026


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://defunds-finance.gitbook.io/whitepaper/introduction.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
