Privacy-Preserving Attribute Authentication via Tamperproof Log
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional attribute verification systems expose user identity information, making them vulnerable to misuse and lacking in privacy preservation, with challenges in distributing public keys, revoking credentials, and ensuring auditing transparency.
Innovation Solution
Implementing a tamperproof log, such as blockchain technology, to facilitate privacy-preserving attribute-based credentials, trusted distribution of public keys, and secure revocation and auditing processes, using accumulators and smart contracts to ensure the integrity and privacy of user credentials.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional attribute verification systems are used, then service providers can verify user attributes, but user identity information is exposed and privacy is compromised
Solution Approach 1:
The system segments user identity information into multiple components: credentials (proving attributes), accumulators (tracking credential issuance), and revocation lists (managing credential validity). This segmentation allows verification of attributes without exposing the full identity, resolving the contradiction between reliable verification and privacy preservation.
Solution Approach 2:
The patent introduces tamperproof logs (blockchain) as an intermediary that mediates between service providers and users. The blockchain stores accumulators and revocation information transparently, enabling providers to verify credentials reliably while users maintain privacy through cryptographic proofs that don't reveal underlying identity data.
2Ease of operation
If public keys are distributed through conventional channels, then authentication can be established, but the distribution process lacks trust and security
Solution Approach 1:
The system performs preliminary action by pre-distributing public keys and accumulator information to the blockchain before actual credential verification occurs. This advance setup creates a trusted foundation that simplifies subsequent operations while ensuring reliability through the immutability of blockchain storage.
Solution Approach 2:
The blockchain infrastructure provides self-service for public key distribution and accumulator management. The system automatically maintains and updates these cryptographic elements without requiring manual intervention or trusted third parties, simultaneously improving ease of operation and trust through decentralized consensus.
3Adaptability or versatility
If credentials are revoked through conventional methods, then credential management is possible, but the revocation process lacks transparency and trust
Solution Approach 1:
The system implements feedback by continuously updating the blockchain with revocation information and accumulator states. When credentials are revoked, the change is immediately recorded on the immutable ledger, providing real-time feedback to all system participants and ensuring trust through transparent, verifiable updates that anyone can audit.
4Reliability
If auditing processes are implemented in conventional systems, then accountability can be established, but the auditing process compromises user privacy
Solution Approach 1:
The patent applies local quality by implementing different levels of information visibility for different parties. Auditors can verify credential validity and system integrity through blockchain accumulators and revocation lists, while users maintain privacy through cryptographic proofs. Service providers receive only the verification results needed for their operations, not underlying identity data. This localized information distribution achieves auditing transparency without universal privacy compromise.
Data Source
AI summary
Computer-implemented methods for privacy attribute based credentials include issuing a privacy-preserving attribute-based credential, which is signed with a private key and has a unique credential handle; updating an accumulator in a tamperproof log to incorporate the credential handle; and facilitating providing access to a service in response to a zero-knowledge proof that the accumulator contains the credential handle. The methods also include generating revocation conditions and initial revocation information; submitting the initial revocation information and the revocation conditions to the tamperproof log; revoking a credential by adding a credential handle of the credential to the initial revocation information; and submitting the updated revocation information to the tamperproof log. Further, the methods include writing to the tamperproof log an audit token that contains an encrypted credential handle, which is encrypted by an auditor's public key that is published on the tamperproof log.


