> For the complete documentation index, see [llms.txt](https://docs.onefootballclub.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onefootballclub.com/the-usdofc-fandom-economy-paper.md). # The $OFC Fandom Economy Paper This document outlines OneFootball’s vision for the Fandom Economy: a new economic model that aligns the incentives of football fans, clubs, brands, and platforms. Powered by FanPass, FanScore, and OneFootball Credits ($OFC), OneFootball Club introduces a framework where fan identity becomes portable, engagement becomes measurable, and value flows directly between all stakeholders. The Fandom Economy is not simply a new product or token. Instead, it is our thesis for how digital communities, fan data, and participation can be organized in the future – and why football is uniquely positioned to lead that transition. The sections that follow explore the limitations of today’s attention economy, the emergence of identity-driven participation, and the infrastructure required to build a more open and aligned future for global fandom. --- # 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://docs.onefootballclub.com/the-usdofc-fandom-economy-paper.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.