On-Demand Distributed Ledger Cross-Validation

Solution Overview

Problem

Distributed ledgers, such as blockchains, face inefficiencies in cross-validation processes, particularly when blocks are added but not immediately accessed, leading to unnecessary network traffic and resource utilization.

Innovation Solution

Implementing an on-demand cross-validation method where nodes only perform cross-validation when requested information is accessed, updating validation information to indicate whether blocks have been cross-validated, and utilizing distributed ledger validation information to determine the need for cross-validation.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If cross-validation is performed for every block added to the distributed ledger, then data integrity and reliability are ensured, but network traffic and resource utilization increase unnecessarily when blocks are not accessed

Engineering Contradiction:

Improvedata integrityVSAvoidresource utilization

Core Design Contradiction:

ReliabilityVSLoss of energy

Solution Approach 1:

The system dynamically adjusts the cross-validation process based on whether blocks are accessed. Blocks that are not accessed skip cross-validation, while accessed blocks undergo validation. This dynamic approach resolves the contradiction by making the validation process adaptive to actual data usage patterns rather than applying a static validation rule to all blocks.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent applies cross-validation selectively to specific blocks based on their access status rather than uniformly to all blocks. This local quality approach ensures that only the necessary portions of the distributed ledger undergo validation, maintaining data integrity for accessed blocks while conserving resources for inaccessible blocks.

Inventive Principle:

Principle #3Local quality

2Reliability

If cross-validation is performed for every block added to the distributed ledger, then data integrity is ensured, but network traffic increases unnecessarily

Engineering Contradiction:

Improvedata integrityVSAvoidnetwork traffic

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The system dynamically adjusts the cross-validation process based on whether blocks are accessed. Blocks that are not accessed skip cross-validation, while accessed blocks undergo validation. This dynamic approach resolves the contradiction by making the validation process adaptive to actual data usage patterns rather than applying a static validation rule to all blocks.

Inventive Principle:

Principle #15Dynamics

Solution Approach 2:

The patent applies cross-validation selectively to specific blocks based on their access status rather than uniformly to all blocks. This local quality approach ensures that only the necessary portions of the distributed ledger undergo validation, maintaining data integrity for accessed blocks while conserving resources for inaccessible blocks.

Inventive Principle:

Principle #3Local quality

3Loss of energy

If on-demand cross-validation is implemented, then resource utilization and network traffic are reduced, but validation may be delayed until data is accessed

Engineering Contradiction:

Improveresource utilizationVSAvoidvalidation timing

Core Design Contradiction:

Loss of energyVSLoss of time

Solution Approach 1:

The system performs cross-validation at the point of data access rather than in advance. When a block is accessed, the validation is initiated immediately, ensuring that validation occurs before the data is used. This approach balances resource conservation with timely validation by performing the action at the optimal moment - neither too early nor too late.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS12155773B2Systems and methods for on-demand validation of distributed ledger records

Publication Date: 2024.11.26 VERIZON PATENT & LICENSING INC

AI summary

A device described herein may maintain a distributed ledger that is also maintained by at least one other device. The device may receive a record for recordation to the distributed ledger, and may add the record to the distributed ledger without communicating with the at least one other device to validate (e.g., cross-validate) the record. The device may receive a request for information included in the record and, after receiving the request for the information included in the record, communicate with one or more devices, of the at least one other device, to validate the record. The device may determine, based on communicating with the one or more devices, that the record is valid; and may output, in response to the request and based on determining that the record is valid, the requested information included in the record.