Flow Hackathon Results

    This dashboard takes a dive into the hackathon's progress.

    About The Flow Hackathon

    Flow Hackathon of 2023, is a global competition for developers to supercharge the Web3 experiences they build for their communities.

    Unlike most hackathons, the Flow Hackathon is a unique event where great ideas can make it all the way to mainnet. The hackathon will happen in the following phases:

    • Phase 1 ) Education Series (February 10-20): Learn from world class blockchain and Web3 experts. Form teams and get ready to start building on the most scalable Layer 1 blockchain.
    • Phase 2 ) Build Sprint (February 21-28): This is the time to work on a prototype and deploy it to testnet. Join us from anywhere in the world virtually or at one of our sprint locations. The submission window will close on February 26. Prizes and awards will be on February 28.
    • Phase 3 ) Launchpad (March - April): Following the hackathon, the best ideas will enter a two-month launchpad where project teams can get support to reach mainnet and take their app mainstream (e.g. mentorship from top exponents in Web3, priority access to grants and venture funding).

    Dashboard Methodology

    The goal of this analysis is to take a dive into the hackathon's progress including the number of new projects, user engagement, and generated volume.

    In this dashboard, we first give a brief overview of the total number of deployed contracts in Flow, then we display the number of newly deployed contracts in 2023, and during Hackathon. On the third tab of the dashboard under the title of "activities of new contracts", we will examine the number of users who have interacted with the new contracts of the Hacktan period, as well as the number of their transactions.

    Note that we have divided the Hackathon timeframe into three parts as shown in the infographic:

    • Education Phase (February 10-20, 2023)
    • Build Sprint & Submit Phase (February 21-28, 2023)
    • Launchpad Phase (Mar 1 - Apr 30, 2023)

    Data source:flow.core.fact_events table

    db_img