What is a Bounty Hack?
A “Bounty Hack” is a hackathon in which teams of up to four developers build a decentralized application (or “dApp”) from a pre-approved list of projects. Teams will have six weeks to complete their projects*.
Each team will be assigned a mentor; a Reach developer in the Algorand community. Mentors work closely with both Reach and Algorand employees to help you succeed to your fullest potential. Your mentor will introduce themselves in Discord, where they'll be available to answer questions, recommend resources, and cheer you on throughout the hack!
The apps are presented at the end of the hack and voted on by participants. Prizes go to the top three teams. $1,000 is also awarded to the project with the most votes from the community. But the hack doesn’t end there! Teams can earn up to $2,000 in prizes and incentives just for participating! Details on prizes, payouts, and incentives are listed below.
* Teams must complete the Reach tutorial before they are allowed to select a project.
Registration Form
If you would like to participate in the Bounty Hack (individually or as a team), complete the registration form. The hack is limited to 15 teams. Submitting the form does not guarantee you a spot in the event. The Reach team will contact you via email shortly thereafter to introduce your mentor.
Projects are assigned on a first-come, first-served basis upon sharing proof of your completed tutorial with your mentor.
Key Dates
There are a few key dates to note throughout the hack. The first is Monday, March 7th. On this day, Algorand will host a kickoff call streaming live for Bounty Hack participants. Guest speakers from Reach and Algorand will review the rules and structure of the hackathon, answer questions, and provide support as you begin the Reach Tutorial. The session will be recorded for those who are unable to attend.
The kickoff call marks the start of Prep Week. During prep week, each member of your team must complete the Reach Tutorial and provide the mentors with proof of completion (either a screenshot or link to your code repository).
Once each member of your team has completed the tutorial, you will be allowed to select a project. The faster you complete the tutorial, the more projects you’ll be allowed to choose from.
| Deadline: You must send a screenshot confirming your completion of the tutorial to a mentor by midnight, on Sunday, March, 13th to continue participation in the hack. |
Throughout Prep Week, mentors will be available to answer questions and provide support in Discord. After completing the tutorial, you’ll have the remainder of the six weeks to complete your project and submit a demo video to your mentor.
|
Period |
Starts |
Ends |
Activities |
|
Prep Week |
Monday, March, 7th |
Sunday, March, 13th |
12:30 PM AEST Kickoff |
|
Tutorial Due |
Sunday, March, 13th |
Sunday, March, 13th |
Completed Tutorial Due |
|
Week 1 |
Monday, March, 21th |
Sunday, March, 27th |
Mentor Check-in |
|
Week 2 |
Monday, March, 28th |
Sunday, April, 3rd |
Mentor Check-in |
|
Week 3 |
Monday, April, 4th |
Sunday, April, 10th |
Mentor Check-in |
|
Midpoint |
Sunday, April, 10th |
Sunday, April, 10th |
Midpoint Code Submission |
|
Week 4 |
Monday, April, 11th |
Sunday, April, 17th |
Mentor Check-in |
|
Week 5 |
Monday, April, 18th |
Sunday, April, 24th |
Mentor Check-in |
|
Deliverables |
Sunday, April, 24th |
Sunday, April, 24th |
Demo Day Deliverables Due |
|
Team Voting |
Wednesday, April 27th |
Thursday, April 28th |
48-Hour Voting Period |
|
Demo Day |
Friday, April 29th |
Friday, April 29th |
12:30 PM AEST Closing Ceremony |
|
Community Voting |
Friday, April 29th |
Friday, May 13th |
Community Voting Period |
Voting and Demo Day
The voting period is from 00:00 AEST on Wednesday, April 27th to 23:59 AEST, on Thursday, April 28th. After the voting window has closed, only one key date remains: Demo Day on Friday, April 29th.
Only projects submitted before the Demo Day deliverables deadline on Sunday, April, 24th are eligible to be voted on. A voting link will be shared via Discord. Each participant gets one vote, regardless of whether or not they completed the hack. You cannot vote for your own project. The team with the most votes wins $3,000 with second- and third-place teams taking home $2,000 and $1,000, respectively. All other teams will receive $800 for completing the hack.
On Demo Day, all of the teams come together to share their projects and celebrate how much you’ve all grown as blockchain developers in just six weeks! Teams who haven’t finished their projects are welcome to attend and encouraged to share their progress. Remember, you can still earn up to $2,000 in payouts and incentives for completing your project after the deadline and creating supplemental content to help share it with the world!
First-, second-, and third-place prizes will be awarded (based on voting results) on Demo Day. The voting window for the $1,000 Community Choice award closes two weeks after Demo Day.
Teams may also complete content incentives to help Reach and Algorand share your project with the world! Descriptions and examples of content incentives are included below.
You may still receive a completion payout even if you miss the demo day deliverables deadline. We care about getting you across the finish line more than we about when it happens! All completed projects are eligible for content incentives.
Prizes and Payouts
|
Payout |
Activity |
|
$800 |
Project Completion |
|
$250 |
Write an article describing your project (including a review/testimonial of Reach as a language, compiler, and deployment tool). Our team can help you draft and tweak your post. |
|
$200 |
Join a video call with the Reach team to discuss the hack and your thoughts on the platform once your project is complete. The call will be recorded and published on our YouTube channel. |
|
Choose One |
|
|
$500 |
Turn your program into a Reach workshop (with a pull request). |
|
$750 |
Turn your program into a Reach tutorial (with a pull request). |
Project List
This list is pending approval of the Reach team and is subject to change and grow.
|
Addicting Social Network |
|||
|
Design a decentralized social network which prioritizes compulsion loops and addictive mechanics. |
|||
|
Algorand Plays Pokémon |
|||
|
A spin-off of the famous Twitch Plays Pokémon experiment. Participants can input a button press. A dedicated observer connected to an emulator, broadcasting to Twitch; perhaps a payment needs to go for more than one frame. The pot goes to a charity and/or the pot accumulates until the observer sends a "cash-in" message, which pays the last sender; cash-ins happen when you detect (in the emulator) events related to progress in the game (e.g. winning battles, capturing Pokemon, and defeating gym leaders). |
|||
|
Arbitrary-Sized Tanda Club |
|||
|
A tanda-style loan club with a variable number of participants. |
|||
|
Basic DAO |
|||
|
A basic DAO in which members vote on whether to call an external function with a certain amount of value. |
|||
|
Battleship |
|||
|
A battleship-like game where you cryptographically commit to the moves. If you lie, you lose. |
|||
|
Blackjack |
|||
|
A blackjack-like game with asymmetric payouts based on proximity to 21. |
|||
|
Bluffing Game |
|||
|
Budget Tic-Tac-Toe |
|||
|
It's tic-tac-toe, but the goal is not just to win, but to stay within a budget. Each move comes at a cost equivalent to the number of wins attainable in that space. A draw splits the pot without returning your initial stake. |
|||
|
Chess Variant With a Wager |
|||
|
Recreate a variant of chess, introducing a wager. |
|||
|
Compile-Time Specified N-Ticket Raffle |
|||
|
Raffle in which the window for buying tickets is dictated by compile time. |
|||
|
Conflux Plays Pokémon |
|||
|
A spin-off of the famous Twitch Plays Pokémon experiment. Participants can input a button press. A dedicated observer connected to an emulator, broadcasting to Twitch; perhaps a payment needs to go for more than one frame. The pot goes to a charity and/or the pot accumulates until the observer sends a "cash-in" message, which pays the last sender; cash-ins happen when you detect (in the emulator) events related to progress in the game (e.g. winning battles, capturing Pokemon, and defeating gym leaders). |
|||
|
Editor Plugin Development |
|||
|
Extend and enhance the range of IDEs and development tools available for the Reach platform. |
|||
|
Hidden Role Game |
|||
|
Build a hidden role game, like The Resistance (also called "social deduction" games). |
|||
|
Horoscope |
|||
|
A horoscope application which calls out to an third-party oracle. |
|||
|
Hot Potato |
|||
|
N-player hot-potato where each player adds randomness and wins the pot when the seed % N is their index. |
|||
|
Insurance DApp |
|||
|
Build an insurance dApp in which subscribers submit claims and a trusted party can approve or deny. |
|||
|
Kickstarter with Refund Bonuses |
|||
|
Build a crowdfunding platform with refund bonuses. |
|||
|
Le Chat Noir |
|||
|
Le Chat Noir with a wager. |
|||
|
Looping Rock, Paper, Scissors (RPS) |
|||
|
A variant of rock, paper, scissors in which moves are submitted in batches (to keep transaction costs low) and the first move alternates between players "Alice" and "Bob". |
|||
|
Marlowe |
|||
|
A Marlowe-like application for deriving traditional financial instruments. |
|||
|
Mancala |
|||
|
Build a game of mancala in which players cryptographically commit their moves to the blockchain. |
|||
|
Microblog |
|||
|
A microblog in which members can post and subscribe to various streams of content. |
|||
|
Morra |
|||
|
Generalize a game of rock, paper, scissors into a game of morra, introducing a wager. |
|||
|
N-Men's Morris |
|||
|
Generalize a game of tic-tac-toe/noughts and crosses into n-men's morris (traditionally "nine men's moris"). |
|||
|
N-Player Poker |
|||
|
When Player A draws a card, they submit a committed number [0, N). Then every other player sends them a card. When they reveal their hand, they reveal the commitments that led to the cards they got, thus their cards remain secret during the game, but the rest of the players can speculate about what they have. They can never send the same card twice. |
|||
|
NFT Auction |
|||
|
An NFT with built-in auction mechanics to facilitate its sale/purchase. |
|||
|
Quadratic Crowdfunding |
|||
|
Crowdfunding platform which relies on quadratic voting like Gitcoin. |
|||
|
Quantum Tic-Tac-Toe |
|||
|
Quantum tic-tac-toe with a wager. |
|||
|
RSVP DApp |
|||
|
Build an RSVP dApp with a trusted attendance oracle. |
|||
|
Settlers of Catan |
|||
|
Settlers of Catan-like game with on-chain resource trading. |
|||
|
Single Deadline Crowdfunding Campaign |
|||
|
Crowdfunding campaign with single deadline (like Kickstarter). |
|||
|
Staged-Approval Crowdfunding |
|||
|
Crowdfunding campaign with staged approval of disbursing funds. |
|||
|
The Optimization Market |
|||
|
The funder proposes a function `f : A -> Int` and a deadline. Whoever submits an `A` that maximizes the value of `f` wins the prize. This can be used for NP-complete functions, which would be valuable. |
|||
|
The Price is Right |
|||
|
Pick a number, submit guesses, reveal the number, then reveal the winning guess. |
|||
|
Timed Auction: Highest Bidder Wins |
|||
|
A timed auction in which the highest bidder wins. |
|||
|
Transferable-Royalty NFT |
|||
|
An NFT for which the initial creator is paid a royalty with each purchase. |
|||
|
Ultimate Tic-Tac-Toe |
|||
|
Ultimate tic-tac-toe with a wager. |
|||
|
Unique Numbers Game |
|||
|
Players submit a number within a predetermined range. Players who submit a unique number get a percentage of the pot. |
|||
|
Vickrey Auction |
|||
|
An auction in which the highest bidder wins, but pays the second-highest bid. |
|||
|
Web Browser |
|||
|
Web-based application browser with annotation functionality and customizable compile-time parameters. |
|||
|
Zero-Randomness Board Game |
|||
|
Build a zero-randomness board game like Caylus or Hansa Teutonica. |
Team Profile
Team Profile
Each team that is assigned a project must agree to complete a "Meet the Team" profile. This means joining the Reach team for a brief recorded call to tell us about yourselves and your project. We’ll follow up with a few written questions. You can use your finished profile to raise support for your project and campaign for the $1,000 Community Choice Award.
Click here to read a "Meet the Team" article from the Decentralized Umoja Bounty Hack. You can watch a team profile video below:
Demo Video
What’s in a Demo Video?
Your demo video should be about three minutes long and include the following:
- Top-level overview of your completed application. Does it do what it's supposed to do?
- Walkthrough of the back end and middleware or smart contract configurations.
- Demo of your completed application running on Algorand.
Consider answering the following questions with any remaining time:
- What challenges did you face in putting the whole ensemble together?
- What would you do to add to/expand upon your app if given the chance?
|
Deadline: you must send Demo Day deliverables (your completed demo video and a link to your GitHub repository) to the mentors by midnight, on Sunday, April, 24th, to be eligible for voting and qualify for a first-, second-, or third-place prize. |
Once the deadline to submit your project for Demo Day has passed, the mentors will share a link to the project showcase in Discord. With this link, you can access the demo video and code repository for each project and vote on a winner!
Video Standards
If and when you appear on camera for the kickoff call, team profile, closing ceremony, and retrospective interview, we ask that you adhere to the following video recording standards:
-
Adjust the light behind you so you don’t look like you’re glowing.
-
The light in front of you should be bright enough to see you clearly.
-
Adjust your camera (or chair) height so your full head and shoulders are in frame.
-
Angle your camera so you’re looking straight ahead.
-
If you wear glasses, be mindful of the glare from your screen.
-
Don’t use a virtual background. We can apply one in post-production, as needed.
Development Article
Draft an article on Dev.to or Medium, detailing your Bounty Hack journey from start to finish and providing an overview of your finished project. Include a review or testimonial of the Reach platform (i.e. the programming language, compiler, and deployment tool). Share a link to your draft in a Google Doc with both your mentor and Estefania Ochoa via email. Make sure you configure the sharing permissions as shown below.
-1.png?width=804&name=unnamed%20(3)-1.png)
Don’t worry about making it perfect in your rough draft. Once submitted, Creative Marketing Director Michael Pirovano will add comments and suggest revisions.
Payout: $250
Examples
- Hamza Karabağ, “How did I write my first dApp in Reach?” (Bounty Hack: Genesis)
- Chris Baunach, “The Reach Algorand Bounty Hack” (Bounty Hack: Genesis)
- Nick Burka, “Developing Multi-Blockchain web-dApps Using Reach: ‘serious’ Rock Paper Scissors” (Bounty Hack: Genesis)
Article Structure
Consider the points below when completing your article:
- Establish the stakes; give readers context for what the Bounty Hack is and what you were trying to accomplish in the span of six weeks.
- Give readers context for how you were able to build a dApp in such a short amount of time using Reach.
- What surprised you about building in Reach?
- How did Reach make it easier to build your app (and what can we do to make it even easier)?
- What did you do to dive into your project (e.g. review documentation, create diagrams, etc.).
- Did you complete your project on time?
- Project overview; include the primary features/functions of your app.
- Development journey; walk us through how your project came together.
- On day one...
- What was going through your head (e.g. questions or concerns)?
- What did you do to dive into your project (e.g. review documentation, create diagrams, etc.)?
- The first time you asked for help (either from your mentor or from other community members), what were you struggling with?
- What were the most challenging obstacles to overcome (and how did you overcome them)?
- Given the chance to enhance or expand upon your app, what features/functions would you add?
- Any closing thoughts on your project or the Bounty Hack experience?
- Gushing testimonial about how building dApps in Reach changed your life (optional).
-
What is a Bounty Hack?
Open or Close
A “Bounty Hack” is a hackathon in which teams of up to four developers build a decentralized application (or “dApp”) from a pre-approved list of projects. Teams will have six weeks to complete their projects*.
Each team will be assigned a mentor; a Reach developer in the Algorand community. Mentors work closely with both Reach and Algorand employees to help you succeed to your fullest potential. Your mentor will introduce themselves in Discord, where they'll be available to answer questions, recommend resources, and cheer you on throughout the hack!
The apps are presented at the end of the hack and voted on by participants. Prizes are awarded to the top three teams. But the hack doesn’t end there! Teams can earn up to $2,100 in prizes and incentives just for participating! Details on prizes, payouts, and incentives are listed below.
* Teams must complete the Reach tutorial before they are allowed to select a project.
-
Registration Form
Open or Close
If you would like to participate in the Bounty Hack (individually or as a group), complete the registration form. The hack is limited to 15 teams. Submitting the form does not guarantee you a spot in the event. Teams may select their project on a first-come, first-served basis upon showing proof of tutorial completion to their mentor.
.
-
Key Dates
Open or Close
There are a few key dates to note throughout the hack. The first is Monday, October 25th. On this day, Algorand will host a kickoff call streaming live for Bounty Hack participants. Guest speakers from Reach and Algorand will review the rules and structure of the hackathon, answer questions, and provide support as you begin the Reach Tutorial. The session will be recorded for those who are unable to attend.
The kickoff call marks the start of Prep Week. During prep week, each member of your team must complete the Reach Tutorial and provide the mentors with proof of completion (either a screenshot or link to your code repository). Once each member of your team has completed the tutorial, you will be allowed to select a project. The faster you complete the tutorial, the more projects you’ll be allowed to choose from.
Deadline: You must send a screenshot confirming your completion of the tutorial to a mentor by midnight, on Sunday, October 31 to continue participation in the hack. Throughout Prep Week, mentors will be available to answer questions and provide support in Discord. After completing the tutorial, you’ll have the remainder of the six weeks to complete your project and submit a demo video to your mentor.
Week
Starts
Ends
Activities
Prep Week
Monday, October 25
Sunday, October 31
19:00 SAST Kickoff
Tutorial Due
Sunday, October 31
Sunday, October 31
Completed Tutorial Due
Week 1
Monday, November 1
Friday, November 7
Mentor Check-in
Week 2
Monday, November 8
Friday, November 14
Mentor Check-in
Week 3
Monday, November 15
Friday, November 21
Mentor Check-in
Midpoint
Monday, November 21
Friday, November 21
Midpoint Code Submission
Week 4
Monday, November 22
Friday, November 28
Mentor Check-in
Week 5
Monday, November 29
Friday, December 3
Mentor Check-in
Deliverables
Sunday, December 6
Sunday, December 6
Demo Day Deliverables Due
Team Voting
Wednesday, December 8
Thursday, December 9
48-Hour Voting Period
Demo Day
Friday, December 10
Friday, December 10
19:00 SAST Closing Ceremony
Community Voting
Wednesday, December 8
Friday, December 24
Community Voting Period
-
Voting and Demo Day
Open or Close
The voting period is from 12:00 AM on Wednesday, December 8th to 11:59 PM, on Thursday, December 9th. After the voting window has closed, only one key date remains: Demo Day on Friday, December 10, 2021.
Only projects submitted before the Demo Day deliverables deadline on Sunday, December 6 are eligible to be voted on. A voting link will be shared via Discord. Each participant gets one vote, regardless of whether or not they completed the hack. You cannot vote for your own project. The team with the most votes wins $1,500 with second- and third-place teams taking home $1,250 and $1,000, respectively. All other teams will receive $600 for completing the hack.
On Demo Day, all of the teams come together in a Zoom meeting to share their projects and celebrate how much you’ve all grown as blockchain developers in just five weeks! Teams who haven’t finished their projects are welcome to attend and encouraged to share their progress. Remember, you can still earn up to $1,000 in payouts and incentives for completing your project after the deadline and creating supplemental content to help share it with the world!
First-, second-, and third-place prizes will be awarded (based on voting results) on Demo Day. The voting window for the $1,000 Community Choice award closes two weeks after Demo Day.
Teams may also complete content incentives to help Reach and Algorand share your project with the world! Descriptions and examples of content incentives are included below.
You may still receive a completion payout even if you miss the demo day deliverables deadline. We care about getting you across the finish line more than we about when it happens! All completed projects are eligible for content incentives.
-
Prizes and Payouts
Open or Close
.png?width=512&name=unnamed%20(2).png)
Deadline: prizes and incentives are paid out in USDCa* for participants in the United States and in ALGO internationally. Reach and Algorand jointly reserve the right to refuse payment of prizes and incentives to apps which fail to meet completion requirements. * USDCa refers to the USDC stablecoin on an Algorand-compatible wallet.
Payout
Starts
$600
Project Completion
$250
Write an article describing your project (including a review/testimonial of Reach as a language, compiler, and deployment tool). Our team can help you draft and tweak your post.
$500
Join a Zoom call with the Reach team to discuss the hack and your thoughts on the platform once your project is complete. The call will be recorded and published on our YouTube channel.
Choose One
$500
Turn your program into a Reach workshop (with a pull request).
$750
Turn your program into a Reach tutorial (with a pull request).
-
Project List
Open or Close
This list is pending approval of the Reach team and is subject to change and grow.
Addicting Social Network
Design a decentralized social network which prioritizes compulsion loops and addictive mechanics.
Algorand Plays Pokémon
A spin-off of the famous Twitch Plays Pokémon experiment. Participants can input a button press. A dedicated observer connected to an emulator, broadcasting to Twitch; perhaps a payment needs to go for more than one frame. The pot goes to a charity and/or the pot accumulates until the observer sends a "cash-in" message, which pays the last sender; cash-ins happen when you detect (in the emulator) events related to progress in the game (e.g. winning battles, capturing Pokemon, and defeating gym leaders).
Arbitrary-Sized Tanda Club
A tanda-style loan club with a variable number of participants.
Basic DAO
A basic DAO in which members vote on whether to call an external function with a certain amount of value.
Battleship
A battleship-like game where you cryptographically commit to the moves. If you lie, you lose.
Blackjack
A blackjack-like game with asymmetric payouts based on proximity to 21.
Bluffing Game
Budget Tic-Tac-Toe
It's tic-tac-toe, but the goal is not just to win, but to stay within a budget. Each move comes at a cost equivalent to the number of wins attainable in that space. A draw splits the pot without returning your initial stake.
Chess Variant With a Wager
Recreate a variant of chess, introducing a wager.
Compile-Time Specified N-Ticket Raffle
Raffle in which the window for buying tickets is dictated by compile time.
Editor Plugin Development
Extend and enhance the range of IDEs and development tools available for the Reach platform.
Hidden Role Game
Build a hidden role game, like The Resistance (also called "social deduction" games).
Horoscope
A horoscope application which calls out to an third-party oracle.
Hot Potato
N-player hot-potato where each player adds randomness and wins the pot when the seed % N is their index.
Insurance DApp
Build an insurance dApp in which subscribers submit claims and a trusted party can approve or deny.
Kickstarter with Refund Bonuses
Build a crowdfunding platform with refund bonuses.
Le Chat Noir
Le Chat Noir with a wager.
Looping Rock, Paper, Scissors (RPS)
A variant of rock, paper, scissors in which moves are submitted in batches (to keep transaction costs low) and the first move alternates between players "Alice" and "Bob".
Marlowe
A Marlowe-like application for deriving traditional financial instruments.
Mancala
Build a game of mancala in which players cryptographically commit their moves to the blockchain.
Microblog
A microblog in which members can post and subscribe to various streams of content.
Morra
Generalize a game of rock, paper, scissors into a game of morra, introducing a wager.
N-Men's Morris
Generalize a game of tic-tac-toe/noughts and crosses into n-men's morris (traditionally "nine men's moris").
N-Player Poker
When Player A draws a card, they submit a committed number [0, N). Then every other player sends them a card. When they reveal their hand, they reveal the commitments that led to the cards they got, thus their cards remain secret during the game, but the rest of the players can speculate about what they have. They can never send the same card twice.
NFT Auction
An NFT with built-in auction mechanics to facilitate its sale/purchase.
Quadratic Crowdfunding
Crowdfunding platform which relies on quadratic voting like Gitcoin.
Quantum Tic-Tac-Toe
Quantum tic-tac-toe with a wager.
RSVP DApp
Build an RSVP dApp with a trusted attendance oracle.
Settlers of Catan
Settlers of Catan-like game with on-chain resource trading.
Single Deadline Crowdfunding Campaign
Crowdfunding campaign with single deadline (like Kickstarter).
Staged-Approval Crowdfunding
Crowdfunding campaign with staged approval of disbursing funds.
The Optimization Market
The funder proposes a function `f : A -> Int` and a deadline. Whoever submits an `A` that maximizes the value of `f` wins the prize. This can be used for NP-complete functions, which would be valuable.
The Price is Right
Pick a number, submit guesses, reveal the number, then reveal the winning guess.
Timed Auction: Highest Bidder Wins
A timed auction in which the highest bidder wins.
Transferable-Royalty NFT
An NFT for which the initial creator is paid a royalty with each purchase.
Ultimate Tic-Tac-Toe
Ultimate tic-tac-toe with a wager.
Unique Numbers Game
Players submit a number within a predetermined range. Players who submit a unique number get a percentage of the pot.
Vickrey Auction
An auction in which the highest bidder wins, but pays the second-highest bid.
Web Browser
Web-based application browser with annotation functionality and customizable compile-time parameters.
Zero-Randomness Board Game
Build a zero-randomness board game like Caylus or Hansa Teutonica.