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

# Disclaimer

This page is a general disclaimer for BlockOps documentation. It is not legal, financial, tax, or investment advice.

## No Financial Advice

Nothing in the BlockOps game, website, documentation, community channels, or related materials should be interpreted as financial advice.

Users should make their own decisions and consult qualified professionals before buying, selling, holding, or using any crypto asset.

## Risk Of Loss

Crypto assets are risky.

Risks may include:

* Loss of funds.
* Token price volatility.
* Smart contract risk.
* Wallet compromise.
* Exchange or liquidity risk.
* Network congestion.
* Regulatory uncertainty.
* Changes to game rules or reward logic.

Users should never spend funds they cannot afford to lose.

## Rewards Are Not Guaranteed

BlockOps may include play-to-earn mechanics, but rewards are not guaranteed.

Reward outcomes may depend on:

* Player eligibility.
* Token-holder status.
* Valid server-confirmed kills.
* Anti-cheat review.
* Available reward pool size.
* Treasury balance.
* Claim timing.
* Technical availability.

Past rewards do not guarantee future rewards.

## Gameplay Comes First

BlockOps is a game. Any reward mechanics are intended to support gameplay and community participation.

Players should not treat gameplay rewards as income, yield, profit guarantees, or investment returns.

## Token And Market Risk

The BlockOps token, if launched or traded, may be highly volatile.

Token prices can move sharply due to market conditions, liquidity, sentiment, trading volume, or project developments.

No statement in this documentation guarantees token price, liquidity, reward value, or future market performance.

## User Responsibility

Users are responsible for:

* Securing their wallet.
* Verifying links before connecting.
* Understanding transaction approvals.
* Checking local laws and regulations.
* Tracking their own tax obligations.
* Evaluating all crypto-related risks independently.

## Changes To The Project

BlockOps is in active development. Mechanics, tokenomics, reward rules, claim rules, eligibility requirements, and treasury processes may change over time.

Documentation should be treated as informational and subject to updates.


---

# 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://documentation.block-ops.fun/disclaimer.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.