Layered Distributed Database with Blockchain State Recording

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing blockchain systems lack an efficient mechanism to record and manage changes in state across a distributed database, particularly in scenarios where complex data such as electronic documents or audio/video data are stored, and there is a need for a robust solution that ensures data integrity and immutability.

Innovation Solution

Implementing a distributed database across multiple nodes of a blockchain network, where changes in state are recorded on the blockchain, utilizing a layered network architecture with nodes performing roles such as forwarding, mining, and storage, and employing proof-of-work to ensure data integrity and immutability.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If blockchain is used to record changes in state to the database, then data integrity and immutability are ensured, but the system complexity and computational overhead increase

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

Solution Approach 1:

The system divides the network into multiple node types (forwarding nodes, mining nodes, storage nodes) with specialized functions. This segmentation allows each node to handle specific tasks efficiently, reducing individual node complexity while maintaining overall system reliability through distributed consensus.

Inventive Principle:
Principle #1Segmentation

Solution Approach 2:

The patent introduces a state change recording mechanism that acts as an intermediary layer between the distributed database and the blockchain. This intermediary records state changes efficiently on the blockchain without requiring every node to process all database operations, thereby reducing computational overhead while maintaining data integrity.

Inventive Principle:
Principle #24Intermediary (Mediator)

2Reliability

If proof-of-work mining is implemented, then data immutability is ensured, but the energy consumption and processing time increase

Engineering Contradiction:
Improvedata immutabilityVSAvoidenergy consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The system implements proof-of-work mining selectively for state change records rather than for every transaction or data operation. This partial application of mining ensures immutability for critical state changes while avoiding the excessive energy consumption that would result from mining all operations.

Inventive Principle:
Principle #16Partial or excessive action

Solution Approach 2:

Different nodes perform different functions: forwarding nodes propagate transactions without mining, storage nodes maintain database copies, and mining nodes perform proof-of-work. This local specialization of quality allows the system to achieve immutability where needed while minimizing energy consumption overall.

Inventive Principle:
Principle #3Local quality

3Adaptability or versatility

If multiple node roles are assigned, then system functionality is enhanced, but the operational complexity increases

Engineering Contradiction:
Improvesystem functionalityVSAvoidoperational complexity
Core Design Contradiction:
Adaptability or versatilityVSEase of operation

Solution Approach 1:

The system segments node functionality into distinct roles (forwarding, mining, storage) that can be independently configured and managed. This segmentation enhances versatility by allowing different nodes to perform different functions while simplifying operation through clear role definitions and standardized protocols for each node type.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentEP4097917B1Distributed database
Publication Date: 2026.03.25 NCHAIN LICENSING AG
  • EP4097917B1 patent drawingFigure 1
  • EP4097917B1 patent drawingFigure 2
  • EP4097917B1 patent drawingFigure 3

AI summary

A method performed in a layered network. The layered network comprises a core layer comprising one or more core nodes, one or more intermediate layers each comprising one or more intermediate layer nodes, and one or more outer layers each comprising one or more outer layer nodes. Each core node is a node of a blockchain network. At least some intermediate layer nodes are database nodes. At least some outer layer nodes are client nodes. Each database node stores at least part of a distributed database. The method comprises, at a database node: receiving one or more update requests from one or more client nodes requesting to update a database entry; and for each update request, applying the update locally and/or forwarding to another database node. At least one transaction including an indication of the one or more update requests is also recorded on a blockchain of the blockchain network.