search

keep-network / Protect-Privacy-Hackathon

Keep & Protect Privacy Gitcoin Hackathon
1 stars 0 forks source link

Build a Creative Privacy Feature on Keep Network #1

Open creckhow-zz opened 4 years ago

creckhow-zz commented 4 years ago

Prize Title

The Keep Privacy Prize

Prize Bounty

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

Challenge Description

Keep judges are open to anything using Keep and/or tBTC, but we’ve got 4 types of submissions we’d prefer to see:

  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 our co-sponsoring friends at ECC and work on bridging ZEC and ETH with a Zcash relay, based on Summa’s BTC relay and our 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. We’ll be considering all submissions that meet the requirements!

Submission Requirements

Requirements:

Some Resources:

Submission Deadline

July 6th @ midnight - submission deadline [edit: Gitcoin privacy hackathon extended 1 week!]

Judging Criteria

We'll be looking for technical value-add as well as a great experience: we 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 we’ll be judging in collaboration with our ECC co-sponsor judges.

Winner Announcement Date

July 2nd - Hackathon winner announced (right before June Play for Keeps winners)

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.004 ETH (0.95 USD @ $236.66/ETH) attached to it.

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Cancelled

The funding of 0.004 ETH (0.94 USD @ $235.81/ETH) attached to this issue has been cancelled by the bounty submitter

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.001 ETH (0.22 USD @ $223.44/ETH) attached to it.

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 0.001 ETH (0.22 USD @ $223.44/ETH) attached to it.

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

This issue now has a funding of 90000.0 KEEP attached to it as part of the keep-network fund.

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work has been started.

These users each claimed they can complete the work by 1 year, 7 months ago. Please review their action plans below:

1) zyra-zia has started work.

tBTC and tornado cash implementation 2) andrian90 has started work.

Waw 3) benesjan has started work.

tBTC support for tornado.cash 4) fragmnt has started work.

Privacy-centric dApp in the works 5) mul1sh has started work.

An integration of the Keep random beacon to allow users to privately fund gitcoin grants via bitcoin 6) sunnyrk has started work.

I will create a private wallet using keep 7) apoorvlathey has started work.

Swap BTC to tBTC and transfer to ETH address Anonymously via Umbra Protocol.

Learn more on the Gitcoin Issue Details page.

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Started 3. Submitted 4. Done

Work for 90000.0 KEEP (10800.0 USD @ $0.12/KEEP) has been submitted by:

  1. @benesjan
  2. @fragmnt
  3. @sunnyrk
  4. @zyra-zia
  5. @codinmaster

@shadowfiend please take a look at the submitted work:

Shadowfiend commented 4 years ago

@fragmnt we can't seem to get to your linked repo (https://github.com/fragmnt/keepsafe). Any chance it's not public yet?

janus commented 4 years ago

@creckhow Please change this line, July 2nd - Hackathon winner announced (right before June Play for Keeps winners)

gitcoinbot commented 4 years ago

Issue Status: 1. Open 2. Cancelled

The funding of 90000.0 KEEP (10800.0 USD @ $0.12/KEEP) attached to this issue has been cancelled by the bounty submitter

benesjan commented 4 years ago

Hello, why was the bounty canceled?

mhluongo commented 4 years ago

It wasn't! We're trying to pay out through profile accounts, since Gitcoin had issues splitting the payments

apoorvlathey commented 4 years ago

Glad to know that @mhluongo . Can you share which projects won the prize?

mhluongo commented 4 years ago

Letting @Shadowfiend get this resolved with @gitcoinbot, then we'll ping you guys. It was a close one, loved seeing everyone's work!

mhluongo commented 4 years ago

@CodinMaster @benesjan @zyra-zia we're discussing combining community efforts to take a tBTC Tornado implementation to mainnet, and maybe even find a way to integrate it with Umbra- if you're interested hop in to the Discord :)