On-Chain Identity - Crypto Gloss

Identity on the internet has always been a fundamental unsolved problem. Web2 identity is siloed: your Twitter followers don’t travel to LinkedIn; your Amazon review reputation doesn’t help you on eBay. Each platform owns your identity and can delete it. Web3’s cryptographic infrastructure offers an alternative: portable, user-sovereign identity built on verifiable credentials — attestations that you own and can share selectively across any application. This entry maps the emerging on-chain identity stack, from basic ENS naming through ZK-proof-based private attestations and biometric proof-of-humanity solutions.

Why Identity Matters for Web3

The following sections cover this in detail.

The Current Identity Problem in Crypto

Wallet addresses are not identities: 0x742d35Cc6634C0532925a3b8D4C9C6d2a5e5... is not a recognizable identity. Users can’t verify counterparties, build reputation, or establish trust without external infrastructure.

Consequence: Crypto protocols must either:

Be fully permissionless and anonymous (enabling sybil attacks, bots, and fraud)
Import traditional identity (KYC via external providers — destroying privacy and creating centralization)
Build new on-chain identity infrastructure — the emerging solution

Key use cases unlocked by on-chain identity:

Sybil resistance: Quadratic voting, quadratic funding, and fair airdrops require 1-person = 1-vote guarantees
Undercollateralized lending: Credit scores based on on-chain transaction history
Reputation portability: Carry your trading skill, governance participation, and social connections across apps
Zero-knowledge proofs about identity: Prove you’re over 18, or a US citizen, or a medical professional, WITHOUT revealing which specific person you are

ENS (Ethereum Name Service)

The following sections cover this in detail.

What ENS Is

ENS maps human-readable names (vitalik.eth) to machine-readable blockchain addresses (0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045):

Core functionality:

Name → Address: vitalik.eth resolves to a specific ETH address
Name → Other records: ENS names can store Twitter handle, email, website URL, avatar, content hash (IPFS website)
Reverse resolution: An ETH address can set its “primary name” — dapps that check the reverse record can display vitalik.eth rather than 0xd8dA... in their UI

Technical structure:

ENS Registry: Central contract mapping name hashes to resolver contract addresses
Resolver contracts: Store the actual records (ETH address, text records, etc.)
Registrar: The smart contract managing .eth name registration and renewal

Registration and fees:

.eth names registered through the ENS App (app.ens.domains)
Annual renewal fees (paid in ETH): 5+ character names: $5/year; 4-character: $160/year; 3-character: $640/year
Names registered for 1–100 years upfront

ENS as identity layer:

3 million+ .eth names registered
Integration: Uniswap, Rainbow Wallet, MetaMask, Etherscan all display ENS names
“ENS identity” is the basic Web3 identity layer — the username system

Subdomains for protocols:

Aave.eth, uniswap.eth for protocol operations
alice.uniswap.eth — protocols can issue subdomains to users
Off-chain signatures for gasless subdomain creation

ENS governance: The ENS DAO governs the ENS Protocol via the ENS token. Revenue (registration fees) goes to the DAO treasury.

Lens Protocol: Portable Social Graph

The following sections cover this in detail.

What Lens Is

Lens Protocol is a decentralized social graph — a protocol for storing and owning your social connections, content, and followers on blockchain (primarily Polygon):

Core objects:

Profile NFT: Your Lens profile is an NFT you own. Moving to a new platform = bringing your profile.
Follow NFT: When someone follows you on Lens, they receive a “Follow NFT” — proof of the social connection that lives in their wallet
Publication: Posts, comments, and mirrors (retweets) stored on-chain via Lens publication
Module system: Custom fee modules (pay to comment, pay to follow), revenue share modules, collect mechanics

The portability argument:

On Twitter, Elon Musk can suspend your account and you lose your 1M followers. On Lens, your followers are on-chain. Any app building on Lens can read your followers. An app can’t take your social graph.

Lens ecosystem:

Lenster (now Hey): Twitter-like front-end for Lens
Phaver: Mobile social app built on Lens
Orb: Lens-native professional network
Buttrfly: Lens mobile app

Lens V2: Added Open Actions (external smart contract calls from Lens posts — enabling buying NFTs, staking, etc. from a social post), improved modules, and Momoka (off-chain data availability for high-frequency social data).

Limitations:

Gas fees on Polygon are minimal but still present for writes
Open invites are required to get a Lens handle (limited access)
Network effects are nascent vs. Twitter/X (much smaller user base)

Farcaster: Decentralized Social Protocol (Revisited as Identity)

The following sections cover this in detail.

