WO2022100063A1

WO2022100063A1 - Method and apparatus for generating and storing logs of smart contract, device, and storage medium

Info

Publication number: WO2022100063A1
Application number: PCT/CN2021/096859
Authority: WO
Inventors: 代健武
Original assignee: 平安科技（深圳）有限公司
Priority date: 2020-11-16
Filing date: 2021-05-28
Publication date: 2022-05-19
Also published as: CN112419057A

Abstract

A method and apparatus for generating and storing logs of a smart contract, a device, and a storage medium. The method comprises: generating a log document of a smart contract; generating a first private key and a first public key matching the first private key; writing the first public key into the log document of the smart contract; generating a pair of second public key and second private key; generating a first shared key according to a first encryption algorithm, the first private key, and the second public key; encrypting original log content according to the first shared key and a second encryption algorithm to obtain encrypted log content; writing the encrypted log content into the log document of the smart contract; and storing the log document of the smart contract. The method improves the timeliness and accuracy of generation of the logs of the smart contract, and the generated first shared key used for encrypting the original log content is different, such that difficulty for an illegal user to crack the logs is greatly increased, and the security is improved.

Description

Log generation and storage method, device, device and storage medium for smart contracts

This application claims the priority of the Chinese patent application filed on November 16, 2020 with the application number 202011280585.9 and the invention titled "Method, Device, Equipment and Storage Medium for Log Generation and Storage of Smart Contracts", all of which The contents are incorporated herein by reference.

technical field

This application relates to the field of blockchain, and in particular, to a method, device, device and storage medium for log generation and storage of smart contracts.

Background technique

A smart contract is a computer protocol designed to disseminate, verify or execute contracts in an information-based manner. Smart contracts allow for trusted transactions without third parties that are traceable and irreversible. The logs generated during the testing or deployment of smart contracts are critical for developers. Developers usually need to use these logs to check for some problems in the smart contract development process. Therefore, generating logs of smart contracts and saving logs to ensure log security are also crucial steps.

The inventor found that the logs generated during the testing or deployment of the existing smart contracts need to be passed to the developers by the testers after the test is completed, which not only has the problems of inconvenient access, easy information lag, etc. Human errors such as confusion are often prone to occur when multiple similar development projects are involved. In addition, the log security is not good, and it is very easy for illegal persons to obtain it.

SUMMARY OF THE INVENTION

Based on this, it is necessary to provide a smart contract log generation and log generation method to solve the problems of inconvenient log acquisition, information lag, poor log security, and easy access by illegal persons during the log generation process of smart contracts. Preservation method, apparatus, computer equipment and storage medium.

A log generation and storage method for a smart contract, comprising:

Generate log files for smart contracts;

generating a first private key and a first public key matching the first private key;

Write the first public key into the log file of the smart contract;

generating a pair of the second public key and the second private key;

generating a first shared secret key according to the first encryption algorithm, the first private secret key and the second public secret key;

According to the first shared secret key and the second encryption algorithm, the original log content is encrypted to obtain the encrypted log content;

Write the encrypted log content to the log file of the smart contract;

Save the smart contract log file including the first public key and the encrypted log content.

A log generation and storage device for smart contracts, comprising:

The log document generation module is used to generate the log document of the smart contract;

a first generation submodule for generating a first private key and a first public key matching the first private key;

The first writing submodule is used to write the first public key into the log file of the smart contract;

The second generation submodule is used to generate a pair of the second public key and the second private key;

The third generating submodule is used to generate the first shared secret key according to the first encryption algorithm, the first private secret key and the second public secret key;

an encryption sub-module for encrypting the original log content to obtain the encrypted log content according to the first shared secret key and the second encryption algorithm;

The second writing submodule is used to write the encrypted log content into the log file of the smart contract;

The saving sub-module is used to save the smart contract log file including the first public key and the encrypted log content.

A computer device, comprising a memory and a processor, the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor executes a log generation and a smart contract. The steps of the preservation method, the steps of the log generation and preservation method of the smart contract executed by the processor, include:

Generate log files for smart contracts;

Write the first public key into the log file of the smart contract;

generating a pair of the second public key and the second private key;

generating a first shared key according to the first encryption algorithm, the first private key and the second public key;

Write the encrypted log content into the log file of the smart contract;

A storage medium storing computer-readable instructions, when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of a method for generating and saving a log of a smart contract, so that the The steps of the log generation and storage method of the smart contract executed by the processor include:

Generate log files for smart contracts;

Write the first public key into the log file of the smart contract;

generating a pair of the second public key and the second private key;

Write the encrypted log content into the log file of the smart contract;

