THORChain Developer Bounty Program

Submit Code, Earn $RUNE, Help Ship THORChain

It is unacceptable that in 2020 centralised exchanges still dominate the landscape, with manual custody of assets. The industry is in desperate need of a byzantine fault tolerant asset manager that enables permissionless liquidity. It’s time to ship THORChain.

Overview

THORChain is a public good, delivered on public money, for a public purpose. The team wish to accelerate progress, get more eyes on the code and engender more support from the community.

Currently there about a dozen internally-managed developers working on all facets of THORChain:

• THORNode
• THORChain TSS
• Bifröst (Observer and Signer)
• Midgard API
• Web-based Client (BEPSwap)
• App-based Client (Asgard Wallet)
• Infrastructure

Over time it will be necessary to transition from 100% internally-contributed to 100% externally-contributed, where the community ship code with some long-term members acting as code-janitors to ensure some level of curation into the official binary. This follows the Bitcoin approach .

The team are ready to begin this process now.

Developer Bounty Program

The above info-graphic summarises the approach and is deliberately kept simple. Anyone should be able to browse issues, provide input and then follow through with code contributions.

If the code is accepted, then the bounty will be paid. The payments are in four tiers, in an effort to keep administrative burden low. They may be adjusted over time.

1. Browse & Apply

Follow this process:

1. THORChain team will tag issues as “Bounty” with a P-Level.
2. Anyone can browse issues, and begin a discussion with the team using Gitlab comments.
3. Once settled on the task, the team will invite the assigned developer as a contributor.

P4 Bounty paying $50

2. Clone & Develop

1. Clone the repo, example: git clone https://gitlab.com/thorchain/asgard-wallet.git
2. Create a new issue-x branch (eg issue-22 for associated Issue 22): git checkout -b issue-22
3. The developer can now submit a Merge Request, tagging #22, or dropping the link to the issue in the MR description.

Submitting a Merge Request against Issue-22

3. Review & Acceptance

The Merge Request will be reviewed by one of the team and may require additional feedback and developer work.

The team will look for the following:

• Clear, readable code
• Addresses the Issue in question
• Is associated with Unit Tests (where appropriate)

The Review process may take a few days before being accepted.

4. Payment

When submitting a Merge Request, add a bnb $RUNE account.

For interest of privacy and preventing wallet-tracking, a BitMax bnb $RUNE account with associated MEMO may be used. Or alternatively, payment recipients can break linkability using BitMax accounts after being paid.

If the Merge Request is accepted, the payment will be followed up within 3 days, with the payment receipt commented in the Gitlab issue.

Other Info

In the interest of speed and flexibility, the team reserve the right to refuse merge requests, or change any part of the Developer Bounty Program at any time. However, the team wish to invest time and effort into this program in order to make it a success, so the community should expect the the program will run smoothly.

Payments will come from the Operational Reserves, which has been allocated for this purpose. There is sufficient $RUNE available.

Communication

Gitlab commenting is preferred, but the team have a telegram and discord chat available for any ongoing discussions. At this stage, a Slack channel is not required.

Telegram Dev Channel: https://t.me/thorchain_dev

Discord: https://discordapp.com/invite/V6pNp8A

Gitlab: https://gitlab.com/thorchain