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

# Ask your questions

Welcome to the most asked questions about Organic.\
Here’s a quick overview for newcomers and curious builders who want to understand how it all works.

***

#### <mark style="color:$primary;">1) What is Organic in one sentence?</mark>

Organic is a decentralized community studio on Solana where real contributions earn rewards, and the community decides what gets built next.

***

#### <mark style="color:$primary;">2) What does $ORG do right now?</mark>

Right now, $ORG acts as a signal and access token for the mission — it gates participation, aligns incentives, and connects users to the platform and future tools. It’s not a financial asset or guarantee of profit; value comes from creating and building together.

***

#### <mark style="color:$primary;">3) Can you mint more tokens or change supply?</mark>

No. Total supply is **123,456,787**, and all tokens are already in circulation.\
We don’t hold mint, freeze, or metadata authority — nothing can be changed or reissued.

***

#### <mark style="color:$primary;">4) How do I start earning with Organic?</mark>

Join our \[Discord] and pick a role.\
Grab a task, submit proof, get scored, and receive your share in the next payout.\
When the platform launches, members will have **Organic IDs** and can complete tasks directly on-site.

***

#### <mark style="color:$primary;">5) How are rewards calculated?</mark>

Each epoch has a revenue pool in SOL or USDC.\
Tasks are weighted (1–10) based on community votes.\
Inside each task, your score (0–100) and any staking boost determine your share.\
All parameters can be changed later through community votes.

***

#### <mark style="color:$primary;">6) Is staking live? How will boosts work?</mark>

Not yet — staking is part of our roadmap.\
We plan to add a fair boost system that rewards long-term contributors without letting whales dominate.\
Exact caps, formulas, and parameters will be voted on by the community.

***

#### <mark style="color:$primary;">7) Who runs the treasury and makes decisions?</mark>

We’re moving to a **Squads multisig**, so no single wallet controls funds.\
Small ops are handled within budget, while major decisions (like listings, burns, or partnerships) go to full community votes.\
Council membership and vote weight depend on contribution points and holdings.

***

#### <mark style="color:$primary;">8) Where does revenue come from?</mark>

Current and future revenue streams include:

* Creator fees
* Platform-as-a-service for other communities
* The **Organic AI Agent** (licensed to detect fake activity)
* Studio services and partner campaigns
* Tool subscriptions and, later, merch/licensing

A portion may be used for **buybacks or burns**, but only if the community approves.

***

#### <mark style="color:$primary;">9) Are you listing on more DEXs or CEXs?</mark>

We’re already verified on **Dexscreener** and **GeckoTerminal**.\
Next, we’ll apply for **CoinGecko**, **CMC**, and possibly larger exchanges — but only when it makes sense for growth.\
Organic moves at its own pace; listings are proposed and voted on by the community.

***

#### <mark style="color:$primary;">10) How do you handle spam, bots, and low-effort work?</mark>

Each submission must include one clear proof.\
Spam or copied content scores zero and earns a strike.\
Appeals stay open for 48 hours and are reviewed by stewards plus a rotating community reviewer.\
Our AI Scoring Agent helps flag botted or low-effort activity, but humans make the final decision.

***

💬 **Still have questions?**\
Ask in the #faq-discussions channel on Discord and someone from the community or team will help you right away.


---

# 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://organic-1.gitbook.io/organic-docs/faq/ask-your-questions.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.