The above-mentioned smart contract log generation and storage method, device, computer equipment and storage medium improve the timeliness and accuracy of smart contract log generation, and provide an effective solution for developers to obtain smart contract logs in a timely and accurate manner. The level is higher, and the log generation and acquisition results are no longer affected by factors such as personnel's subjectivity and mistakes; and since the first private key is generated according to the random function, the generated first shared secret key used to encrypt the original log content It is different, which greatly increases the difficulty of cracking by illegal users, thereby improving the protection of the logs of the smart contract, thus improving the security, and solving the problem of using the same key for encryption and decryption in the prior art, which has security Less technical issues.

Description of drawings

Fig. 1 is the flow chart of the log generation and preservation method of the smart contract provided in one embodiment;

2 is a flow chart of a smart contract pipeline provided in one embodiment;

3 is a detailed flow chart of a smart contract pipeline provided in another embodiment;

Fig. 4 is the flow chart of step S10 in the embodiment corresponding to Fig. 1;

Fig. 5 is the flow chart of step S20 in the embodiment corresponding to Fig. 1;

6 is a structural block diagram of a log generation and storage device of a smart contract in one embodiment;

FIG. 7 is a structural block diagram of a computer device in one embodiment.

Detailed ways

In order to make the purpose, technical solutions and advantages of the present application more clearly understood, the present application will be described in further detail below with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application, but not to limit the present application.

It will be understood that the terms "first", "second", etc. used in this application may be used herein to describe various elements, but these elements are not limited by these terms. These terms are only used to distinguish a first element from another element.

Smart contract sharing creation platform, including smart contract development platform, smart contract code management library, smart contract pipeline platform and smart contract test network.

The smart contract development platform includes user rights management, smart contract project management, smart contract development, review, approval, etc. Among them, the user rights management includes the user's access control to the smart contract development platform, the access control to the smart contract project, and the control of the development rights, audit rights and approval rights of specific smart contracts.

The smart contract code management library includes smart contract code management.

The smart contract pipeline platform includes a series of automated operations such as scanning, compiling, deploying, and testing smart contracts, as well as collecting, storing, and processing related information (such as status, results, logs, etc.) of these operations.

The smart contract test network is used to test smart contracts and simulate the real blockchain network.

Every time the smart contract code is updated, the webhook is triggered, and a pipeline execution request is initiated to the smart contract pipeline platform. The smart contract pipeline platform will generate a new pipeline execution ID for the smart contract, and maintain a pipeline execution history based on the pipeline execution ID, including the status, results and logs of each pipeline execution. The smart contract pipeline platform provides the following functions: query the pipeline execution history of the smart contract according to the smart contract ID; query the execution status and result of the pipeline according to the smart contract ID and its pipeline execution ID; query the pipeline execution status and results according to the smart contract ID and its pipeline execution ID; query Execution results of different stages of the pipeline, log.

The smart contract pipeline platform includes a smart contract scanning module, a smart contract compilation module, a smart contract deployment module and a smart contract testing module.

The smart contract scanning module is used to perform smart contract scanning operations and obtain smart contract scanning logs.

The smart contract compilation module is used to perform smart contract compilation operations and obtain smart contract compilation logs.

The smart contract deployment module is used to perform smart contract deployment operations and obtain smart contract deployment logs.

The smart contract testing module is used to perform smart contract testing operations and obtain smart contract testing logs.

The log generation and storage method for a smart contract according to an embodiment of the present application, as shown in Figure 1, includes the following steps:

S10. Generate a log document of the smart contract.

Specifically, after the smart contract pipeline starts running, it will perform automated operations such as scanning, compiling, deploying, and testing the smart contract, and merge the smart contract scanning log, smart contract compilation log, smart contract deployment log, and smart contract test log together. The logs that make up the smart contract.

The following describes the log generation process according to the different stages of the smart contract pipeline, as shown in Figures 2 to 4. Step S10 includes:

S101. Perform a smart contract scanning operation to obtain a smart contract scanning log.

Specifically, step S101 includes:

i. After the smart contract scanning module receives the smart contract scanning request, it records the scanning request log.

ii. Download the corresponding version of the smart contract from the smart contract code management library and record the download log.

iii. The smart contract scanning module executes the scanning task, records the scanning process log, and generates a scanning result report.

Executing the scanning task includes: reading the smart contract, persistently storing the smart contract and its execution status and execution result, and scanning the persistently stored smart contract with a preset scanning frequency and preset scanning time. The preset scan frequency and preset scan time can be set according to actual needs.

