> For the complete documentation index, see [llms.txt](https://jujuverse.gitbook.io/jujuverse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jujuverse.gitbook.io/jujuverse/background/technical-decisions.md). # Technical Decisions ## Blockchain #### Why Solana? 1. Best blockchain for gaming due it's speed (50k TPS vs 13 TPS). This gives the users a more real time experience in the game. Unlike the current games in the Web 3.0 space 2. Less saturated secondary markets. OpenSea is saturated and full of fakes at the moment. Solana seems to be the solid alternative. 3. Solana is proof of stake and proof of history. So the algorithms are much efficient. Therefore it consumes less energy. Almost 99% less energy than for example ETH which is a proof of work crypto. Relatively very low carbon footprint - better for the environment 4. Low gas fees for the NFT buyers (next to nothing) ## Game Genre #### Multiplayer ARPG Multiplayer Action role playing game: This type of game combines core elements from both the action game and role-playing genre. Some prime examples are Diablo, Warhammer, Path of Exile & Torchlight. Based on the nature of this genre the integration with the chain becomes smoother - making the user experience smoother. The kicker is JuJuverse will have Multiplayer PvP aspects as well - This aspect is not traditionally adapted in the ARPG genre. We aim to create one of a kind experience for the users. The JuJu Devil NFT owners will get a truly unique experience by getting a chance to participate in the beta testing of this game --- # 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://jujuverse.gitbook.io/jujuverse/background/technical-decisions.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.