JP2020042795A - Uncertainty factor detector for smart contract, method and storage medium - Google Patents

Abstract

To provide an uncertainty factor detector for smart contracts, a method, and a medium.SOLUTION: An uncertainty factor detector for smart contract 100 includes an analysis unit 101 and a detection unit 102. The analysis unit 101 converts the smart contract to an abstract syntax tree, and scans the abstract syntax tree and acquires the execution path of ledger operation and ledger write operation. The detection unit 102 detects whether any uncertainty factor is included in the ledger operation on the execution path.SELECTED DRAWING: Figure 1

Description

  The present disclosure relates to the technical field of blockchain, and more particularly, to an apparatus and method for detecting an uncertainty factor for a smart contract.

  This section provides background information related to the present disclosure, but it is not necessarily prior art.

  At present, Hyperledger is the most popular blockchain and flat form suitable for the Consortium Blockchain. Its features are advantageous to developers, and companies have their own Complex business applications can be developed according to needs. In Hyperledger, Go language is the core language for writing smart contracts. In Hyperledger, transactions generated by smart contracts require endorsement of a series of nodes. If the RWSet (Read / Write Set) of the ledger generated by each node does not match, the transaction may fail. Therefore, it is necessary to ensure the consistency of the execution results on each endorsement node of the smart contract written in Go language, that is, cannot include uncertainty.

  However, developers typically ignore smart contract code or transaction uncertainty issues and may write smart contract code that is prone to transaction failure.

  Also, the transactions generated by the smart contract must go through endorsement procedures (simulated execution), transaction sorting procedures, and ledger submission procedures, instead of being immediately effective. Then, the correction to the ledger in the code becomes effective. Conventionally, during a development process, a programmer would typically modify one state value, write the state value back to the ledger, and get the modified state value when reading back the state value. . In practice, the status values written back to the ledger during the endorsement phase do not take effect immediately, but the status values read again are still the same as those read at the first time. It is easy to cause, that is, the result of executing the transaction may be inconsistent with the developer's expectations. Thus, conventionally, a tool that can detect such code or transaction uncertainty is desirable.

  An object of the present disclosure is to provide a technical solution that can solve the above-described problem, and in particular, to provide an uncertainty factor detection device and method for smart contract.

  According to one aspect of the present disclosure, there is provided an uncertainty factor detection device for a smart contract, which is an analysis unit for analyzing a traversal path of the smart contract ledger operation. And a detection unit for detecting whether the ledger operation includes an uncertainty factor with respect to the traversal route, wherein the analysis unit has a branch structure in the traversal route. When it is determined that the traversal route is included, the traversal route is extended.

  According to another aspect of the present disclosure, there is provided an uncertainty factor detection method for a smart contract, which analyzes a traversal path of a ledger operation of the smart contract; Detecting whether the ledger operation includes an uncertainty factor. If it is determined that the traversal route includes a branch structure, the traversal route is extended.

  According to another aspect of the present disclosure, there is provided a program product, wherein the program product includes a machine-readable command code, wherein the command code is read and executed by a computer. And causing the computer to execute the uncertainty factor detection method for smart contract according to the present disclosure.

  According to another aspect of the present disclosure, there is provided a machine-readable storage medium, including a program product according to the present disclosure.

  An apparatus and method for detecting uncertainty for a smart contract according to the present disclosure can greatly improve the efficiency of a developer of a smart contract, and can endorse due to uncertainty of code during a contract execution process. Failures can be reduced and the occurrence of transaction uncertainties can be reduced.

