# Grant Application: PEPL - Privacy Event Pilot - Speak-ez Sessions

**URL:** <https://forum.zcashcommunity.com/t/grant-application-pepl-privacy-event-pilot-speak-ez-sessions/59357>\
**Category:** Community Grants\
**Created:** [November 16, 2026, 2:38pm UTC](https://forum.zcashcommunity.com/t/grant-application-pepl-privacy-event-pilot-speak-ez-sessions/59357 "2026-11-16T14:38:51Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![hard-nett](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/hard-nett/32/39467_2.png) [@hard-nett](https://forum.zcashcommunity.com/u/hard-nett)\
**Post date:** [November 16, 2026, 2:38pm UTC](https://forum.zcashcommunity.com/t/grant-application-pepl-privacy-event-pilot-speak-ez-sessions/59357/1 "2026-11-16T14:38:51Z")

</div>

> <https://github.com/ZcashCommunityGrants/zcashcommunitygrants/issues/559>
>
> \### Terms and Conditions
> 
> \- \[x\] I agree to the \[Grant Agreement\](https://9ba4718…c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_f81ef4e4b5f040038350270590eb2e42.pdf) terms if funded
> \- \[x\] I agree to \[Provide KYC information\](https://9ba4718c-5c73-47c3-a024-4fc4e5278803.usrfiles.com/ugd/9ba471\_7d9e73d16b584a61bae92282b208efc4.pdf) if funded above $50,000 USD
> \- \[x\] I agree to disclose conflicts of interest
> \- \[x\] I agree to adhere to the \[Code of Conduct\](https://forum.zcashcommunity.com/t/zcg-code-of-conduct/41787) and \[Communication Guidelines\](https://forum.zcashcommunity.com/t/zcg-communication-guidelines/44284)
> \- \[x\] I understand all milestone deliverables will be validated and accepted by their intended users or their representatives, who will confirm that the deliverables meet the required quality, functionality, and usability for each user story.
> \- \[x\] I agree that for any new open-source software, I will create a \`CONTRIBUTING.md\` file that reflects the high standards of Zcash development, using the \[\`librustzcash\` style guides\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#styleguides) as a primary reference.
> \- \[x\] I understand when contributing to existing Zcash code, I am required to adhere to the project specific contribution guidelines, paying close attention to any \[merge\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#merge-workflow), \[branch\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#branch-history), \[pull request\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#pull-request-review), and \[commit\](https://github.com/zcash/librustzcash/blob/main/CONTRIBUTING.md#commit-messages) guidelines as exemplified in the \`librustzcash\` repository.
> \- \[x\] I agree to post request details on the \[Community Forum\](https://forum.zcashcommunity.com/c/grants/33)
> \- \[x\] I understand it is my responsibility to post a link to this issue on the \[Zcash Community Forums\](https://forum.zcashcommunity.com/c/grants/33) after this application has been submitted so the community can give input. I understand this is required in order for ZCG to discuss and vote on this grant application.
> 
> \### Application Owners (@Octocat, @Octocat1)
> 
> \[@hard-nett\](https://github.com/hard-nett)
> 
> \### Organization Name
> 
> Discover Decentralization DAO
> 
> \### How did you learn about Zcash Community Grants
> 
> ZechubDAO
> 
> \### Requested Grant Amount (USD)
> 
> 110,985
> 
> \### Category
> 
> Event Sponsorships
> 
> \### Project Lead
> 
> \`\`\`project-lead.yaml
> Name: Austin Hardnett  
> Role: Core Lead  
> Background: Open source contributor, ZecHubDAO member 
> Responsibilities: Coordinating grant proposal funding, working with event curators to materialize events
> \`\`\`
> 
> \### Additional Team Members
> 
> \`\`\`team-members.yaml
> Out of respect of their privacy, additional members are withheld. Roles and responsibilities for a Session:
> 
> | Role | Responsibilities |
> | ------------------------------------ | --------------------------------------------------------------------------------------------------------------------- |
> | Lead event coordinator(s) | Ground floor coordination & event manifestation |
> | Tech Lead | Ticket checkout, printable and QR tickets, door sign-in, payment rails; on later nights, maintenance and coordination |
> | Artist & Vendor Support Lead | Host artists and vendors, keep payouts and hospitality clear, help with wallet setup for payments |
> | Vibe Lead | Space deco, prints and marketing |
> | Event Ushers , Secuity & Saftey Team | Receive printed or QR tickets, passkey sign-in, one entry per ticket, Floor and door safety for the session |
> | Sound, Visuals & Archive Lead | Provide Sound,Lights & Visuals, record sets |
> \`\`\`
> 
> \### Project Summary
> 
> 
> PEPL speakeasy sessions are IRL events where artists, vendors, venue owners, volunteers and attendees utilize open source privacy preserving technology to manifest a space to celebrate each other. We focus on curating an experience where all participants through usage will accumulate experience and awareness of sending and receiving payments in ZEC, as well as being able to provide a spotlight on their work to the broader community.
> 
> \### Project Description
> 
> A Speak-ez Session is an single night IRL event, central to a sound-system, dance-floor, art gallery, & vendor booths to showcase their goods and services. The event locations are not disclosed to anyone other than ticket purchasers, and we have designed a ticket lifecycle that incentivizes usage of private payments to purchase tickets through discounts.
> 
> What is curated is a space for every type of participant to have a reason to either send or receive payments in ZEC, in order to contribute to the awareness and adoption of private unstoppable money from direct hands on experience.
> 
> Done well, each session is a live use of private unstoppable peer to peer electronic cash, and a sustainable opportunity for artist & vendors to share and provide their goods and services.
> 
> Properties of the ticketing is such that checkout that a ticket is not tied to any identity or purchase, printable as QR tickets to be consumed at the door, and authenticity is cryptographically verifiable.
> 
> \### Proposed Problem
> 
> 1. Shielded ZEC is still rarely the default payment option for tickets, artwork in galleries, or at local independent vendor tables.
> 
> 2. Funding events with a focus on increasing awareness through experience of open source, privacy preserving technologies for artists, vendors and event coordinators.
> 
> 3. Extractive & anti-competitive ticketing solutions dominate usage and are not compatible with shielded payments.
> 
> 
> \### Proposed Solution
> 
> Fund three Speak-EZ Sessions in three separate cities that make use of a stack powering ticketing sales & usage through shielded payments, a variant of the vote-sdk implementation, and virtual gallery showcasing artist art and services.
> 
> \### Solution Format
> 
> A Speak-ez Session is a one night event in an undisclosed venue location, built around a sound-system and dance-floor, a gallery, and tables for vendors. Each Session follows the same simple promises: 
> 
> \* \*\*Admission.\*\* A ticket is offered at a discount when paid in shielded ZEC. Checkout is not tied to a legal identity or a published guest roster.
> \* \*\*Ticket lifecycle.\*\* A ticket can be printed or shown as a QR code and used to sign in at the door (OOB ticket consumption).
> \* \*\*Donated to communities in need.\*\* All ticket sales go to local charities chosen by the coordinating team.
> \* \*\*Vendors & artist goods and services.\*\* Gallery sales and vendor purchases can be paid in ZEC. Artists and vendors are paid from the Session budget (see Artists & Vendors), not from ticket sales.
> 
> \### Dependencies
> 
> \### Technical dependencies
> \- https://zafu.pro is the wallet used by event admins.
> \- a custom indexer service that powers lifecycle for ticket payments
> \- a variant of vote-sdk powering proofs for ticket ownership & nullifier generation
> \- zk-cosmwasmvm: powers lifecycle of creating events, holds on-chain verifiable front-end, and also powers ticket proof & nullifier generation verification.
> 
> \### Technical Approach
> 
> \*\*Tickets lifecycle.\*\* An open-source web app powers the ticket purchase and consumption flow, with a custom indexer that identifies & stewards ticket sale & usage recordkeeping. This indexer generates a Merkle tree of the note commitments, allowing ticket holders to generate proofs and a nullifier that will be used for accepting admittance at the event.
> 
> \*\*Event Usher Check-in Keys\*\* Ushers and admins register keys authorized for signing in guests. These keys are whitelisted and the only keys able to add nullifiers to the event admission list, allowing for verifiable check-in to events.
> 
> \*\*Frost Powered Deposits.\*\* Artists, vendors, and the gallery will have direct support for setting up their wallets and galleries for receiving ZEC. Artist and vendor compensation for booking is held and distributed in portions via an event stewards FROST multi-signature, with air-gapped self-custody, so payouts are not sitting on a single hot key.
> 
> 
> \*\*Privacy.\*\* We collect as little as we need to run the night. Tickets are not bound to a specific name, and there is no published guest roster. Where a venue requires an age check, that check stays human verified & separate from ticket consumption, and even so the event ushers cannot associate any ticket proof or nullifier to the actual seed that derived the ticket commitment. First-time wallet help and any exit survey are voluntary and are tallied without collecting identity.
> 
> \*\*Technical Guides.\*\* After each Session we write down what we actually ran: checkout, the door, payouts, charity, what broke, and what we would repeat. That playbook is a public deliverable, updated after later nights, so another coordinator can follow it.
> 
> \### Upstream Merge Opportunities
> 
> n/a
> 
> \### Open Source License
> 
> MIT
> 
> \### Hardware/Software Costs (USD)
> 
> n/a
> 
> \### Hardware/Software Justification
> 
> n/a
> 
> \### Service Costs (USD)
> 
> 104,319
> 
> \### Service Costs Justification
> 
> \### Per Event Budget
> 
> | Line | Arithmetic | Amount |
> | --------------------------------------------------- | ---------- | ----------- |
> | Artists & Vendors | \\- | $6,664 |
> | Ushers | 4 × $111 | $444 |
> | Security | 2 × $222 | $444 |
> | Technical — sound system rental | \\- | $4,444 |
> | Technical — visual and event design | \\- | $1,111 |
> | Coordination & Development — lead event coordinator | \\- | $5,555 |
> | Coordination & Development — lead artist support | \\- | $1,111 |
> | Venue (150–300 person space) | \\- | \*\*$15,000\*\* |
> | \\---------------------------------------------------| \\----------|\\---------- |
> | | TOTAL | 34,773 |
> 
> \### Compensation Costs (USD)
> 
> 6,666
> 
> \### Compensation Costs Justification
> 
> 
> | Line | Arithmetic | Amount |
> | ------------------------------ | ---------- | ------ |
> | Initial Full Stack Development | 1 x 4,444 | $4,444 |
> | Subsequent Infra Maintenance | 2 × 1,111 | $2,222 |
> 
> 
> \### Total Budget (USD)
> 
> 110,985
> 
> \### Previous Funding
> 
> No
> 
> \### Previous Funding Details
> 
> n/a
> 
> \### Other Funding Sources
> 
> No
> 
> \### Other Funding Sources Details
> 
> n/a
> 
> \### Implementation Risks
> 
> 
> | Risk | Mitigation |
> | ---------------------------------------------- | ---------------------------------------------------------------------------------------------------------------- |
> | Artist, Vendors & Service Compensation Custody | Frost Multisig utilizing airgapped self-custody wallet |
> | Ticket Payment Not Registered | Exhaustive E2E testing on ticket payment flows |
> | Age Gated Event / Venue | Id check occurs before ticket consumption, by separate team members to avoid risk of linking identity to ticket. |
> | Bad Internet Or Cellular Connection For Event Ushers | Bluetooth mesh design between event usher devices to ensure propagation of ticket proofs and nullifiers |
> | Design may not support High Attendance / Bandwidth for ticket consumption | Benchmark upper bounds and utilize local ephemeral network with light client verification |
> 
> \### Potential Side Effects
> 
> \* Tickets are reusable & associated to users identity
> \* Not much volume in sales for either digital or virtual art gallery for artists
> 
> 
> \### Success Metrics
> 
> We plan to report these after each Session.
> 
> 
> 
> \### Per Session (targets)
> 
> | What we measure | Target | How we count it |
> | --- | --- | --- |
> | Attendance | 100 attendees per session | Door sign-ins. No guest roster is published. |
> | Ticket Sales | $2000 raised for donations per session | public ovk |
> | Artists and vendors paid | Everyone who performed or vended is paid from the Session budget. ZEC is offered to all, with a target that a majority are paid in ZEC. | 20% transparent deposit records published |
> | First-time ZEC users onboarded | 50 first-time wallet helps per Session | Voluntary exit survey and/or wallet-setup help desk tally, with no identity collected |
> | ZEC volume transacted | $5000 volume in vendor & gallery sales | Survey of participating artists |
> | Post-event survey | Responses from at least 20% of attendees, or 30 surveys, whichever is lower | Voluntary survey, no identity |
> | Recorded artist sets | Archive is offered to every performing artist; released sets are made available | Artist agreement; public archive links |
> | Ticket lifecycle | Every admitted guest has a consumed ticket. Any checkout or door workaround is named in the public note. | Door records and the public note. No silent failures. |
> 
> 
> \### Startup Funding (USD)
> 
> 39,217
> 
> \### Startup Funding Justification
> 
> This will cover resources and effort for first session budget, including the venue, all participating in the event curation, and specifically the one-time $4,444 initial full-stack development:
> 
> We want to provide all participants up front partial deposits for the first night, including the full venue booking deposits, as well as compensate final tuning to the front end and web app powering the event stack.
> 
> Artist are sent a 20% transparent payment up front as a deposit, and following their performance and attendance, receive their 80% in a shielded payment.
> 
> \### Milestone Details
> 
> \`\`\`milestones.yaml
> Dates are not set in stone until we have certainly in a grant supporting these pilot sessions.
> 
> | Tranche | What it funds | Amount | Unlock condition |
> | --- | --- | ---: | --- |
> | Startup | Full cost of event 1, including venue and initial development | $39,217 | Award / kickoff |
> | Milestone 1 | Full cost of second session. Public metrics and playbook from first session | $35,884 | First Session held; Public metrics from second session shared |
> | Milestone 2 | Full cost of third session; Public metrics and playbook from second session | $35,884 | Milestone 1 accepted. Second Session Held. |
> | Milestone 3 | No additional funds. Cumulative results of the three initial Speak-ez Sessions. | $0 | Events 2 and 3 complete (or honestly accounted for); cumulative report published |
> | \*\*Total\*\* | | \*\*$110,985\*\* | |
> 
> 
> \### Milestone 1 — Metrics on the first Speak-ez Session, Funding For Event 2
> 
> \* \*\*Amount:\*\* $35,884, covering the full cost for event 2.
> \* \*\*Expected completion:\*\* TBD (set at filing)
> \* \*\*Why this milestone exists:\*\* It is the public account of the first night, and the evidence that unlocks Milestone 2. It does not pay for the night a second time.
> \* \*\*User stories:\*\*
> \* As a guest, I could buy a ticket at a discount in shielded ZEC or UM, without it being tied to my name, and bring a print or a QR code to the door and sign in with a passkey.
> \* As a coordinator, I have clear deliverables and expectations,
> \* As a vendor or gallery artists, I have been helped with setting up myself for accepting initial deposit, as well as native private zec payments for my goods or services
> \* As an performance artists, I have been helped with setting up myself with a zcash wallet for accepting initial deposit.
> \* As an event usher, I have been helped with registering my usher account to process ticket payments, and have been paid an initial deposit.
> 
> \* \*\*Deliverables:\*\* the first Speak-ez Session, held; all participant payments per the budget is dispersed; ticket proceeds sent to the chosen local charity; a public note of that night's metrics (attendance against capacity, share of tickets paid in ZEC or UM, ZEC volume, people paid, charity amount) with no guest roster; a first version of the playbook and onboarding guides.
> \* \*\*Acceptance / unlock for Milestone 2:\*\* the Session was held; the public note and playbook are up; payments deposits and charity proceeds are accounted for honestly. That package is what releases funding for events 2 and 3.
> 
> \### Milestone 2 — Metrics on the second Speak-ez Session, Funding For Event 3
> 
> \* \*\*Amount:\*\* \*\*$35,884\*\*, covering the full cost for event 3.
> \* \*\*Expected completion:\*\* 1 month after event 1
> \* \*\*Why this tranche waits:\*\* session 2 occurs in a different city than session 1, and will exercise the session playbook again to confirm its reusability. Milestone 1 is that proof. Once it is accepted, this tranche funds the second session in full.
> \* \*\*User stories:\*\*
> \* As an independent artist or vendor, I can take part in our second session and be paid in line with the budget, in ZEC if I can receive it.
> \* As a guest, I can purchase a ticket for the second session, and able to recieve the session location for arrival
> \* As an event coordinator, I have all the reosurces and feedback from previous session coordinators to improve this session experience.
> \* \*\*Deliverables:\*\* the second session flow; playbook updated after each night; ticket proceeds sent to the charity chosen for that night; the same class of public metrics as event 1.
> \* \*\*Acceptance:\*\* Second session is held, all payments are distributed, statics on attentance and charity proceeds are accounted for.
> 
> \### Milestone 3 — Cumulative showcase of each Session
> 
> \* \*\*Amount:\*\* \*\*$0\*\* (no additional funding)
> \* \*\*Expected completion:\*\* TBD (set at filing)
> \* \*\*Why this milestone exists:\*\* It is where we share the cumulative results of each initial Speak-ez Session. It does not fund a fourth night, and it does not re-fund work already paid.
> \* \*\*User stories:\*\*
> \* As a coordinator in another community, I can read the playbook and a complete three-Session account, including how tickets were sold, how people were paid, and how proceeds reached local charities.
> \* \*\*Deliverables:\*\* a brief public close on the series — attendance against capacity, ticket share in ZEC or UM, ZEC volume, artist and vendor payouts, first-time onboard tallies, charity proceeds, archived sets where artists agreed, what we would repeat, and the playbook in its last form. No invented revenue. No published guest list.
> \* \*\*Acceptance:\*\* the cumulative report is published.
> \`\`\`
> 
> \### Supporting Documents
> 
> \`\`\`files.yaml
> \> blog post will contain documentation and further demos are available
> \`\`\`

---

<div class="post-metadata">

**Author:** ![hard-nett](https://sea2.discourse-cdn.com/zcash/user_avatar/forum.zcashcommunity.com/hard-nett/32/39467_2.png) [@hard-nett](https://forum.zcashcommunity.com/u/hard-nett)\
**Post date:** [November 16, 2026, 10:58pm UTC](https://forum.zcashcommunity.com/t/grant-application-pepl-privacy-event-pilot-speak-ez-sessions/59357/2 "2026-11-16T22:58:17Z")

</div>

Hi Zcash Forum!

## Prelude - My Thoughts About ZCG & NU7.1

For archival purposes, I want to start off first noting that this post comes on the first day of NU7.1 coinholder polling; I hope those who can, have expressed their sentiment with regards to the future of the ZCG program, and take a moment to appreciate the ability that this is possible for such a large project. Super cool IMO.

It is my belief that ZCG is a type of program that is one of the many vital arteries within the Zcash community. Completely removing a capability like ZCG without a proper iteration can result in an outcome that is oligarchic, as Brendan Eich stated on his podcast with Lex Fridman:

[**“One dollar one vote means rule by Oligarchs”**](https://x.com/BrendanEich/status/2119901769597857836)

I cannot participate in the polling, but can participate through my actions, like committing to the efforts described in this grant proposal, as well as contribute to communities that are supported by ZCG like ZecHub DAO that show that there is viability to the efforts of ZCG, and should be reflected as such.

I want to live in a future with more choice, not less.

## Introduction

This grant proposal requests sponsorship of hosting what we are calling Speak-ez Sessions (SEZS), an IRL event where tickets are priced in ZEC, artists galleries & vendors booths accept private ZEC payments, and all event stewards are paid in ZEC for their contributions.

SEZS give all participants a reason to **actually** use ZEC, in an environment that is familiar with activities we enjoy and cherish.

With support from this grant, we will pilot 3 events, in 3 separate cities to maximize the local impact that we can make within our teams local communities.

## Technical Approach

### Ticket Payment & Usage Lifecycle

All tickets that can be purchased online will only be denominated in ZEC. This is available through a web-ui, where the TLDR is the tickets can be cryptographically verifiable and consumed through a variant of the vote-sdk flow. Detailed specs are coming, and will link below!

Tickets will also be available at the door, accepting Cash or Venmo/Cashapp payments. We essentially will require admission by verification that an attendee has a Zcash supported wallet available ( except for the scenario where a mobile device is not available or present), and have event ushers assist with installation.

We will offer partial discounts by a small shielded payment back to them, so they can experience their first zcash payment and give another reason to not just delete the wallet once in.

Tickets will not be linked to a specific wallet, and ownership can be transferred, but once a ticket is used for admission, it cannot be used again.

### Artist, Vendors & Stewards Payment Sponsorship & Onboarding

Artists, vendors, the event venue, the sound-system & visual engineers, ushers, security, and event stewards all will be compensated for their time, effort & infrastructure in ZEC, requiring everyone to install a ZCash compatible wallet!

All compensation (other than venue & infrastructure reserving) will be employed through a 20/80 transparent/shielded schedule, where 20% of payment will be up front deposits to transparent addresses, and at the event the remaining 80% will be distributed via shielded deposits directly peer to peer.

This gives us the opportunity for users to directly gain experience with the current properties of Zcash having transparent and private pools.

### Digital And Physical Gallery

SEZS dedicate space for art galleries and vendors to display their goods and services, accepting ZEC as payment.

SEZS also dedicate efforts to curating a virtual gallery for each session, where local artist at sessions or those who can’t make it can display and sell their work in ZEC to the broader community.

## Resources

One of the critical efforts and results of this grant will be the guides, walkthroughs, and direct access to assistance that will be provided to artists and participants that will be reusable between sessions and directly support initial onboarding and usage.

These are going to be shared and available within the reusable web-ui.

## Team, Locations & Timeline

Our core team consist of myself and friends who participate in artist collectives that are dedicated to showcasing art of all forms, from around the world.

We are finalizing our intended locations for the first 3 events, and will be able to share further details as we can get some soft commitments from artists vendors and venues.

I am aiming for the first event to happen before February, and all three event to occur before April (subject to change), and can expect the majority of these initial sessions to be hosted on the East Coast, USA.

## Feedback

This initial post does not cover the full spec of our efforts, and will be followed up here in the coming days with more clear details, source code, and demonstrations of our flows and guides.

Thank you for any time taken to read this handwritten introduction, I hope you got a feel for the vision! Please provide any initial reactions, feedback and suggestions to make this grant effort a no brainer for ZCG to accept 😄
