> For the complete documentation index, see [llms.txt](https://docs.hope.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hope.money/appendix/glossary.md). # Glossary ### $HOPE $HOPE is a utility distributed stablecoin, designed as a currency vehicle for non-crypto natives to enjoy financial inclusion in a fully transparent and secure environment. $HOPE will be backed by distributed reserves of BTC and ETH. ### $stHOPE $stHOPE is a liquid, tokenized representation of staked $HOPE in the in the ecosystem. ### $LT $LT (Light Token) is the single utility token of the HOPE ecosystem that aims to power all protocols within the ecosystem. ### veLT veLT is a special ERC-20 token that stands for vote-escrowed $LT. It represents $LT that is locked for voting and is not transferable or tradable. ### Gömböc HOPE Gömböc is a set of distributed reserve pools for $HOPE. ### The Peg Event As the cryptocurrency market recovers, the market value of $HOPE will gradually achieve $1.0, reaching 100% of face value. ### DeFi Decentralized finance (commonly referred to as DeFi) is an experimental form of finance that does not rely on financial intermediaries such as brokerages, exchanges, or banks, and instead utilizes blockchains, most commonly the Ethereum blockchain. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.hope.money/appendix/glossary.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.