Limiting blockchain size to optimize performance

Patent metadata

Field	Value
Publication number	US-10915512-B2
Application number	US-201916565469-A
Country	US
Kind code	B2
Filing date	Sep 9, 2019
Priority date	Jan 3, 2017
Publication date	Feb 9, 2021
Grant date	Feb 9, 2021

Abstract

A blockchain may include various transactions which are identified and which require processing. The order of processing such transactions may be optimized by examining content of the transactions. One example operation may include one or more of identifying blockchain transactions, designating each of the blockchain transactions as an independent transaction type or a dependent transaction type, and determining an order to process the blockchain transactions based on the independent transaction type or the dependent transaction type.

First claim

What is claimed is:

1. A method, comprising:
identifying at least one transaction, of one or more transactions on a blockchain, as eligible for archiving based on the blockchain reaching a maximum data size threshold;
identifying, on the blockchain, at least one transaction that is related to a portion of the identified at least one transaction;
compressing the at least one transaction and the at least one related transaction; and
archiving the at least one transaction and the at least one related transaction.

2. The method of claim 1 , further comprising determining the maximum data size threshold of the blockchain.

3. The method of claim 1 , further comprising:
identifying a client profile has withdrawn enrollment from the blockchain; and
identifying a plurality of client profile transactions logged in the blockchain corresponding to the client profile.

4. The method of claim 3 , further comprising archiving the plurality of client profile transactions corresponding to the client profile.

5. The method of claim 4 , further comprising:
identifying the client profile has re-enrolled with the blockchain;
identifying the plurality of client profile transactions corresponding to the client profile; and
restoring the plurality of client profile transactions responsive to the client profile being re-enrolled with the blockchain.

6. The method of claim 1 , further comprising determining that blockchain data stored in the blockchain has reached the maximum data size threshold.

7. The method of claim 1 , further comprising:
storing blockchain transactions of the blockchain in a priority queue with the least frequently used transactions at respective topmost positions of the priority queue; and
when the blockchain reaches the maximum data size threshold, archiving the least frequently accessed blockchain transactions at the respective topmost positions of the priority queue.

8. An apparatus, comprising:
a processor configured to:
identify at least one transaction, of one or more transactions on a blockchain, as eligible for archiving based on the blockchain reaching a maximum data size threshold;
identify, on the blockchain, at least one transaction that is related to a portion of the identified at least one transaction;
compress the at least one transaction and the at least one related transaction; and
archive the at least one transaction and the at least one related transaction.

9. The apparatus of claim 8 , wherein the processor is further configured to determine the maximum data size threshold of the blockchain.

10. The apparatus of claim 8 , wherein the processor is further configured to:
identify a client profile has withdrawn enrollment from the blockchain; and
identify a plurality of client profile transactions logged in the blockchain that correspond to the client profile.

11. The apparatus of claim 10 , wherein the processor is further configured to archive the plurality of client profile transactions that correspond to the client profile.

12. The apparatus of claim 11 , wherein the processor is further configured to:
identify the client profile has re-enrolled with the blockchain;
identify the plurality of client profile transactions that correspond to the client profile; and
restore the plurality of client profile transactions responsive to the client profile being re-enrolled with the blockchain.

13. The apparatus of claim 8 , wherein the processor is further configured to determine that blockchain data stored in the blockchain has reached the maximum data size threshold.

14. The apparatus of claim 8 , wherein the processor is further configured to:
store blockchain transactions of the blockchain in a priority queue with the least frequently used transactions at respective topmost positions of the priority queue; and
when the blockchain reaches the maximum data size threshold, archive the least frequently accessed blockchain transactions at the respective topmost positions of the priority queue.

15. A non-transitory computer readable storage medium configured to store at least one instruction that when executed by a processor causes the processor to perform:
identifying at least one transaction, of one or more transactions on a blockchain, as eligible for archiving based on the blockchain reaching a maximum data size threshold;
identifying, on the blockchain, at least one transaction that is related to a portion of the identified at least one transaction;
compressing the at least one transaction and the at least one related transaction; and
archiving the at least one transaction and the at least one related transaction.

16. The non-transitory computer readable storage medium of claim 15 , configured to store at least one instruction that when executed by the processor causes the processor to perform determining the maximum data size threshold of the blockchain.

17. The non-transitory computer readable storage medium of claim 15 , configured to store at least one instruction that when executed by the processor causes the processor to perform:
identifying a client profile has withdrawn enrollment from the blockchain; and
identifying a plurality of client profile transactions logged in the blockchain corresponding to the client profile.

18. The non-transitory computer readable storage medium of claim 17 , configured to store at least one instruction that when executed by the processor causes the processor to perform:
archiving the plurality of client profile transactions corresponding to the client profile.

19. The non-transitory computer readable storage medium of claim 18 , configured to store at least one instruction that when executed by the processor causes the processor to perform:
identifying the client profile has re-enrolled with the blockchain;
identifying the plurality of client profile transactions corresponding to the client profile; and
restoring the plurality of client profile transactions responsive to the client profile being re-enrolled with the blockchain.

20. The non-transitory computer readable storage medium of claim 15 , configured to store at least one instruction that when executed by the processor causes the processor to perform:
storing blockchain transactions of the blockchain in a priority queue with the least frequently used transactions at respective topmost positions of the priority queue; and
when the blockchain reaches the maximum data size threshold, archiving the least frequently accessed blockchain transactions at the respective topmost positions of the priority queue.

Assignees

• IBM

Inventors

• Childress Rhonda L
• Gupta Rahul
• Kumhyr David B
• Mukherjee Maharaj

Classifications

• H04L9/50

  using hash chains, e.g. blockchains or hash trees · CPC title

• G06F16/2219

  Large Object storage; Management thereof · CPC title

• G06F16/217 Primary

  Database tuning (G06F16/2282 takes precedence; database performance monitoring G06F11/3409) · CPC title

• H04L9/3297

  involving time stamps, e.g. generation of time stamps · CPC title

• G06F16/275

  Synchronous replication · CPC title