Blockchain Data Segmentation for Security and Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain systems for cryptocurrency transactions lack sufficient security measures, as they rely on nodes that make transactions public, making them vulnerable to exploitation, and require significant computational power for Proof of Work, leading to high energy consumption.

Innovation Solution

A data management system comprising a colony server and a center server that divides data into partial and body data, where the center server encrypts and stores partial data as a blockchain block, updates hash values, and ensures the body data has no value on its own, even if leaked, thereby enhancing security and reducing computational power requirements.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all transaction data is stored publicly on the blockchain, then transparency and fairness of transactions are ensured, but security vulnerability increases and malicious exploitation becomes possible

Engineering Contradiction:
Improvetransaction fairnessVSAvoidsecurity vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent divides transaction data into two segments: hash values (stored publicly on blockchain) and actual transaction contents (stored privately on server). This segmentation allows the system to maintain transaction fairness through public hash verification while protecting transaction contents from public exposure, thereby reducing security vulnerabilities and preventing malicious exploitation.

Inventive Principle:
Principle #1Segmentation

2Reliability

If Proof of Work is used to guarantee transaction fairness, then transaction security is improved, but computational power requirements and energy consumption increase significantly

Engineering Contradiction:
Improvetransaction securityVSAvoidcomputational power consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent extracts the computational verification function from the blockchain network and relocates it to a centralized server. Instead of requiring all nodes to perform Proof of Work calculations, the server generates and verifies transaction hashes centrally, then stores only the hash values on the blockchain. This dramatically reduces computational power requirements and energy consumption while maintaining transaction security through hash verification.

Inventive Principle:
Principle #2Taking out (Extraction)

3Reliability

If complete transaction data is stored on the blockchain, then data integrity is maintained, but storage requirements and system complexity increase

Engineering Contradiction:
Improvedata integrityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent segments data storage between two locations: hash values are stored on the blockchain for public verification and integrity assurance, while complete transaction contents are stored on a private server. This segmentation maintains data integrity through cryptographic hash verification while significantly reducing blockchain storage requirements and simplifying the overall system architecture.

Inventive Principle:
Principle #1Segmentation

4Reliability

If hash values are updated frequently to enhance security, then security against unauthorized access is improved, but computational burden and energy consumption increase

Engineering Contradiction:
Improvesecurity against unauthorized accessVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent implements periodic hash value updates at predetermined intervals rather than continuous updates. This periodic action maintains security against unauthorized access by regularly refreshing transaction data while significantly reducing computational burden and energy consumption compared to continuous update mechanisms.

Inventive Principle:
Principle #19Periodic action

Data Source

PatentUS12200140B2Data management system
Publication Date: 2025.01.14 SYSNA INC
  • US12200140B2 patent drawing
  • US12200140B2 patent drawing
  • US12200140B2 patent drawing

AI summary

In a blockchain, contents of communication of electronic data are basically made public, and a malicious person can find system vulnerability of the blockchain. Leak of secret information or the like to an unintended third party through unauthorized access or the like by exploiting the vulnerability and cause is actually possible. Thus, it cannot be said that sufficient security measures are taken. In the present invention, a colony server stores partial data containing data of a predetermined size from a beginning of data to be managed received from a terminal, and a center server stores body data containing data of the predetermined size +1 and thereafter. Thus, the data to be managed is managed in a divided manner. Also, even if the body data is leaked from the colony server through unauthorized access or the like, the body data is merely part of the data to be managed, and has no value on its own. Thus, the present invention provides a system and the like for achieving robust security against unauthorized access.