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

# Housing Loyalty

Housing Loyalty recognizes qualifying rent history with soul-bound Rent rebate EQTBLT. It is designed to let residents carry a durable participation record across the Built By DAO network without pretending that rent automatically purchases a property.

## Flexible property economics

Each qualifying property sets a Housing Loyalty rate from 5–15%, with 10% as the standard starting point:

* higher-demand, higher-cost city properties generally use the lower end;
* standard properties can use 10%; and
* rural, lease-up, or lower-demand properties may use the higher end.

The published property schedule and lease stamp the rate for the term. A later policy change applies prospectively rather than rewriting prior periods.

## What earns EQTBLT

Authorized rental operations record a qualifying base-rent period after payment is verified. Deposits, late fees, damages, utilities, and unrelated charges do not earn Housing Loyalty. Each lease period can be issued only once.

For $1,500 in qualifying base rent, the period earns 75 Rent rebate EQTBLT at 5%, 150 at 10%, or 225 at 15%. These are EQTBLT amounts, not dollar-value guarantees.

## What the EQTBLT means

Rent rebate EQTBLT:

* stay soul-bound to the member;
* retain their Housing Loyalty source;
* can enter only enabled closed-loop spending lanes;
* moves into DAO or registered-business custody when spent; and
* does not create Contributor-house voting weight.

It does not by itself grant title, reduce future rent, satisfy underwriting, guarantee admission to another property, or create a fixed cash redemption right.

## Resident path

```mermaid
flowchart LR
    A["Property schedule"] --> B["Signed lease"]
    B --> C["Qualifying rent verified"]
    C --> D["Housing Loyalty issuance authorized"]
    D --> E["Chain confirmation"]
    E --> F["Approved closed-loop use"]
```

The lease and applicable housing law control the occupancy relationship. The contract provides an auditable loyalty record alongside it.

{% content-ref url="/pages/JxkR5zUnET7Ppq6pfpCO" %}
[How Housing Loyalty Works](/housing-loyalty/how-it-works.md)
{% endcontent-ref %}

{% content-ref url="/pages/aaa1h94p4JqUPuy7FMo0" %}
[Rent and Issuance](/housing-loyalty/rent-payments.md)
{% endcontent-ref %}

{% content-ref url="/pages/NZzCduUn7eUsIO6NlvkJ" %}
[What EQTBLT Represents](/housing-loyalty/ownership.md)
{% endcontent-ref %}

{% content-ref url="/pages/5FgocNxR92RaVxnUwBpU" %}
[Portability](/housing-loyalty/portability.md)
{% endcontent-ref %}


---

# 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://docs.builtbydao.com/housing-loyalty/equity-leases.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.