US11182851B2ActiveUtilityA1

Inter-ledger messaging in a blockchain

74
Assignee: IBMPriority: Oct 20, 2016Filed: Oct 20, 2016Granted: Nov 23, 2021
Est. expiryOct 20, 2036(~10.3 yrs left)· nominal 20-yr term from priority
G06Q 40/03H04L 9/3239H04L 9/50G06F 2209/547H04L 2209/56H04L 2209/38G06Q 40/025
74
PatentIndex Score
1
Cited by
21
References
20
Claims

Abstract

Operating conditions of a blockchain configuration may be dynamic and change automatically under certain circumstances. One example method of operation may include receiving a blockchain transaction sent from a first blockchain to a second blockchain, identifying an inter-ledger contract between the first blockchain and the second blockchain, receiving an inter-ledger message at the second blockchain from the first blockchain, and determining whether to log the blockchain transaction in the first blockchain or the second blockchain based on the inter-ledger message.

Claims

exact text as granted — not AI-modified
What is claimed is: 
     
       1. A computer-implemented method, comprising:
 receiving, by a computing system of a first blockchain, a blockchain transaction; 
 identifying, by the computing system, a data value managed by a second blockchain included in the received blockchain transaction; 
 transmitting, via an inter-ledger smart contract, an inter-ledger message including data from the blockchain transaction from the computing system of the first blockchain to a computing system of the second blockchain; 
 determining, by the computing system, to log the blockchain transaction in the first blockchain; and 
 logging the blockchain transaction in the first blockchain. 
 
     
     
       2. The computer-implemented method of  claim 1 , wherein a current consensus procedure of the first blockchain is different from a current consensus procedure of the second blockchain. 
     
     
       3. The computer-implemented method of  claim 1 , further comprising:
 establishing a ledger share agreement, by the computing system, between the first blockchain and the second blockchain; and 
 transmitting an inter-ledger confirmation message confirming the ledger share agreement, by the computing system. 
 
     
     
       4. The computer-implemented method of  claim 3 , wherein the ledger share agreement comprises one or more of a block model, a cryptography type, a verification procedure, and a consensus procedure. 
     
     
       5. The computer-implemented method of  claim 1 , further comprising:
 parsing the blockchain transaction at the first blockchain, by the computing system; 
 identifying one or more identifiers associated with the second blockchain, by the computing system; and 
 determining to log the transaction in the second blockchain based on the one or more identifiers. 
 
     
     
       6. The computer-implemented method of  claim 1 , further comprising:
 identifying, by the computing system, one or more consensus procedures accepted by the first blockchain and the second blockchain to be used for the blockchain transaction. 
 
     
     
       7. The computer-implemented method of  claim 5 , further comprising:
 identifying a third blockchain referenced by the blockchain transaction, by the computing system; and 
 transmitting, via the inter-ledger smart contract, another inter-ledger message to a computing system of the third blockchain to log a portion of the blockchain transaction in the third blockchain. 
 
     
     
       8. An apparatus, comprising:
 a processor configured to:
 receive a blockchain transaction via a computing system of a first blockchain, 
 identify a data value managed by a second blockchain included in the received blockchain transaction, 
 transmit, via an inter-ledger smart contract, an inter-ledger message including data from the blockchain transaction from the computing system of the first blockchain to a computing system of the second blockchain, 
 determine whether to log the blockchain transaction in the first blockchain, and 
 
 log the blockchain transaction in the first blockchain. 
 
     
     
       9. The apparatus of  claim 8 , wherein a current consensus procedure of the first blockchain is different from a current consensus procedure of the second blockchain. 
     
     
       10. The apparatus of  claim 8 , wherein the processor is further configured to:
 establish a ledger share agreement between the first blockchain and the second blockchain, and 
 transmit an inter-ledger confirmation message confirming the ledger share agreement. 
 
     
     
       11. The apparatus of  claim 10 , wherein the ledger share agreement comprises one or more of a block model, a cryptography type, a verification procedure, and a consensus procedure. 
     
     
       12. The apparatus of  claim 8 , wherein the processor is further configured to:
 parse the blockchain transaction at the first blockchain, 
 identify one or more identifiers associated with the second blockchain, and 
 determine to log the transaction in the second blockchain based on the one or more identifiers. 
 
     
     
       13. The apparatus of  claim 8 , wherein the processor is further configured to:
 identify one or more consensus procedures accepted by the first blockchain and the second blockchain to be used for the blockchain transaction. 
 
     
     
       14. The apparatus of  claim 12 , wherein the processor is further configured to:
 identify a third blockchain referenced by the blockchain transaction, and 
 transmit, via the inter-ledger smart contract, another inter-ledger message to a computing system of the third blockchain to log a portion of the blockchain transaction in the third blockchain. 
 
     
     
       15. A non-transitory computer readable storage medium storing one or more instructions that when executed by a processor cause the processor to perform a method comprising:
 receiving a blockchain transaction via a computing system of a first blockchain; 
 identifying a data value managed by a second blockchain within the blockchain transaction; 
 transmitting, via an inter-ledger smart contract, an inter-ledger message including data from the blockchain transaction from the computing system of the first blockchain to a computing system of the second blockchain; 
 determining to log the blockchain transaction in the first blockchain; and 
 logging the blockchain transaction in the first blockchain. 
 
     
     
       16. The non-transitory computer readable storage medium of  claim 15 , wherein a current consensus procedure of the first blockchain is different from a current consensus procedure of the second blockchain. 
     
     
       17. The non-transitory computer readable storage medium of  claim 15 , wherein the instructions are further configured to cause the processor to perform:
 establishing a ledger share agreement between the first blockchain and the second blockchain; and 
 transmitting an inter-ledger confirmation message confirming the ledger share agreement. 
 
     
     
       18. The non-transitory computer readable storage medium of  claim 17 , wherein the ledger share agreement comprises one or more of a block model, a cryptography type, a verification procedure, and a consensus procedure. 
     
     
       19. The non-transitory computer readable storage medium of  claim 15 , wherein the instructions are further configured to cause the processor to perform:
 parsing the blockchain transaction at the first blockchain; 
 identifying one or more identifiers associated with the second blockchain; and 
 determining to log the transaction in the second blockchain based on the one or more identifiers. 
 
     
     
       20. The non-transitory computer readable storage medium of  claim 19 , wherein the instructions are further configured to cause the processor to perform:
 identifying a third blockchain referenced by the blockchain transaction; and 
 transmitting, via the inter-ledger smart contract, another inter-ledger message to a computing system of the third blockchain to log a portion of the blockchain transaction in the third blockchain.

Cited by (0)

No later patents cite this yet.

References (0)

No backward citations on record.