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

# $FLY Questions

Before metapep acquired the project, the $FLY contract itself was made owner of the token thereby freezing the utility of fly in time and within scope of the existing product.. Here’s what this means:

* metapep DOES NOT control the $FLY token.
* The supply CANNOT be fixed or altered.
* Future adventures CANNOT be opened on the original roadmap.
* metapep DID NOT receive any liquidity tokens from anyone.
* $FLY WILL still be generated by Hoppers.
* $FLY CAN still be obtained in adventures currently open.
* $FLY CAN still be used in the breeding pool. &#x20;
* $FLY CAN still be staked for $VeFLY&#x20;
* $FLY CAN still be bought and sold on DEXs.


---

# 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.hoppersgame.io/about/ownership-change/usdfly-questions.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.