iv. The smart contract scanning module completes the recording of logs related to this scan, and uses the scan request log, the download log and the scan process log to form a smart contract scan log.

S102. Execute a smart contract compilation operation to obtain a smart contract compilation log.

Specifically, step S102 includes:

i. After the smart contract compilation module receives the smart contract compilation request, it starts to record the logs related to the compilation request;

ii. Download the corresponding version of the smart contract from the smart contract code management library, and record the download log;

iii. The smart contract compilation module analyzes the smart contract code, builds the corresponding compilation environment, performs compilation operations, records compilation logs and compilation results;

In some embodiments, the step of performing a compilation operation includes:

(1) Lexical analysis and syntax analysis: Parse the smart contract code into an abstract syntax tree, which is implemented using the Crystal macro mechanism. The code can be directly embedded in the Crystal code as a macro, or the abstract syntax tree can be directly input without using the macro language description. , but pass in the object directly in the form of a method call. Crystal is a compiled programming language with features including:

Ruby-like syntax, no need to specify variable types and method parameter types, callable C code, compile-time code simulation and generation, compiled into efficient native code.

(2) Semantic analysis: check whether the abstract syntax tree constitutes legal semantics (for example, whether the smart contract API parameter type is compliant), any wrong lexical and grammar will report a syntax error, not all abstract syntax trees are legal, Semantic analysis will check, and if the check fails, a semantic error will be triggered.

In some embodiments, the compilation environment may be a front-end browser environment; performing compilation operations, including:

Compile the C++ version of the compiler into an asm.js version file that supports the front-end browser environment and Node.js environment through Emscripten or other LLVM tools, and deploy all current Solidity compilers on domestic servers or CDN nodes. The official compiler warehouse of Fangfang regularly compares the version list and updates the latest compiler in time;

Input the source file into the compilation environment. Taking the Solidity source file as an example, the WASM format file of the latest and stable Solidity compiler is built into the browser script. Specifically: Compile the C++ version compiler through Emscripten or other LLVM tools into The WASM file in binary bytecode format supported by the browser, and then package the WASM file into the front-end script code through front-end packaging tools such as Webpack. The WASM format file can be run directly in the browser without interpretation by the browser script engine compile. Whether to use the built-in WASM file compiler is judged by the version number declared in the Solidity file in the browser. This compiler is used when the version matches correctly or the Solidity file does not declare a version number. Compile the smart contract file directly with the built-in WASM version of the Solidity compiler, and return the compilation result in the Javascript main thread; or dynamically add a script tag to the Javascript code to specify the src attribute as the path of the domestic server or CDN node, so as to pull The required Solidity compiler, at the same time, performs the compilation operation of the smart contract file in the Javascript sub-thread, and returns the compilation result to the main thread; when the Solidity file in the browser fails to match the WASM compiler file, the browser dynamically creates a script, Load the compiler version corresponding to the current Solidity file in the domestic server or CDN node, create a WebWorker sub-thread to compile the Solidity file, and return the compilation result to the JavaScript main thread, effectively preventing the JavaScript main thread from blocking.

If the compiler that needs to be pulled has not been downloaded when compiling the smart contract file, or the pulling fails, the source code will be sent to the Node.js back-end service through the client-server request, and the back-end service will send the source code to the Node.js back-end service. Compile the Solidity source code, and then return the compilation result to the front-end browser; specifically: synchronize all Solidity compilers in the domestic server or CDN node in the back-end Node.js, and periodically compare the compiler version list. Go and pull the latest Solidity compiler in the server. When the script is dynamically created in the browser to pull the compiler before the download is completed or fails, a client-server request will be temporarily sent to send the Solidity source file code to the Node.js service, and executed in the Node.js service Compile operation, return the compiled result to the browser side, and use the loaded compiler to perform the compilation operation after the compiler on the browser side is loaded.

iv. The smart contract compilation module stores the generated smart contract executable file according to the request ID, and records relevant logs;

v. The smart contract compilation module completes the log of this smart contract compilation request.

S103. Execute a smart contract deployment operation to obtain a smart contract deployment log.

Specifically, step S103 includes:

i. After the smart contract deployment module receives the smart contract deployment request, it starts to record the logs related to the deployment request.

ii. According to the request ID (identity document), obtain the corresponding smart contract executable file from the smart contract compilation module, and record the relevant logs.

iii. The smart contract deployment module sends smart contract deployment requests to each node of the smart contract test network, records relevant logs, and returns the deployment results, and obtains the corresponding deployment logs through the interface provided by the test network nodes.

iv. The smart contract deployment module finishes recording the logs related to this deployment request.

