> For the complete documentation index, see [llms.txt](https://quor.gitbook.io/quor-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://quor.gitbook.io/quor-docs/whitepaper/fractional-ownership-through-tokenization.md).
# Fractional Ownership Through Tokenization
The core innovation of Quor's approach lies in **dividing large-scale data center facilities into smaller, digitally tradable tokens that represent proportional ownership stakes in the underlying physical infrastructure.** Where traditional data center investments require **minimum capital commitments of $5-50 million,** tokenization reduces entry barriers to accessible thresholds-**potentially as low as $1,000 or less.**
### This fractionalization operates through blockchain-based digital tokens that represent legally binding ownership rights in data center assets. Each token holder possesses:
* **Proportional Ownership Rights:** Direct claim to a fraction of the data center's physical infrastructure and revenue streams
* **Transparent Verification:** Blockchain-recorded ownership that cannot be disputed or falsified
* **Transferable Assets:** Ability to trade ownership stakes without requiring sale of the entire facility
* **Revenue Participation:** Pro-rata distribution of colocation fees, power charges, and service revenues
\
---
# 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 dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://quor.gitbook.io/quor-docs/whitepaper/fractional-ownership-through-tokenization.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
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.