Scalable, secure, efficient, and adaptable distributed digital ledger transaction network
Abstract
The present disclosure relates to systems, methods, and non-transitory computer readable storage media for implementing a scalable, secure, efficient, and adaptable distributed digital ledger transaction network. Indeed, the disclosed systems can reduce storage and processing requirements, improve security of implementing computing devices and underlying digital assets, accommodate a wide variety of different digital programs (or “smart contracts”), and scale to accommodate billions of users and associated digital transactions. For example, the disclosed systems can utilize a host of features that improve storage, account/address management, digital transaction execution, consensus, and synchronization processes. The disclosed systems can also utilize a new programming language that improves efficiency and security of the distributed digital ledger transaction network.
Claims
exact text as granted — not AI-modifiedWhat is claimed is:
1 . A computer-implemented method comprising:
generating an authentication key corresponding to a user account of an authenticated data structure of a distributed digital ledger transaction network; identifying a transaction for modifying the authentication key corresponding to the user account; and upon authenticating the transaction utilizing the authentication key, executing the transaction by generating a new authentication key for the user account.
2 . The computer-implemented method of claim 1 , further comprising:
identifying an additional transaction sent using the user account; and upon authenticating the additional transaction utilizing the new authentication key for the user account, executing the additional transaction.
3 . The computer-implemented method of claim 1 , wherein:
the user account of the authenticated data structure of the distributed digital ledger transaction network corresponds to an address of the authenticated data structure; and executing the transaction by generating the new authentication key for the user account comprises generating the new authentication key for the user account while maintaining the address of the authenticated data structure for the user account.
4 . The computer-implemented method of claim 1 , further comprising:
identifying an additional transaction for modifying the new authentication key corresponding to the user account; and upon authenticating the additional transaction utilizing the new authentication key, executing the additional transaction by generating an additional authentication key for the user account.
5 . The computer-implemented method of claim 1 , wherein generating the authentication key corresponding to the user account of the authenticated data structure of the distributed digital ledger transaction network comprises:
determining an address of the user account within the authenticated data structure; and setting the authentication key corresponding to the user account to the address of the user account.
6 . The computer-implemented method of claim 1 , wherein generating the authentication key corresponding to the user account of the authenticated data structure of the distributed digital ledger transaction network comprises:
identifying a public encryption key corresponding to the user account; generating a hash value by applying a hash function to the public encryption key; and setting the hash value as the authentication key corresponding to the user account.
7 . The computer-implemented method of claim 6 , wherein authenticating the transaction utilizing the authentication key comprises:
generating an additional hash value by applying the hash function to the public encryption key; and determining that the additional hash value corresponds to the authentication key.
8 . The computer-implemented method of claim 1 , further comprising executing the transaction by generating a new public encryption key corresponding to the user account,
wherein generating the new authentication key for the user account comprises generating the new authentication key by applying a hash function to the new public encryption key corresponding to the user account.
9 . A non-transitory computer-readable medium storing instructions thereon that, when executed by at least one processor, cause a computing device to:
generate an authentication key corresponding to a user account of an authenticated data structure of a distributed digital ledger transaction network; identify a transaction for modifying the authentication key corresponding to the user account; and upon authenticating the transaction utilizing the authentication key, execute the transaction by generating a new authentication key for the user account.
10 . The non-transitory computer-readable medium of claim 9 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:
identify an additional transaction sent using the user account; and upon authenticating the additional transaction utilizing the new authentication key for the user account, execute the additional transaction.
11 . The non-transitory computer-readable medium of claim 9 , wherein:
the user account of the authenticated data structure of the distributed digital ledger transaction network corresponds to an address of the authenticated data structure; and the instructions, when executed by the at least one processor, cause the computing device to execute the transaction by generating the new authentication key for the user account by generating the new authentication key for the user account while maintaining the address of the authenticated data structure for the user account.
12 . The non-transitory computer-readable medium of claim 9 , further comprising instructions that, when executed by the at least one processor, cause the computing device to:
identify an additional transaction for modifying the new authentication key corresponding to the user account; and upon authenticating the additional transaction utilizing the new authentication key, execute the additional transaction by generating an additional authentication key for the user account.
13 . The non-transitory computer-readable medium of claim 9 , wherein the instructions, when executed by the at least one processor, cause the computing device to generate the authentication key corresponding to the user account of the authenticated data structure of the distributed digital ledger transaction network by:
determining an address of the user account within the authenticated data structure; and setting the authentication key corresponding to the user account to the address of the user account.
14 . The non-transitory computer-readable medium of claim 9 , wherein the instructions, when executed by the at least one processor, cause the computing device to generate the authentication key corresponding to the user account of the authenticated data structure of the distributed digital ledger transaction network by:
identifying a public encryption key corresponding to the user account; generating a hash value by applying a hash function to the public encryption key; and setting the hash value as the authentication key corresponding to the user account.
15 . The non-transitory computer-readable medium of claim 14 , wherein the instructions, when executed by the at least one processor, cause the computing device to authenticate the transaction utilizing the authentication key by:
generating an additional hash value by applying the hash function to the public encryption key; and determining that the additional hash value corresponds to the authentication key.
16 . The non-transitory computer-readable medium of claim 9 , further comprising instructions that, when executed by the at least one processor, cause the computing device to execute the transaction by generating a new public encryption key corresponding to the user account,
wherein the instructions, when executed by the at least one processor, cause the computing device to generate the new authentication key for the user account comprises generating the new authentication key by applying a hash function to the new public encryption key corresponding to the user account.
17 . A system comprising:
at least one processor; and at least one non-transitory computer-readable medium storing instructions thereon that, when executed by the at least one processor, cause the system to:
generate an authentication key corresponding to a user account of an authenticated data structure of a distributed digital ledger transaction network;
identify a transaction for modifying the authentication key corresponding to the user account; and
upon authenticating the transaction utilizing the authentication key, execute the transaction by generating a new authentication key for the user account.
18 . The system of claim 17 , further comprising instructions that, when executed by the at least one processor, cause the system to:
identify an additional transaction sent using the user account; and upon authenticating the additional transaction utilizing the new authentication key for the user account, execute the additional transaction.
19 . The system of claim 17 , wherein:
the user account of the authenticated data structure of the distributed digital ledger transaction network corresponds to an address of the authenticated data structure; and the instructions, when executed by the at least one processor, cause the system to execute the transaction by generating the new authentication key for the user account by generating the new authentication key for the user account while maintaining the address of the authenticated data structure for the user account.
20 . The system of claim 17 , further comprising instructions that, when executed by the at least one processor, cause the system to:
identify an additional transaction for modifying the new authentication key corresponding to the user account; and upon authenticating the additional transaction utilizing the new authentication key, execute the additional transaction by generating an additional authentication key for the user account.Cited by (0)
No later patents cite this yet.
References (0)
No backward citations on record.