> For the complete documentation index, see [llms.txt](https://docs.amoeba.farm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.amoeba.farm/oracle/02-token-holders-and-contributors.md).

# Token Holders and Contributors

The oracle needs people who can support good sources, challenge bad work, and keep evidence current.

Amoeba Farm separates different roles so raw capital does not automatically become oracle truth.

## Token Holders

Token holders may be able to participate in protocol economics, bounty funding, and rare emergency decisions if a market version enables those paths.

Exact token rights depend on the active product and oracle version.

Normal source support, challenge bonds, and kill stakes may use configured collateral such as cash or stablecoin units rather than the major token directly. The live product version should say exactly what asset is required before a user submits work.

## Contributors

Contributors improve the source layer.

They can:

* propose a public source;
* define what the source measures;
* submit opening print evidence;
* submit source updates;
* challenge wrong, stale, duplicate, or invalid claims.

Contributors should read the evidence rules before submitting work.

## Stake and Review

The current model uses posted stake, challenge bonds, evidence review, and slashing. It does not use a hidden contributor score or credibility multiplier.

Because stake can influence support, each market version should publish its collateral requirements, challenge windows, bounty caps, and emergency fallback before users submit work.

## What to Read Next

* [Evidence Rules](/reference/02-evidence-rules.md)
* [Challenges](https://github.com/SPACE999978/amoeba-oracle-gitbook/tree/main/docs/contributors/03-challenges.md)
* [Bounty Collection](/oracle/03-bounty-collection.md)


---

# 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://docs.amoeba.farm/oracle/02-token-holders-and-contributors.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.