# Overview In the realm of online games and virtual worlds, each in-game item and virtual asset not only represents a unique part of the gaming experience but also a valuable asset created and acquired with specific efforts, often involving in-game purchases. However, until today, these digital assets have been subject to various limitations and risks, including insufficient security during transfer and storage, as well as the inability to legally withdraw invested funds. There exists a "black" market for in-game items, but users face the risk of fraud and numerous other threats. ### Problem The problem lies in the fact that gaming assets lose their real value since players cannot convert them into real money without resorting to the black market. Collaborating with major Role-Play projects (such as Black Russia), we understand the pressing issues in the gaming industry, particularly those related to the storage, transfer, and liquidity of in-game resources. Another challenge is that game owners/creators are often not interested in the secondary market as it leads to a loss of revenue. ### Solution The solution comes in the form of tokenizing gaming assets, allowing them to be legally traded on a specialized platform. In this way, game owners receive a percentage of the sales. We have initiated the Tanpin.io project, a marketplace for in-game items tailored for WEB2 games, powered by the utility token TAPIN. **Note: TANPIN is currently under Public Beta Phase, so contents in the Whitepaper could be changed in the future.** --- # Agent Instructions: 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://whitepaper.tanpin.io/overview.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.