ZK (and similar primitives) is useful in any setting where you want to ensure that rules are being followed despite information asymmetry between participants. as more social, financial, governance, etc. data is uploaded (or hash-committed to) on-chain, ZK becomes 1/

all of these require info asymmetry, and therefore require ZK (or MPC, or something similar).

privacy is important for ideological reasons, but even more fundamentally, information asymmetry is a *mechanic* that most complex coordination systems need to function. 3/3

necessary to allow anyone to permissionlessly make claims about this data at arbitrary levels of granularity. think ID and reputation systems, queries on public social graphs, fine-grained claims of creditworthiness, actions in digital games/virtual worlds... 2/