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

# Glossary

| Term                  | Definition                                                                                       |
| --------------------- | ------------------------------------------------------------------------------------------------ |
| AML                   | Anti Money Laundering. Regulations designed to prevent illegal use of financial systems.         |
| Burn                  | Permanent removal of tokens from circulation by sending them to an inaccessible address.         |
| CEX                   | Centralized Exchange. A cryptocurrency exchange operated by a central authority.                 |
| Cliff                 | A period after TGE during which locked tokens cannot be released.                                |
| Community Growth Pool | HUMB's annual rewards program for verified activity on the platform, paid in H2P.                |
| DAO                   | Decentralized Autonomous Organization. Organization governed by smart contracts and token votes. |
| ERC-20                | Technical standard for fungible tokens on the Ethereum blockchain.                               |
| FHIR                  | Fast Healthcare Interoperability Resources. Standard for healthcare data exchange.               |
| FIU                   | Financial Intelligence Unit. Government agency combating money laundering.                       |
| GDPR                  | General Data Protection Regulation. EU regulation governing data privacy.                        |
| H2P                   | Health To Purpose. The native utility token of the HUMB ecosystem.                               |
| HIPAA                 | Health Insurance Portability and Accountability Act. US medical data privacy law.                |
| KYC                   | Know Your Customer. Identity verification procedures required by regulations.                    |
| KYH                   | Know Your Healthcare. HUMB's framework for verifying healthcare credentials.                     |
| Launchpad             | A platform that hosts token sales and connects projects with verified buyers.                    |
| Market Cap            | Total value of all tokens in circulation, calculated as price multiplied by circulating supply.  |
| MiCA                  | Markets in Crypto Assets. EU regulatory framework for cryptocurrency.                            |
| PHI                   | Protected Health Information. Individually identifiable health data under HIPAA.                 |
| TGE                   | Token Generation Event. Initial creation and distribution of a token.                            |
| VASP                  | Virtual Asset Service Provider. Regulatory classification for crypto businesses.                 |
| Vesting               | Schedule releasing tokens gradually over time to align long-term incentives.                     |
| Zero Knowledge Proof  | A cryptographic method proving something is true without revealing the underlying data.          |


---

# 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://humb-io.gitbook.io/humb.io-docs/glossary.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.