FIG. 2 is a block diagram of an uncertainty factor detecting device for a smart contract according to an embodiment of the present disclosure; FIG. 4 is a diagram illustrating that an analysis unit of the uncertainty factor detection device for smart contract performs path expansion according to an embodiment of the present disclosure; FIG. 4 is a diagram illustrating that a detection unit of an uncertainty factor detection device for smart contract performs detection according to an embodiment of the present disclosure; FIG. 4 is a diagram illustrating uncertainty of a transaction according to an embodiment of the present disclosure. FIG. 4 is a configuration diagram of an entire uncertainty factor detection plan for a smart contract according to an embodiment of the present disclosure; 4 is a flowchart of a method for detecting an uncertainty factor for a smart contract according to an embodiment of the present disclosure; FIG. 1 is a configuration diagram of a general-purpose computer that can implement an uncertainty factor detection device and method for a smart contract in an embodiment of the present disclosure.

  Hereinafter, preferred embodiments for carrying out the present disclosure will be described in detail with reference to the accompanying drawings. Note that such an embodiment is merely an example and does not limit the present disclosure.

  Hereinafter, in order to better understand the technical solution of the present disclosure, an uncertainty factor detecting device and a detecting method for a smart contract according to the present disclosure will be described in detail.

  According to one embodiment of the present disclosure, there is provided an uncertainty factor detection device for a smart contract, which is an analysis unit for analyzing a traversal path of the ledger operation of the smart contract. And a detection unit for detecting whether the ledger operation includes an uncertainty factor with respect to the traversal route, wherein the analysis unit includes a branching structure in the traversal route. When it is determined that the traversal route is present, the traversal route is extended.

  FIG. 1 illustrates an uncertainty factor detection apparatus 100 for a smart contract in one embodiment of the present disclosure. As shown in FIG. 1, the uncertainty factor detection device 100 for a smart contract according to the present disclosure may include an analysis unit 101 and a detection unit 102.

  The analysis unit 101 analyzes the traversal route of the ledger operation of the smart contract. For example, according to one embodiment of the present disclosure, analysis unit 101 first converts the smart contract into an abstract syntax tree (AST). Thereafter, the AST is scanned (traversal) using, for example, a depth-first traversal algorithm, and the ledger operation (eg, ledger reading operation (ie, ledger reading operation) and ledger writing operation) is performed. (I.e., the operation of writing to the ledger)), the traversal route, that is, the execution route is acquired. Here, it should be understood by those skilled in the art that the depth-first traversal algorithm is merely an example, and the present disclosure is not limited to this. One skilled in the art may employ any other known scanning method in the prior art.

  Thereafter, when the analysis unit 101 performs a syntax analysis on the AST, there may be words extending across lines, for example, sentences such as if, switch, for, and the like. In the absence of code, for words that span these lines, the depth-first traversal algorithm typically records only the first line of information. However, since information between phrases that are not recorded may have corrections to the ledger operation target variables, when determining whether there is a change in the specific ledger operation target, It is necessary to record all the phrases between (inside) the phrases across the lines. That is, it is necessary to perform internal expansion on the words extending over these lines.

  According to an embodiment of the present disclosure, the analysis unit 101 determines whether the traversal path of the ledger operation includes a branch structure, that is, a word that extends across lines, for example, a sentence such as if, switch, for, or the like. It may be configured as follows. If the traversal route includes a branch structure, the traversal route is extended.

  Specifically, first, the analysis unit 101 records, by syntactic analysis, an extracted word that extends across lines, for example, a start position of a sentence such as if, switch, or for. Thereafter, it is determined whether or not the first line of the phrase extending over these lines is included in the execution path related to all ledger operations. When the first line of a phrase extending over these lines is included, the first line is replaced with all lines within the corresponding range.

  For example, as shown in FIG. 2, the execution path of the ledger operation function GetState (K1) includes the first line L3 representing the if branch structure, and the L10 line of the ledger operation function GetState (K1) is executed. , Line L3 has already been executed. However, at this time, the execution path of the ledger operation function GetState (K1) is only L1, L2, L3, L9, and L10. Uncertainty risk occurs when a modification to a ledger operation variable occurs in the if branch structure represented by the L3 line, for example, the L5 line (for example, when a state update operation PutState (K1, V1) is performed). Can cause Therefore, it is necessary to extend another range of the if branch condition represented by the L3 line to the execution path. As shown in FIG. 2, the other ranges of the if branch condition represented by the L3 row are L3, L4, L5, L6, L7, and L8. Therefore, the extended execution path of the extended ledger operation function GetState (K1) is L1, L2, L3, L4, L5, L6, L7, L8, L9, L10. By adopting such an extension method, the code inside the if branch condition cannot be ignored in the subsequent control flow analysis.

  Subsequently, the detection unit 102 may detect whether the ledger operation includes an uncertainty factor with respect to the traversal route. According to an embodiment of the present disclosure, the uncertainty factor may include a code uncertainty factor and a transaction uncertainty factor.

  The Go language standard library provides a tool for performing a depth scan (traversal) on an abstract syntax tree (AST), but cannot record traversal path information. Thus, according to one embodiment of the present disclosure, the analysis unit 101 may be further configured to modify a standard library for scanning the AST to record the traversal path.

  For example, according to an embodiment of the present disclosure, when performing a depth scan on the AST, the analysis unit 101 detects a ledger operation code (eg, PutState () and GetState ()) by syntax analysis. When a ledger operation code is detected, a specific execution path corresponding to the ledger operation code can be recorded at the same time.

