Block Verification Device for Private Database Consensus

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

In blockchain systems, especially those using quorum architecture, nodes cannot verify state transitions of private databases shared among specific nodes, leading to challenges in forming consensus among all nodes, resulting in data bloating and security issues.

Innovation Solution

A block verification device and method that includes a private database shared within a group, a communication unit, a transaction processing unit, and a block processing unit, which generates and transmits a proposal including a digest of the private database and private dataset, allowing consensus formation among block verification devices within the same group.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If all nodes store and verify all private database states, then consensus verification is improved, but data bloating and storage overhead worsen

Engineering Contradiction:

Improveconsensus verificationVSAvoiddata storage volume

Core Design Contradiction:

ReliabilityVSQuantity of substance

Solution Approach 1:

The system segments the blockchain network into multiple groups, where each group maintains its own private database. Nodes only store and verify data relevant to their group, rather than all private database states across the entire network. This segmentation allows consensus verification within groups while reducing overall data storage requirements.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Each node is assigned specific verification responsibilities based on its group membership. Nodes verify private database states locally within their own group rather than globally across all groups. This local quality approach enables targeted consensus verification while preventing data bloating by limiting each node's storage to only its group's private data.

Inventive Principle:

Principle #3Local quality

2Loss of information

If private database states are shared among all nodes, then transparency and verification are improved, but security and data privacy worsen

Engineering Contradiction:

Improveverification transparencyVSAvoiddata privacy breach

Core Design Contradiction:

Loss of informationVSObject-affected harmful factors

Solution Approach 1:

The system divides the network into multiple groups with separate private databases. Each group's private data is only shared among members of that group, not across the entire network. This segmentation maintains verification transparency within groups while protecting data privacy by limiting exposure to authorized participants only.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Data sharing and verification are made local to each group rather than global. Each node verifies and shares private database states only with other nodes in its own group. This local quality approach ensures transparency for group members while preventing unauthorized access to other groups' private data, thus maintaining security and privacy.

Inventive Principle:

Principle #3Local quality

3Reliability

If each group maintains complete consensus verification capability, then autonomy and reliability are improved, but system complexity worsens

Engineering Contradiction:

Improvegroup autonomyVSAvoidsystem architecture

Core Design Contradiction:

ReliabilityVSDevice complexity

Solution Approach 1:

The system segments consensus verification into independent group-level processes. Each group maintains its own private database and performs consensus verification autonomously within the group. This segmentation provides group autonomy and reliability while managing complexity by creating modular, independent verification units rather than a single complex global system.

Inventive Principle:

Principle #1Segmentation

Solution Approach 2:

Consensus verification is performed preliminarily at the group level before potential global aggregation. Each group completes its own consensus verification process independently, establishing reliable group-level states. This preliminary action approach simplifies the overall system by handling verification locally first, reducing the complexity of coordinating global consensus across all groups.

Inventive Principle:

Principle #10Preliminary action

Data Source

PatentUS11372847B2Block verification device, block verification method, and program

Publication Date: 2022.06.28 NIPPON TELEGRAPH & TELEPHONE CORP

AI summary

A consensus is formed for a private database shared within a group. A block verification device includes: a private database shared within a group; a communication unit receiving a list of transactions from an overall leader device; a transaction processing unit executing the transactions identified based on the list and outputting the execution results; and a block processing unit generating a proposal including a list, a digest of the private database after execution of the transactions, and a private dataset included in the transactions. The communication unit transmits the proposal to another block verification device belonging to the same group, and transmits the list, the digest of the private database, and the digest of the private dataset to all the other block verification devices when it is determined that a consensus for the proposal is formed.