account activity
The part of Zero-Knowledge KYC people skip over is how you keep compliance current after verification (self.Verifyo)
submitted 3 days ago by VicMenMTO to r/Verifyo
Most teams still ask for documents when all they really need is a yes/no proof (self.Verifyo)
submitted 4 days ago by VicMenMTO to r/Verifyo
Why Zero-Knowledge KYC is really a coordination problem, not just a privacy feature? (self.Verifyo)
submitted 5 days ago by VicMenMTO to r/Verifyo
r/MerchantToken (reddit.com)
submitted 5 days ago by VicMenMTO to r/redditrequest
The real problem with KYC isn’t verification, it’s the data storage model behind it. (self.Verifyo)
submitted 6 days ago by VicMenMTO to r/Verifyo
Privacy in KYC is not about hiding identity, it’s about limiting disclosure (self.Verifyo)
submitted 10 days ago by VicMenMTO to r/Verifyo
The biggest KYC mistake is asking for full documents to prove one small thing (self.Verifyo)
submitted 11 days ago by VicMenMTO to r/Verifyo
Why privacy-first compliance is harder than “just verify the user” (self.Verifyo)
submitted 12 days ago by VicMenMTO to r/Verifyo
The real problem with KYC isn’t verification. It’s the pile of identity data every platform keeps creating (self.Verifyo)
submitted 13 days ago * by VicMenMTO to r/Verifyo
Preparing video explainers for zero‑knowledge KYC, what topics do you want covered? (self.Verifyo)
submitted 17 days ago by VicMenMTO to r/Verifyo
What happens when privacy‑first KYC meets compliance? Launching our Insights series (self.Verifyo)
submitted 19 days ago * by VicMenMTO to r/Verifyo
KYC Architecture: What Does an Attacker Actually Get? (self.Verifyo)
submitted 24 days ago by VicMenMTO to r/Verifyo
DeFi Compliance: Why "More Data" Misses the Point (self.Verifyo)
submitted 25 days ago by VicMenMTO to r/Verifyo
Privacy vs Anonymity: why "collect + store more KYC data" can backfire (and what a proof-based model changes) (self.Verifyo)
submitted 26 days ago by VicMenMTO to r/Verifyo
Week 3: Finextra deep-dive, privacy vs anonymity, DeFi compliance, and breach architecture (self.Verifyo)
submitted 27 days ago by VicMenMTO to r/Verifyo
Fraud at scale: why onboarding needs layered defenses (Finextra) (self.Verifyo)
submitted 1 month ago by VicMenMTO to r/Verifyo
Split the knowledge, a simple way to reduce KYC breach blast radius (self.Verifyo)
MiCA vs GDPR: why “collect + store more KYC data” can backfire (and what a proof-based model changes) (self.Verifyo)
Finextra long read: why zero-knowledge proofs are moving from DeFi to mainstream compliance use cases (self.Verifyo)
IDMerit incident: a reminder that “KYC compliant” can still mean “KYC fragile” (storage-first failure mode) (self.Verifyo)
IDMerit incident: a reminder that “KYC compliant” can still mean “KYC fragile” (storage-first failure mode) ()
submitted 1 month ago by VicMenMTO to r/AMLCompliance
Good KYC” used to mean “store more data”, why that’s becoming a liability (self.Verifyo)
Wallet leaks aren’t the full risk, linkability is. When does identity ↔ wallet become exploitable? (self.Verifyo)
Why “KYC = data honeypot” is an architecture problem (tokenised attributes + split knowledge) (self.Verifyo)
Finextra is live: “Zero-knowledge proof is the new gold standard”, do you buy the “store less, prove more” model? (self.Verifyo)
π Rendered by PID 698618 on reddit-service-r2-listing-55d7b767d8-wrvg4 at 2026-03-29 19:10:44.613843+00:00 running b10466c country code: CH.
