Patent Application
20250097035
The present specification relates generally to decentralized computer platforms and more specifically to decentralized platforms storing tokens.
Decentralized computer platforms such as blockchain can provide computer architecture suitable for enabling a public and verifiable record of data. Users may desire to keep identity data private and share the data with only certain other users, such as a private or public entity.
In accordance with an aspect, a computer-implemented system for identity verification includes: a data verifier configured to validate user identification data associated with a user; a data tokenizer configured to generate a token based on the user identification data and store the token on a blockchain; and a data accessor configured to receive a request from a requestor user for the user identification data and return the token associated with the user identification data to the requestor user following grant of the request by the user.
In some embodiments, the data verifier configured to generate a data representation encoding data for requesting identification data of a user, based on the user identification data.
In some embodiments, the data representation encodes a public key associated with the user and usable for decrypting the token.
In some embodiments, the data representation is a QR code.
In some embodiments, the validation of user identification data includes requesting validation from a remote service.
In some embodiments, the computer-implemented system for identity verification includes an updater configured to update the system based on data received from a remote server.
In some embodiments, the computer-implemented system for identity verification includes a display generator configured to generate at least one display configured to request user identification data and to receive at least one request for user identification data.
In some embodiments, the data verifier is further configured to generate a user account following validation of the user identification data.
In some embodiments, transmission of data is encrypted using private-public key pairs.
In some embodiments, the token is decryptable using a public key associated with the user.
In accordance with an aspect, a computer-implemented method for identity verification includes: validating user identification data associated with a user; generating a token based on the user identification data; storing the token on a blockchain; and receiving a request, at a processor, from a requestor user for the user identification data and returning the token associated with the user identification data to the requestor user following grant of the request by the user.
In some embodiments, the computer-implemented method for identity verification includes generating a data representation encoding data for requesting identification data of a user, based on the user identification data.
In some embodiments, the data representation encodes a public key associated with the user and usable for decrypting the token.
In some embodiments, validating user identification data includes requesting validation from a remote service.
In some embodiments, the computer-implemented method for identity verification includes updating the system based on data received from a remote server.
In some embodiments, the computer-implemented method for identity verification includes generating at least one display configured to request user identification data and to receive at least one request for user identification data.
In some embodiments, the computer-implemented method for identity verification includes generating a user account following validation of the user identification data.
In some embodiments, the transmission of data is encrypted using private-public key pairs.
In some embodiments, the computer-implemented method for identity verification includes decrypting the token using a public key associated with the user.
In accordance with an aspect, there is provided a non-transitory computer readable medium storing a set of machine-interpretable instructions, which, when executed, cause a processor to perform a method for identity verification, the method comprising: validating user identification data associated with a user; generating a token based on the user identification data; storing the token on a blockchain; and receiving a request, at a processor, from a requestor user for the user identification data and return the token associated with the user identification data to the requestor user following grant of the request by the user.
Other aspects and features will become apparent to those ordinarily skilled in the art upon review of the following description of embodiments in conjunction with the accompanying figures.
The principles may better be understood with reference to the accompanying figures provided by way of illustration of an exemplary embodiment, or embodiments, incorporating principles and aspects of various embodiments, and in which:
The description that follows, and the embodiments described therein, are provided by way of illustration of an example, or examples, of particular embodiments of the principles of embodiments. These examples are provided for the purposes of explanation, and not of limitation, of those principles. In the description, like parts are marked throughout the specification and the drawings with the same respective reference numerals. The drawings are not necessarily to scale and in some instances proportions may have been exaggerated in order to more clearly to depict certain features.
In some embodiments, identity verification platform 100 includes data verifier 110, data tokenizer 120, and data accessor 130. In some embodiments, identity verification platform 100 further includes updater 140 and/or display generator 150. A processing device of identity verification platform 100 is configured to execute instructions in memory to configure data verifier 110, data tokenizer 120, data accessor 130, updater 140, and/or display generator 150. A computing device 160, such as a mobile device running a mobile application or a remote server, is configured to connect with identity verification platform 100 and allow for user engagement. Computing device 160 is configured to present a display generated by display generator 150, according to some embodiments. In some embodiments, data in identify verification platform 100 is encrypted, such as message data and/or sensitive information. For example, encryption or other security measures can be in place on a local device used by a user to access identity verification platform 100, while only tokenized data is stored on a database maintained by identity verification platform 100 (e.g., on a blockchain). In some embodiments, end-to-end encryption is used, where message data is encrypted on a sender's device and decrypted on a recipient's device, and, as shown in
In some embodiments, identity verification platform 100 is configured to create an account and associate same with a user and/or the user's identification data. For example, identify verification platform 100 is configured to create a user account, link the user's identity data to the account, and link a device to the user. In some embodiments, a user's account is created before verification is complete and, for security reasons, a user's account is locked until it is verified. In some embodiments, multi-factor authentication is used and includes sending a verification code to the user's email. The device is locked to the user account and can be used only after the user account is verified. To prevent identity theft, user identity is verified before the user can use the application on their mobile device, for example.
In some embodiments, such as shown in
In some embodiments, data tokenizer 120 is configured to generate a key, tokenize the key to generate a token, and store the token in at least one database or data store, such as in a node on a blockchain or decentralized ledger architecture. In some embodiments, no personal identifiable information (e.g., the data from which the token was derived) is stored in same, whether on a remote network or locally on an identity verification platform 100 local network. Personal identifiable information or other data from which the token was derived can remain locally on the user's personal device. In some embodiments, the key is associated with data received from the user, such as personal identifiable information (e.g., cellphone ID, user name). In some embodiments, each key is managed such that the keys are secure and can only be accessed by authorized parties. In some embodiments, each key is managed as follows. In some embodiments, client-side encryption is provided with advanced encryption standard (AEC) to protect data at rest (with master key being syncing to the bits backend, where user authentication will be used to protect the key). In some embodiments, encryption in transit is provided in addition or alternatively. This is separate from https, as data will be encrypted with asymmetrical keys where bits backend will be providing API to exchange public keys before sending data from the user to the consumer of data. The private key in this case will be stored on the user device and encrypted at rest with the first key, according to some embodiments.
In some embodiments, such as shown in
In some embodiments, updater 140 is configured to send and receive data from a remote computer (e.g., server) related to updates. Updater 140 is configured to update identity verification platform 100 (including one or more of its components) based on the updates. For example, updater 140 can receive a command representing a particular software patch related to data tokenizer 120 and configure an update to data tokenizer 120. The update can change the functionality of the component(s) updated, according to some embodiments. Further, an update can fix a security vulnerability. Identify verification platform 100 can be regularly tested and its security evaluated to identify and allow for correction of any vulnerabilities or weaknesses. In some embodiments, identity verification platform 100 is configured with network security, such as firewall(s) and secure protocol(s), which protect data communication between a software application allowing access to identity verification platform 100 (e.g., as installed on a user's device), vendor users, other users, one or more remote computers implementing identity verification platform 100, and an API implemented by identity verification platform 100. An example security protocol requires users accessing identity verification platform 100 via an app installed on their local device to use a password with minimum criteria to login to their account.
Example embodiments of identity verification platform 100 will now be described according to some embodiments. In some embodiments, identity verification platform 100 is a decentralized, digital proof of identification (ID) software system for allowing the secure transmission of identification information between users and private institutions and government departments and agencies. In some embodiments, identity verification platform 100 provides an improvement over existing verification of identity technology at least in that existing technologies do not provide users control over their identification data sharing and lack alerting, encryption, and multifactor authentication.
In some embodiments, advantages of identity verification platform 100 include: (i) enabling users to have a verified, trusted and secure digital proof of ID; (ii) reducing and/or eliminating the risks of identity theft and fraud and related cybercrimes; (iii) securing identification data stored in a database and identification information exchanged between users and institutions; and (iv) providing a white labeled software which can be used by institutions to verify the identity of individuals.
In some embodiments, identity verification platform 100 is configured to include a number of security features including the use of data end-to-end-encryption, which is used to protect the transmission of data in the form of a message from sender to recipient such that messages are encrypted on the sender's device and decrypted on the recipient's device; the use of digital signatures to verify the authenticity of messages from sender to recipient to prevent tampering; multifactor authentication methods such as two-factor authentication to verify the identity of users; the implementation of key management procedures to ensure that the encryption keys are kept secure and can only be accessed by authorized parties; secure API; an alert function in the case of a Personal Identifier Information (PII) data breach or unauthorized attempt and a function to authorize institutions to access users' PII data upon request; storage of data locally on the user's device such that the database included in identity verification platform 100 only stores tokenized data; network security measures such as firewalls and secure protocols, to protect the communication between the app for accessing identity verification platform 100, vendor users, and the server, and the API; regular updates to the mobile device application and/or its components to fix any known security vulnerabilities; and regular testing and evaluation of the mobile device application to identify and fix any security vulnerabilities or weaknesses.
In some embodiments, as shown in
Various embodiments have been described in detail. Since changes in and or additions to the foregoing description may be made. Section headings herein are provided as organizational cues. These headings shall not limit or characterize the embodiments.
