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

# Bounties — Open Competitive Work Submissions | Fundwork

> Launch a Fundwork Bounty to receive open competitive submissions, then select one or more winners and pay out USDC rewards on Base.

Bounties open your problem to everyone. Anyone can submit completed work, you review what comes in, and you award USDC to the submission — or submissions — that meet your bar. No upfront hiring, no negotiation: just results.

## How bounties work

<Steps>
  <Step title="Launch your bounty">
    Set a clear brief: describe exactly what you need, define the deliverables, write your judging criteria, and set the USDC reward. Give the bounty a deadline so participants know how long they have.
  </Step>

  <Step title="Receive submissions">
    Anyone on Fundwork can submit completed work against your bounty. Submissions arrive asynchronously — you can review them as they come in or wait until the deadline passes.
  </Step>

  <Step title="Review submissions">
    Go through each submission against your stated criteria. There is no obligation to accept work that does not meet your requirements.
  </Step>

  <Step title="Select your winner(s)">
    Choose the best submission — or, if your bounty allows multiple winners, select as many as you want to reward. You are in control of how many winners you pick.
  </Step>

  <Step title="Award USDC">
    Winners receive their USDC reward on Base. If you selected multiple winners, the reward is split among them as specified in your bounty terms.
  </Step>
</Steps>

## Defining your bounty

A strong bounty brief increases submission quality. Include:

* **Deliverables** — exactly what files, formats, or outputs you expect (e.g. *one 20-second MP4 video*, *a documented list of onboarding bugs with steps to reproduce*)
* **Requirements** — any constraints or must-haves the submission must satisfy
* **Judging criteria** — how you will evaluate submissions so participants know what "winning" looks like
* **Deadline** — when submissions close

<CardGroup cols={2}>
  <Card title="Example: Launch video" icon="video">
    **\$250 USDC · Video · 6 days remaining**

    Create a 20-second launch video. The strongest single submission wins the full reward.

    *8 submissions received*
  </Card>

  <Card title="Example: Bug documentation" icon="bug">
    **\$500 USDC · Product Testing**

    Find and document onboarding bugs. Three winners split the reward — rewarding thorough, high-quality reports.

    *Multiple winners selected*
  </Card>
</CardGroup>

## Single winner vs. multiple winners

<Tabs>
  <Tab title="Single winner">
    The strongest submission takes the full reward. Use this format when you want one definitive answer — a logo concept, a video, a piece of copy — and you only need the best.
  </Tab>

  <Tab title="Multiple winners">
    You select more than one winner and split the USDC reward among them. Use this format when multiple valid, high-quality responses are valuable — like a bug report bounty where each unique bug found deserves recognition.
  </Tab>
</Tabs>

## What bounties are good for

Bounties work best when you want to see finished work from many different contributors before committing to one:

* **Creative concepts** — logos, brand directions, visual explorations
* **Launch videos** — short-form clips, trailers, social content
* **Product feedback** — usability reviews, onboarding audits
* **Bug reports** — structured QA from community testers
* **Community challenges** — writing contests, meme campaigns, design competitions
* **Research** — quick fact-finding, data gathering, competitive snapshots

<Tip>
  Write specific judging criteria. Vague bounties attract vague submissions. The clearer your standard, the easier it is to pick a winner — and the better the work you will receive.
</Tip>

<Note>
  Fundwork is currently in **alpha**. The bounties experience is live and actively being refined. Expect updates as the platform evolves.
</Note>