<Detection of code uncertainty>
According to one embodiment of the present disclosure, the uncertainty factor includes a code uncertainty factor. The code uncertainty factors include, for example, uncertainty factors by the Go language itself, such as random number generation, global variables, time stamps, scanning of key-value pair data structures, and target addresses. Code uncertainty factors may further include external calls, such as network services, external library calls, and system instructions. Also, the code uncertainty factors may further include uncertainties due to the Fabric execution mechanism, such as cross channel chaincode calls and range query risks. It should be understood by those skilled in the art that such a code uncertainty factor is merely an example, and the present disclosure is not limited thereto.

  The present disclosure provides a code uncertainty detection device for smart contracts.

  An apparatus for detecting code uncertainty for a smart contract according to the present disclosure is an analysis unit that analyzes a traversal path of a ledger operation of the smart contract; For the route, including detecting whether the ledger operation includes an uncertainty factor, among which the analysis unit determines that the traversal route includes a branch structure when the traversal route is included. The detection unit is further configured to determine whether the ledger operation target and value include a code uncertainty factor in a backtracking manner for the traversal route.

  Here, since the configuration related to the analysis unit is the same as the configuration of the analysis unit 101 in the above-described embodiment, a detailed description is omitted.

  According to an embodiment of the present disclosure, the detection unit may further determine whether the ledger operation target and the value include a code uncertainty factor in a backtracking manner for the traversal route. It may be configured. More specifically, the detection unit 102 extracts the operation targets of all ledger operations, and thereafter, an uncertainty factor is assigned to the operation target (variable) on the execution path corresponding to the ledger operation by a backtracking method. You can analyze whether it is included. If it is included, it is determined that a code uncertainty risk may occur. The specific process is as shown in FIG. Among them, line 76 represents the found ledger operation, PutState (), which has two possible execution paths (indicated by solid lines). After that, the operation objects K1 and V1 of the ledger operation PutState () are extracted. Then, it is analyzed whether or not the operation objects K1 and V1 in the execution path corresponding to the ledger operation PutState () include an uncertainty factor by a back tracking method (a back tracking path is indicated by a broken line). When determining whether an operating object includes an uncertainty factor, the present disclosure may support analysis of operating objects in at least three different formats, for example, variables, constants, and combinations of constants and variables. However, since the constants can be directly compared, detailed description thereof is omitted here. In other words, here, when only variables are extracted and backtracking analysis is performed on the execution path, it may be determined whether or not a portion related to the variables includes an uncertainty risk. It should be understood by those skilled in the art that such a detection process is merely an example, and the present disclosure is not limited to the steps and the order in the processes as described above.

  According to one embodiment of the present disclosure, the ledger operation may include a ledger reading operation and a ledger writing operation. Of course, those skilled in the art should understand that such ledger reading operation and ledger writing operation are merely examples, and the present disclosure is not limited thereto.

  By using the smart contract uncertainty detection device based on control flow analysis according to the present disclosure, it is possible to effectively detect the code uncertainty risk of the smart contract by extending the execution path and to determine the location of the risk. Lines can be recorded. Therefore, failure of endorsement in the transaction generated by the smart contract in the hyper ledger can be reduced.