Farcaster as Identity Infrastructure

Farcaster (covered in web3-social.md) is particularly relevant here as an identity layer:

Each Farcaster user has a FID (Farcaster ID) — a unique numeric identifier registered on the Farcaster ID Registry contract on Optimism
FIDs are persistent, wallet-controlled — no platform can remove your identity
Farcaster’s custody address and recovery address model: owners can recover FIDs if primary wallet is compromised

Identity-relevant Farcaster features:

Verified addresses: Link any ETH address to your FID; apps can verify you own claimed addresses
Connected wallets: Multiple wallets can be linked to one FID
Channel memberships: Participation in specific Farcaster channels creates attributable on-chain social signal

Warpcast, the primary Farcaster client: Includes verified ETH wallet display, NFT showcasing, and on-chain activity integration, making Farcaster profiles functionally rich identity cards for crypto-native users.

Worldcoin and World ID: Biometric Proof-of-Personhood

The following sections cover this in detail.

The Problem World ID Solves

Sybil attacks (one entity creating many fake identities) are the fundamental challenge for:

Universal Basic Income (UBI) distribution: One person could claim 1,000× their share
Quadratic voting: Fake identities dilute the 1-person-1-vote property
Fair airdrops: Bots claim disproportionate distribution
AI detection: “Is this a human or a bot?”

World ID is Sam Altman (OpenAI CEO) and Alex Blania’s solution: iris scan = unique human credential.

How World ID Works

Orb hardware: Visit a World ID Orb (available in many countries) for iris scan
Biometric processing: Iris scan converted to an “IrisCode” (numerical representation of iris pattern)
Uniqueness check: IrisCode checked against existing registry — would fail if iris already registered
World ID credential: User receives a ZK-based credential on their phone proving “unique human”
Privacy: The IrisCode itself is deleted; only a hash remains for duplicate-checking

World ID in use:

Proof-of-unique-humanity for dapps
Works via ZK proofs: Prove you’re a unique human without revealing which WLD address you are
Platforms creating “verified human” gated content/features

WLD token:

Distributed as UBI-like payments to World ID holders (biometric data as payment)
Available to trade but utility is primarily identity verification

Worldcoin controversy:

Biometric data collection in the Global South (Ghana, Kenya, Indonesia, India) raised significant ethical concerns — individuals given WLD tokens for their iris scans, raising exploitation concerns
Data security: Biometric data exposure risk is permanent (you cannot change your iris)
Regulatory: Spain, Italy, and others launched investigations or suspended Worldcoin operations (GDPR concerns)
Centralization: Worldcoin Tools Company controls the Orb hardware and IrisCode database

Gitcoin Passport: Aggregated Credential Scoring

The following sections cover this in detail.

What Gitcoin Passport Is

Gitcoin Passport aggregates signals from multiple web2 and web3 sources into a “humanity score” — a measure of whether a wallet address represents a unique, authentic person:

Stamps (credentials):

Web2: Twitter account verification, Google account, GitHub commits, LinkedIn profile, Discord activity
Web3: ENS name ownership, Proof of Humanity registration, BrightID connection, POAP history, Gitcoin donor history, Coinbase ID, Holonym, lens protocol profile, Farcaster account

Score calculation:

Each stamp has a weight
Total score = sum of weighted stamps
Threshold for sybil resistance: typically 15–20+ score required for quadratic funding participation

Use cases:

Gitcoin Grants QF (Quadratic Funding): High Passport score = more matched funding power
Snapshot governance: DAOs can require Passport score for voting
Zora creator access
Linea voyage points program (Linea used Passport for fair airdrop)

Key advantage over Worldcoin: Gitcoin Passport does not require biometrics. It aggregates existing identity signals. Lower guarantee of uniqueness but higher privacy and accessibility.

Sismo: ZK-Proof Identity Attestations

The following sections cover this in detail.

What Sismo Does

Sismo (now partly rebranded around “Reclaim Protocol” concepts) allows users to create selective disclosure proofs about their identity:

Applications:

Prove you hold >10 ETH without revealing your exact balance
Prove you were an early Ethereum adopter (wallet created before 2017) without revealing your wallet address
Prove you have BAYC-holder status without revealing your specific token IDs
Prove you participated in a specific protocol’s governance without revealing voting history

Technical mechanism (ZK attestations):

User has a “source wallet” (the actual wallet with the credential)
User generates a ZK proof that the source wallet satisfies the claim (owns a BAYC, voted in a governance proposal, has 10+ ETH)
The ZK proof is verified on-chain and mints an attestation to the user’s “destination wallet” (the pseudonymous wallet they use for the specific application)
The link between source and destination wallets is not exposed

