Blockchain Data Archiving via Target State Backup
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
As blockchain systems operate over time, the increasing storage space required by node data leads to slow response times or system breakdowns, and existing data archiving methods face challenges in precision and efficiency due to conflicts between snapshot operations and ongoing transactions.
Innovation Solution
A blockchain data archiving method that involves synchronizing data with a consensus node, determining target state data, generating snapshots, and archiving data based on endorsement information, ensuring accurate and efficient data archiving by avoiding conflicts with ongoing transactions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If blockchain data is archived by taking snapshots of state data, then data archiving efficiency is improved, but data precision deteriorates due to conflicts with ongoing transactions
Solution Approach 1:
The system performs preliminary actions by identifying and backing up target state data that will be modified by upcoming transactions before the transactions execute. This allows the snapshot to capture data at a consistent point in time without conflicting with ongoing transactions, thereby maintaining both archiving efficiency and data precision.
Solution Approach 2:
The system introduces an intermediary mechanism (backup and identification process) between the snapshot operation and the original state data. By creating a backup of target state data and using it for snapshot generation, the system mediates the conflict between reading data for archiving and writing data for transactions, ensuring both operations can proceed without compromising precision or efficiency.
2Measurement precision
If all state data is archived to ensure completeness, then data precision is improved, but storage space consumption increases
Solution Approach 1:
The system extracts only the necessary target state data from the complete state data for archiving purposes. By identifying and backing up only the specific state data that is relevant to ongoing transactions, the system achieves data completeness for archiving without the need to store all state data, thereby reducing storage space consumption while maintaining archiving precision.
Solution Approach 2:
The system applies local quality by differentiating between target state data (that needs to be archived) and non-target state data (that does not need to be archived). By applying the archiving operation selectively to only the necessary portions of state data, the system maintains data completeness where needed while avoiding unnecessary storage consumption in other areas.
3Ease of operation
If blockchain nodes continue to operate during data archiving, then system availability is maintained, but archiving reliability deteriorates due to transaction conflicts
Solution Approach 1:
The system uses an intermediary backup mechanism that allows snapshot operations to proceed without interfering with ongoing transactions. By creating a backup of target state data before transactions execute and using this backup for snapshot generation, the system mediates between the need for continuous operation and the need for reliable archiving, ensuring both system availability and archiving reliability are maintained.
Solution Approach 2:
The system performs preliminary backup of target state data before transactions are executed, allowing the snapshot to be generated from this backup rather than from live data. This preliminary action ensures that the archiving process does not conflict with ongoing transactions, maintaining both system availability during operation and reliability of the archived data.
Data Source
AI summary
This application provides methods, apparatus, electronic devices, and computer-readable storage medium for archiving blockchain data. One method includes synchronizing, by a first committing node, blockchain data with a consensus node, and determining a synchronization block height of the synchronized blockchain data, the synchronized blockchain data comprising state data; determining target state data required by a current transaction in the state data, and backing up the target state data; generating a state data snapshot of the synchronization block height according to the backed-up target state data, and transmitting the state data snapshot, the synchronization block height, and signature information of the first committing node to a second committing node as archiving point information; receiving endorsement information of the second committing node for the archiving point information; and archiving the synchronized blockchain data according to the endorsement information and the archiving point information.