# Zuzalu Organizers: Permissioning New Resident Emails - Instructions **Note: This flow is only for adding new *resident* emails, not visitors. Visitors should sign up on Pretix for a subevent or visitor pass, and then they will be automatically permissioned to create a Passport.** First, go to the [Pretix Imports](https://docs.google.com/spreadsheets/d/1-9oULc_PaSXeL3fW-jp2UTo8BJ5kZ-tqqM3M_2ZNdEo/edit#gid=1826723548) spreadsheet, and navigate to the "Residents (INCOMPLETE) sheet." This sheet has been pre-populated with all residents who have incomplete {firstname, lastname, email} information. <details> <summary>Screenshot: Pretix Imports spreadsheet</summary> <img src="https://i.imgur.com/9qDqPxw.jpg"/> </details> <br/> Find the entry (or entries) that you want to permission as resident(s). Each entry needs an email, firstname, and lastname. - You can also add new entries that aren't in the sheet yet. - For example, if someone requested for their email to be changed, add a new entry for them here with their new email, and firstname + lastname. - It's fine that this will end up creating a duplicate in Pretix. We can remove it later if needed, but it's not strictly necessary to do so. Now, create and save a new CSV file that looks like the picture below, with the people you are trying to import. Multiple lines are OK! <details> <summary>Screenshot: CSV Example</summary> <img src="https://i.imgur.com/ovAw7oC.png"/> </details> <br/> Now, go to the [Pretix import link](https://beta.ticketh.xyz/control/event/zuzalu/zuzalu/orders/import/). Select the CSV file you've just saved, and click "Start import." <details> <summary>Screenshot: Import attendees screen</summary> <img src="https://i.imgur.com/HRMPang.jpg"/> </details> <br/> Now you'll get a "data preview" with the first 1-3 entries in your CSV, as well as an "Import settings" form. **Make sure that the Import settings form has the following**: - **Email address** should be set to **CSV column: "email"**. - **Product** should be **Resident** - **Invoice address: Country** can be whatever you want, but is a required field, so you can default to United States or Montenegro. - **Attendee e-mail address** should be **CSV column: "email"**. - **Attendee address: Country** can be whatever you want, but is a required field, so you can default to United States or Montenegro. - **Attendee name: Given name** should be **CSV column: "firstname"**. - **Attendee name: Family name** should be **CSV column: "lastname"**. - **Everything else can be left blank or as the defaults.** After you fill out the form the first time, these settings will be saved, so you won't have to do this each time (though you should double-check each time to make sure). See the example below. <details> <summary>Screenshot: Filling out "Import settings"</summary> <img src="https://i.imgur.com/T0IgSdz.jpg"/> <img src="https://i.imgur.com/3a7CbZR.jpg"/> <img src="https://i.imgur.com/iCjT8LL.png"/> </details> <br/> Hit "Perform import." If the import succeeds, you're done! Modify the **added yet?** column in the [spreadsheet](https://docs.google.com/spreadsheets/d/1-9oULc_PaSXeL3fW-jp2UTo8BJ5kZ-tqqM3M_2ZNdEo/edit#gid=1826723548) to reflect this. <details> <summary>Screenshot: Pretix Imports spreadsheet</summary> <img src="https://i.imgur.com/wqOiTed.jpg"/> </details> <br/> **If you have any issues, contact Althea (@catsnacks) on Telegram.**
Last changed by  
 
gubsheep
65

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

6/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.

6/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:

6/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

4/11/2023
Read more from gubsheep
Published on HackMD