S104. Execute a smart contract test operation to obtain a smart contract test log.

Specifically, step S104 includes:

i. After the smart contract test module receives the smart contract test request, it starts to record the relevant logs of the test request;

ii. According to the test set (involving a series of smart contract execution operations and smart contract query operations), the smart contract test module sends smart contract test requests to each node of the smart contract test network in turn, records relevant logs and returns the test results, and passes the test The interface provided by the network node obtains the corresponding test log.

In some embodiments, the method for each node of the smart contract test network to test the smart contract includes:

(1) According to the smart contract to be tested, a calling interface corresponding to the smart contract is generated.

Usually, after the smart contract is written, the smart contract supports internal calls, but cannot be called externally. If you want to test the smart contract, you need to call and execute the smart contract through the external calling interface. In the embodiment of the present application, the smart contract testing module can automatically generate the corresponding calling interface according to the obtained smart contract, instead of obtaining the calling interface pre-written by the developer in the related art. In this way, for any smart contract to be tested, the calling interface can be automatically generated to realize the automatic processing of calling and testing.

(2) Query at least one account in the smart contract through the calling interface.

After the account information is called, at least one account required for the test can be queried from the account information. The number of the at least one account may be one or multiple. When the number of the at least one account is multiple, the multiple accounts may include user accounts and platform accounts.

(3) Generate a test case of the smart contract according to the at least one account.

After obtaining at least one account, a test case can be generated to trigger the smart contract and execute corresponding functions, so as to judge whether the smart contract can run correctly and whether the business logic of the smart contract is correct. This test case can be used to instruct asset transfers between accounts.

In some embodiments, the generation process of the test case can also be implemented by the target programming language, and the smart contract testing module can generate the test case of the target programming language, and then trigger the smart contract to execute the subsequent test steps. For example, the target programming language may be World Wide Web 3.java script (World Wide Web 3.javascript, Web3.js).

(4) Test the smart contract according to the test case.

After the test case is generated, the smart contract can be triggered to test the smart contract. The smart contract testing module may determine that the test result is abnormal in response to the test result of any test case being different from the expected result included in the test case. Correspondingly, the smart contract testing module may determine that the test result is normal in response to the test result of any test case being the same as the expected result included in the test case.

In some embodiments, the smart contract testing module can also generate a test report according to the test result of testing the smart contract, and subsequent relevant technical personnel can learn the situation of the smart contract according to the test report.

iii. The smart contract deployment module finishes recording the logs related to this test request.

The generated logs can be used for presentation, so that developers can obtain information about each stage of the pipeline. The display process is as follows:

a) When developers view the pipeline execution information of a smart contract, the smart contract development platform can query the pipeline execution history of the smart contract through the interface provided by the smart contract pipeline platform (including pipeline ID, pipeline execution time, pipeline execution status , pipeline execution results and other information), the execution history list can be displayed on the smart contract development platform.

b) When developers view the execution details of a certain pipeline, the smart contract development platform can query the execution information of different pipeline stages (scanning, compiling, deploying, and testing) through the interface provided by the smart contract pipeline platform (including the execution time of each stage). , execution status and execution result).

c) When the developer further checks the details of a pipeline stage, the smart contract development platform can query the execution log of the pipeline stage through the interface provided by the smart contract pipeline platform, related reports (such as scan reports, test reports), and more Multi-chain logs (such as smart contract deployment logs on test network nodes, smart contract execution logs, smart contract query logs, etc.).

S105. Combine the smart contract scan log, the smart contract compilation log, the smart contract deployment log, and the smart contract test log to generate a log file of the smart contract.

S20. Encrypt and save the log file of the smart contract obtained through step S10.

In some embodiments, step S20 includes:

S201. Generate a first private key.

A first private key is generated using a random function. For example, random functions such as rand and srand() can be used, which can be set according to actual needs, such as rounding, remainder, and logical operations.

S202. Generate a first public key matching the first private key.

The first public key is generated using a first encryption algorithm (eg RSA, DSA, ECC, DH). The first encryption algorithm requires two keys: a public key and a private key. The public key and the private key are a pair. If the data is encrypted with the public key, it can only be decrypted with the corresponding private key. For example, if the data is encrypted with the private key, only the corresponding public key can be used to decrypt the data. decrypt.

S203, write the first public key into the log file of the smart contract.

After generating the first public key and the first private key, the generated first public key is written into the log file of the smart contract, so as to obtain the first public key according to the log file of the smart contract.

In order to better mark the address of the first public key, the first public key can be saved according to a preset mark format, so as to facilitate obtaining the address of the first public key according to the log file of the smart contract.

