Verifiable Privacy Computation via Distributed Ledger Signatures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

The challenge of maintaining data privacy is exacerbated when sharing private data between organizations, as existing solutions rely on trusted third parties, which can expose data to risks and increase costs, time, and computation resources, while lacking transparency and verifiability in the computation process.

Innovation Solution

A method and system using verifiable computation modules processed on a private data owner's platform, where computation modules are recorded on a distributed ledger, enabling traceability and verifiability through unique identifiers, key pairs, and execution result signatures, allowing stakeholders to verify computations without relying on third parties.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If trusted third parties are used to process private data, then data processing can be performed, but data security and privacy are compromised

Engineering Contradiction:
Improvedata securityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent extracts the trust verification mechanism from the third-party processing model and implements it locally on the data owner's platform. By generating verification signatures locally and recording them on the distributed ledger, the system eliminates the need for trusted third parties while maintaining data security and processing capability.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The distributed ledger serves as an intermediary that records computation module identifiers and verification signatures without exposing private data. This mediator enables trustless verification of computation results while maintaining data privacy, replacing the traditional trusted third-party model.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If trusted third parties are used for data processing, then verification is simplified, but costs and time consumption increase

Engineering Contradiction:
Improveverification easeVSAvoidprocessing time
Core Design Contradiction:
Ease of operationVSLoss of time

Solution Approach 1:

The system performs preliminary actions by generating verification signatures during the computation process itself, rather than requiring separate verification steps with third parties. The signature is created upfront using the private key and embedded in the computation result, enabling immediate verification without additional time consumption.

Inventive Principle:
Principle #10Preliminary action

3Adaptability or versatility

If private data is shared between organizations, then collaborative processing is enabled, but data privacy risks increase

Engineering Contradiction:
Improvecollaborative processing capabilityVSAvoiddata privacy risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the data processing system into independent computation modules that can be executed on the data owner's platform. Each module is identified and verified through the distributed ledger, enabling collaborative processing while maintaining data privacy through local execution and cryptographic verification.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS11954226B2Verifiable privacy preserving computation
Publication Date: 2024.04.09 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11954226B2 patent drawing
  • US11954226B2 patent drawing
  • US11954226B2 patent drawing

AI summary

Disclosed herein are methods and systems for executing verifiable computation modules to process private data at private data owner platform, comprising obtaining a computation module having a unique identifier recorded in a distributed ledger controlled by a plurality of computing nodes, generating a key pair comprising a signing key and a verification key derived from the signing key, recording, in the distributed ledger, an execution record associating an execution instance of the computation module with the verification key, initiating the execution instance of the computation module to process a private dataset incorporated with the signing key. outputting a computation outcome, computing an execution result signature for the execution instance based on the unique identifier and the private data and the signing key, and recording the execution result signature in the distributed ledger to enable verification of the execution instance.