# 3) The Problem and Our Solution

Traditional real estate, especially auctions and off-market deals, is hard to access. High capital requirements, legal complexity, opaque processes, and time-intensive admin keep most people out.

DeFi promised to make participation more inclusive, but most tokens lack a link to tangible revenue. This leads to price volatility, speculative hype, and short-lived projects with little real utility.

Another key challenge for users is the volatility of on-chain investing. Many investors are either over-exposed to high-risk, high-volatility assets or excluded entirely due to lack of lower-risk options.

LandFi bridges this gap. Our platform converts real estate proceeds into on-chain value, fuelling staking rewards (USDC and LND), buy-backs, and treasury growth. Users can join short-term staking pools (30–60 days) with no long lock-ups, earning rewards from real-world property cycles like acquisitions, subdivisions, sales, and rentals.

We also provide a range of pool types and risk profiles, allowing users to select stable USDC-based pools, LND redistribution pools, or premium gated pools with enhanced reward potential,  creating accessible options for different participation and risk preferences.

LandFi also supports:

* **Buy-back & burn:** Supports long-term token scarcity.
* **DAO-influenced treasury:** Token holders vote on treasury use, new partners, pool parameters, and roadmap.
* **Compliance-first design:** Clear separation between off-chain acquisitions and on-chain utility; no ownership rights implied
* **Resilience:** Off-chain real estate proceeds are less correlated with crypto market volatility.


---

# 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://landfi.gitbook.io/landfi/landfi-whitepaper/problem-and-solution.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.