STARK Verification for Outsourced Data Processing Integrity

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

In computility outsourcing scenarios, the integrity of computational and data processes cannot be guaranteed due to the lack of direct verification of data processors and potential tampering of input data, leading to security risks.

Innovation Solution

Implementing a hash computation process within service algorithms and using Scalable Transparent ARgument of Knowledge (STARK) technology to generate provers and verifiers, ensuring integrity through probabilistic verification of computational results and data integrity by deploying verifiers locally.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of manufacture

If computility outsourcing is used to reduce deployment and operation-maintenance costs, then cost efficiency is improved, but computational integrity and data integrity cannot be guaranteed

Engineering Contradiction:
Improvedeployment and operation-maintenance costVSAvoidcomputational integrity and data integrity
Core Design Contradiction:
Ease of manufactureVSReliability

Solution Approach 1:

The patent introduces a cryptographic intermediary layer (hash computation and STARK proof system) between the data processor and data user. The data processor generates cryptographic proofs (prover) that can be verified by the data user (verifier) without revealing underlying data or computation details. This intermediary mechanism enables trustless outsourcing where integrity is guaranteed through mathematical proofs rather than organizational trust.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent replaces the mechanical/organizational trust mechanism (relying on the data processor's honesty) with a cryptographic verification mechanism. Instead of trusting the processor to behave correctly, the system uses hash computations and STARK proofs to mathematically verify computational integrity and data integrity automatically, substituting human/organizational trust with cryptographic verification.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Device complexity

If traditional centralized or distributed processing architectures are used, then system simplicity is maintained, but they can no longer meet the demands of modern cloud platform systems

Engineering Contradiction:
Improvesystem architecture complexityVSAvoidcapability to meet modern cloud platform demands
Core Design Contradiction:
Device complexityVSAdaptability or versatility

Solution Approach 1:

The patent creates a universal verification layer that can work with any computation type and data format. The STARK proof system and hash verification mechanism are architecture-agnostic and can verify integrity across different computation models (centralized, distributed, fog computing). This universal approach allows the system to adapt to various cloud platform scenarios without requiring architecture-specific solutions.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Solution Approach 2:

The patent adds a new dimension of cryptographic verification to existing processing architectures. Rather than changing the fundamental computation architecture, it overlays a verification dimension using hash computations and STARK proofs. This allows traditional architectures to meet modern demands by adding integrity verification capabilities without complete architectural redesign.

Inventive Principle:
Principle #17Another dimension (Dimensionality change)

3Productivity

If data is outsourced for processing, then operational efficiency is improved, but security risks increase due to potential data tampering

Engineering Contradiction:
Improveoperational efficiencyVSAvoidsecurity risks from data tampering
Core Design Contradiction:
ProductivityVSObject-affected harmful factors

Solution Approach 1:

The patent performs preliminary cryptographic preparation by computing hash values of input data before outsourcing processing. The data user computes hashes of the original data and incorporates these into the verification process. This preliminary action creates a cryptographic fingerprint of the original data that can be used to detect any tampering during or after processing, enabling efficiency gains while maintaining security.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent implements a feedback mechanism where the data processor provides cryptographic proofs (prover) back to the data user for verification. The verifier checks whether the computation was performed correctly and whether the output corresponds to the verified input data. This feedback loop ensures that even in outsourced scenarios, security risks are mitigated through automatic verification of computational integrity and data integrity.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS20260095328A1Data processing method, computer device, and readable storage medium
Publication Date: 2026.04.02 ZTE CORP
  • US20260095328A1 patent drawing
  • US20260095328A1 patent drawing
  • US20260095328A1 patent drawing

AI summary

A data processing method, a computer device and a readable storage medium are disclosed. The method may include: acquiring a service algorithm for an application service, adding a hash computation process for input data to the service algorithm, and performing an arithmetization processing on the service algorithm, thereby obtaining an Algebraic Intermediate Representation (AIR); processing the Algebraic Intermediate Representation according to a predetermined Scalable Transparent ARgument of Knowledge (STARK) transformation rule, thereby obtaining a prover and a verifier; transmitting the prover to a computility processing device; receiving a computational result transmitted by the computility processing device; verifying the proof information with the verifier; and in response to the proof information passing the verification, transmitting the hash value to the data source device; receiving the verification result, and determining a corresponding execution action according to the verification result.