> For the complete documentation index, see [llms.txt](https://olivemvx.gitbook.io/olivemvx/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://olivemvx.gitbook.io/olivemvx/the-olive-experiment.md).
# The Olive Experiment
Balance. Harmony. Growth.
Some promise life-changing returns.
\
Some promise revolutionary technology.
Instead, we ask a different question:
#### **What if a token wasn't just something to own, but a way to participate in building a stronger ecosystem?**
That is the **experiment**.
\
Not an experiment in finance.
\
An experiment in **Unity**, **Trust** and **Balance**.
#### More Than a Token - **Value Created by the Community**
Whether through new utilities, marketplaces, staking, games, collaborations, events, or ideas that have yet to be imagined, the goal remains the same:
\
***Create value with the community for the community***
The founders can plant the first tree.
\
But only the community can grow the forest.
\
The future of **Olive (OLV)** should be influenced by those who participate, contribute and care enough to help it evolve. Buying $OLV or owning an NFT should **not** be viewed as a guaranteed investment or a promise of future returns.
It is a choice to participate. To contribute to an ecosystem that grows through ideas, collaboration, creativity and mutual support. Every holder becomes part of the story.
#### **Why No Telegram? Why No Dedicated Discord?**
We chose a different path.
\
We don't want to create another isolated tribe.
We want **Olive (OLV)** holders to remain active throughout the **MultiversX** ecosystem—supporting projects, joining conversations, helping builders and forming connections wherever they go.
For us, the **MultiversX** ecosystem is the community.
**Olive (OLV)** is simply one grove within a much larger forest.
\
Our success isn't measured by how many people we can keep inside one chat room.
It's measured by the trust we earn, the bridges we build and the positive impact across the ecosystem.
#### **Why Choose Olive?**
There are thousands of tokens.
No one needs another one.
\
If you're looking for guaranteed profits, **Olive (OLV)** can't promise them.
\
If you're looking for quick hype, there will always be louder projects.
But if you believe that **Web3** can be built on **trust** instead of **fear**, **cooperation** instead of **division**, and **long-term participation i**nstead of short-term **speculation**, then perhaps **Olive (OLV)** is worth your attention.
\
Maybe this experiment **succeeds**.
\
Maybe it **doesn't**.
Its **success** will never be determined by one founder, one developer or one community leader.
It will be determined by the people who choose to participate.
\
By those who believe that value can be created together.
If those ideas resonate with you, you may already be part of the experiment. Not as an investor. Not as a customer. As a **participant**.
One person cannot create a grove. A community can.
The value of **Olive (OLV)** never comes from code or tokenomics alone. A token is code. An NFT is art. The **community** behind them gives both **value**.
#### **Plant your Olive. Grow with the Grove.**
---
# 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://olivemvx.gitbook.io/olivemvx/the-olive-experiment.md?ask=&goal=
```
`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.