Multiparty Log Authenticity via Zero-Knowledge Proof Blocks
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing logging systems face challenges in verifying the authenticity of log records across multiple parties without exposing personally identifiable information, and they incur high computational and storage overheads due to the need for per-record signatures and key management.
Innovation Solution
The use of zero-knowledge proofs and digital signatures, facilitated by a trusted third-party, allows for the verification of log records without storing personally identifiable information, by generating and combining proofs into log blocks, which are then signed and stored, enabling efficient verification and anonymity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If per-record digital signatures are used to verify log record authenticity, then record authenticity can be proven, but computational overhead and storage requirements increase significantly
Solution Approach 1:
The patent combines multiple individual log records into a single log block that is signed as one unit. Instead of signing each log record separately, the system aggregates records from multiple parties into a block structure, then applies a single digital signature to the entire block. This merging approach maintains the authenticity verification capability while dramatically reducing the number of signatures required, thereby lowering computational overhead and storage requirements.
Solution Approach 2:
The patent segments the log verification process into two distinct phases: (1) log record aggregation into blocks by the log verification system, and (2) signature verification by the trusted third party. This segmentation allows the computationally intensive signing operation to be performed only once per block rather than once per record, while still providing verifiable authenticity for individual records within the block.
2Reliability
If per-record digital signatures are implemented for multiparty logs, then each record can be individually verified, but key management complexity and storage overhead increase
Solution Approach 1:
The system merges the key management responsibilities by having the trusted third party generate and manage a single key pair for the entire log verification system. Individual parties do not need to manage their own signing keys; instead, they rely on the trusted third party's signature verification. This consolidation eliminates the need for complex distributed key management infrastructure while maintaining verification capabilities for all participating parties.
3Ease of operation
If log records store personally identifiable information, then verification can be more straightforward, but party anonymity is compromised
Solution Approach 1:
The patent extracts and removes personally identifiable information from the log records before they are included in the log block. The log verification system processes records to strip out identifying details, retaining only the essential transaction data needed for verification. This extraction maintains verification simplicity while preserving party anonymity, as the verification process can proceed without needing to know or store identifying information about the parties involved.
Data Source
AI summary
In general, techniques are described for using zero-knowledge proofs and digital signatures to verify the authenticity of log records generated by multiple parties, at least in some cases without exposing personally identifiable information for the parties.