As Zuzalu decentralizes into a network of pop-up cities, the Zupass team has been working to enable a developer ecosystem which scales to support them all. Come learn about the new libraries and tools (mentioned below) we’ve made which enable pop-ups to customize for their own needs, and coordinate with others using Zupass as a user-controlled, privacy-preserving, ZK-enabled framework.
POD (Provable Object Data) is a flexible data format for issuing signed data, which could be tickets, credentials, badges, frogs, or any form of attestation. POD can contain arbitrary name/value pairs, in a format which is optimized for ZK proving.
GPCs (General Purpose Circuits) enable a wide variety of proofs about PODs, generated using General Purpose Circuits. Apps configure their proof in a simple JSON configuration, and the GPC compiler picks a pre-compiled circuit which fits the config, and translates config + PODs into the necessary inputs to prove or verify.
Z API is a new SDK which allows Zupass-enabled web apps (ZApps) to embed Zupass in an iframe, and use it as a cryptographic datastore. ZApps can ask the user for permission to read their PODs (tickets, credentials, etc) directly, create and insert new PODs, or request ZK proofs using the user’s private secrets.
PODBox is a no-code server for issuing POD credentials (tickets, certificates of attendance), or arbitrary PODs. Event organizers can issue tickets by directly importing data, or using integrations with Pretix or Lemonade. PODBox is also self-hostable, allowing infrastructure and user data to be independent of the Zupass backend.
This is a technical session aimed at developers and event organizers, but anyone with an interest is welcome.
Presenters: Andrew Twyman, Rob Knight
First 60 minutes will be technical presentation and workshop, final 30 minutes reserved for Q&A and interaction with presenters.