Digital identity has a bad habit: a system asks one small question—are you old enough, eligible enough, local enough?—and reaches for the whole card, account or profile.
Google’s donation of its Longfellow Zero-Knowledge Proof library to the Post-Quantum Cryptography Alliance is interesting because it points at a better interaction. A verifier could learn a narrow fact, such as whether someone is over 18, without receiving the person’s name, address, date of birth or a photo of an ID.
Google says the library, which it open-sourced last year, will now sit under vendor-neutral stewardship at a Linux Foundation Europe project. That is a sensible move for identity infrastructure. It is also far from a finished privacy revolution.
What Longfellow is trying to change
Zero-knowledge proofs are cryptographic methods for showing that a statement is true without exposing the information used to prove it. The concept sounds abstract until you put it beside an ordinary age gate.
| A typical age check | A privacy-preserving ideal |
|---|---|
| Upload an ID image or share a date of birth | Present a proof that you meet the age threshold |
| A service may receive more personal data than it needs | The service receives the answer to its narrow question |
| The service must store, secure or pass along sensitive details | There is less sensitive detail to collect in the first place |
| The check can become another tracking moment | The design can reduce unnecessary identity exposure |
Google’s example is age verification, but the pattern applies more broadly: membership, residency, a license class or another claim where the receiving service needs a yes-or-no answer rather than a biography.
The attraction is not that the technology makes identity disappear. It makes the request proportional. That is the privacy standard the web has usually failed to meet.
Why the handoff matters
Cryptography is not made trustworthy because a large company says it is useful. It needs inspection, independent expertise, stable governance and the ability for implementers to challenge the owner’s choices.
Moving Longfellow to the Post-Quantum Cryptography Alliance matters because it changes the project’s center of gravity from a single vendor to a collaborative home. Google says it will continue developing and supporting the code in the open; that is helpful, but it should not be confused with a completed standard or universal interoperability.
The published Longfellow materials describe a proof system intended to establish claims about a computation without revealing extra witness information. Its design documents and IETF Cryptography Research Group presentation are useful technical references, but they do not substitute for the kind of sustained implementation review that identity systems deserve.
That caveat is especially important because the project’s language includes post-quantum ambitions. “Post-quantum” is not a magic quality granted to an entire product. It depends on the exact protocol, assumptions, implementation and surrounding credential system. A privacy-preserving proof can be one component of a future-ready design without making every part of a digital-ID stack automatically future-proof.
The phone is not the hard part
The consumer-facing demo will be irresistible: a phone shows a green check; the website learns only “yes.” GearPulse readers should look past the animation.
| Layer | The real question |
|---|---|
| Credential issuer | Who vouches for the claim, and how is that trust established? |
| Wallet | Can people move credentials safely across devices and recover access? |
| Proof library | Has the code been independently audited and implemented correctly? |
| Verifier | Does the website genuinely ask for the minimum necessary fact? |
| Policy | Is age, residency or eligibility defined consistently and fairly? |
| Abuse resistance | Can the system limit fraud without turning every check into surveillance? |
The first four problems are engineering. The last two are where technology often gets used to smuggle in a policy decision. A good proof system cannot decide whether a site should be demanding age verification in the first place.
A realistic measure of success
The best outcome is not every website suddenly adopting a new cryptographic library. It is a boring, interoperable route for a credential issuer, wallet and verifier to agree on a minimal proof—without one platform controlling all three.
That demands published specifications, outside security reviews, accessible reference implementations and genuine multi-vendor testing. It also demands product restraint. If a verifier can learn that a visitor meets an age threshold, it should not use the proof as an excuse to build a new identity trail around that visitor.
Google’s existing Wallet work makes the motivation concrete. Our look at supervised balances for kids showed how quickly financial and family features turn a phone into an identity surface. As wallets accumulate tickets, payments, passes and credentials, presenting the smallest necessary fact becomes more important—not less.
Bottom line
Longfellow’s Linux Foundation handoff is a promising governance step for a technology that deserves skepticism and patience in equal measure.
The useful promise is not “digital ID, but on a blockchain” or “show your phone everywhere.” It is smaller and better: if a service only needs one answer about you, it should not get your whole story. Longfellow gives that idea a technical path. Audits, standards work and restrained product design will decide whether the path becomes trustworthy enough to use.
Support independent source-backed coverage at buymeacoffee.com/gearpulse.site.