> For the complete documentation index, see [llms.txt](https://land-hash.gitbook.io/hashland/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://land-hash.gitbook.io/hashland/white-paper/hashland-introduction.md). # HashLand Introduction HashLand is the first decentralized synthetic assets platform that unites Intellectual Property and hash rate Assets. Bridging NFTs and hash rate assets, HashLand are able to reshape the hash rate market in the form of Synthetic NFT, thereby laying the foundational value for the S-NFT. Through the Minting Contract, Purchase Contract, and Mining Contract, HashLand are able to provide a useful toolbox for hash rate providers and Intellectual Property providers alike. The liquidity of S-NFT are guaranteed by the decentralized infrastructures such as the SWAP, POOL, CREDIT, and AUCTION. Every HashLand Synthetic NFT will exist permanently on the chain, with infinite expandability. All S-NFT data can be accessed by any third party, allowing community developers to build their own contracts above them. HashLand has issued the HC token for the purpose of promoting development. HC tokens are rewarded to users who makes interactions or contribute to the Hashland development. --- # 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://land-hash.gitbook.io/hashland/white-paper/hashland-introduction.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.