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

# Overview

## Step 1: RWA Tokenization

In the first step, RAAC helps RWA asset owners tokenize their assets onchain.

<details>

<summary>REET NFTs</summary>

RAAC tokenizes real estate by creating a REET NFT representing a contractual right to a specific property. REETs NFTs may be traded on third-party marketplaces and eligible holders may also redeem the NFT to exercise its contractual right to title to the off-chain real estate.&#x20;

</details>

<details>

<summary>iREET</summary>

The REET Index, or iREET, allows users to gain exposure to the performance of real estate markets without purchasing a full REET NFT.

</details>

<details>

<summary>RWf(x)</summary>

RWf(x) stablecoin silos operated by third parties allow RAAC to bring RWA assets on-chain. Each independent silo is a self‑contained vault that tokenizes a single asset class. Examples could include: gold, farmland, oil, data, water, etc.

Independent silos mint a branded stablecoin (e.g., pmUSD) against the asset.

</details>

## Step 2: Unlocking Yield

Once RWAs are tokenized, holders may unlock their latent liquidity and earn onchain yield.

<details>

<summary>RAACLend</summary>

REET NFTs and iREET tokens can be used as collateral to borrow crvUSD from the RAAC lending pool.

The interest rate for borrowers is soft-pegged to $$\frac{USPrimeRate}{2}$$, ensuring the rate for borrowers is always competitive. $RAAC emissions may be used to bolster the interest rate dependent on gauge votes directed by token holders. Additionally, stability pool depositors may receive a part of rental income through the secondary gauge managed by veRAAC holders. Stability pool depositors who handle liquidations and are first in line in case of bad debt.

</details>


---

# 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://gitbook.raac.io/learn/overview.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.
