Blockchain Authentication via Dynamic Hashed Blocks

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current authentication methods are vulnerable to compromise due to the use of weak, static passwords, which can be easily guessed or obtained by malicious actors, and require manual entry, making them time-consuming and insecure, especially in devices without accessible keyboards.

Innovation Solution

A system and method utilizing a blockchain-based authentication process where a cryptographic hash function is applied to user account information, generating a hashed block that is stored on the user's device, and updated upon each authentication request, creating a dynamic and changing authentication chain that enhances security and detects unauthorized access.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If traditional password-based authentication is used, then users can easily remember and enter their credentials, but the authentication security is weak and vulnerable to compromise

Engineering Contradiction:
Improveauthentication securityVSAvoiduser convenience
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent extracts the password from the authentication process entirely. Instead of using traditional passwords, the system uses public key cryptography where the user's public key serves as the authentication credential. This eliminates the need for users to remember complex passwords while maintaining strong security through cryptographic mechanisms.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent replaces the mechanical/password-based authentication system with a cryptographic system. Manual password entry and verification is substituted with automated cryptographic verification of digital signatures, providing both enhanced security and improved user convenience through seamless authentication.

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

2Reliability

If static passwords are used for authentication, then the authentication process is simple and fast, but the credentials can be easily guessed or obtained by malicious actors

Engineering Contradiction:
Improvecredential securityVSAvoidauthentication system complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements dynamic authentication credentials through the blockchain system. Each authentication event generates a new signed transaction that serves as a unique credential. These credentials are time-limited and purpose-specific, making them dynamically valid only for particular authentication events rather than being static and reusable.

Inventive Principle:
Principle #15Dynamics

Solution Approach 2:

The patent segments the authentication credential into multiple discrete signed transactions on the blockchain, each valid for a specific authentication event. Instead of one static password, the system creates numerous small, single-use cryptographic credentials, each segmented for a particular purpose and time period.

Inventive Principle:
Principle #1Segmentation

3Reliability

If users manually enter passwords each time they wish to log in, then the authentication process can be secure, but it becomes time-consuming and frustrating, especially in devices without accessible keyboards

Engineering Contradiction:
Improveauthentication securityVSAvoidauthentication time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent enables self-service authentication where the user's device automatically generates and submits the cryptographic proof of authentication without requiring manual password entry. The device itself performs the authentication ritual by signing the authentication transaction with the user's private key, eliminating the need for manual input while maintaining security.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The patent performs preliminary setup of cryptographic key pairs during device initialization or first-use. This preliminary action establishes the authentication credentials in advance, so that subsequent authentication events require only automatic cryptographic verification rather than manual password entry, saving time while maintaining security.

Inventive Principle:
Principle #10Preliminary action

4Ease of operation

If users store passwords in unsecure locations such as unsecurely on their computer or mobile phone, then they can easily access their credentials, but the passwords become vulnerable to being obtained by malicious actors

Engineering Contradiction:
Improvecredential accessibilityVSAvoidcredential security
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts the password storage function entirely and replaces it with blockchain-based credential verification. Users do not store passwords locally; instead, the system verifies authentication through cryptographic signatures on the blockchain, eliminating the security vulnerability of local password storage while maintaining easy access through automatic device authentication.

Inventive Principle:
Principle #2Taking out (Extraction)

Data Source

PatentUS11522711B2Systems and methods for block chain authentication
Publication Date: 2022.12.06 SECUREWORKS CORP
  • US11522711B2 patent drawing
  • US11522711B2 patent drawing
  • US11522711B2 patent drawing

AI summary

A system for providing secure authentication between a service provider and at least one user device having a storage. The system having a processor managed by the service provider, which processor manages authentication between the at least one device and the service provider. The processor is configured to generate a block including at least user account information upon receipt of an authentication request from the at least one device; apply a cryptographic hash function to the block to create a hash; transmit the hash to the at least one device for storage in the memory of the at least one device; and upon receipt of the hash, validate the hash prior to providing access to the service provider.