Blockchain Risk Score Module for Anomalous Transaction Prevention

Resolve Bottlenecks,
Find Innovative SolutionsGenerate Solutions

Solution Overview

Problem

Centralized databases face issues such as single points of failure, dependency on network connectivity, limited data access, and difficulty in retrieving lost data due to lack of redundancy, necessitating a solution for enhanced reliability and access control.

Innovation Solution

Implementing a decentralized database system using a blockchain network with a risk score module to detect and prevent anomalous transactions, ensuring data integrity and redundancy through a distributed ledger and consensus protocols.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Ease of operation

If a centralized database is used, then data management and control are simplified, but the system has a single point of failure and limited data access

Engineering Contradiction:

Improvedata management and controlVSAvoidsingle point of failure

Core Design Contradiction:

Ease of operationVSReliability

Solution Approach 1:

The patent segments the centralized database into multiple distributed nodes across a network. Each node maintains a copy of the database, eliminating the single point of failure. The system divides the database functionality across multiple independent locations while maintaining data consistency through distributed consensus mechanisms.

Inventive Principle:

Principle #1Segmentation

2Quantity of substance

If a centralized database is used, then data redundancy is minimized, but data loss is difficult to retrieve

Engineering Contradiction:

Improvedata redundancyVSAvoiddata retrieval after loss

Core Design Contradiction:

Quantity of substanceVSReliability

Solution Approach 1:

The patent creates multiple copies of the database across distributed nodes in the network. Each node stores redundant copies of the data, ensuring that if one node fails or data is lost, the information can be retrieved from other nodes. This copying mechanism provides both redundancy and fault tolerance.

Inventive Principle:

Principle #26Copying

3Reliability

If a centralized database is used, then network connectivity dependency is reduced, but access time increases with slower connections

Engineering Contradiction:

Improvenetwork connectivity dependencyVSAvoiddatabase access time

Core Design Contradiction:

ReliabilityVSLoss of time

Solution Approach 1:

The patent transitions from a single-dimensional centralized access model to a multi-dimensional distributed access model. Users can access data from multiple nodes simultaneously, adding spatial dimensions to data access. This allows parallel access paths and reduces dependency on any single network connection, thereby reducing access time.

Inventive Principle:

Principle #17Another dimension (Dimensionality change)

4Ease of operation

If a centralized database is used, then security control is simplified, but anomalous transactions are harder to detect and prevent

Engineering Contradiction:

Improvesecurity controlVSAvoidanomalous transaction detection

Core Design Contradiction:

Ease of operationVSDifficulty of detecting and measuring

Solution Approach 1:

The patent implements feedback mechanisms where each distributed node monitors and reports transaction activities to the network. The system continuously receives feedback about transaction patterns, validates transactions against consensus rules, and can detect anomalous behavior through collective analysis across multiple nodes. This distributed feedback system enhances security while maintaining operational simplicity.

Inventive Principle:

Principle #23Feedback

Data Source

PatentUS11809896B2Anomalous transaction commitment prevention for database

Publication Date: 2023.11.07 INTERNATIONAL BUSINESS MACHINE CORPORATION

AI summary

An example operation may include one or more of receiving, by a risk score module, a blockchain transaction proposal, obtaining transaction proposal data, obtaining external data, computing a risk score from the transaction proposal data and the external data, comparing the risk score to a risk score threshold, providing a commitment decision, based on the comparison, and one of committing or rejecting an endorsed transaction corresponding to the transaction proposal.