> For the complete documentation index, see [llms.txt](https://jelly-reimagined.gitbook.io/jelly-holder-documents/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jelly-reimagined.gitbook.io/jelly-holder-documents/introduction.md).

# Introduction

Wholeness, fellow Jelly enthusiasts! Welcome to Jelly (Reimagined) Knowledge Base, your go-to guide for navigating the exciting evolution of our beloved meme coin on the Solana blockchain. The genesis of Jelly (Reimagined) unfolded through a strategic community takeover—a defining juncture where the collective resilience of our community took center stage, steering $JELLY on an even greater trajectory. In this segment, we chronicle the transformative journey, accentuating the synchronized endeavors that converted adversity into a catalyst for both growth and innovation. Delve into the intricacies of Jelly (Reimagined) evolution, tracing its inception from the nascent stages to its current status as a dynamic, community-focused project.

This knowledge base provides an overview of the key elements that define $JELLY, its roots, and its reimagined future.

{% embed url="<https://jellyreimagined.com/>" %}


---

# 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:

```
GET https://jelly-reimagined.gitbook.io/jelly-holder-documents/introduction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.