well, bringing the cost down is probably just a matter of time, isn't it?
what i think is more important is finding form factors of using zK that make sense to enterprises. from outgoing api calls to file sharing, the scope of vulnerabilities is extremely large.
while it probably makes sense for certain consumer data companies, do you think about cases where poor data security/privacy actually harms the company? eg: when sensitive company data gets leaked during third-party interactions?
alright, I don't fully disagree with this sentiment.
on (2), isn't that an application-layer fix? i.e build better/more secure wallets.
the underlying identity system with addresses seems useful is what I meant. I like to think of interesting access control systems that can be built upon this. using a wallet's ownership data/activity, you can assign access/rights.