> For the complete documentation index, see [llms.txt](https://docs.gib.work/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.gib.work/getting-started/create-your-first-bounty.md).

# Create your first bounty

Turn work you need done into a funded opportunity. A bounty tells contributors what to deliver, how you will review it, and what they can earn.

For your first bounty, choose one small, specific outcome: fix a bug, improve a README, or create a graphic.

## 1. Sign in to Gibwork

Open [Gibwork](https://gib.work/) and create an account or sign in. Open the creation flow to start a new bounty.

## 2. Describe the work

Give your bounty a title that names the result you want. In the description, explain the problem and provide the context someone needs to begin.

Include:

* **Deliverable:** The finished work you expect.
* **Resources:** Relevant links, files, examples, or a GitHub issue.
* **Submission requirements:** What contributors should submit, such as a pull request, document, or file.
* **Acceptance criteria:** The specific conditions the submission must meet.
* **Timing:** Any deadline contributors need to know.

Choose resources contributors can access. For a GitHub bounty, link directly to the issue and explain how to test or review the change.

## 3. Set the reward and options

Choose the reward amount and token from the options available in the creation form. Consider the scope, skill, and time the work requires.

Review the available settings before continuing. If you choose a private bounty, share its link with the people you want to participate.

## 4. Review, fund, and publish

Read the bounty as if you were seeing the project for the first time. Check that the requirements are understandable, the resource links work, and the reward is correct.

Follow the funding instructions in Gibwork, complete the required deposit, and publish your bounty. Check that the published bounty shows the details you intended.

## Example: A first bounty

Use this illustrative brief as a starting point. Replace the scope, links, deadline, and reward with your own.

**Title:** Fix broken links in our project README

**Description:** Review the links in our repository's main README and fix any that no longer reach the intended resource. Use the repository link supplied with this bounty.

**Deliverable:** One pull request containing the link fixes and a short summary of what changed.

**Submission requirements:** Submit the pull request URL and a list of the links you checked.

**Acceptance criteria:**

* Every link in the README has been checked.
* Broken links point to the correct replacement resource, or are removed with an explanation if no replacement exists.
* The README still renders correctly.
* The changes are limited to the README.

**Reward:** 25 USDC for the accepted submission. This is an example amount, not a pricing recommendation.

**Deadline:** Add a specific date, time, and time zone before publishing.

## After you publish

Share the bounty link with relevant contributors or your community. Answer questions and clarify the requirements when needed.

Review submissions against the acceptance criteria you published. Give specific feedback when work needs changes. When a submission meets the requirements, approve it and follow the in-app instructions to complete the reward process. Check the submission and payment status before considering the bounty complete.

[Create your first bounty](https://gib.work/)

Looking to contribute instead? Read [How to Start Earning](/getting-started/frequently-asked-questions/how-to-start-earning.md).
