> For the complete documentation index, see [llms.txt](https://docs.descend.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.descend.gg/history-of-usdtear/tear-past.md). # TEAR Ⅰ (Past) ### A CENTRALIZED TOKEN **TEAR** began as a non-transferrable ERC20 utility token used solely within **Descend**.\ It was used to *enter* the dungeon, and also to *buy* items in the $TEAR Store. TEAR was obtainable through burning other NFT projects integrated tokens (including $SLIME, $PIXL & $FRG) and also buy purchasing it using ETH. The burn has since been closed off and was done to provide early supporters a way forward.\ \ TEAR-V1 utilized an off-chain database solution to minimise gas costs for the user. Every purchase or earning of $TEAR was off-chain and did not reflect on an Ethereum Wallet. We further kept this solution as we did not have any alternative solutions to reducing gas costs. L2 infrastructure was not very popular at the time and liquidity on them was not as present. Content creators have made videos on us in the past, which can be found on the Discord in the gameplay section. --- # 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://docs.descend.gg/history-of-usdtear/tear-past.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.