Public Ledger Authentication via Hash Operations
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional authentication systems for online and mobile payment transactions are insecure due to the use of easily guessed credentials and the lack of biometric authentication, compromising 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 verifies user identities through a public ledger network.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If conventional authentication systems use username and password or biometric identifiers, then users can access payment accounts, but security is compromised due to easily guessed credentials or lack of biometric devices
Solution Approach 1:
The patent introduces a public ledger as an intermediary authentication mechanism. Instead of directly storing or transmitting sensitive authentication data, the system uses cryptographic hash operations on the public ledger to verify user identities. This intermediary layer eliminates the need for users to store sensitive information locally while maintaining security through distributed verification.
Solution Approach 2:
The patent extracts and eliminates the need for storing sensitive user information in traditional authentication systems. By using hash operations on publicly verifiable data, the system removes the requirement for storing passwords, biometric templates, or other sensitive credentials, thereby improving security without complicating the authentication process.
2Reliability
If users store sensitive authentication information locally, then authentication can be performed, but security is compromised and user identification information must be stored
Solution Approach 1:
The patent extracts the requirement for storing sensitive user identification information by using hash operations on publicly verifiable data. The system eliminates local storage of passwords, biometric templates, or personal identifiers, replacing them with cryptographic verification through the public ledger.
Solution Approach 2:
The public ledger serves as an intermediary that stores and verifies authentication data without requiring users to store sensitive information locally. The distributed nature of the public ledger provides secure verification while eliminating the security risks associated with local storage of authentication credentials.
3Reliability
If a public ledger authentication system is implemented, then security is enhanced and sensitive information storage is eliminated, but system complexity increases
Solution Approach 1:
The patent leverages the existing public ledger infrastructure to perform multiple functions: transaction recording, authentication verification, and identity management. By making the public ledger multi-functional, the system avoids building separate authentication infrastructure, thereby reducing overall system complexity while maintaining enhanced security.
Data Source
AI summary
Systems and methods for public ledger authentication include 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.


