Distributed Ledger Verification With Probabilistic History Checks

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Distributed systems face challenges in scaling transaction rates while maintaining reliability and integrity in the presence of malicious nodes, with existing solutions either relying on central authorities or requiring all nodes to maintain a complete transaction history, leading to inefficiencies and limited scalability.

Innovation Solution

A distributed resource allocation system that uses probabilistic verification of transactions by randomly selecting previous transactions to check for validity, maintaining a partial order and allowing for partial or probabilistic verification, while using quorums and log nodes to ensure consensus and repair invalid transactions.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all nodes maintain complete transaction history, then reliability is improved, but device complexity and scalability worsen

Engineering Contradiction:

Improvetransaction integrityVSAvoidstorage requirements

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the transaction verification process by dividing nodes into different roles (verifier nodes and prover nodes) and splitting the transaction history into segments that can be selectively verified. Verifier nodes only need to maintain and verify specific segments or samples of transaction history rather than complete histories, reducing storage complexity while maintaining reliability through distributed verification.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

The patent uses cryptographic copying mechanisms where verifier nodes obtain cryptographic proofs or samples of transaction history segments rather than storing complete copies. This allows nodes to verify transaction integrity through cryptographic copies and proofs without duplicating entire transaction histories, reducing device complexity while preserving reliability.

Inventive Principle:

Principle #26Copying

2Productivity

If probabilistic verification is used, then productivity is improved, but measurement precision worsens

Engineering Contradiction:

Improvetransaction processing speedVSAvoidverification accuracy

Core Design Contradiction:

ProductivityVSMeasurement precision

Solution Approach 1:

The patent implements feedback mechanisms where verifier nodes probabilistically select transaction segments for verification, and when invalid transactions are detected, the system provides feedback by rejecting the transaction and potentially increasing verification intensity for related segments. This feedback loop maintains verification precision while allowing probabilistic sampling to improve overall processing productivity.

Inventive Principle:

Principle #23Feedback

Solution Approach 2:

The patent changes verification parameters dynamically, adjusting the probability and depth of verification based on transaction characteristics, node reputation, and system state. By varying verification parameters rather than applying uniform strict verification, the system achieves higher productivity while maintaining adequate precision through adaptive parameter selection.

Inventive Principle:

Principle #35Parameter changes

3Reliability

If quorum systems are implemented, then reliability is improved, but device complexity worsens

Engineering Contradiction:

Improveconsensus accuracyVSAvoidcoordination overhead

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments the quorum system into specialized components with divided responsibilities. Different node types handle different aspects of quorum formation and verification, and transaction history is segmented into manageable portions that can be verified independently. This segmentation reduces coordination overhead by limiting the scope of quorum interactions while maintaining consensus reliability.

Inventive Principle:

Principle #1Segmentation

4Productivity

If parallel processing is enabled, then productivity is improved, but reliability worsens

Engineering Contradiction:

Improvetransaction rateVSAvoidtransaction consistency

Core Design Contradiction:

ProductivityVSReliability

Solution Approach 1:

The patent segments transactions and verification processes into independent parallel tasks that operate on divided portions of the transaction history. By segmenting work into independent units that can be processed in parallel without conflicting, the system achieves higher productivity while maintaining reliability through proper segmentation boundaries and coordination protocols.

Inventive Principle:

Principle #1Segmentation

Data Source

PatentEP3888334B1Systems and methods for distributed resource allocation

Publication Date: 2026.04.01 CUTTS SHAUN

Figure 1
Figure 2
Figure 3

AI summary

Resource allocation systems (aka distributed ledgers) can overcome scalability issues while still ensuring both that system resource amounts are not corrupted and that resource recipients can trust in resources delivered to them by requiring distributed nodes maintaining account histories in return, for instance, for transaction fees to probabilistically verify transaction history and maintain reserve resources in their own accounts for the repair of transactions impaired by invalid previous transactions. Even in a permissionless environment, such systems can maintain eventual consistency of transaction history without impairment of the accounts of non-maintaining users.