> For the complete documentation index, see [llms.txt](https://unite-1.gitbook.io/unite-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://unite-1.gitbook.io/unite-docs/unite-protocol/tokenize-the-gamer.md). # Tokenize The Gamer Web3 gaming has hit a **dead end.** Everyone tried to **tokenize games**. But games die. Gamers don’t. 🎮 It's time to flip the script. It’s time to **tokenize the gamer**. *** When you tokenize a **game**, you’re betting on: * A single title’s success * A short lifecycle (most web3 games fade in a couple of months) * A walled garden economy Result? Fragmented ecosystems, reset-to-zero identities, and useless tokens. *** **Gamers** **outlive games**. Your skills, achievements, gaming buddies, and contribution — that’s what’s **persistent and secured on-chain, forever.** *** With **Unite**, every **moment you play** **matters**. * **Gamer Coins** → capture your gaming identity * **Play Coins** → record your proof of play * Together, they make your value **travel with you** across games and ecosystems *** Why this changes everything: * **Gamers** own their identity and progress * **Developers** plug into an ecosystem built on gamer-created value * **Channels** grow faster as value compounds across ecosystems This isn’t speculation. It’s **gamer-driven value**. *** The future of Web3 gaming isn’t about **tokenizing games**. It’s about **tokenizing gamers**. Because games come and go. You - gamer - stays. Welcome to **Unite**. Your **gameplay = permanent value on chain** 🔗 --- # 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://unite-1.gitbook.io/unite-docs/unite-protocol/tokenize-the-gamer.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.