Zero-Knowledge Attestation Protocol for Secure Distributed Data Querying

Solution Overview

Problem

Existing distributed computing systems face significant security challenges due to the ad-hoc nature of modern networks, where even encrypted data can be compromised by vulnerabilities in remote server devices or unsecured network connections.

Innovation Solution

A multi-directional zero-knowledge attestation protocol is implemented, allowing computing entities to query and selectively receive content without revealing private data. This is achieved through cryptographic approaches that enable entities to prove the existence of data without disclosing it, using a combination of private-public key pairs and zero-knowledge proofs.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If data is transmitted over unsecured networks in distributed computing systems, then network communication flexibility is improved, but security is worsened

Engineering Contradiction:

Improvenetwork communication flexibilityVSAvoidsecurity risks

Core Design Contradiction:

Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent introduces an intermediary verification mechanism using zero-knowledge proofs and cryptographic attestation. This intermediary layer allows unsecured network communication while preventing data leakage by verifying computational integrity without exposing private data. The intermediary proves that computations were performed correctly on private data without revealing the data itself.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces traditional mechanical security measures (encryption, authentication) with cryptographic proof systems. Instead of relying on securing transmission channels or verifying identities through passwords, the system uses zero-knowledge proofs and attestation mechanisms that mathematically guarantee data integrity and computational correctness without requiring trust in the network or intermediate devices.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

2Adaptability or versatility

If private data is transmitted to remote servers for processing, then computing functionality is improved, but data leakage risk is worsened

Engineering Contradiction:

Improvecomputing functionalityVSAvoiddata leakage risk

Core Design Contradiction:

Adaptability or versatilityVSLoss of information

Solution Approach 1:

The patent introduces an intermediary verification mechanism using zero-knowledge proofs and cryptographic attestation. This intermediary layer allows unsecured network communication while preventing data leakage by verifying computational integrity without exposing private data. The intermediary proves that computations were performed correctly on private data without revealing the data itself.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent extracts only the necessary verification information from the computational process. Instead of transmitting private data to remote servers, the system extracts cryptographic proofs that verify computations were performed correctly. The private data remains local, and only small cryptographic artifacts (proofs and attestations) are transmitted for verification.

Inventive Principle:

Principle #2Taking out (Extraction)

3Reliability

If traditional encryption is used to protect data in transit, then confidentiality is improved, but trust in third-party devices is still required

Engineering Contradiction:

ImproveconfidentialityVSAvoidtrust requirements

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces traditional mechanical security measures (encryption, authentication) with cryptographic proof systems. Instead of relying on securing transmission channels or verifying identities through passwords, the system uses zero-knowledge proofs and attestation mechanisms that mathematically guarantee data integrity and computational correctness without requiring trust in the network or intermediate devices.

Inventive Principle:

Principle #28Mechanics substitution (Replace mechanical system)

Solution Approach 2:

The patent implements self-verification mechanisms where the system proves its own integrity without external trust. Remote servers generate cryptographic attestations that self-prove they performed computations correctly on the provided data. The client can independently verify these attestations without needing to trust the server's identity or the network channel, making the system self-verifying and eliminating third-party trust requirements.

Inventive Principle:

Principle #25Self-service

Data Source

PatentUS12206782B2Multi-directional zero-knowledge attestation systems and methods

Publication Date: 2025.01.21 GLIMPSE PROTOCOL LTD

AI summary

Certain examples described herein relate to zero knowledge attestation systems and methods. In one example method, a computing entity obtains query data over at least one network from a messaging service. A query defined by the query data is matched against private data for the computing entity. A use-limited private-public key pair is obtained for the query and an identifier is generated or the computing entity using the public key. A query result package is then generated based on a match for the query. The query result package includes the generated identifier and acts as a zero knowledge attestation. The computing entity obtains content associated with the query that is addressed to the identifier uses the private key of the private-public key pair to authenticate communications that relate to the query.