Private Ledger Verification Using External Consistency Proofs

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Existing data storage solutions, particularly in private blockchains, face challenges in ensuring data persistence and access control without relying on central servers, which can lead to network overload and high computational resource consumption, and lack verification of data persistency outside the network.

Innovation Solution

A method for certifying data stored in private ledgers by calculating ledger digests and consistency proofs, which are then exposed outside the private environment and stored in a persistent storage, ensuring tamper-proof verification of a single consistent history without exposing the data themselves.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If data are uploaded to a central server for storage and verification, then data persistence and access control are guaranteed, but network overload occurs and performance degrades

Engineering Contradiction:

Improvedata persistence verificationVSAvoidnetwork performance

Core Design Contradiction:

ReliabilityVSProductivity

Solution Approach 1:

The patent extracts only the essential verification information (ledger digests and consistency proofs) from the full data set and stores these condensed representations on the blockchain. This allows verification of data persistence without transferring or storing the actual data themselves, thereby preventing network overload while maintaining reliability.

Inventive Principle:

Principle #2Taking out (Extraction)

Solution Approach 2:

The patent creates cryptographic copies (hashes/digests) of the ledger data and stores these on the blockchain instead of the original data. These copies serve as verifiable proxies that confirm persistence without requiring network transmission of the full data, thus resolving the contradiction between verification reliability and network performance.

Inventive Principle:

Principle #26Copying

2Ease of operation

If data are stored in a private blockchain, then access control is maintained, but persistency verification is unavailable outside the network

Engineering Contradiction:

Improveaccess controlVSAvoidpersistency verification outside network

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent introduces the blockchain as an intermediary verification layer between the private ledger system and external verifiers. The blockchain stores cryptographic proofs that mediate the verification process, allowing external subjects to confirm data persistence without accessing the private ledger directly, thus maintaining access control while enabling external verification.

Inventive Principle:

Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent segments the verification function from the data storage function. The private blockchain maintains access control for data storage, while a separate public verification mechanism (using stored digests and proofs) handles persistency verification. This segmentation allows both access control and external verification to coexist without conflict.

Inventive Principle:

Principle #1Segmentation

3Reliability

If proof of work consensus is used in public blockchain, then tamper-proof verification is achieved, but computational resource consumption increases

Engineering Contradiction:

Improvetamper-proof verificationVSAvoidcomputational resource consumption

Core Design Contradiction:

ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent uses inexpensive, easily computable cryptographic hash functions to create ledger digests that can be verified by anyone. These simple, disposable-like verification mechanisms replace energy-intensive proof of work, providing tamper-proof verification through minimal computational effort rather than expensive mining operations.

Inventive Principle:

Principle #27Cheap short-living objects (Disposable)

Solution Approach 2:

The patent copies only the essential verification data (hashes and proofs) to the blockchain rather than storing full transactions. This reduces the amount of data that needs to be processed and verified, significantly lowering computational resource consumption while maintaining the tamper-proof property through cryptographic verification of the copied data.

Inventive Principle:

Principle #26Copying

Data Source

PatentUS20250342282A1Public verification of single consistent history of private ledgers

Publication Date: 2025.11.06 TRAENT SRL

AI summary

A solution is proposed for certifying data stored in one or more ledgers (105) produced in a private environment (110). A corresponding method (600) comprises calculating corresponding ledger digests (LDji) based on a sequence of ledger versions (LVji) of each ledger (105) and then calculating (605-606) corresponding consistency proofs (VCPji/i−1). Verification information based thereon for verifying that each selected ledger (105) to be verified has a single consistent history is exposed (608-614,631-634) outside the private environment, with at least part thereof that is stored (609,613) into a persistent storage (115). Moreover, a software programs (500) and a corresponding software program product are proposed. A certification computing system (410) is also proposed.