The preset mark format can be a special mark or a number, for example, "*&!@&#" can be used, and when the above mark is read, the first public key can be obtained.

S204. Invoke the above-mentioned first encryption algorithm to generate a pair of second public key and second private key.

To improve security, a second private key can be generated based on the user device ID and device type.

S205. Generate a first shared key according to the first encryption algorithm, the first private key, and the second public key.

According to the first private key and the second public key, the first encryption algorithm is used to generate the first shared key. Taking the RSA first encryption algorithm as an example, generating the first shared key according to the first encryption algorithm, the first private key and the second public key includes:

Create the interface of the RSA first encryption algorithm; use the second public key as the first parameter of the RSA first encryption algorithm interface, and use the first private key as the second parameter of the RSA first encryption algorithm interface; call the RSA first encryption algorithm Algorithm interface to generate a secret key, which is used as the first shared secret key.

S206: Encrypt the original log content according to the first shared secret key and the second encryption algorithm to obtain encrypted log content.

After the first shared secret key is generated, the original log content may be encrypted according to the first shared secret key and the second encryption algorithm to generate encrypted log content. The second encryption algorithm is a preset encryption algorithm.

Specifically, the first shared secret key is the key value KEY that is finally used to encrypt the original log content.

S207, write the encrypted log content into the log file of the smart contract.

Specifically, when generating the log content, in order to facilitate the storage and analysis of the log content, the log content can be written into the log file of the smart contract, and the log file of the smart contract can be set according to the actual situation, such as data files, text files Wait.

S208. Save the smart contract log file including the first public key and the encrypted log content.

A second shared key is generated according to the first encryption algorithm, the second private key and the first public key, wherein the second shared key matches the first shared key.

The first private key is generated according to the random function, the first public key paired with the first private key is generated according to the first encryption algorithm, and then the first encryption algorithm, the first private key and the second public key are generated according to the first encryption algorithm. a shared secret key, and then encrypt the original log content according to the first shared secret key and the second encryption algorithm. Since the first private key is generated according to the random function, the generated first shared key used to encrypt the original log content is different, which greatly increases the difficulty of cracking by illegal users, thereby improving the protection of the logs of smart contracts Therefore, the security is improved, and the technical problem of using the same secret key for encryption and decryption in the prior art, which has low security, is solved.

In another embodiment, a log generation and storage device for smart contracts is provided, as shown in FIG. 6 , including:

The log document generation module 10 is used to generate the log document of the smart contract;

The encrypted storage sub-module 20 is used to encrypt and save the log of the smart contract obtained by the log document generation module.

The encrypted storage sub-module 20 includes:

The third generation submodule is used to generate the first shared secret key according to the first encryption algorithm, the first private secret key and the second public secret key;

In certain embodiments, the third generation sub-module includes:

A creation unit is used to create an interface of the RSA first encryption algorithm;

The parameter setting unit, the second public key is used as the first parameter of the RSA first encryption algorithm interface, and the first private key is used as the second parameter of the RSA first encryption algorithm interface;

The secret key generation unit is used for invoking the RSA first encryption algorithm interface to generate a secret key, and the secret key is used as the first shared secret key.

The log document generation module 10 includes an acquisition sub-module and a merge sub-module. The acquisition submodule is used to acquire smart contract scan logs, smart contract compilation logs, smart contract deployment logs, and smart contract test logs; the merge submodule is used to acquire smart contract scan logs, smart contract compilation logs, and smart contracts acquired by the submodule. The deployment log and the smart contract test log are combined to form the log file of the smart contract.

Get submodules include:

The scanning unit is used to perform smart contract scanning operations and obtain smart contract scanning logs;

The compilation unit is used to perform smart contract compilation operations and obtain smart contract compilation logs;

The deployment unit is used to perform smart contract deployment operations and obtain smart contract deployment logs;

The test unit is used to perform smart contract test operations and obtain smart contract test logs;

The scanning unit includes:

The download record subunit is used to download the corresponding version of the smart contract from the smart contract code management library according to the received smart contract scan request, and record the download log;

The scanning record subunit is used to perform the scanning task and record the scanning process log;

The scan construction subunit is used to form a smart contract scan log by using the download log and the scan process log.

Compilation units, including:

The compilation and download subunit is used to download the corresponding version of the smart contract from the smart contract code management library according to the received smart contract compilation request, and record the download log;

Compile and analyze the subunit, analyze the smart contract code, build the corresponding compilation environment, execute the compilation operation, record the compilation process log and compilation result;

The compilation and construction subunit is used to form a smart contract compilation log by using the download log, the compilation process log and the compilation result.

