Blockchain Signature Verification Testing Automation

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current blockchain systems lack effective methods for testing signature verification, particularly for cryptography algorithms and private keys, which is crucial for ensuring transaction validity and security.

Innovation Solution

A computer-implemented method and device that obtain a testing configuration from a configuration file, specifying cryptography algorithms and private keys, sign transactions, and send them to the blockchain system for execution results, allowing for the verification of signature validity and easy updating of configurations for testing various scenarios.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Productivity

If manual testing methods are used for signature verification, then testing can be performed, but testing efficiency and coverage are low

Engineering Contradiction:
Improvetesting efficiencyVSAvoidtesting system complexity
Core Design Contradiction:
ProductivityVSDevice complexity

Solution Approach 1:

The testing system automatically generates test transactions, performs signature verification testing, and produces test reports without manual intervention. The system self-manages the entire testing workflow including configuration loading, test case execution, and result analysis, thereby improving testing efficiency while maintaining manageable complexity through automation.

Inventive Principle:
Principle #25Self-service

Solution Approach 2:

The testing system is designed to support multiple cryptography algorithms and various signature verification scenarios through a unified testing framework. By implementing multi-functionality that can handle different cryptographic standards and test cases, the system achieves high testing coverage and efficiency without proportionally increasing system complexity.

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

2Ease of operation

If configuration files contain all testing parameters, then testing can be performed, but configuration file size becomes large

Engineering Contradiction:
Improveconfiguration managementVSAvoidconfiguration file size
Core Design Contradiction:
Ease of operationVSQuantity of substance

Solution Approach 1:

The system extracts and separates configuration parameters into structured, modular components that can be independently managed. By taking out specific testing parameters from a monolithic configuration file and organizing them into distinct sections or modules, the system reduces overall configuration file size while maintaining ease of operation through organized parameter access.

Inventive Principle:
Principle #2Taking out (Extraction)

Solution Approach 2:

The configuration file is segmented into multiple independent sections or modules, each handling specific testing parameters such as cryptography algorithms, transaction types, or verification methods. This segmentation reduces the perceived size and complexity of the configuration file while improving ease of operation by allowing targeted modification of specific testing aspects without affecting the entire configuration.

Inventive Principle:
Principle #1Segmentation

3Reliability

If comprehensive testing scenarios are implemented, then signature verification security is improved, but testing time increases

Engineering Contradiction:
Improvesignature verification securityVSAvoidtesting time
Core Design Contradiction:
ReliabilityVSLoss of time

Solution Approach 1:

The system performs preliminary setup and configuration of testing parameters before executing comprehensive test scenarios. By pre-configuring cryptography algorithms, transaction templates, and verification rules in advance, the system enables comprehensive security testing to be executed efficiently without excessive testing time, as the foundational testing framework is already prepared.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The testing system implements continuous automated testing that can run comprehensive signature verification scenarios without interruption. By maintaining continuous useful action through automated test execution and parallel processing capabilities, the system achieves thorough security validation while minimizing total testing time compared to manual or batched approaches.

Inventive Principle:
Principle #20Continuity of useful action

Data Source

PatentEP3590084B1Methods and devices for testing signature verification for blockchain system
Publication Date: 2022.05.11 ADVANCED NEW TECHNOLOGIES CO LTD
  • EP3590084B1 patent drawingFigure 1
  • EP3590084B1 patent drawingFigure 2
  • EP3590084B1 patent drawingFigure 3

AI summary

Disclosed herein are methods, devices, and apparatuses, including computer programs stored on computer-readable media, for testing signature verification for a blockchain system. One of the methods includes: obtaining a testing configuration from a configuration file, wherein the testing configuration specifies a cryptography algorithm used in the blockchain system, a group of one or more private keys corresponding to the cryptography algorithm, and a predetermined execution result based on the cryptography algorithm and the group of one or more private keys; signing a transaction, by encrypting data representing the transaction based on the cryptography algorithm and the group of one or more private keys, to generate one or more signed transactions; sending the one or more signed transactions to the blockchain system and receiving an execution result from the blockchain system; and determining whether the predetermined execution result is satisfied based on the execution result.