Ledger-Based Identity Verification Using Hashed Attestation Keys

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing methods for validating information and identity are prone to weaknesses, including data leaks, unreliable network dependencies, and inconsistent protection of personally identifiable information, leading to security breaches and delays in transactions.

Innovation Solution

A method and system utilizing a centralized or distributed ledger to provide attestation of information through the generation of a public attest key by combining a hash of the information with a public key, stored at an attestation address, which can be verified for authenticity and integrity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If existing methods of validating information and identity are used, then the process is simple and familiar, but security breaches and data leaks occur frequently

Engineering Contradiction:
Improveinformation verification securityVSAvoidverification system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent introduces a distributed ledger as an intermediary between the information holder and the verifier. The ledger stores hashed versions of personal information along with cryptographic proofs, allowing verification without exposing the actual sensitive data. This intermediary structure enables secure verification while maintaining privacy and reducing security risks associated with direct data exposure.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

Instead of storing or transmitting actual sensitive information, the system creates and stores cryptographic copies (hashes) of the information on the distributed ledger. These hashed copies serve as verifiable proofs without containing the original sensitive data, thereby enabling verification while preventing data breaches and unauthorized access to actual personal information.

Inventive Principle:
Principle #26Copying

2Reliability

If personally identifiable information is stored for verification, then verification can be performed, but the information is vulnerable to leaks and unauthorized access

Engineering Contradiction:
Improveidentity verification capabilityVSAvoiddata breach risk
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The system stores only cryptographic hashes of personal information on the distributed ledger, not the actual sensitive data. These hashes serve as verifiable copies that prove the existence and integrity of the original information without exposing it. When verification is needed, the system compares new information against these hashed copies, enabling identity verification while keeping the actual personal information secure and private.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The patent transforms personal information from its original sensitive form into a hashed cryptographic representation. This parameter change converts the data into a form that is mathematically linked to the original information but does not reveal it. The hashed form maintains the verification capability while eliminating the security vulnerabilities associated with storing actual sensitive data.

Inventive Principle:
Principle #35Parameter changes

3Ease of operation

If centralized verification systems are used, then the process is straightforward, but network failures and connectivity issues cause transaction delays

Engineering Contradiction:
Improveverification process simplicityVSAvoidtransaction availability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent implements a distributed ledger system where verification data is segmented across multiple independent nodes rather than stored in a single centralized location. Each node maintains a copy of the ledger, allowing verification operations to continue even if some nodes are unavailable. This segmentation provides fault tolerance and ensures transaction availability while maintaining operational simplicity through standardized verification protocols.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The distributed ledger system enables self-service verification where any participant in the network can independently verify information using the cryptographic proofs stored on the ledger, without requiring coordination with a central authority. This self-service capability ensures continuous operation and availability even when network conditions vary, as each node can perform verification autonomously using the distributed data structure.

Inventive Principle:
Principle #25Self-service

4Ease of operation

If physical documents are used for identity verification, then the process is simple and direct, but the documents can be counterfeited and are not secure

Engineering Contradiction:
Improveverification simplicityVSAvoiddocument authenticity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The system replaces physical documents with cryptographic copies stored on a distributed ledger. These cryptographic copies contain hashed information and verifiable proofs that are mathematically secure against counterfeiting. The verification process remains simple as it involves checking cryptographic signatures and hashes, but the reliability is dramatically improved because these digital cryptographic proofs cannot be forged in the same way physical documents can be counterfeited.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS12126715B2Methods and systems of providing verification of information using a centralized or distributed ledger
Publication Date: 2024.10.22 CIVIC TECHNOLOGIES INC
  • US12126715B2 patent drawing
  • US12126715B2 patent drawing
  • US12126715B2 patent drawing

AI summary

A method and system of providing verification of information of a user relating to an attestation transaction is provided, and includes sending a request for information of the user, wherein the information has been previously attested to in an attestation transaction stored within a centralized or distributed ledger at an attestation address; receiving at a processor associated with a verifier the information of the user; sending a cryptographic challenge nonce; receiving at the processor associated with the verifier the cryptographic challenge nonce signed by the user's private key; verifying user identity with the cryptographic challenge nonce signed by the user's private key; deriving a public attest key by using the information of the user; deriving an attestation address using the public attest key; and verifying the existence of the attestation transaction at the attestation address in the centralized or distributed ledger.