Deployment unit, including:

The deployment and acquisition sub-unit is used to acquire the smart contract executable file obtained by executing the smart contract compilation operation according to the received smart contract deployment request, and record the acquisition process log;

The sending and obtaining subunit is used to send the smart contract deployment request to each node of the smart contract test network, record the sending log and the returned deployment result, and obtain the corresponding deployment process log through the interface provided by the test network node;

The deployment construction sub-unit is used to use the acquisition process log, the sending log, the deployment result and the deployment process log to form the smart contract deployment log.

Test unit, including:

The test sending and obtaining sub-unit is used to send the smart contract test request to each node of the smart contract test network in turn according to the test set, record the sending log and the returned test result, and obtain the corresponding test process log through the interface provided by the test network node;

The test construction subunit is used to form a smart contract test log by using the sending log, the test result and the test process log.

In some embodiments, the scanning unit includes a sub-unit for performing a smart contract scanning operation, the sub-unit is specifically configured to read the smart contract, store the smart contract and its execution status and execution result to preset Scan frequency and preset scan time to scan stored smart contracts.

In some embodiments, the compiling unit includes a subunit for performing a smart contract compiling operation, and the subunit is specifically used for:

Parse the smart contract code into an abstract syntax tree;

checking whether the abstract syntax tree constitutes legal semantics;

If so, the check passes; if not, the check fails, triggering a semantic error.

In one embodiment, a computer device is proposed, the computer device comprising a memory, a processor and a computer program stored on the memory and executable on the processor, the processor executing the computer The program implements the steps of the log generation and storage method of the smart contract in the above-mentioned embodiments.

In one embodiment, a storage medium storing computer-readable instructions is provided. When the computer-readable instructions are executed by one or more processors, the one or more processors can implement the intelligence in the above-mentioned embodiments. The steps of the log generation and storage method of the contract.

Those of ordinary skill in the art can understand that the realization of all or part of the processes in the methods of the above embodiments can be accomplished by instructing relevant hardware through a computer program, and the computer program can be stored in a computer-readable storage medium, and the program is During execution, it may include the processes of the embodiments of the above-mentioned methods. Wherein, the aforementioned storage medium may be a non-volatile storage medium such as a magnetic disk, an optical disk, a read-only memory (Read-Only Memory, ROM), or a random access memory (Random Access Memory, RAM) or the like. The storage medium may be non-volatile or volatile.

The technical features of the above-described embodiments can be combined arbitrarily. For the sake of brevity, all possible combinations of the technical features in the above-described embodiments are not described. However, as long as there is no contradiction between the combinations of these technical features, All should be regarded as the scope described in this specification.

The above-mentioned embodiments only represent several embodiments of the present application, and the descriptions thereof are relatively specific and detailed, but should not be construed as a limitation on the scope of the patent of the present application. It should be pointed out that for those skilled in the art, without departing from the concept of the present application, several modifications and improvements can be made, which all belong to the protection scope of the present application. Therefore, the scope of protection of the patent of the present application shall be subject to the appended claims.

Claims

A log generation and storage method for a smart contract, including:

Generate log files for smart contracts;

generating a first private key and a first public key matching the first private key;

Write the first public key into the log file of the smart contract;

generating a pair of the second public key and the second private key;

generating a first shared key according to the first encryption algorithm, the first private key and the second public key;

According to the first shared secret key and the second encryption algorithm, the original log content is encrypted to obtain the encrypted log content;

Write the encrypted log content into the log file of the smart contract;

Save the smart contract log file including the first public key and the encrypted log content.
The method according to claim 1, wherein the first encryption algorithm is an RSA public key encryption algorithm; the first shared key is generated according to the first encryption algorithm, the first private key and the second public key include:

Create an interface for the RSA public key encryption algorithm;

The second public key is used as the first parameter of the RSA public key encryption algorithm interface, and the first private key is used as the second parameter of the RSA public key encryption algorithm interface;

Call the RSA public key encryption algorithm interface to generate a secret key, which is used as the first shared secret key.
The method according to claim 1, wherein the method for generating a log file of a smart contract comprises:

Perform a smart contract scan operation to obtain a smart contract scan log;

Execute the smart contract compilation operation to obtain the smart contract compilation log;

Execute smart contract deployment operations and obtain smart contract deployment logs;

Execute smart contract test operations and obtain smart contract test logs;

The smart contract scan log, the smart contract compilation log, the smart contract deployment log, and the smart contract test log are combined to generate a log file of the smart contract.
The method according to claim 3, wherein the performing a smart contract scanning operation to obtain a smart contract scanning log comprises:

