> For the complete documentation index, see [llms.txt](https://docs.diversifi.trade/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.diversifi.trade/diversifi-platform.md).

# DiversiFi Platform

The DiversiFi app at **diversifi.trade** is the primary interface to the portfolio protocol.

It lets users build and allocate into **managed portfolio vaults**, receiving fungible **portfolio tokens (dTokens)** that can be held, traded, or used across DeFi.

You can either:

* start from **DiversiFi Strategies** (pre-built portfolios), or
* **build your own portfolio** with custom weights and rules.

***

### What users get

**1. DiversiFi Strategies**

DiversiFi ships a curated set of Strategies designed around concrete outcomes, not just narratives:

* **Boomer** – BTC / Gold / yield-bearing stable exposure
* **Big Four** – major L1s (e.g. BTC, ETH, BNB, SOL)
* **Yield Strategies** – diversified yield-bearing assets (e.g. SyrupUSDC and other yield stables)
* **Narrative Strategies** – DeFi, DePIN, Memecoins, RWAs, and others
* **Ecosystem Strategies** – e.g. BONK ecosystem basket

Each DiversiFi Strategy is backed by its own vault and dToken. Users deposit **USDC**, the vault swaps into the target allocation, and the protocol maintains the portfolio via rules-based rebalancing.

These Strategies are explicitly designed to **harvest volatility-driven premium** relative to static hold by rebalancing on drift, subject to fees and market conditions. Historical backtests suggest this can often improve outcomes, but future performance is not guaranteed.

**2. Build-your-own portfolios**

More advanced users can configure:

* the token set (up to a small number of assets)
* target weights
* rebalancing rules (e.g. drift thresholds)

Users still deposit **USDC**; the vault swaps into the chosen allocation and issues a dToken for that custom portfolio. The result is a vault + dToken fully aligned with the user’s view of the market, managed by the same automated engine.

***

### Who it is for

DiversiFi is designed for:

* **Web3 natives** who want their portfolios to **work while they sleep** instead of manually timing rebalances.
* **Long-term holders** who are tired of sitting in static positions and want a rules-based way to try to capture volatility premium on top of their core exposures.
* **Creators and power users** who want to package a thesis into a portfolio + dToken and share it with others.

The goal is not only to make things simple, but to give portfolios a realistic chance to do **better than static hold** over time, while staying fully on-chain and composable.

***

### How the app maps to the protocol

Under the hood, every action on the platform uses the same protocol primitives:

* Creating a DiversiFi Strategy or custom portfolio → deploys / configures a **vault**
* Depositing USDC → vault swaps into the target allocation and mints **dTokens** that represent ownership of that vault
* Withdrawing → burns dTokens and swaps back into USDC (or underlying assets where supported)
* Ongoing management → handled by the **automated rebalancing engine**

For a deeper dive into vaults, rebalancing, and pricing, see:

* [Vault system](/vault-system.md)
* [Auto Rebalancing](/auto-rebalancing.md)
* [dToken price calculation](/index-token-price-calculation.md)


---

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.diversifi.trade/diversifi-platform.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.