Privacy-preserving use case:

An activist wanting to prove they have $10K+ in ETH (proof of financial capacity for a DeFi application) without revealing their actual wallet (which contains transaction history showing their physical location and activities) could use Sismo to generate the proof linking a private destination wallet to the source wallet’s verified balance.

Status: Sismo Protocol underwent evolution; Reclaim Protocol offers similar ZK attestation for web2 credentials (proving a LinkedIn follower count, proving web2 account existence without sharing login credentials).

Decentralized Identifiers (DIDs): The W3C Standard

The following sections cover this in detail.

What DIDs Are

The W3C Decentralized Identifier standard (adopted 2022) defines a standard format for globally-unique identifiers that:

Can be controlled by the subject (user)
Can be cryptographically verified
Do not require centralized registration authorities

DID format: did:method:method-specific-identifier

did:ethr:0x742d35Cc... — Ethereum-method DID based on wallet address
did:key:z6MkH... — Public key-based DID
did:web:example.com — Domain-based DID

DID documents: DIDs resolve to DID documents — JSON-LD documents specifying the authentication methods (public keys), service endpoints, and verification methods for that DID.

In the crypto identity stack: Most Ethereum-based identity projects use DIDs implicitly (wallet addresses as DIDs) or explicitly (issuing formal DID documents for wallet addresses).

Verifiable Credentials (VCs)

Paired with DIDs, Verifiable Credentials are standardized credentials:

Issuer: Signs a credential (e.g., “Harvard University certifies Alice graduated in 2020”)
Holder: Receives and stores the credential in their digital wallet
Verifier: Asks holder to present proof; verifies issuer signature against issuer’s DID document

The W3C VC standard is the formal framework underlying most “on-chain attestation” systems.

On-Chain Identity in Practice: Current State (2024)

Adoption:

ENS: 3M+ names; widely integrated in wallets/dapps
Farcaster: 300K+ monthly active users
Lens: 100K+ active users
World ID: 8M+ verifications globally
Gitcoin Passport: 900K+ wallets with score

Challenges remaining:

Interoperability: ENS doesn’t speak to Lens doesn’t speak to Farcaster natively
Cost: On-chain writes still cost gas, limiting casual usage
User experience: Privacy-preserving ZK proofs are technically complex for average users
Adoption chicken-and-egg: Apps need users to have identity credentials; users won’t set up credentials for unused apps

Optimistic outlook: The Ethereum attestation service (EAS), Sign Protocol, and similar infrastructure are building credentialing infrastructure that works across ENS, Farcaster, Lens, and World ID — eventually enabling a coherent “portable identity” that any dapp can read.

How to Establish an On-Chain Identity

Step 1: Register an ENS name at app.ens.domains. Cost: ~$5/year. This is the baseline.

Step 2: Set up a Farcaster account (via Warpcast). Cost: ~$5 in ETH one-time. This provides your social identity.

Step 3: Build Gitcoin Passport score — free, stamps from web2 accounts you already own.

Optional: World ID registration (available in many cities), Lens Protocol handle.

Buy ETH for identity setup:

Keep identity management secure with hardware wallet:

Social Media Sentiment

On-chain identity is gaining traction as a serious CT topic in 2026. ENS name registration continues as a status symbol; short .eth names signal membership in early crypto culture. Worldcoin’s World ID generates polarized debate — privacy advocates and anti-surveillance CT voices are critical of biometric data collection, while World ID supporters see it as viable proof-of-personhood. Lens Protocol and Farcaster debates focus on which decentralized social graph will achieve meaningful developer and user adoption.

Last updated: 2026-04

Related Terms

Sources

https://hey.xyz (Lens Protocol)

Reed, D., et al. (2020). Decentralized Identifiers (DIDs) v1.0: Core Architecture, Data Model, and Representations. W3C Working Draft, World Wide Web Consortium.

Buterin, V., Weyl, E.G., & Ohlhaver, P. (2022). Decentralized Society: Finding Web3’s Soul. SSRN Working Paper 4105763.

Sporny, M., et al. (2022). Verifiable Credentials Data Model v1.1. W3C Recommendation, World Wide Web Consortium.

Trask, N., et al. (2019). Peer DID Method Specification. Decentralized Identity Foundation Working Group Report.

Lesavre, L., Varin, P., Yaga, D., & Davidson, M. (2020). A Taxonomic Approach to Understanding Emerging Blockchain Identity Management Systems. NIST Interagency Report 8289. National Institute of Standards and Technology.