<Detection of transaction uncertainty>
Since the execution of the smart contract is performed at the endorsement stage, and at the endorsement stage, no update operation is performed on the ledger, so that one contract can be modified first for one specific ledger state. When performing an operation of performing and then reading, there is a possibility that the contents read by the developer may still be the same as those before the correction, so that the risk of transaction uncertainty is likely to occur. In the present disclosure, such an uncertainty risk is referred to as “RYW risk” (“Read-Your-Write Risk”), and is specifically as shown in FIG.

  In one transaction, if the developer writes “K1 = V1” for the ledger's operation target K1 and value V1, as described above, the transaction generated by the smart contract will not be effective immediately. That is, the write does not take effect immediately, and in the ledger database K1 is still equal to V0. In this case, when the developer needs to obtain the value of K1, it obtains “K1 = V0” instead of “K1 = V1”, which can cause an uncertainty of the transaction.

  Thus, the present disclosure provides a transaction uncertainty detection device for smart contracts.

  The transaction uncertainty detection device for the smart contract includes the above-described analysis unit 101 and the detection unit 102. Since the analysis unit 101 has been described in detail above, a detailed description thereof will be given here. Omitted.

  According to one embodiment of the present disclosure, detecting whether the ledger operation includes the transaction uncertainty factor by the detection unit 102 is performed in an execution path ending in the ledger reading operation. The method of tracking may include determining whether the ledger write operation has occurred on the execution path.

  Specifically, the detection unit 102 may analyze whether or not the ledger write operation (PutState ()) is included in the previous execution path for all ledger read operations (GetState ()). If a ledger write operation is included before a ledger read operation in one of the execution paths, and the operation target is the same ledger state (variable), the ledger write operation and the ledger read operation are further performed before the ledger write operation and the ledger read operation. Determine whether the variable has been modified. If the variable is not corrected, it indicates that the target of the ledger reading operation and the ledger writing operation are in the same ledger state, and in this case, it is determined that the transaction uncertainty risk, that is, the RYW risk has occurred.

  In summary, the present disclosure provides a scheme for detecting smart contract uncertainty factors based on control flow analysis. As shown in FIG. 5, first, the smart contract is converted into an abstract syntax tree (AST), which can then record the traversal path (ie, execution path) by optimizing the depth traversal algorithm So that Then, by scanning the AST using the optimized depth scanning algorithm, all ledger operations (ledger reading operation and ledger writing operation) are found, and the execution path of each ledger operation is recorded. I do. Also, when syntactic analysis is performed on the AST, a range of several phrases extending over a line, for example, a range relating to a sentence such as if, switch, for, etc. is extracted, and the range information of the phrase extending over these lines is extracted. To extend the execution path.

  Next, regarding the code uncertainty detection of the smart contract, first, the syntax analysis is performed on the AST, and then the code uncertainty is determined in the ledger operation target and value by the back tracking method in the ledger operation execution path. Gender factor is included, and for transaction uncertainty detection, first, all execution paths ending with the ledger reading operation are analyzed, and it is determined whether ledger writing operation has occurred on the ledger. If the target of the write operation and the ledger read operation are the same ledger target (variable) and the target has not been modified between the ledger write operation and the ledger read operation, the transaction uncertainty risk, that is, the RYW risk risk Is determined to have occurred.

  By using the uncertainty detection device for smart contract according to the present disclosure, the efficiency of the smart contract developer can be greatly improved, and endorsement due to code uncertainty during the contract execution process can be achieved. Failures can be reduced, and the occurrence of transaction uncertainty can be reduced.

  Hereinafter, an uncertainty factor detection method for a smart contract according to an embodiment of the present disclosure will be described with reference to FIG. As shown in FIG. 6, the uncertainty factor detection method for a smart contract according to the embodiment of the present disclosure starts in step S610.

  In step S610, the traversal route of the ledger operation of the smart contract is analyzed, and when it is determined that the traversal route includes a branch structure, the traversal route is extended.

  Subsequently, in step S620, it is detected whether the ledger operation includes an uncertainty factor for the traversal route.

  The method for detecting uncertainty factors for a smart contract in one embodiment of the present disclosure further comprises: converting the smart contract into an abstract syntax tree; and Including modifying the traversal path so that it can be recorded.

  In the method for detecting an uncertainty factor for a smart contract according to an embodiment of the present disclosure, the uncertainty factor includes a code uncertainty factor and a transaction uncertainty factor.

  In the method for detecting an uncertainty factor for a smart contract according to an embodiment of the present disclosure, the detection of whether or not the code uncertainty factor is included in the ledger operation is performed in a backtracking manner, and the object of the ledger operation is And determining whether the value includes a code uncertainty factor.

  In the uncertainty factor detecting method for a smart contract according to an embodiment of the present disclosure, the ledger operation includes a ledger reading operation and a ledger writing operation.

  In the uncertainty factor detection method for a smart contract according to an embodiment of the present disclosure, the detection of whether the ledger operation includes the transaction uncertainty factor is performed in an execution path ending with the ledger reading operation, Determining whether or not the ledger write operation has occurred in the execution path in a backtracking manner.

  In the method of detecting an uncertainty factor for a smart contract according to an embodiment of the present disclosure, the ledger reading operation and the ledger writing operation are performed on the same ledger target variable.

  In the uncertainty factor detecting method for a smart contract according to an embodiment of the present disclosure, the detection of whether the ledger operation includes the transaction uncertainty factor may further include the ledger writing operation and the ledger reading operation. Before determining whether the ledger target variable has been modified.

  By using the uncertainty detection method for smart contracts according to the present disclosure, the efficiency of a smart contract developer can be greatly improved, and endorsement due to code uncertainty during the contract execution process can be achieved. Failures can be reduced, and the occurrence of transaction uncertainty can be reduced.

  Various specific implementations of the above steps in the method of detecting uncertainty factors for smart contracts in the embodiment of the present disclosure have been described in detail previously, and will not be described here. Omit.

  Also, as will be apparent, each operating process of the uncertainty factor detection method for a smart contract according to the present disclosure can be implemented by a computer-executable program included in various machine-readable storage media. .

  Further, the object of the present disclosure may be realized in the following manner, that is, a storage medium including the above-described executable program code is directly or indirectly provided to a system or an apparatus, and the system or the apparatus is provided. The inside computer or central processing unit (CPU) is to read and execute the above program code. At this time, the system or the device only needs to have a function of executing the program. Note that the implementation method of the present disclosure is not limited to a program, and the program may be in any form, for example, an object program, a program for executing an interpreter, or a script provided to an operating system. It may be a program or the like.

  These machine-readable storage media may include various storage devices, storage units, semiconductor storage devices, disk units, such as optical, magnetic, and magneto-optical disks, and other media that can store stored information. However, the present invention is not limited to this.

  Further, the technical solution according to the present disclosure can be realized by a computer accessing a website on the Internet, downloading and installing the computer program code according to the present disclosure, and then executing the program.

  Note that the above-described series of processing may be realized by software and / or firmware. When realized by software and / or firmware, a program having the software is installed from a storage medium or a network into a computer having dedicated hardware, for example, a general-purpose computer 1300 shown in FIG. When the program is installed, various functions can be executed.

  FIG. 1 is a configuration diagram of a general-purpose computer that can implement an uncertainty factor detection device and method for a smart contract in an embodiment of the present disclosure.

  In FIG. 7, a central processing unit (CPU) 1301 performs various processes based on a program stored in a ROM 1302 or a program loaded from a storage unit 1308 into a RAM 1303. The RAM 1303 may further store data required when the CPU 1301 executes various processes. The CPU 1301, the ROM 1302, and the RAM 1303 are connected to each other by a bus 1304. An input / output interface 1305 is also connected to the bus 1304.

  In addition, the following components are connected to the input / output interface 1305, that is, the input unit 606 (including a keyboard, a mouse, and the like), the output unit 1307 (a display, for example, a CRT, an LCD, and the like, a speaker, and the like). And a communication unit 1309 (including a network interface card, for example, a LAN card, a modem, etc.). The communication unit 1309 performs communication processing via a network, for example, the Internet. Note that the drive 1310 may be connected to the input / output interface 1305 as needed. A removable medium 1311 such as a magnetic disk, an optical disk, a magneto-optical disk, or a semiconductor storage device is set in the drive 1310 as necessary, and a computer program read out of the storage device is stored in the storage unit as needed. 1308 can be installed.

  In addition, the present disclosure further provides a program product including a machine-readable command code. Such instruction codes, when read and executed by a machine, may perform the methods in the embodiments of the present disclosure described above. Accordingly, such program products carry, for example, magnetic disks (including floppy disks (registered trademark)), optical disks (including CD-ROMs and DVDs), magneto-optical disks (MD (registered trademark)). ), And various storage media such as semiconductor storage devices are also included in the present disclosure.

  The above-described storage medium may include, for example, a magnetic disk, an optical disk, a magneto-optical disk, and a semiconductor storage device, but is not limited thereto.

  Further, each operation (process) of the above-described method of the present disclosure can be realized by a method of a computer-executable program stored in various machine-readable storage media.

  Further, with respect to the above embodiments and the like, additional notes are disclosed as follows.

