Blockchain Node Segmentation for Large Data Storage
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current blockchain technologies face challenges in managing large and sensitive data, such as GDPR-controlled data, due to limitations in data distribution and sensitivity handling, leading to issues with network bandwidth and storage resources, and existing solutions like 'data off the chain' approaches do not effectively address data integrity and sensitivity.
Innovation Solution
A computer-implemented method and system that validates large data for upload to a blockchain, utilizing a distributed architecture with block store nodes, verifier nodes, and backup nodes, where roles are assigned based on data sensitivity, allowing only metadata to be stored on verifier nodes and backup nodes to participate in data recovery, optimizing storage and ensuring data integrity.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If large data is distributed to all nodes in the blockchain, then data integrity and trust are maintained, but network bandwidth and server storage resources become bottlenecks
Solution Approach 1:
The patent segments the blockchain network into three distinct node types with differentiated functions: block store nodes (full nodes) that maintain complete blockchain data, block verifier nodes that verify block validity without storing all data, and block backup nodes that provide backup capabilities. This segmentation allows data to be distributed only to necessary nodes, reducing overall network bandwidth consumption and storage requirements while maintaining data integrity through the coordinated operation of these specialized node types.
2Quantity of substance
If data is stored off the chain using tokens, then storage space is reduced, but data sensitivity and integrity cannot be effectively addressed
Solution Approach 1:
The patent introduces an intermediary mechanism where block backup nodes serve as mediators between block store nodes and block verifier nodes. These backup nodes store redundant copies of blockchain data and can restore data if corruption or loss occurs. This intermediary backup system maintains data integrity and sensitivity without requiring all nodes to store complete data, thus optimizing storage space while ensuring reliability through the backup restoration capability.
3Reliability
If all nodes store complete blockchain data, then data authenticity is ensured, but thin nodes like mobile devices cannot participate
Solution Approach 1:
The patent applies local quality by assigning different data storage and processing capabilities to different node types based on their specific functions and resource constraints. Block verifier nodes, which can include thin nodes like mobile devices, store only essential verification data and rely on block store nodes for complete blockchain data. This localized quality approach allows thin nodes to participate in the blockchain network with limited resources while still contributing to data authenticity through their verification functions.
4Productivity
If data is distributed to all nodes, then data availability is improved, but GDPR compliance and data sensitivity control become difficult
Solution Approach 1:
The patent introduces dynamics by implementing a configurable node role assignment system where nodes can be dynamically assigned to different types (block store, block verifier, or block backup) based on their capabilities and the specific requirements of the blockchain network. This dynamic role assignment allows the system to adapt data distribution strategies to comply with GDPR and sensitivity requirements while maintaining data availability through the coordinated operation of different node types with appropriate data access permissions.
Data Source
AI summary
A computer implemented method for managing large and sensitive data in a blockchain includes determining a master block store node from a plurality of block store nodes to add large and sensitive data to the blockchain after validation, and generating a block including the large and sensitive data that is validated and its metadata. If the block store nodes, a plurality of block verifier nodes and a plurality of block backup nodes of the blockchain are in synchronization, the method adds, using the master block store node, the block to its chain and generates a synchronization request to the block store nodes, the block verifier nodes and the block backup nodes of the blockchain. Based on assigned roles, the method performs enabling the block store nodes to store the block, enabling the block verifier nodes to store only the metadata, and enabling the block backup nodes to store the block.