Devcon Archive logo
Devcon Devconnect Forum Blog
  • Watch
  • Event
    Event: background logo
    • Devcon 7
    • Devcon 6
    • Devcon 5
    • Devcon 4
    • Devcon 3
    • Devcon 2
    • Devcon 1
    • Devcon 0
    • Devconnect ARG
  • Categories
    Categories: background logo
    • Cryptoeconomics
    • Devcon
    • Developer Experience
    • Coordination
    • Core Protocol
    • Layer 2s
    • Real World Ethereum
    • Cypherpunk & Privacy
    • Security
    • Applied Cryptography
    • Usability
  • Playlists

Suggested

Loading results..

View all

About Devcon —

Devcon is the Ethereum conference for developers, researchers, thinkers, and makers.

An intensive introduction for new Ethereum explorers, a global family reunion for those already a part of our ecosystem, and a source of energy and creativity for all.

  • Watch
  • Devcon
  • Devconnect
  • Forum
  • Blog

Get in touch

devcon@ethereum.org

Subscribe to our newsletter

Crafted with passion ❤️ at the Ethereum Foundation

© 2026 — Ethereum Foundation. All Rights Reserved.

devcon8 / proof of personhood without scanning your eyeballs

  • YouTube
⁠Proof of personhood without scanning your eyeballs preview
  • Details

⁠Proof of personhood without scanning your eyeballs

Duration: NaN:NaN:NaN

Speaker: Jay Sojitra

Type: Lightning Talk

Expertise: Deep prior knowledge

Event: Devcon

Date: Nov 2026

AI agents can now pass for human in most online interactions, which quietly breaks something load-bearing: "one human, one account." Sybil resistance underpins voting, airdrops, reputation, and moderation and CAPTCHAs and phone numbers fail the moment a model solves them faster than we do. The industry's default fix is biometric: scan an iris or face for a uniqueness token. I'll argue this fails on three axes that also work as a rubric for judging any personhood system, revocability (you can't rotate a leaked iris), linkability (the enrollment set becomes the ultimate cross-context tracking key), and inclusivity (scan-or-be-excluded). Then the alternatives, with honest tradeoffs: ZK nullifiers for one-token-per-person without a stored identifier; proofs derived from credentials people already hold; and social-graph attestation. None is free, I'll be clear on where each leaks or breaks.

Categories

IdentityAIBiometricsPrivacy