Blockchain Malicious Peer Detection via Hash Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, dependency on network connectivity, limited access, and data redundancy, leading to potential data loss and system bottlenecks, necessitating a solution for enhanced reliability and accessibility.

Innovation Solution

A blockchain network is employed, featuring a decentralized storage system with multiple nodes that communicate to maintain a distributed ledger, allowing for consensus-based validation and immutability of data, thereby detecting malicious peers and preventing chain forks through cryptographic hashing and endorsement protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used, then ease of management and control is improved, but reliability deteriorates due to single point of failure

Engineering Contradiction:
Improveease of managementVSAvoidreliability
Core Design Contradiction:
Ease of operationVSReliability

Solution Approach 1:

The patent divides the centralized database into multiple distributed nodes across a blockchain network. Each node maintains a copy of the ledger, eliminating the single point of failure while preserving management capabilities through consensus protocols.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent creates multiple identical copies of the database ledger distributed across numerous nodes. These copies ensure that if one node fails, the data remains accessible and intact on other nodes, thereby improving reliability while maintaining centralized-like consistency through consensus mechanisms.

Inventive Principle:
Principle #26Copying

2Quantity of substance

If a centralized database is used, then data redundancy is minimized, but loss of information worsens due to limited access and single location storage

Engineering Contradiction:
Improvedata redundancyVSAvoiddata loss
Core Design Contradiction:
Quantity of substanceVSLoss of information

Solution Approach 1:

The patent segments the database into distributed copies across multiple nodes. Each node holds a complete or partial copy of the ledger, creating controlled redundancy that prevents data loss while maintaining data integrity through cryptographic hashing and consensus validation.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the parameter of data storage from centralized single-location to distributed multi-location. This transformation creates redundancy as a protective measure, where multiple copies ensure data availability and prevent information loss even when some nodes fail or are compromised.

Inventive Principle:
Principle #35Parameter changes

3Productivity

If a centralized database is used, then network dependency is reduced, but productivity deteriorates due to bottlenecks at single location

Engineering Contradiction:
Improveprocessing throughputVSAvoidaccess time
Core Design Contradiction:
ProductivityVSLoss of time

Solution Approach 1:

The patent segments the database processing workload across multiple distributed nodes. Each node can independently process transactions and validate blocks, eliminating the bottleneck at a single location and increasing overall system throughput while reducing access time through parallel processing.

Inventive Principle:
Principle #1Segmentation

4Reliability

If a centralized database is used, then access control is simplified, but reliability worsens due to vulnerability to malicious activities

Engineering Contradiction:
ImprovesecurityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements feedback mechanisms through consensus protocols where nodes continuously verify each other's operations. This distributed verification system detects and prevents malicious activities by requiring majority agreement, thereby improving security while managing complexity through standardized protocol rules.

Inventive Principle:
Principle #23Feedback

Data Source

PatentUS11949691B2Malicious peer identification
Publication Date: 2024.04.02 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US11949691B2 patent drawing
  • US11949691B2 patent drawing
  • US11949691B2 patent drawing

AI summary

An example operation may include one or more of receiving, by each of one or more peripheral peers of a blockchain network, a new block from an orderer peer, calculating a hash of the new block, determining the calculated hash is different than hashes from a majority of peripheral peers, determining that one or more blocks that correspond to the different hashes from the majority of peripheral peers are different from the new block, and in response ceasing committing blocks to the blockchain network.