> For the complete documentation index, see [llms.txt](https://guide.equinox.fund/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.equinox.fund/celestial-collection-nfts/history-of-the-celestial-collection/gifted-celestial-collection-nfts.md).

# Gifted Celestial Collection NFTs

OG Community Members who followed the Equinox Founders from Apollo-X received gifted NFTs matching their contributions to IDOs within Apollo-X, allowing them to participate in launches on Equinox. This gesture was an expression of gratitude to loyal community members, affirming the team's commitment to reciprocate the trust and loyalty bestowed by the community. It stands as a testament to the symbiotic relationship between Equinox and its community, acknowledging their pivotal role in the shared journey.

### Gifted NFT Restrictions

Providing a large number of community members with gifted NFTs required the team to impose restrictions on these NFTs to protect the interests of the growing community and new members who needed to purchase NFTs for launchpad access.

Gifted NFTs came with the following restrictions:

* Non-transferable until sold.
* A total of 80% in Tax and Royalty fees on the first sale.
* Unable to sell below the mint price.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://guide.equinox.fund/celestial-collection-nfts/history-of-the-celestial-collection/gifted-celestial-collection-nfts.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 `automate deployments from our CI pipeline` 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.
