Smart Contract Execution Integrity via Multi-Platform Consensus

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Existing smart contract systems lack assurance that the third-party executor is neutral and cannot be influenced or tampered with, leading to potential collusion and altered results, which undermines the trust and integrity of the agreement execution.

Innovation Solution

Implementing a system where multiple platforms execute a copy of the software that includes a smart contract, with results compared to determine a matching outcome that meets or exceeds a threshold, ensuring that the agreed-upon output is accepted only if a majority or predetermined number of platforms concur, thereby reducing the likelihood of successful collusion.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a single third-party platform executes the smart contract software, then the execution process is simple and fast, but the system lacks assurance of neutrality and is vulnerable to collusion and tampering

Engineering Contradiction:
Improvetrustworthiness of executionVSAvoidnumber of platforms
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent divides the execution of smart contract software into multiple independent instances across different platforms. Instead of relying on a single executor, the system segments the execution task and distributes it to multiple platforms, each running identical software with the same input data. This segmentation ensures that no single platform can manipulate the result, as all platforms must produce matching outputs for the execution to be considered valid.

Inventive Principle:
Principle #1Segmentation

2Reliability

If multiple platforms execute copies of the software to ensure neutrality, then the trustworthiness increases, but the execution time and system complexity increase

Engineering Contradiction:
Improveintegrity of executionVSAvoidexecution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent performs preliminary verification by having multiple platforms execute the identical software instance with the same input data before finalizing the result. This preliminary parallel execution allows the system to compare outputs and verify consistency across all platforms. By conducting this verification in parallel rather than sequentially, the system minimizes time loss while ensuring integrity.

Inventive Principle:
Principle #10Preliminary action

3Object-affected harmful factors

If multiple platforms are used to prevent collusion, then the number of entities required for successful manipulation increases, but the system complexity and coordination requirements increase

Engineering Contradiction:
Improveresistance to collusionVSAvoidsystem architecture
Core Design Contradiction:
Object-affected harmful factorsVSDevice complexity

Solution Approach 1:

The patent creates identical copies of the smart contract software and deploys them across multiple platforms. Each platform receives and executes the same software instance with identical input parameters. The system then compares the outputs from all copies to ensure they match. This copying approach simplifies the system architecture because it relies on replication rather than complex coordination mechanisms, making the system more resistant to collusion while maintaining relative simplicity.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10853064B2System and method for ensuring correct execution of software
Publication Date: 2020.12.01 RIPPLE LABS INC
  • US10853064B2 patent drawing
  • US10853064B2 patent drawing
  • US10853064B2 patent drawing

AI summary

In a method for executing software, a result produced from an execution of a copy of the software by a corresponding platform can be received from each of a plurality of platforms. A number of results of execution of the software can be determined. The extent to which the results match can be compared to a threshold. The matching results can be accepted as an agreed-upon output of the software when the extent to which the results match is equal to or greater than the threshold. The software can include an implementation of at least a portion of an act associated with an agreement between at least two entities.