Alok Vasudev
@alok
Let's assume that (1) KYC as-is is broken and a security risk due to potential data leakage and (2) dropping ID checks altogether is a nonstarter. What's the solution?
5 replies
3 recasts
39 reactions
Alok Vasudev
@alok
I've seen a lot of hand-waivey "zk fixes this". Ok, how?
2 replies
0 recast
12 reactions
Dan Romero
@dwr.eth
PII with an expectation of privacy should be locked down within companies. Like private keys or passwords. Any leak should come with a per instance leak penalty of $10,000 automatic disclosure / pay out to the individual affected. Companies have 3 years to migrate. Put a clear penalty in place, companies would update their systems.
1 reply
2 recasts
14 reactions
df
@df
orbs
0 reply
0 recast
1 reaction
Seth
@sethpate
zk.me works well. Totally eliminates the data at rest attack surface. The client side production of snarks means the onus of responsiblity lies on the user to not have their devices compromised tho... Also the SBT is static. So reproofing must occur for KYC compliance checks. I'm using their service in my app for sybil resistance and to detect and expel fraudsters. Very grateful they exist.
0 reply
0 recast
1 reaction
DrBoolean
@drboolean
some really interesting projects working on this. I find it odd how little alignment there is between different wgs as I imagine a unified spec benefits all 🤷♂️ anywhoo, gordion envelope has some firepower imo👌 🔐 https://github.com/BlockchainCommons/Gordian/blob/master/Envelope/Use-Cases/README.md
0 reply
0 recast
0 reaction
