Alternatives
Products that do what There's No Cryptographic Integrity in How We Prove We're Safe does
I built a platform that lets users verify their identity and run a background check—and securely share proof of a clean record without exposing personal details like full name, address, or date of birth. This is something we found missing in all other services: they keep the data locked in their systems and share way too much when you want to prove you're safe. We built a privacy-first solution where you control your data. Use case: You’re a high-profile individual or just privacy-conscious, and want to prove you're safe to meet—say on a dating app—without revealing where you live or your…
- 1NA
We just shipped a new feature in NextDNS: Bypass Age Verification. More and more sites (especially adult ones) are now forcing users to upload IDs or selfies to continue. We think that’s a terrible idea: handing over government documents to random sites is a huge privacy risk. This new setting workarounds those verification flows via DNS tricks. It’s available today to all users, including free accounts. We’re curious how the HN community feels about this. Is it the right way to protect privacy online, or will it just provoke regulators to push harder? https://nextdns.io
2025
- 2
- 3
- 4
- 5
This project has been kicking around in my head since I first heard about the webauthn PRF extension in early 2024. I've slowly chipped away at it since, and finally got things to a shareable state over the summer thanks to a very fun parental leave. Headed back to work tomorrow, so I figure there's no time like the present. tldr: A client-held encryption key derived during passkey authentication encrypts all sensitive user data prior to persistence so that only the user is able to decrypt and reuse that data on their device. This allows short-lived, privacy-preserving age proofs to be…
18d ago · loginwithone.com
- 6AA
So I'm not an expert in this area, but here's an attempt at cost effective, anonymous, age verification flow that probably covers ~70% of use cases in the United States. The basic premise is to leverage your bank (who already has had to perform KYC on you to open an account) to attest to your age for age-restricted merchant sites (pornhub, gambling, etc) without sharing any more information than necessary. Flow works like this: 1) You go to gambling.com 2) They request you to verify your age 3) You choose "Bank Verification" 4) You trigger a WebAuthn Credential Creation flow 5) gambling.com…
2025 · gist.github.com
- 7
- 8
- 9
- 10HP
2018 · webbkoll.dataskydd.net
- 11
- 12SA
Hi HN, We (myself, Adhyyan1252 and yush_g) are undergrad students that hacked out this side project last month during Hack Lodge[1] (the ideas and many of the underlying circuits for which came from the 0xPARC community[2])! We’re extremely excited to share this new primitive. Besides the technical challenges building this project that folks here would find interesting (fixing the ZK proof compiler, modifying nodeJS V8 params etc.), we think this is a very novel use case for ZK tech, and ECDSA inside ZK-SNARKs is a starting point that unlocks many other ideas! :D A summarized version of our…
2022 · github.com
- 13
- 14
- 15
- 16
- 17
- 18
- 19
- 20
- 21
- 22
- 23SM
2021 · safeapps.io
- 24SP
So the main purpose here is to show _a_ way that session-token theft can be mitigated. Clearly, this isn't NSA proof or something you'd use to secure a BL5 containment facility, but to prevent session-jacking; if feels like it could help a lot, and would be pretty quick and easy to roll out if an IDP wanted to implement it.
2024 · github.com
Ranked by how close each launch is in meaning, then by votes. Refine with a description →