According to the received smart contract scan request, download the corresponding version of the smart contract from the smart contract code management library, and record the download log;

Perform scanning tasks and record scanning process logs;

Using the download log and the scanning process log, a smart contract scanning log is formed.
The method according to claim 3, wherein the executing the smart contract compilation operation to obtain the smart contract compilation log comprises:

According to the received smart contract compilation request, download the corresponding version of the smart contract from the smart contract code management library, and record the download log;

Analyze the smart contract code, build the corresponding compilation environment, perform compilation operations, record compilation process logs and compilation results;

Using the download log, the compilation process log and the compilation result, a smart contract compilation log is formed.
The method according to claim 3, wherein the executing the smart contract deployment operation to obtain the smart contract deployment log comprises:

According to the received smart contract deployment request, obtain the smart contract executable file obtained by executing the smart contract compilation operation, and record the acquisition process log;

Send the smart contract deployment request to each node of the smart contract test network, record the sending log and the returned deployment result, and obtain the corresponding deployment process log through the interface provided by the test network node;

Use the acquisition process log, the sending log, the deployment result and the deployment process log to form a smart contract deployment log;

The execution of the smart contract test operation and the acquisition of the smart contract test log include:

According to the test set, send the smart contract test request to each node of the smart contract test network in turn, record the sending log and the returned test result, and obtain the corresponding test process log through the interface provided by the test network node;

Using the sending log, the test result and the test process log, a smart contract test log is formed.
The method according to claim 1, wherein the performing the smart contract scanning operation comprises: reading the smart contract, storing the smart contract and its execution status and execution result, and scanning the smart contract with a preset scanning frequency and a preset scanning time. The stored smart contract is scanned;

The performing smart contract compilation operation includes:

Parse the smart contract code into an abstract syntax tree;

checking whether the abstract syntax tree constitutes legal semantics;

If so, the check passes; if not, the check fails, triggering a semantic error.
A log generation and storage device for smart contracts, including:

The log document generation module is used to generate the log document of the smart contract;

a first generation submodule for generating a first private key and a first public key matching the first private key;

a first writing submodule, used to write the first public key into the log file of the smart contract;

The second generation submodule is used to generate a pair of the second public key and the second private key;

a third generating submodule, configured to generate a first shared secret key according to the first encryption algorithm, the first private key and the second public key;

an encryption submodule, configured to encrypt the original log content to obtain encrypted log content according to the first shared secret key and the second encryption algorithm;

The second writing submodule is used to write the encrypted log content into the log file of the smart contract;

The saving submodule is used to save the smart contract log file including the first public key and the encrypted log content.
A computer device, comprising a memory and a processor, the memory stores computer-readable instructions, and when the computer-readable instructions are executed by the processor, the processor executes a log generation and a smart contract. The steps of the preservation method, the steps of the log generation and preservation method of the smart contract executed by the processor, include:

Generate log files for smart contracts;

generating a first private key and a first public key matching the first private key;

Write the first public key into the log file of the smart contract;

generating a pair of the second public key and the second private key;

generating a first shared key according to the first encryption algorithm, the first private key and the second public key;

According to the first shared secret key and the second encryption algorithm, the original log content is encrypted to obtain the encrypted log content;

Write the encrypted log content into the log file of the smart contract;

Save the smart contract log file including the first public key and the encrypted log content.
The computer device according to claim 9, wherein the first encryption algorithm is an RSA public key encryption algorithm; The key generation first shared secret key includes:

Create an interface for the RSA public key encryption algorithm;

The second public key is used as the first parameter of the RSA public key encryption algorithm interface, and the first private key is used as the second parameter of the RSA public key encryption algorithm interface;

Call the RSA public key encryption algorithm interface to generate a secret key, which is used as the first shared secret key.
The computer device according to claim 9, wherein the method of generating a log file of a smart contract executed by the processor comprises:

Perform a smart contract scan operation to obtain the smart contract scan log;

Execute the smart contract compilation operation to obtain the smart contract compilation log;

Execute smart contract deployment operations and obtain smart contract deployment logs;

Execute smart contract test operations and obtain smart contract test logs;

The smart contract scan log, the smart contract compilation log, the smart contract deployment log, and the smart contract test log are combined to generate a log file of the smart contract.
The computer device according to claim 11, wherein the executing the smart contract scanning operation performed by the processor to obtain the smart contract scanning log comprises:

According to the received smart contract scan request, download the corresponding version of the smart contract from the smart contract code management library, and record the download log;

Perform scanning tasks and record scanning process logs;

