> For the complete documentation index, see [llms.txt](https://whitepaper.heroeschained.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.heroeschained.com/introduction/our-key-difference.md). # Our Key Difference ### Play & Earn > Play To Earn Heroes Chained is developed by Inventuna Inc. We founded Inventuna to develop great games and contribute to the web3 gaming evolution. Heroes chained is a manifestation of our thesis on web3 gaming: We don’t develop Play To Earn, we develop **Play And Earn**; and the difference is game changing. This whitepaper introduces not only “Heroes Chained”, but also “Play & Earn”, as well. In play & earn Web3 is an option to our gamers, where they can enjoy self-custody, censorship-resistance, free ownership, p2p trade, and zero-knowledge privacy. Some will chose that option while some others will keep the conventional game play.\ \ We believe Play & Earn will be a new distinct class of its own as a revolution against Play To Earn. The new GameFi projects that focus on game experience first will classify and announce themselves in this group. We may see games move from “P2E” to “P\&E” and maybe see the term P2E dissolve in or evolve to P\&E, eventually. --- # 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://whitepaper.heroeschained.com/introduction/our-key-difference.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.