> 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/risk-factors-and-disclaimers.md).

# Risk Factors and Disclaimers

Participating in the H2P ecosystem involves significant risks. Prospective participants should carefully consider the following risk factors before making any decision.

#### Market Risks

**Price Volatility**

The price of H2P may fluctuate significantly due to market conditions, speculation, regulatory developments, and other factors beyond HUMB's control. You may lose some or all of your participation value.

**Liquidity Risk**

There may be periods where it is difficult to sell H2P tokens at desired prices or volumes. Liquidity depends on market adoption and trading activity.

**Token Releases**

Tokens from vesting enter circulation every month after TGE, which increases the supply available to trade and can affect the price.

**Sale Terms**

Presale and listing prices are set after the private round closes and may differ from any indicative figures shared earlier.

**Market Adoption**

The success of H2P depends on widespread adoption by healthcare providers, patients, and traders. There is no guarantee that such adoption will occur.

#### Regulatory Risks

**Changing Regulations**

Cryptocurrency and healthcare regulations are evolving rapidly across jurisdictions. Future regulatory changes could restrict H2P trading or impose additional compliance requirements.

**Jurisdictional Restrictions**

H2P tokens may not be available to residents of all jurisdictions. It is your responsibility to ensure that your participation complies with applicable laws.

#### Technology Risks

**Smart Contract Vulnerabilities**

H2P's smart contracts will be audited before TGE, but no audit can rule out every bug or vulnerability, and a flaw could result in loss of funds.

**Platform Security**

While HUMB employs industry-standard security measures, no system is completely immune to cyberattacks or security breaches.

#### Disclaimers

**Not Financial Advice**

This whitepaper is for informational purposes only and does not constitute financial, investment, legal, or tax advice.

**Forward-Looking Statements**

This whitepaper contains forward-looking statements regarding HUMB's plans, objectives, and expectations. Actual results may differ materially from those expressed or implied.

**No Guarantees**

HUMB makes no representations or warranties regarding the future value of H2P tokens, the success of the platform, or the achievement of any stated objectives. Community Growth Pool rewards are not guaranteed and depend on platform activity, participant eligibility, and program terms, which may change.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://humb-io.gitbook.io/humb.io-docs/risk-factors-and-disclaimers.md?ask=<question>&goal=<user_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 `build a script that syncs our docs to a CMS` 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.