> For the complete documentation index, see [llms.txt](https://hit-zone.gitbook.io/hit-zone-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hit-zone.gitbook.io/hit-zone-whitepaper/technology.md).

# TECHNOLOGY

## Building on Binance Smart Chain Blockchain

The Blockchain is a paradigm shift beyond traditional video gaming. Blockchains remove predatory middle-men and enable communities to build and shift democratically, creating skills and imbuing players and users with skills and absolute, censorship-resistant, verifiable ownership over their in-game assets and effort. On-chain games will revolutionize the gaming ecosystem: rewarding players for the skills they develop ‘in-game’ that are valued by the community. The use of tradable tokens in return for their achievements and progression makes blockchain games appealing to a broader audience of players.

HIT ZONE runs on the Binance Smart Chain blockchain.&#x20;

Binance Smart Chain is a useful blockchain for storing and accessing HIT ZONE

**On chain components include**:&#x20;

·      HIT ZONE token&#x20;

·      All non fungible tokens (NFT)

·      All core game play&#x20;

·      DAO: Super VIP users can discuss and proposed ideas in a Discord channel

·      Database of Arenas and gaming reward distribution mechanism&#x20;

**Off chain elements include:**&#x20;

·      Graphical elements including of NFTs (avatars and other gameplay modifying NFTs)&#x20;

·      User interfaces&#x20;

·      DAO management interface.

·      Additional games and activity.

**Core NFTs**

**NFTs on BSC Blockchain:**

&#x20;The NFTs on BSC are built on the BEP 721 and BEP 1155 standard. The NFTs on BSC exist as data in the state tree of BSC and their associated data is in a JSON file on an IPFS server.


---

# 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://hit-zone.gitbook.io/hit-zone-whitepaper/technology.md?ask=<question>&goal=<endgoal>
```

`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.
