> For the complete documentation index, see [llms.txt](https://kamimaster.gitbook.io/kami-master-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://kamimaster.gitbook.io/kami-master-whitepaper/play-and-earn/enjin.md). # Enjin Today many non-blockchain game studios opt into monopolizing digital asset ownership through traditional resell restrictions where selling your earned digital assets can result in having your account banned. Kami Master believes players should truly own their digital assets and be rewarded for their time spent playing the game. Digital assets and tokens drive the in-game economy and can be swapped and exchanged for other currencies through existing platforms. The large majority of NFT’s Kami Master are powered by ENJIN blockchain technology and their smart contracts give Kami Master the ability to leverage virtual assets from the Ethereum blockchain INTO the game. ENJIN continues to evolve its network capabilities, offers a Software Development Kit (SDK) enabling users of the network the ability to create, trade and even burn various types of digital assets. Assets can even be backed with the ENJIN coin itself! --- # 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: ``` GET https://kamimaster.gitbook.io/kami-master-whitepaper/play-and-earn/enjin.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.