> 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.md).

# History of the Celestial Collection

The Celestial Collection was created to mitigate token price volatility and enable Equinox to operate until the development of a suitable tokenomics model. This innovative approach distinguished Equinox from other launchpads and placed it in a unique position at the dawn of the new bull run.

## Celestial Collection NFTs Original Utility

* **Summer - Tier 4**
  * Guaranteed allocation in IDOs.
  * Highest allocation.
* **Vernal - Tier 3**
  * Lottery & FCFS (First-Come, First-Served).
  * High allocation.
* **Winter - Tier 2**
  * Lottery & FCFS.
  * Moderate allocation.
* **Autumnal - Tier 1**
  * Lottery & FCFS.
  * Low allocation.

The first 65% of each pool was allocated to lottery winners. Once those were filled, the final 35% of each tier’s total pot was available to non-winning lottery participants on a FCFS basis.

To ensure the Summer NOX tier remained the top tier, a waterfall allocation method was used, meaning that participation levels in the top tier determined the allocation for each tier below.


---

# 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://guide.equinox.fund/celestial-collection-nfts/history-of-the-celestial-collection.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.