Multi-party Smart Contract Batch Verification

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain networks face inefficiencies and security challenges in verifying and executing multi-party smart contracts, particularly in ensuring all parties confirm transactions before execution.

Innovation Solution

The method involves receiving and verifying transaction information from multiple nodes in a blockchain network, maintaining a confirmation status of unconfirmed transactions, and executing the transaction only after all parties have confirmed, using digital signatures and public keys to ensure validity and security.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If separate signature verification is performed for each participating entity, then transaction security is improved, but transaction execution time increases

Engineering Contradiction:
Improvetransaction securityVSAvoidtransaction execution time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The patent combines multiple separate signature verifications into a single batch verification process. Instead of verifying each entity's signature separately, the system aggregates all signatures and verifies them simultaneously using elliptic curve cryptography, reducing the total verification time while maintaining security.

Inventive Principle:
Principle #5Merging (Combining)

Solution Approach 2:

The system performs preliminary aggregation of signatures before the final verification step. By collecting and combining all signatures in advance, the system prepares the data in a format that enables efficient batch verification, avoiding repeated verification operations.

Inventive Principle:
Principle #10Preliminary action

2Reliability

If all participating entities must confirm before execution, then transaction reliability is improved, but system complexity increases

Engineering Contradiction:
Improvetransaction confirmation reliabilityVSAvoidsystem complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The smart contract automatically manages the confirmation process by itself. The contract collects signatures from all participating entities, verifies them in batch, and executes the transaction when all confirmations are received, eliminating the need for external coordination mechanisms.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The batch verification mechanism serves multiple functions: it verifies all signatures simultaneously, determines transaction execution eligibility, and maintains security standards. This multi-functional approach reduces the need for separate verification and decision-making components.

Inventive Principle:
Principle #6Universality (Multi-functionality)

3Productivity

If batch verification is implemented, then processing efficiency is improved, but computational requirements increase

Engineering Contradiction:
Improveverification processing efficiencyVSAvoidcomputational energy consumption
Core Design Contradiction:
ProductivityVSUse of energy by moving object

Solution Approach 1:

The patent replaces multiple separate verification computations with a single batch verification computation using elliptic curve cryptography. This mathematical substitution reduces the total computational load by leveraging the properties of elliptic curve operations to verify multiple signatures more efficiently than individual verifications.

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

Data Source

PatentEP3559891B1Executing multi-party transactions using smart contracts
Publication Date: 2021.11.17 ADVANCED NEW TECHNOLOGIES CO LTD
  • EP3559891B1 patent drawingFigure 1
  • EP3559891B1 patent drawingFigure 2
  • EP3559891B1 patent drawingFigure 3

AI summary

Implementations of the present specification include receiving first transaction information from a first node, wherein the first node is a computer node in the blockchain network, and wherein the first transaction information comprises a transaction payload, a first public key, and a signed transaction payload for a transaction, verifying the signed transaction payload using the first public key, in response to the verifying the signed transaction payload, constructing an unconfirmed transaction data package, and setting a confirmation status of the unconfirmed transaction data package, receiving second transaction information from a second node, wherein the second node is a computer node in the blockchain network, and wherein the second transaction information includes a hash of the transaction payload, a second public key, and a signed hash of the transaction payload for the transaction, verifying the second transaction information using the second public key, updating the confirmation status of the unconfirmed transaction data package, and executing the transaction payload in response to the confirmation status indicating that all parties to the transaction have confirmed the transaction.