(Appendix 1)
An uncertainty factor detection device for a smart contract,
An analysis unit that analyzes a traversal route of the ledger operation of the smart contract; and a detection unit that detects whether the ledger operation includes an uncertainty factor for the traversal route. Including
The detection device, wherein the analysis unit expands the traversal route when determining that the traversal route includes a branch structure.

(Appendix 2)
The detection device according to claim 1, wherein
The analysis unit further comprises:
A detection device for converting the smart contract into an abstract syntax tree; and modifying a standard library for scanning the abstract syntax tree to record the traversal path.

(Appendix 3)
The detection device according to Supplementary Note 1 or 2, wherein
The detection device, wherein the uncertainty factor includes a code uncertainty factor and a transaction uncertainty factor.

(Appendix 4)
The detection device according to claim 3, wherein
The detection unit detects whether the ledger operation includes the code uncertainty factor,
A detection device, comprising: determining whether a target and a value of the ledger operation include a code uncertainty factor by a back tracking method.

(Appendix 5)
The detection device according to claim 4, wherein
The detection device, wherein the ledger operation includes a ledger reading operation and a ledger writing operation.

(Appendix 6)
The detection device according to claim 5, wherein
The detection unit detects whether the ledger operation includes the transaction uncertainty factor,
A detection device, comprising: determining whether the ledger write operation has occurred on the execution path in an execution path ending with the ledger reading operation by a back tracking method.

