How to create a bounty on

Step 1

Please create a new issue explaining the details of the bounty via YOUR Own Github.

The github issue should include a detailed description of this bounty. As detailed as possible.


Step 2

Go to to create a bounty. Or you can go directly to (login needed).

Step 3

Put the github issue URL in the blank, press “Enter”. You will see the details are automatically updated on this page.

Step 4

a. You can add more details (like bounty requirements, skills needed, bounty reward and bounty duration) in this form.

*All the details can be edited after the bounty is published!

b. For “Key works” section, please give reference to all the skills developers need to complete the bounty, for their convenience to find best-fit bounties.

c. For bounty reward, currently all the ERC-20 tokens, like ETH, USDC, USDT, etc., are supported. After entering the token amount, its USD value will be calculated instantly.

d. Bounty duration is recommended to be at least 60 days for developers to build. If the bounty finds no suitable hunter after the estimated end time, you can prolong the bounty duration or terminate the bounty.

Step 5

After setting up the details, please connect your wallet via Metamask. All of the major ERC-20 tokens are supported.

The prizes will be reserved for the bounty until the bounty is finished or terminated by the bouty publisher.


  • Please make sure you have enough balance for locking the rewards.
  • 10% of the reward will be deducted as smart contract fee for the bounty earner. So if the reward is 100 USDT, he/she will ultimately receive 90 USDT. No fee charged from the bounty poster.

Step 6

If someone completed your bounty, he/she will submit a Pull Request at your github PR. If the solution is satisfying enough, you can merge the PR and the status will be updated to HackerLink at the same time.

Then congrats! You have a bounty completed successfully!

A bounty explained workshop

A bounty is a great way to: 1. invite helpers to solve issues that’s important while not that urgent; 2. help developers know your tech stack well, and increase the influence of your tech stack/github/brand.

To help the developers better understand the bounty, every bounty poster needs to have a workshop to explain the bounties. The themes should include:

  • Introduce bounties posted, including: what are the bounties, the background of each bounty, who are the bounty posters/funders, rewards, so on and so forth.
  • Goals: what’s the bounty aiming for? What’s the ideal output you want to see from the developers?
  • Requirements: what’s the skills needed? What skills are necessarily included in the final output? (like do you want the developers to use specific tech stacks in the PR they give?)
  • Developer resources.
  • Support: if developers encounter problems, how can they ask for help? (Usually we recommend the developers and the bounty posters communicate in the bounty issue page on github via comments!)

Our operations team will help you arrange the workshop and it will e live streamed at DoraHacks Youtube channel.

We have a good example at

A leading global hacker organization.