> 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/6-the-economics-of-participation/6.5-usdofc-tokenomics-and-utility.md).
# 6.5 $OFC tokenomics and utility
$OFC has a fixed supply of 1 billion tokens and is designed with a community-first allocation model. The largest share of supply is reserved for community, ecosystem, and partnership growth, reflecting the central role fans play in creating value across the Fandom Economy. Inspired by German football’s 50+1 principle, the community retains at least 51% of the token supply – reinforcing that the community remains at the heart of the system it powers.
$OFC’s token allocation is designed to balance three priorities. First, enough supply must be available to reward users, fund ecosystem growth, support partnerships, and activate the community. Second, the team, advisors, and contributors must remain aligned over the long term through structured vesting and milestone-based incentives. Third, the network needs sufficient treasury, liquidity, and operational reserves to support sustainable growth, market access, and future product development.
Fans earn $OFC through match predictions, community challenges, and wagers among other in-app engagement. The earned $OFC can then be used across multiple features in the ecosystem, including:
* Payment Voucher: $OFC is a payment mechanism for exclusive digital and physical assets, pay-per-view live streams, and premium in-app experiences.
* 1F Predict: fans hold 2,500 $OFC to participate in weekly prediction contests on real football matches for monthly reward pools, leaderboard prizes, and unique fan experiences.
* FanPass (On-Chain Fan Identity): fans mint a verifiable on-chain identity that serves as their portable football ID – storing achievements, predictions, purchases, match attendance, and badges – building a persistent reputation layer and portable fan graph across the ecosystem.
* OneFootball GamesHub: $OFC powers a competitive gaming hub where fans can compete in wagers and tournaments across multiple high-quality football-themed games, creating gameplay-driven demand through skill-based competitions, sponsored tournaments, and prize pools.
* OneFootball Heads IP: $OFC powers the creation, customization, and trading of “OF Heads” avatars – the universal fan persona within the ecosystem – with strong monetization through customization packs, branded collaborations (ex. FC Barcelona & Jordan), in-app revenue, and secondary markets.
This structure supports the broader economic model of the Fandom Economy. Commercial demand can enter the system through partner-funded campaigns and reward pools, while utility gives $OFC places to circulate once earned. Community allocation gives the network fuel for growth, vesting supports long-term alignment, and utility creates the basis for recurring participation. The tokenomics are therefore designed not only around supply and demand, but around circulation – how value enters, moves through, and compounds across the football ecosystem.
---
# 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/6-the-economics-of-participation/6.5-usdofc-tokenomics-and-utility.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.