> For the complete documentation index, see [llms.txt](https://jester.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jester.gitbook.io/docs/faq/q-and-a.md).

# Q\&A

<details>

<summary>Q:  Why Jester?</summary>

A: Originally, the system was named "The Juggler" because it juggles falling knives. However, we've rebranded it as Jester.

</details>

<details>

<summary><strong>Q: Why charge for this? Don't you make enough trading with it?</strong></summary>

**A:** As the Joker once said, "If you are good at something, never do it for free." While the Juggler system was initially built for personal use, Jester was developed to assist friends and family who wanted to trade. It provides them with substantially improved entry points, especially when compounding with traditional methods.

We then realize the scope and scale of what we can accomplish with the Jester system, and this was the next step. This expansion aims to leverage our capabilities to create a comprehensive trading ecosystem that benefits a broader community.

</details>

<details>

<summary><strong>Q: What happens if the cost of</strong> JESTER <strong>becomes too high? Will the tiers be reworked?</strong></summary>

A: We are committed to maintaining JESTER as a unique and exclusive product, especially for our higher-tier users. If the cost of JESTER reaches a certain threshold, we are prepared to take action. This may involve a redesign of the tokenomics or tiers. \
\
Additionally, we are planning to introduce a subscription-based model for the lower tiers. Our aim is to ensure the continued exclusivity, accessibility, and value of Jester to our community while also giving new users and the broader population access. This approach allows us to maintain the prestige and benefits of being a tier holder without compromising on exclusivity or reputation.

</details>

<details>

<summary><strong>Q: Will there be revenue sharing?</strong></summary>

A: Revenue sharing is an active topic of discussion, and we have several ideas in mind. While we do not have a definitive plan in place yet, we are exploring various possibilities to create a rewarding experience for our users.

However, revenue sharing introduces considerable issues, with only significant whales benefiting from it. We believe buybacks are a much better option. Buybacks help to stabilize the token price by reducing the overall supply, which benefits all holders, not just the largest ones. This approach ensures a more equitable distribution of benefits across the entire community, maintaining the value of $JEST and supporting a healthier ecosystem.

</details>

<details>

<summary><strong>Q: Will you ever show the source code?</strong></summary>

A: No, the JESTER system is **proprietary** and not **open-source**. We believe in the system's potential across various markets, including traditional finance (TradFi). We plan to explore its applications in different areas to maximize its impact and effectiveness.

</details>

<details>

<summary><strong>Q: Why not start a hedge fund if it's that good?</strong></summary>

A: It's an idea that has been considered and is certainly a possibility for the future. Due to our buyback mechanism, where people invest in JESTER and we use those funds to buy back tokens, JESTER essentially operates as a soft hedge fund. We’re always looking to expand and explore new opportunities, and formalizing JESTER as a hedge fund could be one of them as we continue to grow and evolve.

</details>

<details>

<summary><strong>Q: Can I use</strong> JESTER <strong>on any trading platform or exchange?</strong></summary>

A: [Tiers](/docs/guide/tiers.md#premium-10000-usdjest) gain exclusive access to an invite-only, protected, closed-source version of the JESTER indicator, built with Pinescript on TradingView. This version can be used on any trading pair and exchange of their choice, providing advanced capabilities to enhance their trading experience.

</details>

<details>

<summary><strong>Q: What technology is</strong> JESTER <strong>built on?</strong></summary>

A: JESTER is currently built using Pinescript on TradingView, a platform renowned for its rapid prototyping and seamless integration capabilities. In the future, we have ambitious plans to enhance JESTER capabilities even further. Our vision includes porting the system directly to higher level languages. This expansion will empower users to utilize JESTER both on-chain and off-chain, providing greater flexibility and broader access to advanced trading tools.

</details>

<details>

<summary><strong>Q: How frequently do you update</strong> JESTER <strong>features and strategies?</strong></summary>

A: We are committed to continuous improvement. JESTER calls are continually monitored, and features and strategies are regularly updated to adapt to changing market conditions and incorporate user feedback. We have done multiple updates, and have just finished releasing v2.

</details>


---

# 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://jester.gitbook.io/docs/faq/q-and-a.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.
