Try   HackMD

ETH Summer Topic Leader + Mentor Responsibilities

Thanks for helping out with ETH Summer! Here is a summary of what we'll need from you before and during the program.

Unlike during ETH Winter, we're distinguishing between two types of mentor roles: Topic Leaders and Project Mentors. Topic Leaders will guide a group of students on a specific topic on one or both weeks. Project Mentors will be matched to one or more students (or groups of students) in the final two weeks, and help guide students as they work to ship a project. Previously, "mentors" served in both roles, but this time around we're giving you the option to take on only one role if you'd like.

Topic Leaders

Preparation

To be done in advance of program.

  • Build out a reading list and "quests" list that can be shared with students, by a week before the program start. Example from ETH Winter, ZK Crypto Track: ZK track resources (Note from Brian: I recommended that students pick 1-2 of the subtopics to go through asynchronously each week, and then ask me questions during office hours. However, you're free to structure your resource lists however you'd like - see here for more examples).
  • Plan ~2 workshops or lessons for your topic during the week. We're hoping to make hands-on experience a substantial part of the curriculum; students won't just be reading about ethereum or decentralized systems abstractly, they'll actually be interacting with protocols and dapps.

During the Program

At the beginning of Week 1 and Week 2, students indicate topic preferences and are assigned to topic groups. You can expect to have a group of about 4-10 students assigned to you on any week that you are running a topic. We anticipate the time commitment to be 10-15h/wk, upper bound.

  • Run the workshops you prepared before the program (these should be scheduled between 5-8PM PT on weekdays - Therese will coordinate to build the calendar).
  • Run 1-2 "office hours" sessions for students assigned to you/your topic (these should be scheduled between 5-8PM PT on weekdays - Therese will coordinate to build the calendar).
  • Check in with all students in your group before Friday to make sure that all students have a lightning talk / demo they can do at the week-end session.
  • Attend all-program events, including the weekly Friday lightning talks and the Week 1 Monday opening session. Attending the weekly T/Th talks + socials are optional but highly recommended!

Project Mentors

This will get fleshed out a little more as we get closer to Weeks 3 and 4, but for now we anticipate that mentoring ~3-4 students/teams would take at most ~10h/wk for each of two weeks (note from Brian: this is based on my approximate time commitment from ETH Winter). You can scale up or down your involvement, letting us know during the matching process how many teams you're willing to take on.

Your ultimate mandate is to make sure that your assigned group(s) ship!

  • [tbd exactly what this looks like] Help students during the project selection process, before the start of Week 3. Matt/Scott have some ideas from Treehacks and Hack Lodge
  • Schedule synchronous checkins with your assigned student(s)/group(s) throughout the two project weeks - suggested checkin times are WF on week 3 and MWF on week 4.
  • Be available to asynchronously answer questions on Discord throughout the weekdays.
Last changed by 
 
gubsheep
0
144

Read more

ZK Frontiers: Week 3 Exercises

For this week's exercise, you will write a spec for one of the following proposed applications. If you are working on a project, you're automatically "exempt," as you'll already be building one of these! In your spec, you should: Outline precisely the ZK circuit(s) you'll be using. You can use our template from class if you'd like. Describe the business logic of the major components of the application: the server (what it stores, what it verifies, etc.) smart contracts (if applicable), clients (what they store, what they prove, etc.), and any additional services (for example, an auxiliary server that stores, verifies, and serves Merkle groups). WhaleChat

Jun 14, 2023
ZK Frontiers: Week 2 Exercises

ZK Passwords In this exercise, you will implement a ZK-based password verifier! Instructions can be found in the README of the scaffolding repo. You are aiming to produce something that looks like this video demo. You can start with the scaffolding repo, or you can roll your own from scratch. If you use the scaffold repo, make sure to check out circom-starter, the base repo which this is based on! Extension: make proving happen in-browser. We’ll go over this during next week’s Monday optional session. You may also find this circom and snarkjs diagram useful.

Jun 6, 2023
ZK Frontiers: Week 1 Exercises

This week's exercises are hands-on coding exercises. Try writing the following circuits on your own. If you get stuck, you can check the solutions. We'll go over these circuits in the second Optional Session in Week 2. If you need to look up circom language features or syntax, take a look at the circom docs. I recommend trying to build these circuits in zkREPL, for fast iteration. I recommend doing these exercises in order, as later circuits may build on previous ones. References Field Size All signals in circom are treated as numbers modulo this big prime:

Jun 1, 2023
Zupass Resources for Developers

Zupass Official Repo: https://github.com/proofcarryingdata/zupass The README provides a starting point for devs. Usage Examples for Devs: https://consumer-client.onrender.com This page contains examples for devs on how to integrate Zupass into various application flows, such as authentication, proof generation/consumption. Code for these examples is in the official Zupass repo. Example Application: Zuzalu Confessions: https://confessions-client.onrender.com/ This is a fully-functional anonymous message board built on Zupass, demonstrating authentication and identity-hiding proofs. For development/demonstration/reference purposes only! Zuzalu Confessions Reference Code: https://github.com/proofcarryingdata/zuzalu-confessions

Apr 11, 2023
Read more from gubsheep
Published on HackMD