Blockchain Data Validation via Cryptographic Signatures

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current systems for verifying entity information in computer networks face inefficiencies and security risks due to the need for manual checks and reliance on centralized approaches, which can lead to fraud and increased processing overheads.

Innovation Solution

A method and system using public-key cryptography and blockchain technology to securely verify entity information, where one entity vouches for another's data by cryptographically signing it, allowing for efficient and trustworthy validation without repeated checks, and enabling distributed trust networks.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If manual KYC checks and centralized verification systems are used, then entity information can be verified, but processing overheads and costs increase significantly

Engineering Contradiction:
Improveverification reliabilityVSAvoidprocessing overhead
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent replaces manual mechanical verification processes with automated cryptographic verification. Entities use digital signatures and public-key cryptography to verify information automatically, eliminating the need for manual document checking and reducing processing overhead while maintaining or improving verification reliability.

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

Solution Approach 2:

The patent introduces blockchain technology as a decentralized intermediary that enables direct peer-to-peer verification without centralized authorities. The blockchain serves as a trusted mediator that records and verifies entity information, allowing entities to validate each other's data without requiring manual intervention or centralized processing.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If repeated verification checks are performed across multiple entities, then information accuracy is maintained, but network bandwidth and processing resources are consumed

Engineering Contradiction:
Improveinformation accuracyVSAvoidnetwork resource consumption
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent implements preliminary verification where entity information is verified once and the results are stored on the blockchain. Subsequent entities can retrieve and verify this pre-validated information through cryptographic proof, eliminating the need for repeated verification checks and reducing network resource consumption while maintaining information accuracy.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent allows entities to copy and reuse verified information from the blockchain without requiring re-verification. Once information is validated and recorded, it can be efficiently copied and referenced by multiple entities, reducing redundant processing and network bandwidth consumption while maintaining accuracy through cryptographic integrity checks.

Inventive Principle:
Principle #26Copying

3Ease of operation

If personal documentation is transmitted over public networks, then verification can be performed, but security risks increase

Engineering Contradiction:
Improveverification convenienceVSAvoidsecurity risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts sensitive personal information from direct transmission over public networks. Instead of sharing actual documentation, entities share cryptographic proofs and hashed representations of their information stored on the blockchain. This extraction of essential verification data without exposing sensitive originals eliminates security risks while maintaining verification convenience.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses disposable cryptographic tokens and temporary verification credentials that can be generated and discarded. Entities create ephemeral proof objects for verification purposes that contain no sensitive personal data, use them once for verification, and then discard them, eliminating security risks associated with transmitting and storing personal documentation.

Inventive Principle:
Principle #27Cheap short-living objects (Disposable)

4Reliability

If stronger verification checks are implemented, then trustworthiness improves, but transaction costs and processing time increase

Engineering Contradiction:
ImprovetrustworthinessVSAvoidtransaction speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent implements periodic verification where strong verification is performed initially and recorded on the blockchain, followed by efficient periodic checks using cryptographic proofs. The initial thorough verification establishes trustworthiness, while subsequent periodic validations using stored cryptographic data maintain this trustworthiness at low cost and high speed, resolving the contradiction between strong verification and transaction efficiency.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS10924264B2Data validation and storage
Publication Date: 2021.02.16 BARCLAYS EXECUTION SERVICES LTD
  • US10924264B2 patent drawing
  • US10924264B2 patent drawing
  • US10924264B2 patent drawing

AI summary

Method and system for recording data describing a first entity, the data endorsed by a second entity comprising the second entity validating data describing the first entity, wherein an identifier is associated with the data, the identifier being generated from a public key of the first entity. Cryptographically signing data corresponding with the data describing the first entity using at least a private key of the second entity. Posting a transaction to a block chain including the cryptographically signed data. Method and system for obtaining data describing a first entity the data endorsed by a second entity comprising. Receiving an identifier of data describing the first entity. Retrieving an entry from a block chain based on the received identifier. Authenticating the entry using a public key of the second entity. Extracting the data describing the first entity from the retrieved entry.