(Appendix 7)
The detection device according to claim 6, wherein
A detection device, wherein the ledger reading operation and the ledger writing operation are performed on the same ledger object.

(Appendix 8)
The detection device according to claim 7, wherein
Wherein the detecting unit detects whether the ledger operation includes the transaction uncertainty factor,
A detection device, comprising: determining whether a variable of the ledger has been corrected before the ledger writing operation and the ledger reading operation.

(Appendix 9)
The detection device according to claim 7, wherein
The detection device, wherein the type of ledger object includes a general constant, a variable, and a combination of a constant and a variable.

(Appendix 10)
An uncertainty factor detection method for smart contracts,
Analyzing the traversal path for the ledger operation of the smart contract; and detecting, for the traversal path, whether the ledger operation includes an uncertainty factor;
A detection method for expanding the traversal route when it is determined that the traversal route includes a branch structure.

(Appendix 11)
The detection method according to supplementary note 10, further comprising:
A method for detecting, comprising: converting the smart contract into an abstract syntax tree; and modifying a standard library for traversing the abstract syntax tree to record the traversal path.

(Appendix 12)
The detection method according to Supplementary Note 10 or 11, wherein
The detection method, wherein the uncertainty factor includes a code uncertainty factor and a transaction uncertainty factor.

(Appendix 13)
The detection method according to supplementary note 12, wherein
Detecting whether the ledger operation includes the code uncertainty factor,
A detection method, comprising: determining whether a target and a value of the ledger operation include a code uncertainty factor by a back tracking method.

