Testing Open Bounty
We have a continuously deployed version tracking the
development branch live https://openbounty.status.im:444. It uses the Ropsten Ethereum testnet. Any one is welcome to use it and your help with testing CommitETH is greatly appreciated!
For testing you will need:
- a web browser (Chrome is known to work, testing with others appreciated)
- an Ethereum account on the Ropsten testnet
- a GitHub account with administrative access to one or more repositories
The developers can be reached on the
#openbounty channel in the Status riot.
- point your browser to https://openbounty.status.im:444 and click
- grant OpenBounty read access to your public profile
You should now see
Open bounties and
Manage payouts tabs. In the upper right hand corner, there should be a dropdown with
Update address and
Connecting your wallet
(instructions for MetaMask)
- install MetaMask + configure your account
Update addressfrom the top-right dropdown and click
Creating bounty issues
Before you can create bounties, you need to have administrative access to one or more repositories. These can be either in the scope of your personal user account or in the scope of a GitHub organization.
- click the
- grant CommitETH the needed additional permissions for managing repository webhooks, adding and modifying comments
- now you should see your repositories, click
Addon one. This should cause the
bountylabel to available in the repository's labels and a new webhook should now exist for the repository.
- now, add the bounty label to a new or an existing issue. This should cause CommitETH to post a new comment for the issue containing an image with text
Deploying contract, please wait
- once the contract has been mined, the comment will be updated to contain the bounty contract's address and a QR code
The GitHub comment has a QR code as an image containing the bounty contract address. The address is also on the comment as text. Use any Ethereum wallet to send ETH and/or supported ERC20 tokens to this address. After a small delay (max 5 minutes), the activity feed should show that the related bounty issue's balance increased and comment should be updated.
Open a pull request against the target repository with
Fixes: #NN in the comment where
NN is the issue number of the bountied GitHub issue. After the PR has been opened, the activity feed should show an item indicating the your username has opened a claim for the related bounty issue. The repository admin should also see the claim under
Open claims in the
Manage payouts view.
Repository admins see a listing of all open claims and bounties that have already been paid out. The
open claims listing includes unmerged claim pull requests and merged pull requests. Once a claim pull request has been merged, it is selected as the winning claim. The repository admin will still need to sign off the payout with his connected Ethereum wallet. This is done with the
Sign off button. Once the payout transaction has been mined, the activity feed view will show that the claimer received the bounty funds. All tokens and ETH will be transferred to the claimer's Ethereum address.
All bugs should be reported as issues in the OpenBounty Github repository.
Please first check that there is not already a duplicate issue. Issues should contain exact and minimal step-by-step instructions for reproducing the problem.