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

# Bounty Hub

**1. Purpose**

Bounty Hub is envisioned as the public “jobs board” for HackAI. Model owners will be able to post vetted security tasks, stake HACK, and pay out rewards automatically when a valid exploit (or patch) is reproduced. Researchers will browse open bounties, submit proofs, and build a verifiable reputation without private NDAs or off-platform negotiations.

<figure><img src="https://lh7-rt.googleusercontent.com/docsz/AD_4nXd-SqQ--WnK90UI91FlyUXfJhtHSFVMCHFKaE4xaJYZ95mTWCZiipSq5ypHo5GD3Ez45JDxXU058FTyx9Olm0Wt6Q4jl5JjmKvZMKgARTgqnHJRd8PBTfF1RXGDV0_Ntm_qjoqQGw?key=8dnxn4l7fPuleI7loQGLNg" alt=""><figcaption></figcaption></figure>

All logic will live in a dedicated Solana program; the UI will surface inside the existing Launch dApp.

***

**3. Example Workflow (Concept Draft)**

1. Post AcmeAI stakes 10 000 HACK and posts “jailbreak prompt that bypasses policy-X on model hash 0x…”.
2. Discover Researcher A finds a working prompt, submits payload + Merkle root.
3. Verify At least N independent peers reproduce the root in the Adversarial Sandbox.
4. Payout Contract releases 10 000 HACK to Researcher A; reputation NFT minted.
5. Patch AcmeAI uploads a fix diff, links it to the exploit ID, earns a “patched” badge in Security Vault.

***

**4. Why It Matters**

* Open coverage – crowdsources edge-case exploits that in-house red teams miss.
* Aligned incentives – researchers get paid instantly; model owners get reproducible proofs.
* Transparent history – every exploit–patch pair lives on-chain for future audits and regulators.