(Appendix 14)
The detection method according to supplementary note 13, wherein
The detection method, wherein the ledger operation includes a ledger reading operation and a ledger writing operation.

(Appendix 15)
The detection method according to supplementary note 14, wherein
Detecting whether the ledger operation includes the transaction uncertainty factor,
A detection method, comprising: determining whether the ledger write operation has occurred on the execution path in the execution path ending with the ledger reading operation by a back tracking method.

(Appendix 16)
The detection method according to supplementary note 15, wherein
A detection method, wherein the ledger reading operation and the ledger writing operation are performed on the same ledger object.

(Appendix 17)
The detection method according to Supplementary Note 16, wherein
Detecting whether the ledger operation includes the transaction uncertainty factor,
A detection method, comprising: determining whether the ledger target variable has been corrected before the ledger writing operation and the ledger reading operation.

(Appendix 18)
The detection method according to Supplementary Note 16, wherein
The detection device, wherein the type of ledger object includes a constant, a variable, and a combination of a constant and a variable.

(Appendix 19)
A program for causing a computer to execute the detection method according to any one of supplementary notes 10-18.

(Appendix 20)
A computer-readable storage medium storing the program according to supplementary note 19.

  Although the preferred embodiment of the present disclosure has been described above, the present disclosure is not limited to this embodiment, and any changes to the present disclosure belong to the technical scope of the present disclosure unless departing from the spirit of the present disclosure.

Claims (10)

An uncertainty factor detection device for a smart contract,
An analysis unit for analyzing a traversal route of the ledger operation of the smart contract; and a detection unit for detecting whether the ledger operation includes an uncertainty factor for the traversal route,
The detection device, wherein the analysis unit expands the traversal route when determining that the traversal route includes a branch structure. The detection device according to claim 1,
The analysis unit further comprises:
A detection device for converting the smart contract into an abstract syntax tree; and modifying a standard library for scanning the abstract syntax tree to record the traversal path. The detection device according to claim 1 or 2,
The detection device, wherein the uncertainty factor includes a code uncertainty factor and a transaction uncertainty factor. The detection device according to claim 3,
The detection unit detects whether the ledger operation includes the code uncertainty factor,
A detection device, comprising: determining whether a target and a value of the ledger operation include a code uncertainty factor by a back tracking method. The detection device according to claim 4,
The detection device, wherein the ledger operation includes a ledger reading operation and a ledger writing operation. The detection device according to claim 5,
The detection unit detects whether the ledger operation includes the transaction uncertainty factor,
A detection device, comprising: determining whether the ledger write operation has occurred on the execution path in an execution path ending with the ledger reading operation by a back tracking method. The detection device according to claim 6,
A detection device, wherein the ledger reading operation and the ledger writing operation are performed on the same ledger object. The detection device according to claim 7,
Wherein the detecting unit detects whether the ledger operation includes the transaction uncertainty factor,
A detection device, comprising: determining whether a variable of the ledger has been corrected before the ledger writing operation and the ledger reading operation. An uncertainty factor detection method for smart contracts,
Analyzing the traversal path for the ledger operation of the smart contract; and detecting, for the traversal path, whether the ledger operation includes an uncertainty factor;
A detection method for expanding the traversal route when it is determined that the traversal route includes a branch structure. A computer-readable storage medium storing a program,
10. A storage medium for causing a computer to execute the detection method according to claim 9.

Images