> 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/token-economy/eqtblt.md).

# EQTBLT Token

EQTBLT is soul-bound earned ownership credit. It cannot be bought, sold, or freely transferred.

## Issuance paths

### Contribution Credits

1. A task defines scope, reward, and evidence requirements.
2. A member completes the work and submits typed evidence.
3. An authorized reviewer approves, requests changes, or rejects.
4. The dashboard records final approval idempotently.
5. The authorized project vault releases funded contribution credits to the member’s stable account, records the work, and consumes the unique payment ID.
6. The app reconciles the confirmed receipt before presenting the payment as settled.

### Housing Loyalty

Housing Loyalty applies to qualifying base rent under an active lease. The property schedule selects a 5–15% rate based on economics and demand: lower for high-demand/high-cost properties, 10% standard, and higher for rural, lease-up, or lower-demand properties. The lease stamps the rate until renewal.

Fees, penalties, and unrelated charges do not earn Housing Loyalty. Later schedule changes do not rewrite an active lease retroactively.

## Balances and use

The dashboard distinguishes accrued off-chain workflow state, confirmed on-chain balance, recent versus seasoned amounts, reserved amounts, and redeemed amounts. Cash liquidity is not a standing member right; any program is separately authorized, capped, and solvency-gated.

Contracts record whether credits came from approved contribution or Housing Loyalty. Legal, accounting, housing, labor, and tax classification and reporting remain off-chain.

## Governance

Contributor power uses eligible contribution credits through the square-root curve plus bounded rank and tenure weight. Housing Loyalty does not buy governance power.

## DAO reserves and custody retirement

The token distinguishes member balances from DAO-held custody. Separately authorized reserve capitalization can create credit in an eligible contract custodian, subject to policy bounds. The reviewed unit-credit path pays that credit to members only through recorded work. The token cannot prove the behavior of an arbitrary privileged custodian; release wiring remains part of the control.

Ordinary member spending transfers credits. An authorized burner may separately retire credits held in its own custody. That operation takes no member account to burn from, and repayment does not automatically burn the revolving reserve.

See [Smart Contract Catalog](/developers/contracts.md) for the work, unit-credit, and partner boundaries.


---

# 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/token-economy/eqtblt.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.
