Hackathon Structure

Open Discussion on Hackathon Structure


  • Provide venue to network, learn, and discover the chicago web3 community
  • Connect chicago’s web3 community with the greater web3 community
  • Create a fun but productive environment

The Value Prop for Hackers:

  • Networking and meeting opportunities with industry professionals and potentially entering the space
  • Learning about the bleeding edge of web3 and the unique properties of blockchain technology
  • Present own projects to large group of engineers
  • Pitching to potential investors?
  • Some food/snacks/drinks
  • Having fun building and potentially winning rewards
  • Access to after-hour side events


  • The branding and theme of the event is Chicago world fair, how do we want to incorporate this?

Target audience:

  • 18+ Hackers to win bounties require KYC, Code of Conduct, and Photo/Video Agreements
  • Software Engineers
  • Creatives who are building in the space
  • Audience should be technical to get the most out of the event


  • Oak Room in M Club, Willis Tower
  • Side Events locations

Available Times:

  • Not 24hs available, i think from morning to 10pm probably - decided
  • Are there hacker houses? - open for discussion


  • target of a 5 figure collection of bounties - decided
  • bounties are in usd - open for discussion
  • Chicago World Fair NFT collection or something similar for art blocks or similar - open for discussion
  • Arbitrum Stylus CTF - take existing challenges in https://ethernaut.openzeppelin.com/ or similar , convert to stylus challenges - open for discussion
  • Hackers Favorite reward? - open for discussion
  • Best use of Wormhole? - open for discussion
  • Best Web3 solution for real world? - open for discussion
  • Nouns Dao hack? - open for discussion
  • Education based project? - open for discussion
  • User experience improvement for Staking? - open for discussion

Digital Operations:

  • Devpost for submitting hackathon entries - open for discussion
  • Notion for day of event information and scheduling - decided
    • requires migration to our own notion
  • Gitbook for hackathon agreement documents - open for discussion
  • How to organize day of hacker communication? - open for discussion
  • Hacker Tools? Testnet Access? What do hackers need to use?
  • Streaming and video done by local AV and StreamETH


  • Hacker Tickets will have a cost associated - decided
  • Hacker Tickets will cost 100 dollars or less - decided
  • Will there be subsidized tickets? - open for discussion
    • maybe we provide a waitlist? work with sponsors, school groups to sponsor hacker tickets?
    • give out free tickets somehow at pre-events?

Dev Engagement:

Day of Event Structure:

  • Ticketing

    • code of conduct
  • Finding Teams:

    • How do we facilitate this?
    • Open mic to find team members?
    • Speed dating for organizing teams?
  • Workshops:

    • Buildl Guildl?
    • Holaplex?
    • Arbitrum?
    • ETHStaker?
    • Wormhole?
  • Speaking Events:

    • Learn about L2s
    • Learn Staking
    • Protocol Guild - James might present
  • Volunteer Types:

    • Judge - open discussion
    • Mentor - genius bar?
  • Submissions

    • Cutoff at 9:30am Sunday 17th
    • Devpost
    • Github
    • Video??
  • Demos

    • Sunday the 17th, 10am-12:30pm?
    • 5min presentations + 5 min max transition?
    • there are 3 core rooms maybe 2 for demos 36 presentations in total max, maybe cut to 20? Should everyone be able to present?
    • How do people vote? judging on winners?
  • Bounties

    • 1 person from each team requires KYC and is responsible for distributing to their members
    • Have bounty rules before the event
    • Requirements for the Bounty
    • only 1 submission per bounty
    • requires devpost upload

Post Event

  • sending out videos
  • winning reward distribution
  • further connections and follow-ups? should we create a discord or Reddit group or something for participants to keep connected?