Smart Contract Hash Verification for Blockchain Efficiency

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain systems are wasteful due to massively replicated execution of smart contract code, leading to privacy loss as execution occurs on decrypted data, necessitating optimization for efficient processing.

Innovation Solution

The method involves identifying and processing smart contracts to create a smart contract definition, determining acceptance by parties, generating a hash, and forwarding it to blockchains, utilizing a smart contract processing engine that models contracts as passive deterministic finite automations and monitors events for state changes based on blockchain data and private communications.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If smart contract code is massively replicated and executed on all blockchain nodes, then the system ensures decentralization and trust, but it causes waste of computational resources and loss of privacy due to execution on decrypted data

Engineering Contradiction:
Improvedecentralization and trustVSAvoidcomputational resource waste
Core Design Contradiction:
ReliabilityVSLoss of energy

Solution Approach 1:

The patent applies preliminary action by generating and storing the hash of the smart contract definition before the contract is executed on the blockchain. This pre-computation of the hash allows the system to verify contract integrity without requiring all nodes to execute the full contract code, thereby reducing computational waste while maintaining decentralization and trust through hash verification.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If smart contract code is massively replicated and executed on all blockchain nodes, then the system ensures decentralization and trust, but it causes loss of privacy because execution has to happen on decrypted data

Engineering Contradiction:
Improvedecentralization and trustVSAvoidprivacy loss
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent uses copying by storing and verifying the hash of the smart contract definition instead of requiring all nodes to hold and execute copies of the actual contract code. This allows the system to maintain decentralization through hash verification while preventing privacy loss, as the decrypted contract data is not unnecessarily replicated and executed across all nodes.

Inventive Principle:
Principle #26Copying

3Reliability

If smart contract code is massively replicated and executed on all blockchain nodes, then the system ensures comprehensive verification, but it reduces processing efficiency and increases operational complexity

Engineering Contradiction:
Improvecomprehensive verificationVSAvoidprocessing efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

The patent extracts the essential verification element (the hash of the smart contract definition) from the full contract code and stores it on the blockchain. This allows nodes to verify contract integrity by checking the hash without executing the entire contract, thereby maintaining comprehensive verification while significantly improving processing efficiency by eliminating unnecessary code execution.

Inventive Principle:
Principle #2Taking out (Extraction)

4Reliability

If smart contract code is massively replicated and executed on all blockchain nodes, then the system ensures thorough contract validation, but it increases device complexity and operational overhead

Engineering Contradiction:
Improvethorough contract validationVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent uses copying by replacing the need for all nodes to store and execute complex smart contract code with a simple hash verification mechanism. The hash of the contract definition is stored on the blockchain, and nodes only need to verify this hash against their local copies, thereby reducing device complexity and operational overhead while maintaining thorough validation through hash-based integrity checking.

Inventive Principle:
Principle #26Copying

Data Source

PatentUS10963400B2Smart contract creation and monitoring for event identification in a blockchain
Publication Date: 2021.03.30 INTERNATIONAL BUSINESS MACHINE CORPORATION
  • US10963400B2 patent drawing
  • US10963400B2 patent drawing
  • US10963400B2 patent drawing

AI summary

An example operation may include one or more of identifying a smart contract, processing the smart contract to create a smart contract definition, determining whether the smart contract has been accepted by identified parties, when the smart contract has been accepted by the identified parties, generating a smart contract definition hash, and forwarding the smart contract definition hash to one or more blockchains.