Selected work / Ethereum / attendance
POPE
An attendance-proof prototype connecting attendee credentials, organizer signing and a separate staff console.
The idea
Separate proof of attendance from the attendee secret.
This selection brings the attendee and staff interfaces together with their organizer and verification workflow.
Research prototype with local and Sepolia paths. Screenshots do not certify cryptographic security or successful issuance. The original hosts remain available while credential and organizer recovery is unresolved.
Three selected moments
A closer look.
Move through the selected stills.
01 / Selected moment
The attendee opening
The public attendee opening introduces event creation, attendance credentials and proof checking.
Open full image ↗
02 / Selected moment
The roles and recovery boundary
The walkthrough explains organizer, staff, attendee and verifier responsibilities.
Open full image ↗
03 / Selected moment
The staff console
The staff production check-in workspace accepts a signed manifest, scoped capability and attendee commitment.
Open full image ↗Make something of your own
Build your own.
Take the idea into Codex and adapt it to your own subject, sources and audience.
Reconstructed recipe · Not the original prompts
An end-to-end recreation has not been tested.
01BriefDefine the experience
Build a new interpretation of POPE: an attendance-proof prototype with attendee, organizer, staff and verifier roles. Read repository instructions and preserve existing work first. Treat these as reconstructed instructions, not the original prompt history. Keep local demonstrations visibly separate from real event operations.
02IngredientsPrepare sources and artifacts
Use the retained attendance-zk-pwa monorepo, workspace lockfile, protocol and crypto packages, circuits, proving artifacts and public event manifests. Record artifact hashes, circuit versions and Sepolia configuration. Keep attendee credentials, organizer keys and passphrases outside the showcase and source package. Independent security review remains a prerequisite for a real attendance pilot.
03InteractionBuild the connected flow
Reconstruct event setup, signed invite, attendee commitment QR, staff capability validation, organizer issuance request signing, local credential import, proof generation and verification. The staff device creates a scoped issuance request; the organizer signs the credential. Preserve explicit local-versus-on-chain results and require deliberate wallet approval for chain operations.
04Verify & preserveProve recovery before moving origins
Check keyboard and mobile operation, malformed payloads and failure states. Use isolated test credentials to verify encrypted attendee export/import and organizer key plus manifest restoration on a replacement origin. Keep original origins available until each relevant device has a verified private recovery path. Do not copy private recovery material into logs or this recipe. Preserve selected source, lockfiles and artifact provenance; record untested boundaries and label the package as a local selection, not a complete mirror or NAS backup.