"Privacy by default. Disclosure by choice." Meet @GustavoValverde, developer at @zcashfoundation, Zama Developer Program winner and the builder behind @zentityID which is privacy-preserving identity. A conversation from the Builder Villa at EthCC[9] ⬇️

My paper was accepted for Open Identity Summit 2026 🎉 "From Evidence to Eligibility: A Privacy-First Architecture for Interoperable Eligibility Verification" I've been quiet here, but I've made a lot of improvements to @zentityID architecture htw-dresden.de/hochschule/ak…

Identity verification worldwide is built on a false premise: that confirming who someone is requires collecting and storing their personal data.

The common industry assumption that "KYC means storing plaintext PII" is a design choice, not a legal requirement. Why are the mainstream Identity Verification providers choosing to store it in plaintext?

RT @zachxbt: @sumsub A bit tone deaf to publish an article on other company incidents when Sumsub just disclosed a threat actor had access…

This is why Zentity is being built, because KYC won't stop, and breaches will only increase in size as time passes. theverge.com/tech/875309/dis…

We're not only reforming KYC, but also Authorization. We've created a centralized authorization server that achieves privacy properties previously only seen in decentralized wallet-based systems (SIOPv2, SSI), while maintaining full compatibility with standard OAuth 2.1/OIDC

Every breach proves the KYC and Identity verification model is broken. - Coinbase: $355M, 69K IDs stolen. - ICRC: 515K refugees exposed. - Optus: 10M Australians documents. We've been building a different approach. Identity verification and authorization with nothing to steal

Identity verification for KYC has a design flaw. When you verify someone's age, you don't need their birthday. You need to know they're old enough. But traditional systems store everything anyway. Then spend billions "securing" data they didn't need to keep.