> 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/dual-token.md). # Dual-Token System One instrument should not simultaneously represent labor, housing participation, public-market demand, and investor capital. Built By DAO separates those jobs. ## EQTBLT Records Contribution and Rent History EQTBLT is soul-bound and earned. Its two neutral provenance buckets record the source of an issuance: * Contribution EQTBLT from reviewed, approved activity; * Rent rebate EQTBLT from qualifying rent. Only eligible Contribution EQTBLT enters contributor governance power. Paying rent cannot buy contributor influence. ## BLTBY Supports Network Utility BLTBY is the separate transferable network utility token. Liquidity, distribution, and market operations follow their applicable policies and approvals. BLTBY is not bundled with the investor securities offering and does not convert automatically from EQTBLT. The separation keeps contribution, housing, capital, and public-market activity legible instead of collapsing them into one balance. --- # 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/dual-token.md?ask=&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.