> ## Documentation Index
> Fetch the complete documentation index at: https://docs.omi.me/llms.txt
> Use this file to discover all available pages before exploring further.

# Bounties

> Paid, team-posted tasks with a public proof spec and an open race to the first PR that meets it.

From time to time the Omi team posts paid bounties on specific issues. This page is the contract for how they work.

> **[Open Bounties](https://github.com/BasedHardware/Omi/issues?q=is%3Aopen+is%3Aissue+label%3A%22Paid+Bounty+%F0%9F%92%B0%22)**
>
> Issues labeled "Paid Bounty 💰"

## Rules

* **Only the team posts bounties**, on issues labeled "Paid Bounty 💰". There are no contributor-suggested bounties. Good bug reports with reproductions are always welcome.
* **Every bounty states a proof spec**: a measurable target, how it is verified, and a real-hardware demo where that is relevant. It also names the maintainer who judges the result and handles the claim.
* **Open race.** The first pull request that meets the proof spec wins. Tasks are not locked; "can I take this?" comments carry no weight. PRs that miss the spec or duplicate another PR may be closed without detailed review.
* **AI-assisted work is fine.** The submitter must demo the result and answer review questions themselves.
* **Payment happens only after the work ships in a release.** Once it has, claim by emailing [team@basedhardware.com](mailto:team@basedhardware.com) with a link to the bounty issue.

## Questions about a bounty

Ask in the bounty issue itself. The judging maintainer named in the proof spec is the authority on what "done" means. No one else can promise acceptance.

For everything else (bug reports, apps, core PRs), see the [Contribution Guide](https://docs.omi.me/doc/developer/Contribution.md).


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.