Selective Attribute Disclosure via Zero Knowledge Proofs

39 concepts29 papers1 proposal

When you buy a drink at a bar, the bartender needs to verify that you are of legal drinking age. To prove this, you typically hand over a driver's license. While the license successfully proves your age, it also unnecessarily reveals your full name, exact home address, date of birth, and organ donor status.

In the digital world, this over-disclosure creates massive privacy risks. Traditional identity systems routinely force users to trade comprehensive personal profiles for access to services. However, a growing body of research demonstrates that this trade-off is a false dichotomy. By leveraging zero-knowledge proofs (ZKPs) and selective disclosure cryptography, it is possible to prove specific attributes about an identity—such as "is older than 21" or "possesses a valid security certification"—without revealing the underlying raw data or the user's real-world identity.

The Core Intuition: Decoupling Truth from Data

To understand why selective attribute disclosure works, we must look at how digital credentials are traditionally structured. Normally, an authority signs a digital document containing a bundle of attributes. To verify any single attribute, the user must present the entire signed document so the verifier can check the signature.

Selective disclosure breaks this rigid structure. Instead of verifying the raw data itself, the verifier checks a mathematical proof derived from the data.

As Jörg Rothe explains in a foundational tutorial on computational complexity, Some Facets of Complexity Theory and Cryptography: A Five-Lectures Tutorial, zero-knowledge protocols allow a prover to demonstrate the mathematical truth of a statement without revealing any underlying secrets. If one-way functions exist, any problem that can be verified efficiently (the NP complexity class) can be proven using these privacy-preserving interactive methods.

To bridge this theoretical capability into practical identity systems, researchers use two primary cryptographic primitives: cryptographic commitments and selective disclosure signatures.

Cryptographic Commitments

Think of a cryptographic commitment as a digital "sealed envelope." You place a piece of data (like your birth year) inside the envelope and lock it. You can hand this envelope to a verifier; they cannot see what is inside, but you can no longer change the value.

Krause et al. demonstrate in A Utility-Theoretic Approach to Privacy and Personalization that high-quality personalization can be maintained by selecting a small, optimized subset of user attributes rather than sharing comprehensive profiles. This minimizes identifiability risk while maximizing utility.

In an access control scenario, Nabeel et al. show in Towards privacy preserving access control in the cloud how authorization can be verified through these commitments. Their system, CloudMask, uses oblivious attribute-based authorization. A user can prove to a cloud server that their attributes meet specific policy criteria using commitments, completely decoupling authorization from identity disclosure. The server learns that the criteria are met, but learns nothing about the user's actual identity or extraneous attributes.

Selective Disclosure Signatures

Instead of signing an entire identity profile as a single block, issuers can use specialized signature schemes. Arfaoui et al. leverage this in A Privacy-Preserving NFC Mobile Pass for Transport Systems, combining Direct Anonymous Attestation (DAA) with a smartphone's secure element. This allows a transit passenger to prove they possess a valid fare credential without revealing their identity or allowing service providers to track their movements across the transit network.

The Architecture of Self-Sovereign Identity

In production environments, these primitives are organized into decentralized frameworks known as Self-Sovereign Identity (SSI), which rely on Decentralized Identifiers (DIDs) and Verifiable Credentials (VCs). As surveyed by Mazzocca et al. in A Survey on Decentralized Identifiers and Verifiable Credentials, these mechanisms allow a credential holder to share only specific attributes with a verifier while keeping the remaining data private, drastically reducing the risk of identity leakage during verification.

The architecture relies on a three-party dynamic:

  1. The Issuer cryptographically signs an attribute bundle.
  2. The Holder stores this bundle securely and uses it to generate zero-knowledge proofs or tokens for specific transactions.
  3. The Verifier validates the mathematical proof against the issuer's public key.
+------------+     Signs bundle      +------------+
|   Issuer   | --------------------> |   Holder   |
+------------+                       +------------+
      |                                    |
      | Publishes                          | Generates ZKP
      | Public Key                         | for specific attribute
      v                                    v
+------------+     Validates proof   +------------+
| Ledger/PKI | <-------------------- |  Verifier  |
+------------+                       +------------+

Liu et al. formalize this lifecycle in Design Patterns for Blockchain-based Self-Sovereign Identity, detailing architectural design patterns where users generate verifiable proofs for individual data fields. This architectural shift moves the security burden away from centralized silos.

