Public Ledger Authentication Using Hashed Static Keys

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Conventional online and mobile payment systems face security challenges due to users often using easily guessed authentication credentials, lacking biometric devices, which compromises the security of payment accounts.

Innovation Solution

A public ledger authentication system that uses a registration method involving hash operations to generate static user keys, allowing users to authenticate securely without storing sensitive information, and an authentication method that uses previous authentication attempts to verify user identity through a public ledger.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If conventional authentication credentials (username/password) are used, then ease of operation is improved, but security is worsened due to easily guessed credentials

Engineering Contradiction:
Improveease of authenticationVSAvoidsecurity
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent extracts sensitive authentication information from the system by using public key cryptography. Instead of storing passwords or personal identification information on servers, the system uses only public keys for authentication, completely removing the risk associated with storing sensitive data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent introduces public keys as an intermediary between users and the authentication system. Public keys serve as a mediator that enables secure authentication without requiring users to remember complex passwords or share sensitive information with the service provider.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If biometric authentication is used, then security is improved, but device complexity is worsened due to requirement of biometric devices

Engineering Contradiction:
ImprovesecurityVSAvoiddevice requirement
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses public keys as disposable, inexpensive authentication credentials that can be generated without specialized hardware. These public keys serve as temporary, single-use authentication tokens that eliminate the need for expensive biometric devices while maintaining security.

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

3Ease of operation

If user identification information is stored, then ease of operation is improved, but security is worsened due to potential unauthorized access

Engineering Contradiction:
Improveauthentication convenienceVSAvoidunauthorized access risk
Core Design Contradiction:
Ease of operationVSObject-affected harmful factors

Solution Approach 1:

The patent extracts and removes all sensitive user identification information from the system. Instead of storing usernames, passwords, or personal information, the system exclusively uses public keys for authentication, completely eliminating the security vulnerability of storing sensitive data.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The patent uses public keys as public copies of user identity that can be freely shared and stored without security risks. Unlike private information that must be protected, public keys are designed to be publicly available while still providing secure authentication.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS11861610B2Public ledger authentication system
Publication Date: 2024.01.02 PAYPAL INC
  • US11861610B2 patent drawing
  • US11861610B2 patent drawing
  • US11861610B2 patent drawing

AI summary

Systems and methods for public ledger authentication includes receiving a first previous authentication public ledger address and a first current authentication public ledger address from a user. A verified static user key is identified in a public ledger using the first previous authentication public ledger address. A second current authentication public ledger address is then provided to the user for use in the current authentication attempt. Authentication attempt information is determined that includes a number of authentication attempts by the user, and used in a hash operation with the verified static user key to generate a first user authentication key. A second user authentication key is retrieved from the public ledger that was sent from the first current authentication public ledger address to the second current authentication public ledger address in a transaction, and the user is authenticated if the second user authentication key matches the first user authentication key.