Scalable, secure, efficient, and adaptable distributed digital ledger transaction network
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.
1. A method comprising:
generating, for a first user account of a distributed digital ledger transaction network and a second user account of the distributed digital ledger transaction network that maintains one or more sub-accounts within a private digital ledger, a request for a transaction between the first user account and the second user account by:
identifying a main public address identifier that locates the second user account within a state data structure of the distributed digital ledger transaction network, a sub-address identifier that locates a sub-account from the one or more sub-accounts within the private digital ledger maintained by the second user account, and a public encryption key associated with the second user account; and
generating an encrypted sub-address unique to the transaction by applying the public encryption key to the sub-address identifier; and
submitting, for execution via the distributed digital ledger transaction network, the request for the transaction between the first user account and the second user account using the main public address identifier and the encrypted sub-address unique to the transaction.
2. The method of claim 1 , wherein generating the encrypted sub-address unique to the transaction comprises:
adding a nonce value to the sub-address identifier; and
applying the public encryption key to the sub-address identifier with the nonce value.
3. The method of claim 1 , wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises scanning a digital visual code that encodes the main public address identifier, the sub-address identifier, and the public encryption key.
4. The method of claim 1 , further comprising identifying the main public address identifier, the sub-address identifier, and the public encryption key based on an email address of a user corresponding to the second user account.
5. The method of claim 4 , wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises:
identifying a domain name and personal email identifier from the email address of the user corresponding to the second user account;
determining the main public address identifier based on the domain name from the email address; and
determining the sub-address identifier based on the personal email identifier from the email address.
6. The method of claim 5 , wherein determining the main public address identifier based on the domain name comprises accessing a DNS record corresponding to the domain name to identify at least one of: the main public address identifier or the public encryption key.
7. The method of claim 6 , further comprising utilizing DNSSEC to validate the main public address identifier or the public encryption key identified by accessing the DNS record corresponding to the domain name.
8. The method of claim 6 , wherein generating the encrypted sub-address comprises applying the public encryption key, determined by accessing the DNS record, to the sub-address identifier determined based on the personal email identifier.
9. The method of claim 5 , wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises, in response to providing the personal email identifier from the email address to a remote server corresponding to the domain name, receiving the public encryption key from the remote server corresponding to the domain name.
10. The method of claim 1 , further comprising identifying the main public address identifier, the sub-address identifier, and the public encryption key based on at least one of: a telephone number of a user corresponding to the second user account or a user ID of the user.
11. A non-transitory computer-readable medium storing instructions thereon that, when executed by at least one processor, cause a computing device to:
generate, for a first user account of a distributed digital ledger transaction network and a second user account of the distributed digital ledger transaction network that maintains one or more sub-accounts within a private digital ledger, a request for a transaction between the first user account and the second user account by:
identifying a main public address identifier that locates the second user account within a state data structure of the distributed digital ledger transaction network, a sub-address identifier that locates a sub-account from the one or more sub-accounts within the private digital ledger maintained by the second user account, and a public encryption key associated with the second user account; and
generating an encrypted sub-address unique to the transaction by applying the public encryption key to the sub-address identifier; and
submit, for execution via the distributed digital ledger transaction network, the request for the transaction between the first user account and the second user account using the main public address identifier and the encrypted sub-address unique to the transaction.
12. The non-transitory computer-readable medium of claim 11 , wherein generating the encrypted sub-address unique to the transaction comprises:
adding a nonce value to the sub-address identifier; and
applying the public encryption key to the sub-address identifier with the nonce value.
13. The non-transitory computer-readable medium of claim 11 , wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises scanning a digital visual code that encodes the main public address identifier, the sub-address identifier, and the public encryption key.
14. The non-transitory computer-readable medium of claim 11 ,
further comprising instructions that, when executed by the at least one processor, cause the computing device to identify the main public address identifier, the sub-address identifier, and the public encryption key based on an email address of a user corresponding to the second user account; and
wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises:
identifying a domain name and personal email identifier from the email address of the user corresponding to the second user account;
determining the main public address identifier based on the domain name from the email address; and
determining the sub-address identifier based on the personal email identifier from the email address.
15. The non-transitory computer-readable medium of claim 14 , wherein:
determining the main public address identifier based on the domain name comprises accessing a DNS record corresponding to the domain name to identify at least one of: the main public address identifier or the public encryption key; and
generating the encrypted sub-address comprises applying the public encryption key, determined by accessing the DNS record, to the sub-address identifier determined based on the personal email identifier.
16. The non-transitory computer-readable medium of claim 14 , wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises, in response to providing the personal email identifier from the email address to a remote server corresponding to the domain name, receiving the public encryption key from the remote server corresponding to the domain name.
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, for a first user account of a distributed digital ledger transaction network and a second user account of the distributed digital ledger transaction network that maintains one or more sub-accounts within a private digital ledger, a request for a transaction between the first user account and the second user account by:
identifying a main public address identifier that locates the second user account within a state data structure of the distributed digital ledger transaction network, a sub-address identifier that locates a sub-account from the one or more sub-accounts within the private digital ledger maintained by the second user account, and a public encryption key associated with the second user account; and
generating an encrypted sub-address unique to the transaction by applying the public encryption key to the sub-address identifier; and
submit, for execution via the distributed digital ledger transaction network, the request for the transaction between the first user account and the second user account using the main public address identifier and the encrypted sub-address unique to the transaction.
18. The system of claim 17 , wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises scanning a digital visual code that encodes the main public address identifier, the sub-address identifier, and the public encryption key.
19. The system of claim 17 , further comprising instructions that, when executed by the at least one processor, cause the system to identify the main public address identifier, the sub-address identifier, and the public encryption key based on an email address of a user corresponding to the second 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 the main public address identifier, the sub-address identifier, and the public encryption key based on an email address of a user corresponding to the second user account; and
wherein identifying the main public address identifier, the sub-address identifier, and the public encryption key comprises:
identifying a domain name and personal email identifier from the email address of the user corresponding to the second user account;
determining the main public address identifier based on the domain name from the email address; and
determining the sub-address identifier based on the personal email identifier from the email address.