As Le et al. analyze in A comparative cyber risk analysis between federated and self-sovereign identity management systems, while traditional federated identity systems create massive honeypots of user data prone to systemic breaches, SSI systems utilizing zero-knowledge proofs ensure that only the minimum necessary information is shared, mitigating the risk of data over-collection.

This capability is particularly powerful when dealing with complex data types, such as ranges. Melissa Chase outlines a system for electronic healthcare infrastructure in An Anonymous Health Care System. By using anonymous credentials and cryptographic delegation, patients can generate tokens proving that their medical data falls within an insurance policy's covered range without revealing their identity or full medical history to insurers and pharmacies.

Applications Across Web3, Cloud, and the Metaverse

The ability to verify attributes while preserving anonymity has unlocked new paradigms across several computing domains.

Web3 and Address Abstraction

In public blockchain networks, user privacy is often compromised because all transactions are linked to a public address. Park et al. address this in Beyond the Blockchain Address: Zero-Knowledge Address Abstraction via zkAA. Their system allows users to authenticate transactions using existing Web2 identities (like social logins) by verifying a zero-knowledge identity certificate on-chain, keeping the underlying account details private.

Similarly, Xu et al. introduce deController in deController: A Web3 Native Cyberspace Infrastructure Perspective, utilizing ZKPs and verifiable random functions (VRFs) to derive service-specific identifiers. This enables users to prove application-specific membership or attributes without revealing their primary wallet address.

Cloud Information Flow

In cloud environments, data must often pass through semi-trusted intermediaries. Han et al. address this in Fine-grained information flow control using attributes by merging Access Control Encryption (ACE) with Attribute-Based Systems (ABS). This allows data senders to disclose only the specific subset of attributes required by a security policy to an intermediary sanitizer, ensuring compliance while preventing the intermediary from fingerprinting the user.

The Metaverse and Virtual Spaces

Immersive 3D environments require strict access control for safety and regulatory compliance, yet users demand privacy.

Hardware and Integrity Attestation

The principle of selective disclosure extends down to hardware configurations. In Integrity Measurement based on Trusted Computing, Ba et al. explore property-based attestation. Instead of forcing a machine to reveal its entire software configuration log to a remote challenger—which allows for system fingerprinting—the system uses cryptographic proofs to verify only that the system meets specific functional security properties.

Ensuring Trust and Correctness

If a system allows users to selectively hide information, how do we prevent them from fabricating attributes? Pang et al. highlight this vulnerability in A New Access Control Scheme for Facebook-style Social Networks, noting that in attribute-based privacy systems, users may provide fraudulent information about affiliations or locations to gain unauthorized access. Therefore, selective disclosure systems must mathematically bind the disclosed attributes to an unalterable cryptographic signature from a trusted issuer.

Because the underlying mathematics of these systems are highly intricate, implementing them safely is difficult. Wang et al. address this challenge in A General Formal Framework of Analyzing Selective Disclosure Attribute-Based Credential Systems. They introduce a formal verification framework using applied Pi calculus and automated tools to model and mathematically prove the authenticity and untraceability of selective disclosure protocols (such as Microsoft's U-Prove).

By formally proving that a protocol cannot leak data or accept forged proofs, computer scientists can confidently deploy selective disclosure systems—ensuring that we can verify what is necessary, while protecting everything else.

Key Foundational Work

Some Facets of Complexity Theory and Cryptography: A Five-Lectures Tutorial (2001) — contributed 1 concept elements to this direction.
A Utility-Theoretic Approach to Privacy and Personalization (2008) — contributed 1 concept elements to this direction.
History & citationVersion 1 · 2026-10-04

Current · Permanent link

View frozen version 1

Cite this direction

Latest version (a living page):

@misc{lacuna_zero_knowledge_attribute_verification_0dcf7fe4,
  title = {zero-knowledge attribute verification},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/zero-knowledge-attribute-verification/rdr_0dcf7fe419d5453c86cbed7116ebc79d},
  note = {Latest version of a living research direction; cite a version for a fixed text. Accessed 2026-11-19},
}

This exact version (version 1, frozen text):

@misc{lacuna_zero_knowledge_attribute_verification_0dcf7fe4_v1,
  title = {zero-knowledge attribute verification},
  author = {{Lacuna}},
  howpublished = {Lacuna research direction},
  year = {2026},
  url = {https://lacuna.tiptreesystems.com/direction/zero-knowledge-attribute-verification/rdr_0dcf7fe419d5453c86cbed7116ebc79d/v/1},
  note = {Version 1, frozen 2026-10-04. Accessed 2026-11-19},
}
About

These directions overlap with this one through shared papers.

See something wrong? Report a mistake