Binance Futures Competition for Africa

Go to event page

About Keep Hackathon

Keep judges are open to anything using Keep and/or tBTC, but there are 4 main types of applications:

  1. Randomness for privacy – Keep’s random beacon allows for robust randomness in decentralized applications, tBTC being the first example. In tBTC, signer selection is done through the random beacon, which prevents collusion in deposit federations. This challenge asks you to build any dApp or integration using Keep’s random beacon.
  2. tBTC privacy hacks – tBTC is a Bitcoin bridge on Ethereum, it’s a 1:1 BTC supply peg ERC-20, allowing Bitcoiners to use DeFi and other decentralized applications. Privacy is a huge use case, which has been less explored so far. Build a dApp that would help protect BTC user’s privacy using tBTC. The sky’s the limit here. Tornado Cash + tBTC? A UTXO mixer? Privacy is a great way to convince Bitcoiners to use Ethereum!
  3. Hack a Zcash relay for tZEC – Bitcoin isn’t the only coin that can use tBTC’s bridge spec. Join with co-sponsoring friends at ECC and work on bridging ZEC and ETH with a Zcash relay, based on Summa’s BTC relay and recent Blake2 pre-compile EIP.
  4. Signature test vector library – Come up with a set of test vectors that will work across different Bitcoin-based chains. Valid transactions that will work on Bcash, but not Bitcoin? How about SegWit, but not Zcash? This is a challenge the team faced when working on tBTC, and the creation of a common test vector repository or library would help strengthen interop bridges like tBTC and tZEC. Also, don’t forget you can get creative with Keep and tBTC. The team will be considering all submissions that meet the requirements!

Additional Information


Grand Prize of 50,000 KEEP (and instant eligibility to win up to 50k more in June’s Playing for Keeps)

2 runner up prizes of 20,000 KEEP

Submission Requirements


  • Must be open source
  • Show us the GitHub & on-chain (Ropsten)
  • Demo strongly recommended

Some Resources:

Key dates:

Submission Deadline June 29th – submission deadline

Winner Announcement Date: July 2nd – Hackathon winner announced (right before June Play for Keeps winners)

Judging Criteria

Judges will be looking for technical value-add as well as a great experience: want to see usability, utility, and creativity. On the technical side, the fewer obvious attacks your project has, the better. Good, clean architecture and a good API (when applicable) will also be weighed.

If you choose challenge \#3 or #4 it will be judging in collaboration with ECC co-sponsor judges.