Random Oracle Consensus for Decentralized Database Security

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Decentralized databases, such as blockchain networks, face challenges with consensus mechanisms that either slow down transaction processing due to proof-of-work requirements or expose networks to control by malicious actors and consensus failures.

Innovation Solution

Implementing a system that uses external validity multi-valued Byzantine agreement (MVBA) and random oracles in open networks to ensure consistent updates to decentralized databases without exposing the network to malicious control, allowing for efficient and reliable validation and ordering of transactions across nodes.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If proof-of-work requirements are used in consensus mechanism, then network security and prevention of malicious control are improved, but transaction processing speed and resource efficiency deteriorate

Engineering Contradiction:
Improvenetwork securityVSAvoidtransaction processing speed
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent changes the fundamental parameter of consensus from proof-of-work computational difficulty to random oracle-based probabilistic agreement. Nodes use random oracle queries to deterministically agree on transaction ordering without intensive computation, transforming the consensus mechanism from resource-intensive to efficient while maintaining security through cryptographic randomness.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent replaces the mechanical proof-of-work system (computational puzzles requiring brute-force solving) with a random oracle system that uses cryptographic hashing and probabilistic sampling. This substitution eliminates the need for intensive computational mechanics while achieving the same security goal of preventing malicious control through deterministic randomness.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

2Reliability

If proof-of-work requirements are used in consensus mechanism, then network security against malicious actors is improved, but resource consumption increases

Engineering Contradiction:
Improvenetwork securityVSAvoidcomputational resource consumption
Core Design Contradiction:
ReliabilityVSUse of energy by moving object

Solution Approach 1:

The patent fundamentally changes the resource consumption parameter from computational work (CPU/GPU power) to minimal cryptographic operations. Random oracle queries require only standard hash computations, reducing energy consumption from proof-of-work intensive levels to routine transaction validation levels while preserving security through cryptographic strength.

Inventive Principle:
Principle #35Parameter changes

Solution Approach 2:

The patent substitutes the energy-intensive mechanical proof-of-work system with a lightweight random oracle system based on cryptographic hashing. This replacement eliminates the need for sustained high-power computation while maintaining security through the computational infeasibility of predicting random oracle outputs, thereby drastically reducing energy consumption.

Inventive Principle:
Principle #28Mechanics substitution (Replace mechanical system)

3Productivity

If consensus mechanism without proof-of-work is used, then transaction processing speed is improved, but network exposure to malicious control increases

Engineering Contradiction:
Improvetransaction processing speedVSAvoidnetwork security
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent introduces random oracles as an intermediary between nodes to achieve consensus. The random oracle acts as a trusted mediator that provides deterministic randomness, allowing nodes to agree on transaction ordering without direct negotiation or intensive computation. This intermediary enables fast consensus while preventing malicious control through cryptographic security.

Inventive Principle:
Principle #24Intermediary (Mediator)

Solution Approach 2:

The patent changes the security parameter from relying on computational dominance (proof-of-work) to relying on cryptographic randomness (random oracles). This parameter change allows nodes to achieve consensus through probabilistic agreement rather than computational races, enabling fast transaction processing while maintaining security through the unpredictability and determinism of random oracle outputs.

Inventive Principle:
Principle #35Parameter changes

4Productivity

If consensus mechanism without proof-of-work is used, then resource efficiency is improved, but network may get stuck requiring manual intervention

Engineering Contradiction:
Improveresource efficiencyVSAvoidconsensus reliability
Core Design Contradiction:
ProductivityVSReliability

Solution Approach 1:

The patent implements feedback mechanisms where nodes continuously query random oracles and adjust their transaction ordering based on oracle responses. This feedback loop ensures that consensus progresses deterministically without getting stuck, as nodes can always reach agreement by following the random oracle's guidance, eliminating the need for manual intervention while maintaining resource efficiency.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent changes the consensus reliability parameter from depending on computational dominance to depending on probabilistic agreement through random oracles. This parameter change ensures that consensus can always progress as long as nodes follow the random oracle protocol, preventing consensus failures and manual intervention requirements while maintaining high resource efficiency.

Inventive Principle:
Principle #35Parameter changes

Data Source

PatentUS11240010B2Random oracles in open networks
Publication Date: 2022.02.01 RIPPLE LABS INC
  • US11240010B2 patent drawing
  • US11240010B2 patent drawing
  • US11240010B2 patent drawing

AI summary

Systems and techniques are provided for random oracles in open networks. A node computing device of an open network may choose a random secret. The random secret may be a numeric or alphanumeric value. The node computing device may distribute shares of the random secret to node computing devices that are members of essential subsets for the node computing device. The node computing device may receive a share of a random secret from a second node computing device. The node computing device may be a member of an essential subset of the second node computing device. The node computing device may sign a deterministic seed message using the share of the random secret received from the second node computing device to generate a signature share. The node computing device may reveal the signature share and may receive a random value in response.