Smart contract testing method based on path coverage sufficiency criterion

Abstract

The invention discloses a smart contract test method based on a path coverage sufficiency criterion. The method comprises the following steps: step 1, inputting byte codes of a smart contract and ABIsof the smart contract; step 2, generating a control flow chart according to the byte code; step 3, using an EPP algorithm for analyzing the control flow chart, finding out blocks needing instrumentation, and conducting instrumentation; step 4, deploying the instrumented smart contract on the trace; and step 5, generating a test case set meeting requirements according to a path coverage test sufficiency criterion. Compared with other technologies for analyzing the source code, the byte code of the smart contract is analyzed, and the method is more efficient. According to the method, the test case is automatically generated for the smart contract, whether the sufficient test case set is generated or not is judged according to the adequacy criterion of path coverage, errors possibly existingin the smart contract code are fully exposed as much as possible, the vulnerability detection effect is improved, and the labor cost is reduced.

Description

technical field [0001] The invention relates to the field of computer technology, in particular to a smart contract testing method based on path coverage sufficiency criteria. Background technique [0002] Smart contracts are programs that run on top of blockchain consensus protocols to allow people to come to an agreement while minimizing trust. Once the smart contract is deployed, the contract content is open, transparent, non-tamperable, and automatically executed. But precisely because of the non-tamperable nature of the smart contract, if the smart contract fails to detect loopholes or logic errors in time before deployment, it may make mistakes or be maliciously used by bad people, causing people's property losses, for example: the loopholes in The DAO contract caused Lost $60 million. In order to avoid errors or loopholes in the deployed smart contracts and ensure the safety of people's property, the testing of smart contracts is very important. [0003] Existing s...

AI Technical Summary

Problems solved by technology

[0003] Existing smart contract testing tools are designed to detect specific patterns of known vulnerabilities. The disadvantage is that they can only detect a limited number of known vulnerabilities. Oyente can only detect 4 specific vulnerabilities, and contractFuzzer can only detect 7 specific vulnerability

However, other vulnerabilities or errors other than these vulnerabilities may exist in the smart contracts written by programmers

These tools cannot detect logic errors that do not have a specific pattern

Images