Proof of personhood without CAPTCHAs
Confirming a real, distinct human is behind a request, without a puzzle that machines now beat and many disabled people never could. The service keeps out bulk automation without turning away the disabled users the old puzzles excluded.
The impact of agents
As agents defeat the challenge tests that once both blocked bots and rationed access by friction, government has to confirm a real, distinct human is behind the request without falling back on a method that shuts people out.
The old test fails on both sides: AI has defeated most CAPTCHA types, and the test itself excludes people with disabilities. The W3C's "Inaccessibility of CAPTCHA" working note records that "the very nature of the interactive task inherently excludes many people with disabilities, resulting in a denial of service to these users."
What must be verified
Government needs to confirm that a request comes from a real, distinct human without running an identity dragnet or collecting biometric data, so that bot abuse is curbed while the person keeps their pseudonymity.
Protecting access
Device-bound attestation assumes a personal, recent device. Users on shared, borrowed, or older hardware are denied outright. Any CAPTCHA fallback re-imposes the denial of service the W3C documents for people with disabilities. No one must ever lose access to government for a well-founded refusal to hand over an iris scan.
Keeping the path open
- Hold a non-device pathway at parity: in-person verification that mints the same time-limited token.
- Make no CAPTCHA modality the only route.
- Have the token attest nothing but personhood, so the pseudonymous stay pseudonymous.
Response surface
Human presence is confirmed in the background, with an in-person route offered alongside, in place of the visual puzzle that locks out people with disabilities.
Your device confirmed you’re a person automatically. No further step is needed.
The check confirms a person is present. It never asks the person to prove they are the right kind of person — no puzzle, no timed test, no image grid. When the automatic path fails, the route is in-person issuance, and no submission records which path minted the token.
Maturity
- Emerging Headline
For the cryptographic, privacy-preserving response this pattern proposes, workable today but not yet a settled government practice.
- Frontier
For biometric approaches, deployed at scale by a private venture with no government adopter, and restricted by regulators in Kenya and Spain.
Precedents
World ID, biometric proof of personhood. The system uses iris scans taken on a proprietary device to generate cryptographic proof that a user is a unique human, with zero-knowledge proofs verifying personhood without revealing identity. Buterin warned that strict one-person-one-ID systems threaten pseudonymity and could be defeated by fakes built to fool the device or by coerced scans. The design creates a centralized registry of the most sensitive data there is.
Regulatory action against World ID. Kenya's High Court found the collection of biometric data unlawful and ordered the data deleted within seven days, and Spain's AEPD ordered Tools for Humanity to stop collecting and processing personal data in Spain and to block what it already held. Brazil's ANPD ended the practice of paying people in cryptocurrency for their biometric data, and at least eight countries have banned, suspended, or restricted operations. The mechanism works and has been stopped by regulators in several jurisdictions on data-protection grounds.
Privacy Pass and Private Access Tokens. The IETF-standardized protocol, developed by Cloudflare, Apple, Google, and Fastly, lets a user prove they are human without revealing identity, with Apple's Private Access Tokens attesting legitimacy from the device's secure enclave. Extensions cover per-origin rate-limited tokens and credentials presentable a fixed number of times per context. It avoids the biometric registry, at the cost of device binding and platform dependency.
W3C on the inaccessibility of CAPTCHA. The Group Draft Note states that the interactive task 'inherently excludes many people with disabilities, resulting in a denial of service to these users', and the Accessible Platform Architectures Working Group recommends non-interactive approaches where possible and a choice of modalities where interactive verification is required. The New Zealand Government's accessibility guide gives the same direction for government services. The incumbent check is documented by the web's own standards body as excluding.
What carries over to agent use
The transferable principle for government digital services is to verify human presence with a privacy-preserving, rate-limited token rather than a challenge test or a biometric registry. The rate-limited token model (Privacy Pass and related schemes) shows that principle:
- It does not require biometric data collection.
- It builds on existing device attestation infrastructure.
- It can be layered onto existing government identity systems (myGovID, GOV.UK One Login) to provide rate-limited but privacy-preserving access.
- The IETF (Internet Engineering Task Force) standardization provides an interoperable foundation.
Biometric proof-of-personhood is unlikely to be appropriate for government services in democratic jurisdictions, given regulatory hostility and the surveillance implications.
Where things go wrong
This is an access-gating pattern; the failure to avoid is an automated personhood check that excludes people who cannot pass it. No notice is given, and there is no route to review. A mandatory non-device fallback is the safeguard against that exclusion. A device-attested or in-person token can still be coerced or resold: someone can be paid or pressured to mint one and hand it over, or a compromised device can mint tokens on someone else's behalf. Binding each token to a single origin and a strict per-period rate limit caps what a resold or coerced token is worth, though it does not stop the coercion itself.
Sources
8 references
The instrument, the operating deployment, or the official record itself.
Writing about the subject rather than the framework itself, including vendor commentary.