Using the download log and the scanning process log, a smart contract scanning log is formed.
The computer device according to claim 11, wherein the executing the smart contract compilation operation performed by the processor to obtain the smart contract compilation log comprises:

According to the received smart contract compilation request, download the corresponding version of the smart contract from the smart contract code management library, and record the download log;

Analyze the smart contract code, build the corresponding compilation environment, perform compilation operations, record compilation process logs and compilation results;

Using the download log, the compilation process log and the compilation result, a smart contract compilation log is formed.
The computer device according to claim 11, wherein the executing smart contract deployment operation performed by the processor to obtain a smart contract deployment log comprises:

According to the received smart contract deployment request, obtain the smart contract executable file obtained by executing the smart contract compilation operation, and record the acquisition process log;

Send the smart contract deployment request to each node of the smart contract test network, record the sending log and the returned deployment result, and obtain the corresponding deployment process log through the interface provided by the test network node;

Use the acquisition process log, the sending log, the deployment result and the deployment process log to form a smart contract deployment log;

The execution of the smart contract test operation and the acquisition of the smart contract test log include:

According to the test set, send the smart contract test request to each node of the smart contract test network in turn, record the sending log and the returned test result, and obtain the corresponding test process log through the interface provided by the test network node;

Using the sending log, the test result and the test process log, a smart contract test log is formed.
A storage medium storing computer-readable instructions, when the computer-readable instructions are executed by one or more processors, the one or more processors execute the steps of a method for generating and saving a log of a smart contract, so that the The steps of the log generation and storage method of the smart contract executed by the processor include:

Generate log files for smart contracts;

generating a first private key and a first public key matching the first private key;

Write the first public key into the log file of the smart contract;

generating a pair of the second public key and the second private key;

generating a first shared key according to the first encryption algorithm, the first private key and the second public key;

According to the first shared secret key and the second encryption algorithm, the original log content is encrypted to obtain the encrypted log content;

Write the encrypted log content into the log file of the smart contract;

Save the smart contract log file including the first public key and the encrypted log content.
The storage medium according to claim 15, wherein the first encryption algorithm is an RSA public key encryption algorithm; The key generation first shared secret key includes:

Create an interface for the RSA public key encryption algorithm;

The second public key is used as the first parameter of the RSA public key encryption algorithm interface, and the first private key is used as the second parameter of the RSA public key encryption algorithm interface;

Call the RSA public key encryption algorithm interface to generate a secret key, which is used as the first shared secret key.
The storage medium according to claim 15, wherein the method of generating a log file of a smart contract executed by the processor comprises:

Perform a smart contract scan operation to obtain a smart contract scan log;

Execute the smart contract compilation operation to obtain the smart contract compilation log;

Execute smart contract deployment operations and obtain smart contract deployment logs;

Execute smart contract test operations and obtain smart contract test logs;

The smart contract scan log, the smart contract compilation log, the smart contract deployment log, and the smart contract test log are combined to generate a log file of the smart contract.
The storage medium according to claim 17, wherein the executing the smart contract scanning operation performed by the processor to obtain the smart contract scanning log comprises:

According to the received smart contract scan request, download the corresponding version of the smart contract from the smart contract code management library, and record the download log;

Perform scanning tasks and record scanning process logs;

Using the download log and the scanning process log, a smart contract scanning log is formed.
The storage medium according to claim 17, wherein the executing the smart contract compilation operation performed by the processor to obtain the smart contract compilation log comprises:

According to the received smart contract compilation request, download the corresponding version of the smart contract from the smart contract code management library, and record the download log;

Analyze the smart contract code, build the corresponding compilation environment, perform compilation operations, record compilation process logs and compilation results;

Using the download log, the compilation process log and the compilation result, a smart contract compilation log is formed.
The storage medium according to claim 17, wherein the executing the smart contract deployment operation performed by the processor to obtain the smart contract deployment log comprises:

According to the received smart contract deployment request, obtain the smart contract executable file obtained by executing the smart contract compilation operation, and record the acquisition process log;

Send the smart contract deployment request to each node of the smart contract test network, record the sending log and the returned deployment result, and obtain the corresponding deployment process log through the interface provided by the test network node;

Use the acquisition process log, the sending log, the deployment result and the deployment process log to form a smart contract deployment log;

The execution of the smart contract test operation and the acquisition of the smart contract test log include:

According to the test set, send the smart contract test request to each node of the smart contract test network in turn, record the sending log and the returned test result, and obtain the corresponding test process log through the interface provided by the test network node;

Using the sending log, the test result and the test process log, a smart contract test log is formed.