ABCDEFGHIJKLMNOPQRSTUVWXYZAAABACADAEAFAGAHAI
1
QA1Zoey 0x
QA2 Alessandro ctrlc03
QA3 John Guilding
QA4 Andy
QA5 Vivian Plasencia
QA6 Thore Hildebrandt
QA7 ChrisQA8 BrechyWesleySectorCategoryPersona User StoryComments / Questions
2
KeepKeepKeepKeepAsset ManagementSwapInstitutionAs a professional fund manager, I want to execute multi-hop hedges (e.g., collateralised short + perpetual long) without revealing the net exposure, so that my proprietary edge remains secret.
3
KeepKeepUnsureUnsureDX
Developer Tooling
DeveloperAs a developer, I want to swap elliptic-curve back ends through a high-level API, so that I stay flexible across back end tech stacks.
4
KeepKeepKeepKeepAsset ManagementSwapEnd userAs an End user, I want to approve tokens and execute DEX swaps privately, so that my trading strategies cannot be tracked.
Chris: conversely, some want their 'strategy' to be visible so that it can rally people to follow suit and 'pump' the investment more
5
KeepKeepKeepKeepAsset ManagementSwapInstitutionAs a institution, I want to deposit swap and borrow while keeping asset mix and strategy confidential, so that competitors cannot front-run me.
6
KeepUnsureKeepAsset ManagementSwapEnd userAs a liquidator, I want shielded lending protocols to expose at-risk positions only at liquidation time, so that I can keep pools solvent without learning every borrower’s health factor.
7
KeepKeepKeepKeepAsset ManagementSwapEnd userAs a end user, I want my wallet’s liquidity-provision and yield-harvesting actions to stay unlinkable, so that scammers and phishers cannot profile or target me.
8
KeepKeepKeepKeepAsset ManagementSwapEnd userAs a end user, I want to hide my loop-leveraged positions across lending and AMMs, so that competitors cannot copy or front-run my strategy.
9
UnsureUnsureKeepAsset ManagementSwapInstitutionAs an institution, I want a dark second-price auction that still proves winner-pays-second-bid, so that participants trust the fairness without seeing every bid.
10
UnsureUnsureKeepAsset ManagementSwapEnd userAs a end user, I want my maximum bid and wallet balance to stay confidential until settlement, so that rivals cannot anchor future bids on my valuation.
11
KeepUnsureKeepAsset ManagementSwapInstitutionAs an institution, I want to support non-crypto bidders through MPC-based sealed bids, so that we attract more customers without sacrificing on-chain auditability.
12
KeepKeepKeepKeepAsset ManagementTransferInstitutionAs an institution, I want to send funds to anonymous teams with proof they are outside sanctioned regions, so that we reduce legal risk while preserving grantees’ privacy.
13
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a end user, I want AMM prices to stay publicly observable even when liquidity is shielded, so that I can correct mis-pricing and maintain peg stability.
14
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a end user, I want to enter and exit lending pools directly from shielded balances in one transaction, so that observers cannot measure my position size or view my strategy.
15
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a end user, I want to collect rewards and restake them from shielded pools, so that copy-traders cannot see my strategy .
16
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a privacy-focused user, I want to send encrypted queries to Ethereum RPCs so the server cannot know what I’m querying, even if it sees my IP.
17
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a end user, I want to send private calldata through an encrypted mempool, so that intent leaks are prevented.
18
KeepKeepKeepKeepKeepAsset ManagementTransferDeveloperAs a developer, I want a privacy-preserving onboarding flow that lets users derive key-pairs from familiar channels (email, phone, chat), so that they can receive private payments without any prior crypto setup.
19
UnsureUnsureKeepUnsureAsset ManagementTransferDeveloperAs a developer, I want to publish proof-carrying data blobs that hide individual transfers yet validate batches, so that rollup integrity and privacy coexist.
20
KeepKeepKeepKeepAsset ManagementTransferEnd userAs an End user, I want to enjoy cheap efficient cash-like payments on Ethereum and EVM chains, so that I can transact privately without high fees.
21
KeepKeepKeepKeepAsset ManagementTransferEnd userAs an End user, I want to manage every stealth address with one master account, so that account management stays simple.
22
KeepKeepKeepKeepAsset ManagementTransferEnd userAs an End user, I want to send any ERC-20 token with the same privacy guarantees, so that token transfers remain confidential.
23
KeepKeepKeepKeepAsset ManagementTransferEnd userAs an End user, I want to send ETH with sender receiver and amount hidden, so that no observer can learn my payment details.
24
KeepKeepKeepKeepAsset ManagementTransferEnd userAs an End user, I want to transfer ERC-721 or ERC-1155 assets without revealing ownership change, so that my NFT activity stays private.
25
KeepUnsureKeepUnsureAsset ManagementTransferEnd userAs a end user, I want to compare each private transfer solution and key properties against cash, so that I advise on product-market fit.Chris: cash refers to cash notes or fiat currency?
26
KeepUnsureKeepUnsureAsset ManagementTransferEnd userAs a end user, I want to place solutions on a spectrum of transfer value, so that business models align with user segments.Chris: isn't this more from business perspective instead of end user?
27
UnsureUnsureDeleteUnsureAsset ManagementTransferEnd userAs a End User, I want to position each solution along a value spectrum for different transfer sizes, so that adoption drivers are clear.Chris: isn't this more from business perspective instead of end user?
28
KeepKeepKeepKeepUx
Trust Experience
End userAs a user, I want to understand why an dAPP is requesting permissions, so I am well informed with what data I am sharing
29
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a user, I want cheap affordable privacy tools so that I can afford to use them.
30
KeepKeepKeepKeepAsset ManagementTransferEnd userAs an End user, I want sponsored gas for my first private transactions, so that entry friction is minimal.
31
KeepKeepKeepKeepAsset ManagementTransferEnd userAs an End user, I want to receive assets on fresh unlinkable addresses, so that observers cannot profile my inflows.
32
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a multisig participant, I want my approvals to remain private, so that outsiders cannot see which keys signed.
33
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a End user, I want to use privacy dApps without paying high gas or meeting big deposit minimums, so that private transactions stay affordable.
34
KeepKeepKeepKeepAsset ManagementTransferEnd userAs a user, I want to deposit and later withdraw to a new address without exposing my transaction history, while still proving my funds are clean, so that my activity stays unlinkable.
35
KeepUnsureDeleteUnsureAsset ManagementTransferEnd userAs a casual user with $5, I could not deposit because the minimum amount was 0.1 ETH — too expensive.
36
KeepKeepKeepKeepAsset ManagementTransferInstitutionAs an institution, I want to test small deposits in new protocols from shielded addresses, so that my treasury identity is never linked to experimental positions.
37
KeepKeepKeepKeepAsset ManagementTransferDeveloperAs a protocol designer, I want an EIP that subsidises a standard shielded-state tree and enshrined verifier opcode, so that gas for shield/unshield becomes competitive with transparent calls.
38
KeepKeepKeepKeepKeepAsset ManagementTransferEnd userAs a End user, I want to perform financial transactions without being surveilled, so I can maintain privacy over my spending habits.
39
KeepKeepKeepKeepKeepAsset ManagementTransferDeveloperAs a developer, I want to offer users an aggregate view of their shielded positions without exposing raw addresses, so that they can track performance privately.
40
KeepKeepKeepKeepKeepAsset ManagementTransferDeveloperAs a developer, I want an unshieldToContract() helper that atomically bridges shielded balances into existing DeFi contracts, so that users need no intermediate steps.
41
KeepKeepKeepKeepUnsureAsset ManagementTransferDeveloperAs a developer, I want a white-label self-custody on- or off-ramp delivering all privacy features with minimal code, so that I can launch quickly.
42
UnsureUnsureKeepAsset ManagementTransferInstitutionAs an institution, I want defences against users colluding with developers to exaggerate balances, so that under-collateralised loans are impossible.
43
KeepUnsureKeepUnsureAsset ManagementTransferEnd userAs a end user, I want my wallet to add random delays to credential-use telemetry, so that observers cannot infer sensitive patterns about me.
44
UnsureKeepDeleteKeepDeleteDX
Developer Tooling
DeveloperAs a developer, I want one-click optional compliance reports for shielded users, so that regulated entities can still use my app.
45
UnsureUnsureDeleteKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want best-practice DevOps guidelines for privacy apps, so that I handle credentials, CI/CD and monitoring securely.
46
UnsureKeepKeepKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want tools to automate reproducible builds and circuit versioning, so that users can verify exactly what is running.
47
UnsureUnsureUnsureKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want guidelines on monitoring and logging for privacy rollups, so that I can detect and respond to exploits quickly.
48
KeepKeepKeepKeepKeepDX
Developer Tooling
DeveloperAs a developer, I want tools to simulate and test key-lifecycle events, so that I catch edge-case failures before main-net deployment.
49
UnsureKeepKeepKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want cryptographic complexity abstracted so I focus only on business logic, so that I ship features faster.
50
KeepKeepDeleteKeepKeepDX
Developer Tooling
DeveloperAs a developer, I want template repos for React Native or Next.js that mirror common Web3 patterns, so that I reduce boilerplate work.
51
KeepKeepKeepKeepKeepDX
Developer Tooling
DeveloperAs a developer, I want to build mobile ZK apps without wrestling with libraries or toolchains, so that development time is reduced.
52
UnsureUnsureUnsureKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want to generate and verify privacy proofs via a universal verifier opcode, so that gas usage remains competitive.
53
UnsureUnsureUnsureKeepKeepDX
Developer Tooling
DeveloperAs a developer, I want to integrate a TypeScript SDK that hides proving key details behind one function call, so that I can add privacy quickly.
54
UnsureUnsureUnsureKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want to embed circuit verification hooks in the sequencer to reject invalid proofs before L1 submission, so that bad transactions never hit mainnet.
55
KeepKeepKeepKeepKeepDX
Developer Tooling
DeveloperAs a developer, I want a simple SDK that hides the complexity of web-proof generation, so that I integrate privacy proofs with a few lines of code.
56
KeepKeepKeepKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want high-quality docs and reference flows, so that I can debug without reverse-engineering sample apps.
57
DeleteUnsureUnsureKeepDeleteDX
Developer Tooling
DeveloperAs an engineer, I want to work in a dedicated group focused on read privacy, so we can make meaningful progress on infrastructure improvements.
58
KeepUnsureUnsureDeleteDeleteDX
Developer Tooling
DeveloperAs an engineer, I want to work in a dedicated group focused on read privacy, so we can make meaningful progress on infrastructure improvements.
Q: Doesn't this apply to every use case? e.g. I want to be part of x dedicated group [..]
59
KeepKeepUnsureKeepKeepDX
Developer Tooling
DeveloperAs anyone experimenting with privacy tools, I want free or low-fee testnet/sandbox environments, so that I can try features safely before committing real funds.
60
KeepKeepKeepKeepKeepDX
Developer Tooling
DeveloperAs a developer, I want a proof system with a Rust (or Noir) API and existing SHA-256 examples, so that I can integrate it without writing low-level crypto code.Q: why just sha256?
61
UnsureUnsureDeleteKeepUnsureDX
Developer Tooling
DeveloperAs a developer, I want guidance on splitting credential storage and signing logic between TEE and software, so that damage from a compromise is limited.
62
KeepKeepUnsureDeleteUnsure
Ecosystem Coordination
Specifications
Developer
As a developer/researcher, I want to establish common protocols for privacy‑preserving governance so that different DAO platforms can implement compatible private voting solutions for interoperability & to avoid vendor lock in.
63
KeepKeepKeepKeepUnsure
Ecosystem Coordination
Specifications
Developer
As a developer, I want publicly accessible audit reports, changelogs, and maintenance signals for privacy protocols, so that I can safely depend on them in production without running a full in-house security review.
64
KeepKeepDeleteKeepKeep
Ecosystem Coordination
StandardsDeveloperAs a developer, I want an accepted standard, so that any two compliant implementations interoperate out of the box.
65
KeepKeepKeepKeepUnsure
Ecosystem Coordination
StandardsDeveloperAs a developer, I want an openly licensed spec, so that no single vendor controls the protocol’s future.
66
KeepKeepKeepKeepUnsure
Ecosystem Coordination
StandardsDeveloperAs a developer, I want clarity that a protocol is past experimentation and into a standard, so that I can invest resources with lower risk.
67
KeepKeepDeleteKeepUnsure
Ecosystem Coordination
StandardsInstitutionAs an institution, I want best practices tailored to group custody and governance, so I can manage risk and compliance securely.
68
KeepKeepKeepKeepKeep
Ecosystem Coordination
StandardsDeveloperAs a developer, I want a stable, widely adopted standard, so I can justify long-term support and documentation effort.
69
KeepKeepUnsureKeepUnsure
Ecosystem Coordination
StandardsInstitutionAs an institution, I want a publicly ratified standard, so I have a neutral reference when assessing compliance or safety.
70
KeepKeepKeepKeepUnsure
Ecosystem Coordination
StandardsDeveloperAs a developer, I want conformance tests defined by the standard, so I can verify my product before shipping to millions of users.
71
KeepKeepUnsureKeepUnsure
Ecosystem Coordination
StandardsDeveloperAs a developer, I want open standards for privacy oracles, so that different providers interoperate without custom bridges.
72
KeepKeepUnsureKeepUnsure
Ecosystem Coordination
StandardsDeveloperAs a developer, I want a standard format for issuing attestations, so that every wallet can consume my proofs without custom code.
73
KeepUnsureUnsureKeepUnsure
Ecosystem Coordination
StandardsInstitutionAs an institution, I want privacy proofs that meet eIDAS and similar standards, so that my product is legal in regulated markets.
74
KeepKeepUnsureKeepUnsure
Ecosystem Coordination
StewardshipDeveloperAs a privacy-oracle maintainer I want robust nullifier schemes based on vOPRF, so that proofs cannot be replayed across contracts.
75
KeepKeepKeepKeepKeep
Ecosystem Coordination
Specifications
DeveloperAs a developer, I want a versioned spec, so that I can evolve features while signalling breaking changes downstream.
76
KeepKeepDeleteDeleteDelete
Ecosystem Coordination
StandardsDeveloperAs an open-source library maintainer, I want a stable widely adopted standard, so that I can justify long-term support and documentation effort.Duplicate to row 68
77
KeepKeepUnsureDeleteDelete
Ecosystem Coordination
StandardsDeveloperAs a developer, I want evidence that a trusted team is behind a project, so that I can overcome initial scepticism.
78
KeepUnsureUnsureKeepEducationCurationEnd userAs an End user I would like to know why I should trust this app, dApp or server. I would like to compare it with other similar tools
79
KeepKeepDeleteDeleteUnsureEducationResourcesDeveloperAs a developer, I want dashboards that prove a project is not just shilling its own token, so that I can rely on neutral data.
80
KeepKeepKeepKeepKeepEducationResourcesDeveloper
As a developer, I want a side-by-side comparison dashboard that documents guarantees, trade-offs, and team credibility, so that I can select the right integration partner based on objective facts rather than hype.
John: PrivacyBeat?
81
KeepKeepUnsureUnsureEducationResourcescoordinatorAs an ecosystem coordinator I want periodic workshops that align zkEmail, Reclaim, Clique and other teams, so that duplication of work is reduced.
82
KeepKeepKeepKeepKeepEducationResourcesEnd userAs an End User, I want a dashboard of live data about zkApps (circuits, audits, trusted setups), so that I can check their latest security status.
83
KeepKeepKeepKeepKeepEducationResourcesEnd userAs an End user, I want to know if the app I use has been battle-tested, so that I have practical assurance beyond documentation.
84
KeepKeepUnsureKeepEducationResourcesInstitutionAs an institution, I want neutral guidance when choosing key management solutions, so I can trust that it’s not just marketing from a specific project.
85
KeepKeepUnsureUnsureEducationResourcesEnd userAs a End User, I want to track tools and libraries for privacy in one searchable catalog, so that the community can find resources.
86
DeleteUnsureDeleteDeleteEducationResourcesEnd userAs a End User, I want to generate markdown reports that highlight uncovered weaknesses and mitigation steps, so that teams remediate quickly.
87
KeepKeepUnsureKeepEducationResourcesEnd userAs a End user, I want to understand which key management options are available for me, so I can make informed decisions to protect my assets.
88
KeepKeepUnsureKeepEducationResourcesEnd userAs a End User, I want to compare privacy solutions against cash properties in a clear matrix, so that trade-offs are explicit.
John: I'm not sure what "cash properties" means here. Typo? Cash as in money?
89
KeepUnsureUnsureDeleteEducationResourcesEnd userAs a End User I want impossibility results that clarify online versus privacy trade-offs, so that I choose feasible designs.
90
KeepKeepDeleteKeepEducationResourcesEnd userAs a End user, I do not want to use privacy tools with unclear legal risk, so that I avoid future prosecution or account freezes.
91
KeepKeepKeepKeepEducationResourcesEnd userAs a user, I want a neutral, easy-to-find dashboard that explains the main privacy tools available, so that I can choose one to protect my data without digging through niche forums or marketing claims.
92
DeleteDeleteDeleteDeleteEducationResourcesEnd userAs a End User I want public metrics on proof reuse and nullifier collisions, so that I can quantify real-world risk.
93
DeleteDeleteDeleteDeleteEducationResourcesEnd userAs a End User, I want metrics on drop-off during credential upload flows, so that I can identify and fix pain points before launch.
94
KeepKeepKeepKeepKeepEducation
Specifications
DeveloperAs a developer, I want a clear authoritative spec, so I can build a new implementation without reading the original codebase.
95
KeepDeleteDeleteDeleteDeleteEducation
Specifications
DeveloperAs a developer I want a clear, authoritative spec, so I can build a new implementation without reading the original codebase.Duplicate
96
KeepKeepKeepDeleteEducation
Specifications
InstitutionAs a new team member, I want a living spec that tracks current reality, so that I become productive without tribal knowledge.
97
UnsureUnsureDeleteKeepGovernance
Private delegation
InstitutionAs an institution, I want to delegate transaction-signing rights to employees while keeping our multisig addresses private, so that operations scale without exposing strategy.
Q: what does it mean "so that operations scale without exposing strategy."?
98
UnsureKeepKeepKeepGovernance
Private delegation
End userAs a DAO member, I want to delegate my voting power to a representative privately so that my choice of delegate isn’t visible to everyone.
note: something to be solved at the ERC20 (ERC20Votes) token standard level
99
UnsureKeepKeepKeepGovernance
Private delegation
End userAs an elected DAO delegate, I want to accept voting power from supporters without revealing their identities so that holders can support me without public scrutiny.
100
KeepKeepKeepKeepGovernance
Private voting
End userAs a DAO token holder, I want my votes to remain anonymous by default so that I can express my true opinion without fear of retaliation or social pressure.