ACTIVITY AUTHENTICATION USING TIME-BASED ONE-TIME PASSWORD
In one aspect, a device may include at least one processor and storage accessible to the at least one processor. The storage may include instructions executable by the at least one processor to identify a time-based one-time password (TOTP) associated with an activity such as a transaction. The instructions may also be executable to authenticate the transaction via the TOTP using a public key associated with a first party to the transaction and using one or more of data related to a name of the first party to the transaction, data related to an amount of the transaction, data related to a date of the transaction, and/or data related to an account number associated with the transaction. Based on the authentication, the instructions may then be executable to process the transaction.
1 . A device, comprising:
at least one processor; and
storage accessible to the at least one processor and comprising instructions executable by the at least one processor to:
identify a time-based one-time password (TOTP) associated with an activity;
authenticate the activity via the TOTP using a public key associated with a first party to the activity and using one or more of: data related to a name of the first party to the activity, data related to an amount of the activity, data related to a date of the activity, data related to an account number associated with the activity;
based on the authentication, process the activity.
2 . The device of claim 1 , wherein the TOTP is authenticated using a hash of the amount of the activity, the hash indicated in a Merkle tree accessed by the device.
3 . The device of claim 2 , wherein the Merkle tree is a sparse Merkle tree.
4 . The device of claim 3 , wherein the public key is identified from the sparse Merkle tree.
5 . The device of claim 1 , wherein the TOTP is authenticated using a first hash of the amount of the activity as indicated in a first distributed Merkle tree, and using a second hash of the amount of the activity as indicated in a second distributed Merkle tree, the first distributed Merkle tree being different from the second distributed Merkle tree.
6 . The device of claim 1 , wherein the TOTP is a six-digit TOTP.
7 . The device of claim 1 , wherein the activity is authenticated using each of: the data related to the name of the first party to the activity, the data related to the amount of the activity, the data related to the date of the activity, the data related to the account number associated with the activity.
8 . The device of claim 1 , wherein the activity is also authenticated using data related to a name of a second party to the activity, the second party being different from the first party, the first and second parties being on opposing ends of the activity.
9 . The device of claim 1 , wherein the activity is also authenticated using data related to an amount of funds available as indicated via a Merkle tree.
10 . The device of claim 1 , wherein the TOTP is a first cryptographic hash of one or more of: a second cryptographic hash of the name of the first party to the activity, a third cryptographic hash of the amount of the activity, a fourth cryptographic of the date of the activity, a fifth cryptographic hash of the account number associated with the activity.
11 . A method, comprising:
identifying a hash associated with an activity;
verifying the activity via the hash using a key associated with a first party to the activity and using one or more of: data related to a name of the first party to the activity, data related to an amount of the activity, data related to a date of the activity, data related to an account number associated with the activity;
based on the verification, processing the activity.
12 . The method of claim 11 , wherein the hash is a time-based one-time password (TOTP).
13 . The method of claim 11 , wherein the activity is verified using each of: the data related to the name of the first party to the activity, the data related to the amount of the activity, the data related to the date of the activity, the data related to the account number associated with the activity.
14 . The method of claim 11 , wherein the hash is a first hash, and wherein the method comprises:
accessing a sparse Merkle tree to verify the first hash using a second hash of the amount of the activity, the second hash indicated in the sparse Merkle tree.
15 . The method of claim 14 , wherein the key is identified from the sparse Merkle tree.
16 . The method of claim 11 , wherein the activity is a first activity, the first activity being a current activity that is the subject of the verification, and wherein the first activity is also verified using data related to a second activity, the second activity being a past activity.
17 . The method of claim 11 , wherein the activity is also verified using data related to an address associated with the first party.
18 . At least one computer readable storage medium (CRSM) that is not a transitory signal, the at least one computer readable storage medium comprising instructions executable by at least one processor to:
identify a hash associated with an activity;
authenticate the activity via the hash using a key associated with a first party to the activity and using one or more of: data related to a name of the first party to the activity, data related to an amount of the activity, data related to a date of the activity, data related to an account number associated with the activity;
based on the authentication, process the activity.
19 . The CRSM of claim 18 , wherein the hash is a time-based one-time password (TOTP), and wherein the activity is authenticated using the TOTP and a sparse hash tree.
20 . The CRSM of claim 18 , wherein the activity is a digital activity.