dHack pilot summary part 1: What we did

Part 1: What we did

The first phase of dHack – proof of concept and validation has been established at bitfwd, ETHIndia, and ETHBerlin. We created a lot of buzz around dHack and DAOstack as participants understood the value proposition of a decentralized hackathon and the inconsistency of having a centralized committee that picks winners. We received a lot of good feedback, and a fair share of negative one as well. Most of it around the onboarding process, which eventually became too long.

dHack is on a trajectory to become a standard for hackathons in the Crypto/Blockchain space, and if we get things right on a wider scale, this could also be valuable for companies and organizations outside the ecosystem.

The purpose of this post is to get more people involved in dHack, help brainstorm ideas, create content, implement dHacks, and shape and spec out of what dHack 1.0 would look like.

dHack value proposition (to DAOstack / GenDAO)

  • Decision making at scale. dHack confined a lot of decisions into a constrained period of time. mimicking what a scalable DAO would look like.
    • User behavior (Staking)
    • System behavior (Alchemy stress test)
  • Exposure: devs, entrepreneurs, general ecosystem, social.
  • Kickstarting the staking network

Some Validation:

Some statistics on ETHBerlin:


  • First - I felt like there wasn’t enough cooperation/support from DAOstack or GenDAO members either in Berlin or online

    • Ultimately it is my fault, Should have made more effort to connect GenDAO members to the goals of dHack, why it’s important for Genesis, and how could they help.
  • dHack -> GenDAO bridge/funnel

    • How do we get participants of dHack to onboard to Genesis?
  • Onboarding - The Critical issue. due to the use of Ether.cards we were confined to a tedious onboarding process, and so we lost a lot of people. (Combined with 0 internet at Dappcon)

    • Right before ETHBerlin we managed to deploy a MUCH better solution in the form of scannable QR codes that send you directly to the redeem scheme. Paste your voting address and you’re good to go.
  • Gas Funding - Cost almost 4ETH to fund all participating addresses with Gas-Money, and there were plenty of gas related issues with the redeem function.

    • Possible solutions: GSN (temp), or Abridged for a more permanent solution
  • Everything needs to be inside Alchemy

  • This proposal was very successful. a brief explanation about - How to propose (Template), how staking works, and a bit about holographic consensus. I boosted it as soon as the dHack opened and it proved to be a great way to teach users about how the system works, proposal format, and holographic consensus (Staking!!)

  • From both ETHBerlin and ETHIndia you learn that Alchemy is counter-intuitive to say the least.

  • Imo we will need to add centralized information fields inside Alchemy.

  • If a user clicks out of Alchemy to read an explanation or a blog post, slim chances that he will come back

Part 2 will come out soon

Explaining a bit about where we want to go, the vision, and how to get there.


Admin note: moved to Genesis category.

Part 2: Where we want to go

In this section, I detail a bit about where I see dHack in the future. This post, it’s feedback and replies will be the basis of a blog post outlining the future of dHack.


Become the ultimate hackathon judging committee, to be used by hackathon facilitators and participants who wish to get the best curation, exposure, and mentorship for their events and products.

I see two main ways this could go, both can exist together.
(Would love some feedback here)

One Mega-dHack ongoing DAO:

  • Each hackathon would propose a new ‘dHack scheme’
    • Mint new reputation for event participants
    • Contribute funds to the Scheme/DAO
  • The DAO will approve their request, accept their funds, and grant their participants reputation
  • Open Qs:
    • Scheme specific reputation/Total DAO.
    • Reputation distribution/Inflation

Create your own dHack

  • Self-Served DAOcreator with documentation, support, and best practices on how to run the dHack.
  • Anyone will be able to easily create a dHack DAO for their event.
  • Pre-set parameters (Fast, Medium, extended) + option to setup your own.
  • Reputation distribution
    • Upload JSON file
    • Integrate Kickback
  • Support from the GenDAO/dHack Community

Open questions:

Non tech improvements to dHack. Mostly issues that rose from dHack ETHBerlin and ETHIndia.

  • How do we get GenDAO more involved with dHack events as they happen?
  • How do we create an onboarding funnel of dHack participants to Genesis (or DevDAO?)
  • How do we create a better first impression of Alchemy, pick interests, etc


short and mid term opportunities for offline, online, and ongoing physical dHacks.

  • DevFolio - InOut 6.0 Hackathon (Oct 19-20)
    The local company of ETHIndia. They have between 40-60 hackathons planned in Universities during the fall Semester (Oct-Apr)
  • ETHGlobal, ETHWaterloo (Nov 8-10).
    Further collaboration in 2020:
    • ETHGlobal Online Virtual Hackathon with dHack
    • ETHGlobal ongoing dHack DAO (A DAO that includes all ETHGlobal physical events)
  • ETHDenver - the largest ETH hackathon (1,600) we are proposing the opentrack to be dHack exclusive. (~Feb)
  • GitCoin - Run an online Hackathon/Bounty.
  • Bitfwd - use dHack as part of the Market penetration plan for China.

dHack used Alchemy’s existing stack and repurposed it for a hackathon. If we want to capture the value of ethereum hackathons and grant distributions, work has to be made in three main Verticals:

DAO Design – How do you create a friction-minimized ongoing hackathon.

One DAO - multiple physical hackathons

  • New event init process ETHGlobal(n)
    • Scheme registrar proposal:
      • ETHGlobal(n) hackathon reputation minting (Inflation)
      • Create new RepFromToken contract
        • Rep allocation x1.1-x2 ETHGlobal(n-1)
          • JSON rep holder list
          • Read from Kickback contract
          • Use POAP
  • RepFromToken contract
  • RepFromToken read POAP holder list.
  • DAO parameters (In the case of high inflation these will be significantly adjusted compared to what we have today)
    • Early voters reputation loss percentage
    • Successful proposer reputation gain

New Scheme (Best M of N/Secretary problem)

  • Competition Scheme
    • Define in Scheme init (Scheme registrar proposal)
      • Init time.
      • N - number of winners
      • T - finish time.
    • At T time, N winners from boosted will be picked by order of best Yes/No Vote ratio.
    • Rest of the proposals fail
    • Scheme deletes itself?
  • Competition+phase scheme
    • Define in Scheme init (Scheme registrar proposal)
      • Init time
      • Proposal time - PT (Instead of Regular queue time)
      • Stake time - ST (Instead of Pending time to boost)
      • Vote time - VT (Instead of Boosted voting period)
    • Each phase has it’s defined time
      • Proposals can only be made during the proposal time
      • Staking on proposals can only be done during

Any time defined proposal puts a question the quiet-ending time. A solution could be making it a very short period of time, as we expect peak interests around phase transition times


  • Clear participation instructions Inside Alchemy

    • Onboarding
      • Videos
      • full how-to guide
      • How to win
      • Staking
        • Deep dive into how staking works
        • Examples
        • Staking positions
        • Staking “politics”
        • How to make money from staking.
        • Staking cases and how you can “navigate” the staking challenge
  • Website: Check out these designs by collin

    Redo the website, this is what we currently have: dhack.io. I’ve been trying to follow @collins designs in webflow but

    • a) I’m not a designer and
    • b) I think it’s time for something a bit more serious if we want to take over the world.
  • The website should include:

Please feel free to comment on any of the topics here, should anything change