zkMe (@zkme

zkMe

2,860 posts

zkMe

@zkme_

Building Web3's go-to zk-credential layer, ensures secure, private verification DIDs w/o oversharing personal info. Backed by @multicoin, @OKX_Ventures

linktr.ee/zkme

Joined September 2022

Pinned
zkMe
@zkme_
Jun 18
Age checks for under-16s could leave everyone needing a digital ID to use social media. That worry makes sense. Calling the system "privacy-preserving" does not make it go away. Can we check one age threshold without building a reusable identity layer? #SocialMediaBan
zkMe
@zkme_
Jun 18
Article
Privacy-Preserving Age Verification Without Universal Digital ID
The case for checking age online usually starts with a reasonable aim: children should not be exposed to products and content that are not meant for them. The objection is reasonable too. If social...
1.2K
zkMe
@zkme_
Jun 18
Yes/no is a good start. It doesn't settle the privacy question. The concern is everything around that answer: account IDs, device data, IPs and whatever metadata gets kept. If separate checks can be connected back to the same person, you've reduced disclosure. You haven't
Sam
@SamCKx
Jun 17
The biggest lie being spread about age verification is that it’s some backdoor for the government to see everything you do online. That’s simply not how modern age verification works. I’ve worked with KYC, AML and age verification systems for years. In nearly all cases, the age
505
zkMe
@zkme_
Jun 18
Good age assurance should answer four questions: 1. Is the proof unlinkable across services? 2. Who retains the metadata, and for how long? 3. Does raw identity data ever leave the user’s device? 4. Can the system be repurposed beyond the original age check? Privacy needs
170
zkMe
@zkme_
Jun 18
Replying to @zkme_
Read more:
Privacy-Preserving Age Verification Without Universal Digital ID
From blog.zk.me
609
zkMe
@zkme_
Jun 18
Article
Privacy-Preserving Age Verification Without Universal Digital ID
The case for checking age online usually starts with a reasonable aim: children should not be exposed to products and content that are not meant for them. The objection is reasonable too. If social...
1.8K
zkMe
@zkme_
Jun 17
The UK's under-16 social media ban has people worried for a reason. Nobody wants child safety to become an excuse for every app, platform, or device to collect more identity data. Age checks may be coming. The question is whether they can be designed without building another
910
zkMe
@zkme_
Jun 17
Replying to @zkme_
zkMe's view is that device-level age checks should evolve into privacy-preserving device-level proofs. Keep proof generation close to the user. Use selective disclosure. Avoid making proofs linkable across apps. Do the check without turning age assurance into cross-platform
116
zkMe
@zkme_
Jun 17
That gives platforms a way to meet access rules without storing raw identity data. It gives users fewer reasons to hand over documents again and again. And it gives regulators a cleaner path: prove the threshold, reveal the minimum, and do not make child safety depend on
105
zkMe
@zkme_
Jun 16
Meta is right about one thing: people should not have to hand over ID to every app they use. But device-level age checks only solve the problem if they avoid becoming another identity database. The better model is simple: Prove the age threshold. Reveal nothing else. Create no
Politics UK
@PolitlcsUK
Jun 15
🚨 NEW: Facebook and Instagram owner Meta has called for device-level age checks in response to the UK's social media ban for children "People shouldn't be asked to hand over ID to dozens of individual services to prove their age"
707
zkMe
@zkme_
Jun 15
Monday thought, as the UK announces its under-16 social media ban: People are asking whether enforcement means digital ID for everyone, where age-check data goes, and how plans to give 16-year-olds the vote sit alongside possible social media curfews. These concerns are not
479
zkMe
@zkme_
Jun 10
Proof of human will probably land first in places where impersonation has a real cost. Video meetings. Signing flows. Dating. Agent delegation. When trust failure gets expensive, "this account exists" stops being enough. That is usually when a trust check starts turning into
407
zkMe
@zkme_
Jun 8
For a long time, the internet treated accounts as a rough stand-in for people. That worked well enough. Until it didn't. As agents, synthetic interactions, and automated actions get closer to real product use, "this account exists" is no longer much of a trust signal. A lot of
338
zkMe
@zkme_
Jun 5
The next phase of Web3 and AI will need more than access. It will need verifiable trust, accountable identity, and compliance without raw data exposure. Our Founder & CEO @zkm_alex will be speaking on this at #WikiEXPOHK2026. See you there. #zkMe #zkKYC #WikiGlobal
WikiEXPO
@Wikiexpo_global
Jun 3
🎤 Speaker at #WikiEXPOHK2026 Alex D. Scheer is Founder & CEO of @zkme_ , a leading self-sovereign identity platform enabling privacy-preserving KYC and compliance through zero-knowledge technology. With over 10 years of SaaS product experience at companies including Bosch, BMW,
546
zkMe
@zkme_
Jun 3
The Instagram account hijacking story is the kind of thing AI builders should sit with for a minute. The scary part is not that a support bot gave a bad answer. It is that an AI assistant appears to have been close enough to account recovery to help someone take control. 🧵
994
zkMe
@zkme_
Jun 3
Replying to @zkme_
This is the direction we are building toward at zkMe. privacy-preserving identity, selective disclosure, verifiable credentials, and agent authorization infrastructure that can support policy checks, TEE-backed execution, and auditable flows. 🧵 11/12
161
zkMe
@zkme_
Jun 3
AI agents are moving from answering questions to taking actions. That changes the security standard. Agents should not be trusted because they sound convincing. They should be allowed to act only when authority can be proven. 🧵 12/12
143