Systems and methods for distributed ledger management

Abstract

Methods and systems are described for managing a distributed ledger. A user may manage permissions and other settings for devices associated with an account by adding transactions to the distributed ledger. Versions of the distributed ledger may be stored by the devices. A master version of the distributed ledger may be managed by a ledger node configured to add data blocks to the master version of the ledger. A consensus process may be used to determine an approved version of the distributed ledger if a condition, such as an error condition or an inconsistency, is detected for the distributed ledger.

What is claimed is: 
     
         1 . A method comprising:
 receiving, from a first device, data indicative of a first ledger associated with an account, wherein the first ledger comprises a first version of a distributed ledger associated with the account;   determining, based on the data indicative of the first ledger, a condition associated with the first ledger;   sending, based on the condition and to a second device associated with the account, a request for a second ledger, wherein the second ledger comprises a second version of the distributed ledger associated with the account;   receiving, based on the request, at least a portion of the second ledger;   determining, based on applying consensus rules to the first ledger and the second ledger, that one of the first ledger or the second ledger is an approved ledger; and   sending data indicative of the approved ledger.   
     
     
         2 . The method of  claim 1 , wherein the condition comprises one or more of an error condition, a validation failure, a failure state, or a condition associated with failing a validation process, and wherein the condition is based on a determination that a data block of the first ledger has been added, removed, or modified. 
     
     
         3 . The method of  claim 1 , wherein sending the request for the second ledger comprises determining a plurality of devices associated with the account and sending, to the plurality of devices, requests for corresponding versions of the distributed ledger stored by the plurality of devices. 
     
     
         4 . The method of  claim 1 , wherein the first ledger is stored by the first device, and wherein the first device is associated with the account, and wherein the second ledger is stored by the second device. 
     
     
         5 . The method of  claim 1 , wherein the distributed ledger comprises a plurality of transactions stored in corresponding data blocks, wherein each data block comprises only one transaction of the plurality of transactions. 
     
     
         6 . The method of  claim 1 , wherein a master version of the distributed ledger is stored by a service platform comprising one or more computing devices configured to add transactions to the distributed ledger. 
     
     
         7 . The method of  claim 1 , wherein at least one of a plurality of devices associated with the account comprises a version of the distributed ledger that has less than all data blocks stored on a master version of the distributed ledger. 
     
     
         8 . A method comprising:
 sending, to a first device, data associated with adding a transaction to a distributed ledger associated with an account;   receiving, from the first device and based on the data associated with adding the transaction, a condition associated with the distributed ledger;   sending, to a second device and based on the condition, data associated with determining an approved ledger, wherein the approved ledger comprises an approved version of the distributed ledger determined based on applying a consensus algorithm to a plurality of versions of the distributed ledger received from one or more devices associated with the account;   receiving, from the second device, data indicative of the approved ledger; and   sending, to the first device, data associated with adding the transaction to the approved ledger.   
     
     
         9 . The method of  claim 8 , wherein the condition comprises one or more of an error condition, a validation failure, a failure state, or a condition associated with failing a validation process, and wherein the condition is based on a determination that a data block of at least one of the plurality of versions of the distributed ledger has been added, removed, or modified. 
     
     
         10 . The method of  claim 8 , wherein the second device is configured to determine the one or more devices associated with the account and send, to the one or more devices associated with the account, requests for corresponding versions of the distributed ledger stored by the one or more devices associated with the account. 
     
     
         11 . The method of  claim 8 , wherein the distributed ledger comprises a first ledger stored by a first computing device associated with the account and a second ledger stored by a second computing device associated with the account. 
     
     
         12 . The method of  claim 8 , wherein the distributed ledger comprises a plurality of transactions stored in corresponding data blocks, wherein each data block comprises only one transaction of the plurality of transactions. 
     
     
         13 . The method of  claim 8 , wherein a master version of the distributed ledger is stored by a service platform comprising a plurality of devices configured to add transactions to the distributed ledger. 
     
     
         14 . The method of  claim 13 , wherein at least one of the one or more devices associated with the account comprises a version of the plurality of versions of the distributed ledger that has less than all data blocks stored on the master version of the distributed ledger. 
     
     
         15 . A method comprising:
 receiving data associated with adding a transaction to a distributed ledger associated with an account;   determining, based on the data associated with adding the transaction, a condition associated with the distributed ledger;   sending a message indicative of the condition;   receiving, based on the condition, data indicative of an approved ledger, wherein the approved ledger comprises an approved version of the distributed ledger determined based on applying a consensus algorithm to a plurality of versions of the distributed ledger received from one or more devices associated with the account; and   causing an update of the approved ledger with data indicative of the transaction.   
     
     
         16 . The method of  claim 15 , wherein the condition comprises one or more of an error condition, a validation failure, a failure state, or a condition associated with failing a validation process, and wherein determining the condition comprises determining that a data block of at least one of the plurality of versions of the distributed ledger has been added, removed, or modified. 
     
     
         17 . The method of  claim 15 , wherein the plurality of versions of the distributed ledger comprise a first version stored by a first device associated with the account and a second version stored by a second device associated with the account. 
     
     
         18 . The method of  claim 15 , wherein the distributed ledger comprises a plurality of transactions stored in corresponding data blocks, wherein each data block comprises only one transaction of the plurality of transactions. 
     
     
         19 . The method of  claim 15 , wherein a master version of the distributed ledger is stored by a service platform comprising a plurality of devices configured to add transactions to the distributed ledger. 
     
     
         20 . The method of  claim 19 , wherein at least one of the one or more devices associated with the account comprises a version of the distributed ledger that has less than all data blocks stored on the master version of the distributed ledger.