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

# NO TEAM TOKENS

**No Team Tokens OF ANY KIND for any part of the project. EVER.**&#x20;

No team members will own tokens. There will be no transfer to personal or project wallets before the launch, or after.  One of the many risks in farming is, far too often, teams get greedy. Developers feel the pressure in the atmosphere when they see their wallet balance grow.  They split up and go their separate ways and either, one of the team members or all, end up dumping their tokens. When this happens, no matter how aligned the stars are, the project will certainly die. With no one having the ability to do this within AstroFarms™, there can be no soft or hard rug.

We believe it when we say it, "AstroFarms, where every star has an equal chance to shine".

Please see Cardinal Qualities under Contracts & Security, for additional safety protocols.&#x20;


---

# 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://astrofarms.gitbook.io/astrofarms/tokenomics/no-team-tokens.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.
