Decentralized Graph Database Using Masternode Sharding

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current graph database and distributed ledger technologies face issues such as lack of robust security, data and knowledge sharing concerns, high costs, and inefficient data accessibility, particularly with centralized architectures that are not scalable for large data storage and querying.

Innovation Solution

A decentralized and distributed graph database system utilizing graph computing and decentralized ledger technologies, where users can outsource storage and computation to a network of peers, ensuring secure, verifiable, and efficient data management with masternodes that rent out storage and computational power, and implement encryption for privacy.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If graph database is replicated across multiple datacenters, then data availability is improved, but security is worsened due to single point of failure at the hosting company

Engineering Contradiction:
Improvedata availabilityVSAvoidsecurity vulnerability
Core Design Contradiction:
ReliabilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the centralized graph database into distributed shards across multiple independent nodes in a peer-to-peer network. Each node stores only a portion of the graph data, eliminating the single point of failure at any single datacenter while maintaining data availability through distributed replication. This segmentation transforms the architectural model from centralized multi-datacenter to decentralized peer-to-peer.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces cryptographic hashing and Merkle trees as intermediaries between the distributed nodes and the graph data. These cryptographic mechanisms enable secure verification of data integrity without requiring trust in any single node or hosting provider, thus improving security while maintaining distributed availability.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Ease of operation

If graph database is stored in centralized cloud services, then ease of operation is improved, but cost is worsened due to lack of price transparency and sharing difficulties

Engineering Contradiction:
Improvedata storage convenienceVSAvoidstorage cost
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The patent enables nodes in the peer-to-peer network to self-organize and self-manage the distribution of graph data shards. Each node independently validates and stores data portions, eliminating the need for centralized cloud service management while reducing costs through resource sharing among participants. The system automatically handles data placement, replication, and retrieval without requiring expensive centralized infrastructure.

Inventive Principle:
Principle #25Self-service

3Reliability

If distributed ledger technology is used for data storage, then security is improved, but data accessibility is worsened due to difficulty in querying and manipulating data

Engineering Contradiction:
Improvedata securityVSAvoiddata accessibility
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The patent applies different data structures and access methods to different portions of the distributed ledger. Graph data is organized with local indexing and adjacency lists at each node, enabling efficient local queries while maintaining the security benefits of distributed storage. This local optimization allows fast graph traversals and queries without requiring full data retrieval from all nodes.

Inventive Principle:
Principle #3Local quality

Solution Approach 2:

The patent performs preliminary data organization and indexing at each node before queries are executed. Graph data is pre-processed and structured with efficient lookup mechanisms in place, allowing nodes to quickly respond to queries without requiring complex real-time coordination across the entire network. This preliminary structuring maintains security while enabling accessible querying.

Inventive Principle:
Principle #10Preliminary action

4Reliability

If blockchain is used for immutable data storage, then reliability is improved, but productivity is worsened due to high storage costs and irregular block creation

Engineering Contradiction:
Improvedata immutabilityVSAvoiddata storage efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent segments the immutable ledger requirements from the graph data storage. Only critical metadata and verification information are stored immutably on the distributed ledger, while the bulk of graph data is stored efficiently in the peer-to-peer network with cryptographic proofs for verification. This segmentation achieves immutability where needed while maintaining storage efficiency for the majority of data.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent changes the storage parameters from blockchain's fixed block structure to a flexible peer-to-peer shard structure. Data is divided into可变-sized shards that can be distributed and updated efficiently without requiring expensive block reorganizations. This parameter change maintains the immutability guarantee through cryptographic hashing while dramatically improving storage efficiency and accessibility.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11126659B2System and method for providing a graph protocol for forming a decentralized and distributed graph database
Publication Date: 2021.09.21 GRAPHEN INC
  • US11126659B2 patent drawing
  • US11126659B2 patent drawing
  • US11126659B2 patent drawing

AI summary

A system for providing a graph protocol for forming a decentralized and distributed graph database is disclosed. The system involves receiving, from a device, a bid request to generate a graph on a graph protocol network via the graph protocol. A plurality of masternodes in the system may transmit ask requests associated with providing storage and computation power to service the bid request. If the system determines that the requirements of the bid request match or correlate with the requirements of the ask request, the system may select any masternodes having matching or correlating ask requests to service the ask request. The system may then arrange the masternodes into a unique artificially-intelligent router of the graph protocol network. The system may then proceed to generate the graph on the graph protocol network by utilizing the masternodes of the router and may process any queries associated with the generated graph.