Please give a short description of the topic/cause for your Community Hub
The ZK Community Hub is a gathering point for various sub-communities in the applied ZK ecosystem. This includes communities focused around development and maintenance of proving system libraries, ZK circuit developers, ZK tooling, developers of ZK-enabled apps for either privacy or scalability, ZK rollup and zkEVM-focused teams, and more.
Zero-Knowledge cryptography is poised to be one of the most impactful tools for Ethereum application developers in the next few years. This topic has already spawned a number of subcommunities working at all different levels of the stack. Community infrastructure that brings these teams together to share knowledge can accelerate everyone’s work.
What will you offer to the Devcon attendees?
The Hub would have three primary “use cases.”
Firstly, the ZK Community Hub can be a space for ZK teams and subcommunities to run informal events; these teams can register the space in advance for meet-and-greets, office hours, etc. Such events would be less structured than a workshop or presentation registered specifically under the ZK track; they would be more informal, accessible, and open-ended.
Secondly, there will be a number of ZK track presentations throughout Devcon, and the ZK Community Hub can serve as the default followup spot for ZK track presenters to hang out at after their sessions.
Finally, the ZK Community Hub may serve as a default “hangout” spot or Schelling Point for ZK-focused attendees.
To dig deeper into the first use case, which we expect to be the core “driver” of usage of the Community Hub: teams or individuals in the ZK space may “reserve” one of four 75-minute slots per day, during which they would lead informal activities that are open to the ZK community broadly.
We expect that informal activities could include:
- Meet-and-greet sessions. For example, a rollup team (like zkSync, Scroll, Hermez, Starkware) may host a meet-and-greet for third-party developers who are interested in developing on top of the rollup.
- Office hours. A team building a ZK toolstack (for example, circom) may book a slot and invite community members to come by to ask the core development team questions.
- Guided demos. Informal sessions where community members can drop by the Community Hub to i.e. try out a ZK app / set of apps (try out HeyAnon, Zordle, etc.), with guidance from a team member.
- Fireside chats or round-table discussions. These would be guided discussions on specific topics (ZK Identity, ZK machine learning, ZK security), led by a domain expert where anyone at Devcon who is interested in the topic may participate in.
We would invite teams from across the ecosystem, including:
- Rollup and zkEVM teams.
- Teams building ZK infrastructure—proving stacks, libraries, etc.
- ZK application development teams, such as PSE or 0xPARC’s identity application teams.
In addition, the ZK community hub is also available for speakers participating in the ZK track to host followup discussion after their presentations.
Add a rough outline of your Community Hubs program
- The space will be operated from 10am - 3pm. Each day, this period is broken up into four 75-minute slots.
- We’ll find four teams per day that will sign up for slots to “own” the space for 75 minutes each. During a slot, the chosen team will drive a “primary activity”—see the examples above.
- Additionally, we imagine that the space will be used informally for followups with speakers on the ZK track, or other meetups.
List the people who will organise, oversee and be responsible for the Community Hub
The 0xPARC team (gubsheep, Remy, Michael) will take the lead. Over the next few weeks, we will make sure there is coverage from our community during open hours, by coordinating ZK teams to sign up for slots.
List the equipment or production needs (see what’s possible in the RFP)
- In decreasing order of priority:
- Seating for discussion groups
- TV-sized screen
- Power Outlets
- Signage
- Desks and tables
- Whiteboards
