Multi-stage Smart Contract Encryption via Oracle Conditions

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Smart contracts face challenges in securely managing sensitive information across multiple stages, as existing solutions expose sensitive data to malicious access or exposure if compromised, and require external data verification from multiple oracles without secure encryption mechanisms.

Innovation Solution

A multi-stage smart contract mechanism is implemented, where each stage is encrypted with keys that can only be decrypted upon satisfaction of conditions precedent, using a threshold cryptosystem and oracle-provided encryption keys to ensure secure access and verification, preventing exposure of sensitive data until previous stages are completed.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Adaptability or versatility

If smart contracts store sensitive information for multiple stages, then the contract can execute complex multi-stage operations, but the sensitive data becomes exposed to malicious access or compromise

Engineering Contradiction:
Improvemulti-stage operation capabilityVSAvoiddata exposure risk
Core Design Contradiction:
Adaptability or versatilityVSObject-affected harmful factors

Solution Approach 1:

The patent segments the smart contract into multiple encrypted stages, where each stage is independently encrypted and can only be accessed after completing previous stages. This segmentation allows the contract to maintain multi-stage operational capability while protecting sensitive data in each stage from exposure, as only the current executable stage is decrypted in memory.

Inventive Principle:
Principle #1Segmentation

2Object-affected harmful factors

If all stages of smart contract are encrypted, then sensitive data security is improved, but the contract executor cannot access next stage information without decryption keys

Engineering Contradiction:
Improvesensitive data securityVSAvoidaccess to next stage information
Core Design Contradiction:
Object-affected harmful factorsVSEase of operation

Solution Approach 1:

The patent implements preliminary action by pre-encrypting all future stages before contract execution begins. Each stage is encrypted with keys that will only be released after completing the current stage, allowing the contract executor to access next stage information sequentially without compromising security. This preliminary encryption maintains both security and operational ease.

Inventive Principle:
Principle #10Preliminary action

3Ease of operation

If encryption keys are provided to contract executor, then decryption and execution of stages is enabled, but the executor gains access to sensitive information in successive stages

Engineering Contradiction:
Improvedecryption capabilityVSAvoidexposure of sensitive information
Core Design Contradiction:
Ease of operationVSLoss of information

Solution Approach 1:

The patent applies dynamics by implementing dynamic key management where encryption keys are released in real-time as each stage completes. The contract executor receives decryption keys only for the current stage after verification, not for all future stages. This dynamic approach enables decryption capability while preventing premature access to sensitive information in successive stages.

Inventive Principle:
Principle #15Dynamics

Data Source

PatentUS11316660B2Multi-stage secure smart contracts
Publication Date: 2022.04.26 RED HAT INC
  • US11316660B2 patent drawing
  • US11316660B2 patent drawing
  • US11316660B2 patent drawing

AI summary

Encrypted multi-stage smart contracts are disclosed. A smart contract that is to be performed by a contract executor in a plurality of successive stages is generated. For each respective stage of at least some stages, a package of data is encrypted with at least one key to generate an encrypted package that corresponds to the respective stage, and an envelope that corresponds to the respective stage is generated. The envelope includes a condition precedent confirmable by an oracle, and an encrypted package-decryption key that is encrypted with a key of the contract executor. The encrypted package-decryption key, when decrypted, is configured to facilitate the decryption of the encrypted package that corresponds to the respective stage. For at least some of the stages, the encrypted package comprises an envelope and an encrypted package that corresponds to a next successive stage.