Blockchain Transaction Data Deletion Method
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing blockchain systems do not have mechanisms to efficiently manage and delete unused data, leading to blockchain enlargement, increased memory consumption, and operational costs.
Innovation Solution
A control method that determines and deletes transaction data from the blockchain if it has not been used for a predetermined period, ensuring the integrity of the blockchain by using headers to verify its validity without being considered tampering.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If transaction data is permanently stored on the blockchain, then data integrity and security are maintained, but blockchain size increases and memory consumption increases
Solution Approach 1:
The system performs preliminary identification of unused transaction data before deletion. It monitors transaction data to determine if it has been accessed or used for a predetermined period, and only then proceeds with deletion. This preliminary action ensures that important data is preserved while unnecessary data is removed, maintaining integrity while reducing size.
Solution Approach 2:
The system discards transaction data that has become obsolete by not being used for a predetermined period. The deletion is performed selectively based on usage patterns, recovering storage space while preserving data that remains relevant. This principle allows the blockchain to shed unnecessary data while maintaining its essential integrity.
2Use of energy by stationary object
If unused transaction data is deleted from the blockchain, then memory consumption and operational costs are reduced, but blockchain integrity may be compromised
Solution Approach 1:
The system implements a feedback mechanism by continuously monitoring whether transaction data is being used or accessed. Based on this feedback, it determines whether the data should be retained or deleted. Transaction data that has not been used for a predetermined period is identified as candidate for deletion, while actively used data is preserved. This feedback-driven approach ensures integrity is maintained while enabling safe deletion of obsolete data.
Solution Approach 2:
Before deleting transaction data, the system performs preliminary verification to ensure the data is indeed unused and safe to remove. It checks whether the data has been accessed or used within the predetermined period, and only proceeds with deletion when this condition is met. This preliminary action prevents accidental deletion of important data, thereby maintaining blockchain integrity.
3Loss of information
If blockchain size increases due to permanent storage of all transaction data, then complete historical record is maintained, but operational costs increase
Solution Approach 1:
The system changes the retention parameter of transaction data from permanent to time-based. It introduces a predetermined period as a threshold parameter, beyond which unused transaction data is eligible for deletion. This parameter change allows the system to balance historical record completeness with operational efficiency, maintaining records only as long as they remain relevant while reducing long-term storage costs.
Solution Approach 2:
The system discards transaction data that has exceeded the predetermined retention period and shows no usage patterns. By selectively removing this obsolete data, the system recovers storage space and reduces operational costs associated with maintaining the blockchain, while preserving the essential historical record of actively used transactions.
Data Source
AI summary
A control method according to the present disclosure includes: determining the presence or absence of transaction data related to a first target that has not been used for a predetermined period among targets each being transaction data stored in a blockchain; and deleting the transaction data related to the first target from the blockchain based on a determination result indicating that the transaction data related to the first target is present.