DIDs are public liability. A Decentralized Identifier (DID) anchored to a blockchain like Ethereum or Solana creates a permanent, public record of a researcher's affiliations and activities. This transparency directly conflicts with the need for pre-publication privacy and competitive advantage in fields like drug discovery.
decentralized-science-desci-fixing-research
Blog
Why Decentralized Identifiers Are Useless Without Privacy-Preserving Proofs
Decentralized Identifiers (DIDs) promise user sovereignty but create a permanent, public record of all activity. For DeSci, this is catastrophic. Zero-Knowledge Proofs (ZKPs) are the only way to prove credentials—like a medical diagnosis or peer review—without doxxing the researcher's master identity.
introduction
THE IDENTITY GAP
Introduction: The DeSci Privacy Paradox
Decentralized Identifiers (DIDs) fail to enable meaningful scientific collaboration because they expose sensitive researcher data on public ledgers.
Privacy is the predicate for trust. The promise of verifiable credentials (VCs) for peer review or grant distribution is nullified without privacy. A public DID allows competitors to map a researcher's entire network and review history, creating disincentives for honest participation.
Zero-Knowledge Proofs are the bridge. Protocols like Sismo and zkPass demonstrate that privacy-preserving proofs are the missing layer. A researcher proves credential validity (e.g., a PhD from MIT) via a ZK-SNARK without revealing the underlying DID, solving the paradox.
Evidence: The World Wide Web Consortium (W3C) DID standard has 100+ implementations, but adoption in biotech is near-zero. Contrast this with the growth of zk-rollups like Aztec, built explicitly for private state, highlighting the market demand for privacy-first infrastructure.
key-trends
WHY PUBLIC IDENTIFIERS FAIL
The Three Fatal Flaws of Public DIDs in Research
Decentralized Identifiers (DIDs) promise user sovereignty, but public on-chain implementations create critical vulnerabilities for research and collaboration.
01
The Correlation Problem: Public DIDs Are a Deanonymization Engine
Every on-chain action linked to a public DID creates a permanent, linkable record. This destroys privacy and enables sophisticated tracking.
- Activity Correlation: A single public DID can link your Gitcoin grant history, Snapshot votes, and research paper submissions.
- Social Graph Exposure: Public attestations reveal your entire professional network, exposing collaborators and affiliations.
- Impossible for Sensitive Research: Makes participation in fields like healthcare, finance, or policy research untenable due to data leakage.
100%
Linkable
0
Plausible Deniability
02
The Sybil Problem: Public DIDs Enable Low-Cost Reputation Gaming
Without privacy, reputation systems built on public DIDs are trivial to manipulate, rendering them useless for credible research.
- Cost of Attack: Creating thousands of fake public identities costs only gas fees, not social capital.
- Reputation Inflation: Systems like Gitcoin Passport become vulnerable to sybil farming, diluting grant funding and peer review.
- No Trust Layer: Makes it impossible to verify unique human contribution in decentralized science (DeSci) platforms like VitaDAO or LabDAO.
$<1
Cost per Fake ID
Infinite
Sybil Scale
03
The Solution: Zero-Knowledge Proofs for Private Credentials
Privacy-Preserving Proofs (ZKPs) are the only viable foundation for DIDs in research. They allow verification of credentials without revealing underlying data.
- Selective Disclosure: Prove you are a tenured professor or published in Nature without revealing your public DID or specific paper.
- Unlinkable Interactions: Use credentials across Snapshot, Galxe, and research platforms without creating a correlatable trail.
- Sybil Resistance: Platforms like Worldcoin (for uniqueness) or Sismo (for ZK badges) provide the privacy layer public DIDs lack, enabling ZK-proof-of-personhood.
ZK-Proofs
Core Tech
0
Data Leaked
deep-dive
THE PRIVACY IMPERATIVE
From Identity Graph to Zero-Knowledge Credential
Decentralized Identifiers (DIDs) create a public, linkable graph of user activity that is useless for real-world adoption without zero-knowledge proofs.
DIDs are public linkability graphs. A Decentralized Identifier on Ethereum or Solana is a permanent, on-chain record. Every attestation, credential update, or verification creates a public transaction, allowing anyone to map a user's entire digital footprint and relationships.
Zero-knowledge proofs are the privacy layer. Protocols like Sismo and zkPass transform raw DID data into private credentials. They generate a ZK-SNARK proof that you hold a valid credential without revealing the credential itself or your underlying DID, breaking the public link.
The standard is insufficient without the proof. The W3C Verifiable Credentials data model provides interoperability, but publishing VCs on-chain or to a public resolver like Ceramic replicates the linkability problem. Privacy is not an add-on; it is the core requirement.
Evidence: Sismo's ZK Badges, used by protocols like Aave and Lens, demonstrate the model. Users prove membership or reputation from sources like GitHub or Twitter without exposing their handles, making Sybil resistance compatible with privacy.
WHY VERIFIABLE CREDENTIALS AREN'T ENOUGH
Public DID vs. ZKP-Enabled Identity: A Comparative Breakdown
Compares the core architectural and privacy trade-offs between public, on-chain identifiers and those enhanced with zero-knowledge proofs, demonstrating why DIDs are a liability without selective disclosure.
| Feature / Metric | Public DID (e.g., Ethereum Name Service, Veramo) | ZKP-Enabled Identity (e.g., Polygon ID, Sismo, zkPass) | Hybrid / Off-Chain Verifier (e.g., Worldcoin, Iden3) |
|---|---|---|---|
On-Chain Data Exposure | Full credential payload (e.g., birth date, KYC status) | Only cryptographic commitment (e.g., Merkle root, nullifier) | Selective data hashes; biometric template off-chain |
Selective Disclosure Granularity | |||
Proof of Uniqueness (Sybil Resistance) | Requires public linkage of all actions | Private nullifier proofs (1 user = 1 proof, no linkage) | Biometric orb attestation; on-chain nullifier |
Gas Cost for Verification (Mainnet, approx.) | $0.50 - $2.00 (simple sig verify) | $2.00 - $10.00 (ZK-SNARK verify) | $0.10 - $1.00 (sig verify + nullifier check) |
Trust Assumption (Verifier Side) | None (cryptographic only) | Trusted setup for circuit; soundness security | Trust in hardware/operator (e.g., Orb) + cryptography |
Composability with DeFi | Direct (e.g., token-gated DAO) | Via proof verification contracts (e.g., Aave GHO with zk-KYC) | Via attestation registry (e.g., World ID smart contracts) |
Data Correlation Risk | Permanent, global graph of all activity | Unlinkable across sessions via nullifiers | Linkable if using same identifier; mitigated by application design |
Revocation Mechanism | On-chain CRL update (costly, transparent) | ZK proof of non-revocation from accumulator | Centralized issuer updates off-chain attestation state |
protocol-spotlight
THE ZERO-KNOWLEDGE IDENTITY LAYER
Architecting Privacy: Protocols Building the Stack
Decentralized Identifiers (DIDs) without privacy are just public databases. The real stack is being built by protocols that enable selective, verifiable disclosure.
01
The Problem: DIDs Are Just Public Keys in a Fancy Wrapper
A standard DID on a public ledger like Ethereum reveals your entire interaction graph. Every attestation, from KYC to credit score, becomes a permanent, linkable record.
- Enables mass surveillance and deanonymization.
- Creates toxic data that users cannot selectively hide.
- Fails GDPR's 'right to be forgotten' by design.
100%
Linkable
0
Selective Disclosure
02
The Solution: Semaphore-Style Anonymous Credentials
Protocols like Semaphore and Sismo use ZK proofs to decouple identity from action. You prove membership in a group (e.g., 'verified human') without revealing which member you are.
- Enables anonymous voting and signaling from a verified set.
- Prevents sybil attacks while preserving individual privacy.
- Gas-efficient group membership proofs (~100k gas).
~100k
Gas per Proof
∞:1
Anonymity Set
03
The Infrastructure: zkPass & Privado for Private Data Verification
These protocols act as TLS-Notary equivalents for web2 data. They let you generate a ZK proof that your private data (e.g., bank statement) satisfies a condition (e.g., 'income > $50k') without revealing the raw data.
- Bridges web2 trust to web3 privately.
- No data intermediaries; user holds keys.
- Critical for undercollateralized lending and compliance.
TLS 1.3
Security Standard
0
Data Leakage
04
The Application: Polygon ID & Verifiable Credentials Flow
Frameworks that operationalize the W3C Verifiable Credentials standard with ZK. Issuers sign claims, holders generate ZK proofs for verifiers.
- Replaces SSO with privacy-preserving authentication.
- Enables portable reputation across dApps.
- Interoperable via IETF/BBS+ signature standards.
W3C
Standard
BBS+
Crypto Primitive
05
The Limitation: The Oracles of Identity
The privacy stack's weakest link is the issuer. A government issuing a ZK-proof passport still knows your identity. Decentralized attestation networks (Ethereum Attestation Service, Bloom) mitigate but don't eliminate this.
- Shifts trust, doesn't eliminate it.
- Requires decentralized issuance for censorship resistance.
- Active research area in consensus-based attestation.
1-of-N
Trust Assumption
EAS
Key Protocol
06
The Future: Proof-Carrying Data & Recursive Reputation
Next-gen systems like Succinct Labs' SP1 enable proofs about proofs. Your reputation becomes a recursive ZK attestation that compounds privately.
- Enables complex credential graphs (e.g., 'prove you have 2 of 3 credentials').
- Makes reputation a private, composable asset.
- Lays groundwork for private DAO governance and hiring.
Recursive
Proofs
SP1
Execution Engine
counter-argument
THE PRIVACY PARADOX
Steelman: Transparency Ensures Accountability, Right?
Public on-chain identity is a surveillance tool, not an accountability mechanism.
Public DID is a liability. A Decentralized Identifier (DID) on a public ledger like Ethereum creates a permanent, linkable record of all associated actions. This enables sophisticated chain analysis by firms like Chainalysis, turning transparency into a weapon for profiling and censorship.
Accountability requires selective disclosure. True accountability is proving a specific claim (e.g., 'I am accredited') without revealing your entire identity. Systems like zero-knowledge proofs (ZKPs) and platforms like Sismo enable this, moving from 'everything is public' to 'nothing is revealed except the proof'.
Transparency without privacy fails. The Web2 model of data breaches and surveillance repeats if DIDs are public. The correct architecture uses privacy-preserving proofs on-chain with private state management off-chain, akin to how Aztec handles private transactions.
takeaways
WHY DIDs ARE USELESS WITHOUT PRIVACY
TL;DR for Builders and Funders
Decentralized Identifiers (DIDs) promise user sovereignty, but without privacy-preserving proofs, they create permanent, linkable ledgers of identity—the antithesis of self-sovereignty.
01
The Problem: Public DIDs are a Reputational Prison
On-chain DIDs create a permanent, public ledger linking all your actions. This enables Sybil attacks but also destroys privacy for legitimate users. Every interaction—from a DeFi loan to a governance vote—becomes a public dossier.
- Permanent Linkability: All activity is trivially correlated.
- Chilling Effects: Users avoid sensitive on-chain actions (e.g., health DAOs, political donations).
100%
Public
0
Privacy
02
The Solution: Zero-Knowledge Proofs (zkProofs)
zkProofs (e.g., zk-SNARKs, zk-STARKs) allow users to prove credential validity (e.g., "I am over 18", "I have a score > 750") without revealing the underlying data. This separates authentication from identification.
- Selective Disclosure: Prove only what's necessary for the interaction.
- Unlinkability: Proofs for different apps cannot be correlated back to a single DID.
~300ms
Proof Gen
~10KB
Proof Size
03
The Architecture: Private Identity Stacks (Sismo, Polygon ID)
Practical systems like Sismo (ZK Badges) and Polygon ID use zkProofs to create reusable, private attestations. They act as a privacy layer between raw credentials and on-chain DIDs.
- Portable Reputation: Prove your GitHub contributions without revealing your handle.
- Composability: Private credentials can be used across DeFi, DAOs, and social apps.
1M+
ZK Badges
Gasless
Verification
04
The Business Case: Unlocking Regulated Markets
Privacy-preserving proofs are the key to compliant decentralization. They enable KYC/AML verification for DeFi without doxxing users, unlocking institutional capital and regulated assets (RWA).
- Institutional Onboarding: Prove accredited investor status privately.
- Regulatory Compliance: Audit the proof system, not the user's personal data.
$10B+
RWA Market
GDPR
Compliant
05
The Pitfall: Centralized Attesters
If the entity issuing the credential (the Attester) is centralized, the system fails. The goal is decentralized attestation networks (e.g., Ethereum Attestation Service) where trust is distributed.
- Single Point of Failure: A centralized attester can revoke or censor identities.
- Trust Minimization: Credentials should be verifiable against decentralized consensus.
1
Failure Point
High
Censorship Risk
06
The Metric: Privacy Budget & Linkability
Measure privacy leakage. A privacy budget quantifies how much information is revealed over time. Systems must be designed to minimize cross-context linkability.
- Key Metric: Entropy loss per transaction.
- Build For: Unlinkability across applications, not just anonymity within one.
~0.1 bits
Leak/Tx Goal
Zero
Cross-App Link
ENQUIRY
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.
NDA Protected
Confidentiality24h Response
Time to ValueDirectly to Engineering Team
No Sales Fluff10+
Protocols Shipped
$20M+
TVL Overall