Skip to main content

How to Claim a Bounty

Before you start​

  • Read the bounty carefully. Each card links to a GitHub issue holding the full scope, deliverables and acceptance criteria
  • Check the status: only OPEN bounties are available to claim
  • Check the issue's assignee too. The board updates in batches, so a bounty showing OPEN may already be assigned to someone, and the issue is always the authoritative source
  • Make sure you can finish before the expiry date, if one is set
  • You'll need a GitHub account to claim and to submit

Claim process​

Find a bounty

Browse the Active Bounties board and find an OPEN bounty that matches your skills. Filter by category, discipline, status, or reward to narrow it down.

Both the Apply and GitHub buttons take you to the same place, which is the GitHub issue with the full requirements.

Comment to claim

Leave a comment on the GitHub issue expressing your intent to work on it. Include a brief note on your approach, your estimated timeline, and any relevant experience.

A core contributor will confirm your claim and assign the issue to you, which is what marks it CLAIMED. Only one contributor holds a claim at a time. The board card may take a little while to catch up, so treat the assignment as what counts.

Do the work

Complete the work according to the acceptance criteria in the issue. Those criteria are what reviewers check against, so treat them as the definition of done rather than a suggestion.

If you have questions, ask in the issue thread or in the Arrow Discord. Keep the team updated, and if you're running behind, say so early. Bounties that go silent may be re-opened to others.

Sign the CLA

Before your first contribution can be merged, sign the Contributor License Agreement. It takes a minute and only needs doing once.

Worth doing now rather than at the end, because pull requests from anyone who hasn't signed fail the cla-signed check automatically.

Submit for review

Open a pull request, or submit your deliverable however the issue describes. Link back to the bounty issue so the reviewer has the context.

Reviewers work through the acceptance criteria. If something can't be met, say so in the pull request with your reasoning rather than leaving it out silently.

Get paid

Once your submission is reviewed and accepted, payment is processed in USDC and $ARROW.

Arrange payment details with a core contributor in Discord. Don't post a wallet address in a public GitHub issue. Payments are typically processed within 5 business days of approval.

Tips​

  • Start with smaller bounties to build a track record in the community
  • If a bounty is CLAIMED by someone else, watch the issue anyway, because claims sometimes lapse
  • Bounties marked CLOSED are no longer available; see Previous Bounties for the archive
  • Not a developer? Plenty of bounties are Content, Growth or Local work rather than code, so filter by discipline to find them
  • If you have an idea for a bounty, post it in Discord, or open one with the bounty form. Anyone can propose one, and a core contributor reviews it before it reaches the board