Platform for generating authenticated data objects

Abstract

Current systems for data authentication, such as in the course of financial transactions to comply with anti-money laundering and know-your-customer legislation, are burdensome and inefficient for banks and their clients. A platform of some embodiments provides a system for utilizing distributed ledger technologies, such as a blockchain data structure residing on a distributed ledger. A client may use this blockchain data structure to register the client's personal information in a data object that then may be routed to specific identified trusted individuals who verify that the information in the data object is correct. Once verification is complete, the client or other trusted individuals may use the data object as necessary to register the client for various programs or services, such as additional bank services.

What is claimed is: 
     
       1. A computer-implemented method for provisioning a locked data block, the method comprising:
 registering a data object encapsulating information data sets associated with a client individual onto a cryptographically secured chain of data blocks on a distributed ledger such that the data object is only accessible with a client private key associated with the client individual; 
 routing the data object to one or more computing systems associated with one or more trusted individuals, each trusted individual being associated with a trusted individual private key; 
 upon verification of the information data sets by each of the one or more trusted individuals, receiving, from each computing system of the one or more computing systems, a corresponding digital signature associated with the corresponding trusted individual; 
 appending the digital signatures of the one or more trusted individuals to the data object; and 
 appending a final block to the data object; 
 wherein a mechanism that appends the final block uses an unknown private key, said final block transforming the data object and the digital signatures into the locked data block incapable of linkage with further data blocks on the distributed ledger. 
 
     
     
       2. The method of  claim 1 , wherein the data object is maintained in the distributed ledger and housed on one or more distributed computing nodes synchronized in accordance with a consensus mechanism, the cryptographically secured chain of data blocks on the distributed ledger storing the data object both in one or more transformed states, the final block, and in an initial untransformed state. 
     
     
       3. The method of  claim 2 , wherein each of the one or more distributed computing nodes is configured to receive one or more update messages including transition instructions to transition the data object to a next transformed state of the one or more transformed states, the next transformed state of the data object incorporating a digital signature derived at least based on data stored within the data object. 
     
     
       4. The method of  claim 3 , wherein the data object includes one or more state transition data fields which represent state transition conditions, the state transition conditions including logical operators which enable transformation of the data object if the state transition conditions are met through corresponding operations on the data object. 
     
     
       5. The method of  claim 4 , wherein the state transition conditions are incorporated into the consensus mechanism, and wherein each of the one or more distributed computing nodes is configured to reject the one or more update messages if the state transition conditions are not met by the one or more update messages. 
     
     
       6. The method of  claim 4 , wherein the state transition conditions are incorporated into the data object upon initialization in the initial untransformed state, and wherein each of the one or more distributed computing nodes is configured to parse the data object to retrieve the state transition conditions and reject the one or more update messages if the state transition conditions are not met by the one or more update messages. 
     
     
       7. The method of  claim 4 , wherein the one or more update messages and corresponding digital signatures are compared against a database of public keys associated with the one or more trusted individuals to validate an identity of the corresponding trusted individual to which the corresponding digital signatures are indicated to relate to. 
     
     
       8. The method of  claim 7 , wherein the state transition conditions include at least a specific order of transformations of the data object based on a specific set of digital signatures associated with a specific set of the one or more trusted individuals. 
     
     
       9. The method of  claim 7 , wherein the state transition conditions include at least a combined digital signature derived from the trusted individual private keys of at least two trusted individuals combined together, the combined digital signature representing a simultaneous approval. 
     
     
       10. The method of  claim 7 , wherein the one or more transformed states includes at least the appending of the final block, wherein the data object is modified through a final update message that appends a new data block onto the cryptographically secured chain of data blocks on the distributed ledger, and wherein the consensus mechanism is configured to reject any further data blocks for linkage to the final block. 
     
     
       11. A computer-implemented system for provisioning a locked data block, the system comprising:
 one or more computer processors operating in conjunction with a computer memory and non-transitory computer readable media, the one or more processors configured to:
 register a data object encapsulating information data sets associated with a client individual onto a cryptographically secured chain of data blocks on a distributed ledger such that the data object is only accessible with a client private key associated with the client individual; 
 host the distributed ledger configured to route the data object to one or more computing systems associated with one or more trusted individuals, each trusted individual being associated with a trusted individual private key; 
 upon verification of the information data sets by each of the one or more trusted individuals, receive, from each computing system of the one or more computing systems, a corresponding digital signature associated with the corresponding trusted individual; 
 append the corresponding digital signatures of the one or more trusted individuals to the data object; and 
 append a final block to the data object; 
 wherein a mechanism that appends the final block uses an unknown private key, said final block transforming the data object and the one or more digital signatures into the locked data block incapable of linkage with further data blocks on the distributed ledger. 
 
 
     
     
       12. The system of  claim 11 , wherein the data object is maintained in the distributed ledger and housed on one or more distributed computing nodes synchronized in accordance with a consensus mechanism, the cryptographically secured chain of data blocks on the distributed ledger storing the data object both in one or more transformed states, the final block, and in an initial untransformed state. 
     
     
       13. The system of  claim 12 , wherein each of the one or more distributed computing nodes is configured to receive one or more update messages including transition instructions to transition the data object to a next transformed state of the one or more transformed states, the next transformed state of the data object incorporating a digital signature derived at least based on data stored within the data object. 
     
     
       14. The system of  claim 13 , wherein the data object includes one or more state transition data fields which represent state transition conditions, the state transition conditions including logical operators which enable transformation of the data object if the state transition conditions are met through corresponding operations on the data object. 
     
     
       15. The system of  claim 14 , wherein the state transition conditions are incorporated into the consensus mechanism, and wherein each of the one or more distributed computing nodes is configured to reject the one or more update messages if the state transition conditions are not met by the one or more update messages. 
     
     
       16. The system of  claim 14 , wherein the state transition conditions are incorporated into the data object upon initialization in the initial untransformed state, and wherein each of the one or more distributed computing nodes is configured to parse the data object to retrieve the state transition conditions and reject the one or more update messages if the state transition conditions are not met by the one or more update messages. 
     
     
       17. The system of  claim 14 , wherein the one or more update messages and corresponding digital signatures are compared against a database of public keys associated with the one or more trusted individuals to validate an identity of the corresponding trusted individual to which the corresponding digital signatures are indicated to relate to. 
     
     
       18. The system of  claim 17 , wherein the state transition conditions include at least a specific order of transformations of the data object based on a specific set of digital signatures associated with a specific set of the one or more trusted individuals. 
     
     
       19. The system of  claim 17 , wherein the one or more transformed states includes at least the appending of the final block, wherein the data object is modified through a final update message that appends a new data block onto the series of cryptographically secured chain of data blocks on the distributed ledger, and wherein the consensus mechanism is configured to reject any further data blocks for linkage to the final block. 
     
     
       20. A non-transitory computer-readable medium storing machine-interpretable instructions for provisioning a locked data block, the machine-interpretable instructions, which when executed by a processor, perform steps of a method comprising:
 registering a data object encapsulating information data sets associated with a client individual onto a cryptographically secured chain of data blocks on a distributed ledger such that the data object is only accessible with a client private key associated with the client individual; 
 routing the data object to one or more computing systems associated with one or more trusted individuals, each trusted individual being associated with a trusted individual private key; 
 upon verification of the information data sets by each of the one or more trusted individuals, receiving, from each computing system of the one or more computing systems, a corresponding digital signature associated with the corresponding trusted individual; 
 appending the one or more digital signatures of the one or more trusted individuals to the data object; and 
 appending a final block to the data object; 
 wherein a mechanism that appends the final block uses an unknown private key, said final block transforming the data object and the one or more digital signatures into the locked data block incapable of linkage with further data blocks on the distributed ledger.