WO2020082917A1

WO2020082917A1 - Methods and systems for publishing programming problem, publishing solution code, and checking solution code

Info

Publication number: WO2020082917A1
Application number: PCT/CN2019/104897
Authority: WO
Inventors: 杨达一
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2018-10-26
Filing date: 2019-09-09
Publication date: 2020-04-30
Also published as: CN109345392A; CN109345392B; TWI706252B; TW202016778A

Abstract

Methods and systems for publishing a programming problem, publishing solution code, and checking solution code. A device from any IT organization may access a blockchain network as a node. In the blockchain network, any node may, on the basis of a blockchain protocol, publish a programming problem created by said node, which is to say, any node may establish a problem publishing transaction on the basis of a programming problem created by said node, and then broadcast the problem publishing transaction to other nodes. Every node receiving the problem publishing transaction will, on the basis of a consensus mechanism between the nodes, write the problem publishing transaction into the blockchain.

Description

Programming problem release, answer code release, answer code verification method and system

Technical field

The embodiments of the present specification relate to the field of information technology, and in particular, to a method and system for issuing programming questions, issuing answer codes, and verifying answer codes.

Background technique

At present, many information technology (IT) institutions at home and abroad (such as colleges and universities, computer schools, IT companies, etc.) generally build their own programming question bank for testing users (such as school students, on-the-job employees, interviewers Etc.) programming level.

In practice, many IT organizations have a need to share each other's programming question banks. However, for any IT organization, how to prevent other IT organizations from modifying the programming problems created by the IT organization without authorization is a technical problem to be solved.

Summary of the invention

In order to solve the problem that programming problems shared by any IT organization to other IT organizations are easily modified by other IT organizations, the embodiments of this specification provide a method and system for publishing programming problems. In addition, the embodiments of the present specification also provide a method and system for issuing answer codes and checking answer codes.

The above technical solutions are as follows:

According to the first aspect of the embodiments of the present specification, there is provided a blockchain-based programming topic publishing method, including:

The target node creates a programming topic to be released; the target node is any node in the blockchain network;

The target node constructs a topic publishing transaction based on topic related data, and broadcasts the topic publishing transaction to the blockchain network; the topic related data includes the programming topic;

For each node that obtains the topic release transaction, the node writes the topic release transaction into the blockchain based on the consensus mechanism between the nodes.

According to the second aspect of the embodiments of the present specification, a blockchain-based solution code issuing method is provided, including:

The target node obtains the programming topic; the target node is any node in the blockchain network, and the programming topic is issued through the method of the first aspect above;

The target node provides the programming problem to the tested user for answering, and receives the answer code uploaded by the tested user;

The target node constructs an answer release transaction based on the answer-related data, and broadcasts the answer release transaction to the blockchain network; the answer-related data includes the title identification of the programming topic, the answer code, and the The user ID of the tested user;

For each node that obtains the answer release transaction, the node writes the answer release transaction into the blockchain based on the consensus mechanism between the nodes.

According to a third aspect of the embodiments of this specification, a method for verifying a solution code based on a blockchain is provided, including:

The obtaining module obtains the answer code corresponding to the programming question and the user ID of the user under test uploading the answer code; the programming question is issued through the method of the first aspect above, and the answer code is through the second aspect above Issued by the method, the verification node is a node in the blockchain network that stores the solution verification data corresponding to the programming problem;

The verification node uses the stored solution verification data corresponding to the programming problem to verify the solution code;

If the verification passes, the verification node constructs a result publishing transaction based on the result-related data, and broadcasts the result publishing transaction to the blockchain network; User identification

For each node that obtains the result publishing transaction, the node writes the result publishing transaction into the blockchain based on the consensus mechanism between the nodes.

According to a fourth aspect of the embodiments of the present specification, there is provided a blockchain-based programming topic publishing system, including a blockchain network composed of multiple nodes;

Any node creates a programming topic to be released; based on the data related to the topic, constructs a topic release transaction, and broadcasts the topic release transaction to the blockchain network, and the topic related data includes the programming topic;

Each node that obtains the topic release transaction writes the topic release transaction into the blockchain based on the consensus mechanism between the nodes.

According to a fifth aspect of the embodiments of the present specification, there is provided a blockchain-based solution code issuing system, including a blockchain network composed of multiple nodes;

Get a programming question at any node; the target node is any node in the blockchain network, and the programming question is issued through the method of the first aspect above; provide the programming question to the tested user for answering , And receive the answer code uploaded by the tested user; based on the answer-related data, construct an answer release transaction, and broadcast the answer release transaction to the blockchain network; wherein, the answer-related data includes the programming topic Title identification, the answer code and the user identification of the tested user;

Each node that obtains the answer release transaction writes the answer release transaction into the blockchain based on the consensus mechanism between the nodes.

According to a sixth aspect of the embodiments of the present specification, there is provided a blockchain-based solution code verification system, including a blockchain network composed of multiple nodes;

Check the node to obtain the answer code corresponding to the programming question and the user ID of the user under test who uploaded the answer code. The programming question was issued through the method of the first aspect above, and the answer code was passed through the second aspect above Issued by the method, the verification node is a node in the blockchain network that stores the solution verification data corresponding to the programming problem; use the stored solution verification data corresponding to the programming problem to verify the solution code; if If the test passes, the result release transaction is constructed based on the result-related data, and the result release transaction is broadcast to the blockchain network; wherein, the result-related data includes the title identification of the programming topic and the user identification;

Each node that obtains the result publishing transaction writes the result publishing transaction into the blockchain based on the consensus mechanism between the nodes.

In the technical solution provided by the embodiments of this specification, the equipment of any IT organization can be connected to the blockchain network and called a node. In a blockchain network, any node can publish a programming topic created by itself based on the blockchain protocol, that is, any node can build a topic publishing transaction based on the programming topic created by itself, and then broadcast the topic publishing transaction to Other nodes. Each node that obtains the topic release transaction will write the topic release transaction into the blockchain based on the consensus mechanism among the nodes. In this way, on the one hand, any IT organization can share the programming problems created by itself to other IT organizations; on the other hand, the process for any node to issue programming problems is restricted by the blockchain protocol, and the programming problems are created from being created to being During the entire process of writing to the blockchain, it is difficult to be tampered with. After the programming problem is written to the blockchain, it is also difficult to be tampered with.

In addition, in the embodiment of the present specification, any node may extract programming questions from the programming questions shared among the nodes and provide the tested user with answers to test the programming level of the tested user. In addition, the answer code uploaded by the tested user will also be encapsulated into the answer release transaction and written to the blockchain for publicity.

In addition, in the embodiment of this specification, for any node, if the node stores the answer verification data corresponding to a programming problem, then the node can also perform the answer code given by the user under test for the programming problem. Check to determine whether the user under test passes the test. In addition, if the tested user passes the test, the node will also construct the result release transaction and broadcast it, so that the message of the tested user passing the test will be written into the blockchain for publicity.

It can be seen that the present invention actually provides a blockchain-based programming proficiency testing solution, which includes the stages of programming problem release, code answering release, and code answering verification. The answer records and the results of the tested users passing the test are written on the blockchain for publicity, making the entire programming level test process open and transparent.

It should be understood that the above general description and the following detailed description are only exemplary and explanatory, and do not limit the embodiments of this specification.

In addition, any one of the embodiments of this specification does not need to achieve all the above-mentioned effects.

BRIEF DESCRIPTION

In order to more clearly explain the embodiments of the present specification or the technical solutions in the prior art, the following will briefly introduce the drawings required in the embodiments or the description of the prior art. Obviously, the drawings in the following description are only These are some of the embodiments described in the embodiments of this specification, and those of ordinary skill in the art can also obtain other drawings based on these drawings.

FIG. 1 is a schematic flowchart of a method for publishing a programming topic based on a blockchain provided by an embodiment of this specification;

2 is a schematic flowchart of a method for issuing a solution code based on a blockchain provided by an embodiment of this specification;

FIG. 3 is a schematic flowchart of a method for verifying a solution code based on a blockchain provided by an embodiment of this specification;

4 is a schematic flowchart of a parallel method for executing a blockchain transaction provided by an embodiment of this specification;

5 is a schematic diagram of a serialized transaction execution method in the prior art;

6 is a schematic diagram of a parallel transaction execution method provided by an embodiment of this specification;

FIG. 7 also provides a block diagram of a block-based programming issue issuing device according to an embodiment of this specification;

FIG. 8 also provides a block diagram of a block-based solution code issuing device corresponding to the embodiment of this specification;

FIG. 9 also provides a structural schematic diagram of an answer code verification device based on a blockchain corresponding to an embodiment of this specification;

10 is a schematic flowchart of a programming level test system based on blockchain provided by an embodiment of this specification;

FIG. 11 is a schematic structural diagram of a computer device for configuring the method of the embodiment of the present specification.

detailed description

Here, the business scenario (ie, programming level test) applied by the present invention will be described in more detail first. Taking information technology company A as an example, if company A wants to understand the programming level of a certain user (eg, employee, interviewer), then company A can extract any programming topic from its programming question bank and provide it to the user. The user answers according to the programming question, gives an answer code to answer the programming question, and uploads the answer code to company A's online judgment system. Company A's online judgment system stores the answer test data (specifically, standard input data and standard output data) corresponding to each programming question in the above programming question bank, which is used to verify the correctness of the answer code. Specifically, the online question judgment system of Company A will input the standard input data corresponding to the programming question into the answer code and run the answer code, and then determine whether the answer code can output the standard output data corresponding to the programming question. The user passed the test, otherwise, the user is deemed to have failed the test.

In practice, many IT organizations have a need to share each other's programming question banks. For this reason, in the prior art, for any IT organization, the IT organization generally uses a crawler program to crawl programming questions from the programming question bank of other IT institutions, and provides the crawled programming questions to the tested user for answers. Then, the IT institution also needs to send the answer code given by the tested user to the online question-finding system of the IT institution that created the programming question for verification.

However, this approach has the following disadvantages:

1. After the IT organization crawls the programming problems of other IT organizations through the crawler program, sometimes it will make some inappropriate modifications to the programming problem without authorization. This aspect cannot protect the rights and interests of the IT organization that created the programming problem. On the other hand , The answer code given by the tested user for the modified programming problem often does not match the modified programming problem, and the online judgment system uses the answer test data adapted to the modified programming problem to test whether the code is correct As such, the test results cannot accurately reflect the programming level of the user under test.

2. Once the databases of other IT organizations are inaccessible, the IT organization cannot crawl other programming topics through the crawler program. In other words, this way of sharing programming topics is not always effective.

For this reason, in the embodiment of this specification, any IT organization can use the blockchain protocol to publish the programming problems created by itself to the blockchain, which is equivalent to sharing the programming problems created by itself to other IT organizations. There is no need to worry that other IT organizations will modify the programming topic.

In order to enable those skilled in the art to better understand the technical solutions in the embodiments of the present specification, the technical solutions in the embodiments of the present specification will be described in detail in conjunction with the drawings in the embodiments of the present specification. Obviously, the described implementation Examples are only a part of the embodiments of this specification, but not all the embodiments. Based on the embodiments in this specification, all other embodiments obtained by those of ordinary skill in the art should fall within the scope of protection.

The technical solutions provided by the embodiments of this specification will be described in detail below in conjunction with the drawings.

FIG. 1 is a schematic flowchart of a blockchain-based programming topic publishing method provided by an embodiment of this specification, including the following steps:

S100: The target node creates a programming problem to be released.

In the embodiment of this specification, the equipment of each IT organization can be connected to the blockchain network and become a node in the blockchain network. That is to say, each node in the blockchain network corresponds to each IT organization that wants to share programming issues with each other.

In step S100, the target node may be any node in the blockchain network. That is to say, the equipment of any IT organization can create and publish programming problems through the method shown in FIG. 1.

It should be noted that the target node creates a programming problem, which may specifically be that the target node receives a programming problem uploaded by an IT institution that controls the target node, or the target node may automatically create a programming problem according to a preset programming model.

S102: The target node constructs a topic release transaction based on topic related data.

It should be noted that the transaction described in this article refers to the data structure specified in the blockchain protocol. In the blockchain protocol, a transaction refers to a node that is created by the installed blockchain client and needs to finally write a piece of data on the blockchain. In other words, according to the blockchain protocol, all data that needs to be written into the blockchain for publicity needs to be encapsulated into a transaction data structure.

In step S102, the topic-related data includes at least the programming topic created by the target node in step S100. The target node constructs a topic release transaction based on the topic-related data, and actually encapsulates the topic-related data into a transaction, a data structure specified by the blockchain protocol.

S104: The target node broadcasts the topic release transaction to the blockchain network.

In step S104, the target node broadcasts the topic publishing transaction to the blockchain network, in fact, broadcasting the topic publishing transaction to other nodes, which is equivalent to sharing the programming topic to other nodes.

S106: For each node that obtains the topic publishing transaction, the node writes the topic publishing transaction into the blockchain based on the consensus mechanism between the nodes.

For each node that obtains the topic publishing transaction, the node can verify the legality of the topic publishing transaction before writing the topic publishing transaction into the blockchain.

The items for verifying the legality of the issue publishing transaction can be specified according to business needs. For example, assuming that not every node has the authority to publish programming topics, it is possible to publish the node identifier in the title issue transaction to determine whether the node corresponding to the node identifier (ie, the target node) has the authority to issue programming topics If there is no authority, it refuses to write the issue publishing transaction into the blockchain.

In step S106, the consensus mechanism between each node ensures the consistency of the data written by each node to the blockchain each time. Therefore, even if a node modifies the programming topic encapsulated in the topic publishing transaction without authorization, thereby changing the content of the topic publishing transaction, the modified topic publishing transaction will not be written into the blockchain by most nodes.

In this way, the programming problems created by the target node can always be written into the blockchain without modification, so as to complete the sharing of programming problems. In addition, the distributed storage feature of the blockchain is difficult to be tampered with.

It should be noted that, for the answer release transaction and result release transaction that will appear later, for the same reason, the content of these transactions is also difficult to be tampered with.

Through the method shown in Figure 1, any IT organization's equipment can access the blockchain network called a node. In a blockchain network, any node can publish a programming topic created by itself based on the blockchain protocol, that is, any node can build a topic publishing transaction based on the programming topic created by itself, and then broadcast the topic publishing transaction to Other nodes. Each node that obtains the topic release transaction will write the topic release transaction into the blockchain based on the consensus mechanism among the nodes. In this way, on the one hand, any IT organization can share the programming problems created by itself to other IT organizations; on the other hand, the process for any node to issue programming problems is restricted by the blockchain protocol, and the programming problems are created from being created to being During the entire process of writing to the blockchain, it is difficult to be tampered with. After the programming problem is written to the blockchain, it is also difficult to be tampered with.

In addition, in the embodiment of the present specification, the topic-related data may further include the node identifier of the target node. This means that the target node will also encapsulate its own node ID into the topic release transaction, and then write it into the blockchain for publicity. In this way, it is possible to clearly share the creator of each programming topic of each IT organization, and protect the rights and interests of the IT organization that created the programming topic.

In addition, in practical applications, due to the complexity of the data storage method such as blockchain, the operation of the node is more complicated when it wants to retrieve a programming problem from the programming problems written in the blockchain.

For this reason, in the embodiment of the present specification, for each node that obtains the topic issue transaction, the node may create a topic storage address and store the topic-related data in the topic storage address. This is equivalent to storing programming topics in a simple storage manner. It should be noted that if a transaction is issued for any topic, the transaction can be issued based on the topic written in the blockchain to verify whether the programming topic stored in the topic storage address has been tampered with. In the above way, the node can be more convenient when it wants to call up a programming topic.

Further, the node may specifically store the title smart contract encapsulated with the title-related data in the title storage address. In this case, the title storage address is actually the contract identifier of the title smart contract.

Smart contracts are data structures that are naturally supported by many blockchain protocols (such as Ethereum), and many blockchain protocols also naturally support the rapid invocation of smart contracts. Therefore, it is possible to store programming topics in the form of a data structure such as a smart contract, which is convenient for subsequent retrieval of programming topics for programming level testing by calling a smart contract.

According to the method for publishing programming questions shown in FIG. 1, the embodiment of this specification further provides a method for issuing answer codes based on blockchain. As shown in FIG. 2, it includes the following steps:

S200: The target node obtains the programming problem.

The target node is any node in the blockchain network. In practical applications, when any IT organization wants to test the programming level of the user under test, it can trigger a target node controlled by itself to obtain programming problems. The programming topic acquired by the target node is issued based on the programming topic release method shown in FIG. 1.

Specifically, the target node can read the programming topic from any topic publishing transaction in the blockchain.

Or, if the topic-related data packaged by the topic publishing exchange is also stored in a topic storage address, then the target node may also obtain the programming topic from the topic storage address. When using this method to obtain programming topics, it is faster.

Further, if the topic-related data is stored in the topic storage address in the form of a smart contract (that is, a topic smart contract), the target node can call the topic smart contract to obtain the programming topic.

S202: The target node provides the programming problem to the tested user for answering, and receives the answer code uploaded by the tested user.

S204: The target node constructs an answer release transaction based on the answer-related data.

In the embodiment of the present specification, the solution-related data includes at least the title identification of the programming topic, the solution code, and the user identification of the user under test.

Wherein, if the target node reads the programming topic from any topic publishing transaction in the blockchain, the topic identification of the programming topic is the transaction hash of the topic publishing transaction; if the target node If a program storage address is used to obtain a programming problem, the problem of the programming problem is identified as the storage address.

Further, the target node may check whether there is a compilation or running problem in the answer code. If the check passes, the answer release transaction will be constructed. If the check fails, the answer release transaction will be rejected.

S206: The target node broadcasts the solution release transaction to the blockchain network.

S208: For each node that obtains the answer release transaction, the node writes the answer release transaction into the blockchain based on the consensus mechanism between the nodes.

For each node that obtains the answer release transaction, the node may verify the validity of the answer release transaction before writing the answer release transaction into the blockchain.

The matters for verifying the legality of the answering issue transaction can be specified according to business needs. For example, assuming that the format of the answer code is specified in advance, the format of the answer code in the answer publishing transaction can be verified, and if the format does not meet the requirements, the answer publishing transaction is refused to be written into the blockchain.

In step S208, it is equivalent to publicize to each node the identity information of the tested user, the identification information of the programming question answered by the tested user, and the answer code given by the tested user.

In addition, in order to facilitate the node to quickly retrieve the answer code of the user under test for verification, in the embodiment of this specification, each node may also create a solution storage address, and store the solution-related data in the solution storage address.

Further, each node may store a solution smart contract encapsulated with the solution-related data in the solution storage address.

According to the method for issuing programming questions shown in FIG. 1 and the method for issuing answer codes shown in FIG. 2, the embodiment of this specification further provides a method for verifying the answer codes based on blockchain.

S300: The verification node obtains the answer code corresponding to the programming problem and the user identification of the user under test who uploaded the answer code.

In the embodiment of the present specification, the verification node stores a node that answers verification data corresponding to the programming problem. The answer verification data is data for verifying the correctness of the answer code given to answer the programming problem. As mentioned above, the solution verification data generally includes standard input data and standard output data.

The verification node is generally a node that creates the programming problem. Of course, the node that created the programming problem may also distribute the solution verification data corresponding to the programming problem to at least one other node. In this way, the verification node may be another node that stores the solution verification data in addition to the node that created the programming problem.

In the embodiment of the present specification, the verification node may determine the question identification corresponding to the answer test data based on any stored answer test data. Then, from the query in the blockchain, a solution publishing transaction containing the title identification is found, and the solution code and the user identification are read from the solution publishing transaction.

Further, the verification node may also query the solution storage address where the question identification is stored, and obtain the solution code and the user identification from the solution storage address.

Furthermore, the verification node may query a topic smart contract encapsulated with the topic identification, and call the topic smart contract to obtain the corresponding answer code and user identification.

S302: The verification node verifies the solution code using the stored solution verification data corresponding to the programming problem.

S304: If the verification is passed, the verification node constructs a result release transaction based on the result-related data.

In the embodiment of the present specification, if the verification node passes the answer code verification, it can publish the message of the verification to the blockchain. In this case, the result-related data actually includes the title ID of the programming topic and the user ID. The meaning of the result release transaction is, for example, "user Zhang San answered the correct topic 1".

Further, if the verification node fails the verification of the answer code, it may also publish the message that the verification failed on the blockchain. In this case, the result release transaction may mean that the test passed or failed. In order to distinguish, the result-related data also needs to include a test passed result or a test failed result.

S306: Broadcast the result release transaction to the blockchain network.

S308: For each node that obtains the result publishing transaction, the node writes the result publishing transaction into the blockchain based on the consensus mechanism between the nodes.

For each node that obtains the result publishing transaction, the node may verify the validity of the result publishing transaction before writing the topic publishing transaction into the blockchain.

The matters for verifying the legality of the transaction for issuing the result can be specified according to business needs. For example, assuming that only the node that created the programming topic has the authority to verify the answer code corresponding to the programming topic, it can be determined whether the verification node that broadcasts the result release transaction has the verification authority. The results are published and the transaction is written to the blockchain.

In step S308, it is equivalent to publicize to each node the identity information of the tested user, the identification information of the programming question answered by the tested user, and the result of whether the tested user passed the test.

In addition, in order to facilitate the node to quickly retrieve the test result of the user under test for reference, in the embodiment of this specification, each node may also create a result storage address and store the result-related data in the result storage address.

Further, each node may store the result smart contract encapsulated with the result related data in the result storage address.

In addition, in practice, the user under test may answer more than one programming question and upload more than one answer code. In this case, for each node, the node can store the results of the tested user in solving multiple programming problems into the same result storage address, which is convenient for statistics and reference.

Specifically, in the embodiment of this specification, for each node that obtains the result publishing transaction, if the node obtains other result publishing transactions associated with the result publishing transaction, it is based on the consensus mechanism between the nodes, The other result publishing transaction is written into the blockchain, wherein the other result publishing transaction is constructed based on the user identification and other topic identifications. Then, the node issues a transaction based on the other results, and stores the other topic identifiers in the result storage address.

That is to say, the result publishing transaction can be regarded as generated by the first programming question answered by the tested user, and the other result publishing transaction can be regarded as generated by other programming questions subsequently answered by the tested user . For the results of other programming problems that the tested user will subsequently answer, there is no need to recreate the result storage address for storage, but directly store it in the previously created result storage address.

In this way, each user under test has a unique storage address corresponding to his own, which is used to record his / her answers.

In addition, it should be noted that, in the method shown in FIG. 1, there may be cases where more than one check node checks the problem-solving code. In this case, for each verification node, the verification node obtains the answer code corresponding to the programming question and the user ID of the user under test uploading the answer code; then uses the stored answer verification data corresponding to the programming question, Verify the answer code; if the answer code is verified, construct a result release transaction based on the result-related data, and broadcast the result release transaction to the blockchain network.

Based on this, for each node, when the node determines that the number of obtained result publishing transactions is the specified number, it will write any obtained result publishing transactions into the blockchain based on the consensus mechanism between the nodes. Wherein, the specified number is not greater than the number of inspection nodes.

In addition, in the embodiment of the present specification, there are three types of transactions, namely, a topic issue transaction, an answer issue transaction, and a result issue transaction. Among them, for any type of transaction, creating a storage address and storing relevant data encapsulated by that type of exchange can be regarded as an execution operation for that type of transaction.

Obviously, no matter what kind of transaction is mentioned above, the execution result of executing such a transaction will only affect one storage address. Therefore, the three types of transactions in the embodiments of this specification are suitable for execution using the parallel transaction execution method given below. The following will introduce and explain this parallel transaction execution method.

For common blockchain application scenarios, when consensus among nodes is required, each node will elect a node that has the authority to package several pending transactions into blocks based on the consensus algorithm, that is, an accounting node. After consensus, the accounting node takes a number of transactions to be executed from the cache and packages them into blocks, and broadcasts the blocks to other nodes. Then, for each node, on the one hand, the node will execute each transaction in turn from the first to the last in accordance with the order in which the transactions in the block were initiated, and on the other hand, the block will be written to the blockchain .

Generally, the method of executing each transaction in the block one by one from first to second is called a serialized transaction execution method. The reason why this serialized transaction execution method is adopted is that in common blockchain application scenarios, the execution of a transaction sometimes updates the information stored on more than one storage address. If serialization is not used In the form of transaction execution, it is easy for some transactions to fail.

However, in some blockchain application scenarios, there are no transactions that update information stored on more than one storage address. In these blockchain application scenarios, adopting the above serialized transaction execution method will result in lower transaction execution efficiency.

The following uses a blockchain protocol such as Ethereum as an example to explain in detail the reasons for the serialized transaction execution method. It is worth emphasizing that in other blockchain protocols besides Ethereum, the reasons for using serialized transaction execution methods are similar.

In Ethereum, there are external accounts and contract accounts. The external account is used to store the user's Ether balance, and the external account is essentially a storage address where the balance information is stored. The contract account is used to store the smart contract created by the user. The contract account is essentially a storage address where the smart contract code is stored.

In Ethereum, there are generally two types of transactions, namely, transfer transactions from external accounts to other accounts (which can be external accounts or contract accounts), and contract creation transactions for external account creation contract accounts.

The execution of transfer transactions generally updates information stored on more than one storage address. Specifically, the execution of a transfer transaction usually changes the balance of the two accounts (that is, the balance information stored on the two account addresses), that is, the transfer amount is deducted from the balance of the transfer account and added to the balance of the collection account Increase the transfer amount. The premise of a transfer transaction is that the balance of the transfer account is not less than the transfer amount.

In practical applications, the transfer account in a certain transfer transaction (denoted as transfer transaction A) may be the collecting user in another previous transfer transaction (denoted as transfer transaction B). If the transaction is not executed in the order in which the transaction was initiated, then the following situation may occur, that is, the transfer transaction B has not been executed, resulting in the transfer account in the transfer transaction A not having sufficient balance for the transfer. Because of this, all blockchain application scenarios involving transfer transactions have to adopt serialized transaction execution methods to ensure that transactions can be executed smoothly.

The execution of the contract creation transaction is actually creating a contract account, that is, creating a storage address, and storing the smart contract code in the created storage address. Obviously, the execution of the contract creation transaction will only affect one storage address.

In addition, blockchain application scenarios are diverse. In some blockchain application scenarios, it can be expanded based on Ethereum to develop new types of transactions. The execution of such transactions may only affect one storage address. . For example, the use of blockchain for content certification. The execution of a deposit transaction is essentially to create a storage address and store the content to be deposited into the created storage address.

Based on the above, this paper proposes a method for parallel execution of blockchain transactions, specifically for a certain type of blockchain application scenarios. In this type of blockchain scenario, the execution result of each transaction will only affect one storage address. .

FIG. 4 is a schematic flowchart of a method for executing a blockchain transaction in parallel provided by an embodiment of the present specification, including the following steps:

S400: For each node in the blockchain network, the node obtains the block to be written.

In the embodiment of the present specification, after the blocks to be written are actually agreed by all nodes, the blocks packed by the accounting node. The accounting node broadcasts the block to be written to other nodes. As we all know, in the blockchain protocol, on the one hand, each node needs to execute each transaction in the block to be written, on the other hand, it needs to write the block to be written into the blockchain for publicity. Once the block to be written is written into the blockchain, it is equivalent to publicizing each transaction in the block to be written. The transaction published on the blockchain can be used to check whether the corresponding transaction execution result is correct to prevent any node from doing evil.

In step S400, for each node, if the node is an accounting node, then the way for the node to obtain the block to be written may specifically be to grab several transactions from its own cache and package it into the area to be written Block; if the node is not an accounting node, then the way for the node to obtain the block to be written may specifically be to receive the block to be written broadcast by the accounting node.

It is worth emphasizing that for each transaction in the block to be written, the execution result of the transaction is to create a storage address and store the information, or update the information stored on a storage address Enter information or modify the information stored on a storage address). In other words, the execution result of each transaction in the block to be written will only affect one storage address.

For example, a contract creation transaction that creates a contract account is a transaction whose execution result is to create a storage address and deposit information. The issue publishing transaction and answer publishing transaction mentioned above are also the transactions whose execution results are creating a storage address and storing information.

As another example, in some blockchain application scenarios, each user's shopping record needs to be documented. Then, it is necessary to create a record storage address corresponding to each user in the database. When the target user makes a purchase, a shopping record will be generated, and any node in the blockchain network will build a record and record the transaction based on the shopping record and broadcast it. Then, for each node, the node will execute the record storage transaction at the appropriate time (that is, when the record storage transaction is packaged into the module to be written and broadcast to each node), that is, store the shopping record into the target user Corresponding record storage address. Obviously, multiple shopping records generated by the target user making multiple purchases will be stored in the record storage address corresponding to the target user. Therefore, the above record-storage transaction is the transaction whose execution result is updating the information stored on a storage address.

The results mentioned above issue the transaction, and the execution result is the transaction that updates the information stored on a storage address.

S402: Read each transaction from the block to be written, and organize each transaction into N transaction queues.

In the prior art, each node usually adopts a serialized transaction execution method to execute each transaction in the block to be written. As shown in FIG. 5, the so-called serialized transaction execution method refers to that each node executes each transaction in the to-be-written block one by one according to a certain first order.

In the embodiment of the present specification, each transaction in the block to be written is divided into N groups, where N is a natural number greater than 1. Then, for each group, arrange the transactions in this group into a transaction queue. This specification does not specifically limit the order of transactions in each transaction queue.

S404: At the same time, for each transaction queue, each transaction in the transaction queue is executed in order from first to last.

In step S404, the parallel execution of transaction execution for each transaction queue is actually started at the same time. And specific to each transaction queue, actually execute each transaction in the transaction queue serially. As shown in Figure 6.

The so-called "simultaneously" means that the nodes start executing transactions in each transaction queue at the same time. It is equivalent to the node creating N transaction execution processes at the same time, and each transaction process is responsible for executing transactions in a transaction queue.

Comparing the two transaction execution methods of FIG. 5 and FIG. 6, it is clear that the transaction execution method shown in FIG. 6 can execute more transactions per unit time.

S406: Write the block to be written into the blockchain.

In the embodiment of the present specification, for each node, step S406 may be performed after step S404; or step S406 may not be performed after step S404 is performed.

Through the parallelized method of executing blockchain transactions shown in FIG. 4, if each transaction to be written in the block is not a transaction that updates information stored in more than one storage address, then, in the blockchain network Each node of can organize each transaction to be written into the block into at least two transaction queues, and then, at the same time, start executing the transactions in each transaction queue. In this way, each node can execute a larger number of transactions per unit time, which improves the efficiency of transaction execution.

In addition, in the embodiment of the present specification, the number of transactions corresponding to each transaction queue (that is, the number of transactions in each transaction queue) may be relatively close. In this way, when the transaction execution is executed for each transaction queue while being parallelized, the number of transactions executed by each execution process is relatively close, and some processes are not idle and some processes are overloaded. This also means that nodes can execute as many transactions as possible in a unit of time.

Specifically, it may be set that the variance calculated based on the number of transactions corresponding to each transaction queue is not greater than a specified threshold. The smaller the variance calculated based on the number of transactions corresponding to each transaction queue, the closer the number of transactions corresponding to each transaction queue.

In addition, in the embodiments of this specification, the Ethereum protocol can be used to construct a blockchain network. In Ethereum, a virtual machine program is installed on each node to provide a running environment for the implementation of the Ethereum protocol.

Usually, a virtual machine program is used to execute a blockchain process. However, in the embodiment of the present specification, since more than one transaction queue needs to be simultaneously executed and more than one blockchain process needs to be executed in parallel, it is necessary to deploy more than one virtual machine program in advance on each node.

Specifically, if the transactions to be written in the block need to be organized into N transaction queues, then N virtual machine programs need to be deployed on each node in advance.

As such, in step S404, a one-to-one correspondence between N virtual machine programs and N transaction queues that are pre-deployed can be established; at the same time, for each transaction queue, the virtual machine program corresponding to that transaction queue Then execute each transaction in the transaction queue in turn.

In addition, in the embodiment of the present specification, generally, the transactions to be written in the block include both the first type transaction and the second type transaction. Among them, the first type of transaction refers to the transaction whose execution result is to update the information stored on a storage address; the second type of transaction refers to the transaction whose execution result is to create a storage address and store the information.

Obviously, there may be more than one type 1 transaction in the block to be written, which will update the information stored on the same storage address. Nodes often need to first access the storage address targeted by the currently executing first-class exchange when executing each first-class transaction. In this case, when the node executes the transactions in the block to be written, if it can perform batch execution of all the first type transactions corresponding to the same storage address, then only one access to the same storage address is required, This will significantly increase the speed at which nodes execute transactions.

Specifically, in step S402, a transaction whose execution result is to update the information stored on a storage address may be selected from each transaction as a first-type transaction, and other transactions except the first-type transaction in each transaction As a second type of transaction; in each first type of transaction, the corresponding first type of transaction with the same storage address is organized into a transaction sub-queue; each transaction sub-queue is a processing unit, and each second type of transaction The transaction is regarded as one processing unit; each processing unit is organized into N transaction queues.

In this way, in the block to be written, all the first-type transactions corresponding to any storage address will be integrated into a transaction sub-queue, and the transaction sub-queue will be put into a transaction queue as a whole. When the node executes a transaction for the transaction queue, once accessing the storage address, it will continuously execute all the first-type transactions corresponding to the storage address.

Further, each processing unit is organized into N transaction queues, which can be as follows:

According to the number of transactions corresponding to each processing unit, the processing units are sorted from large to small; and, the number of transactions corresponding to each transaction queue is initialized to 0; according to the sorting result, the first processing unit is selected; the currently selected The processing unit is added to the tail of the minimum transaction queue, and the number of transactions corresponding to the minimum transaction queue is updated; the minimum transaction queue is the transaction queue with the smallest corresponding number of transactions; continue to select the next processing unit until all processing units are Add to the transaction queue.

In this way, the number of transactions corresponding to each transaction queue can be made substantially the same. In this way, when parallel transaction execution is performed based on each transaction queue, the workload on each execution process is also roughly the same, and no execution process will be idle, so that the most transactions can be executed in a unit time, significantly Improve the transaction execution efficiency of nodes.

Based on the method shown in FIG. 1, the embodiment of this specification also correspondingly provides a blockchain-based programming issue issuing device. As shown in FIG. 7, the device is any node in the blockchain network. The device includes:

Create a module 701 to create programming topics to be released;

Construct a broadcast module 702, construct a topic release transaction based on the topic-related data, and broadcast the topic release transaction to the blockchain network; the topic-related data includes the programming topic, so that the topic release transaction is obtained Each node writes the issue publishing transaction into the blockchain based on the consensus mechanism between the nodes.

Based on the method shown in FIG. 2, the embodiment of this specification also correspondingly provides a blockchain-based solution code issuing device. As shown in FIG. 8, the device is any node in the blockchain network. The device includes:

The obtaining module 801 obtains programming topics; the programming topics are issued by the method according to any one of claims 1 to 4;

The answering module 802 provides the programming question to the tested user for answering, and receives the answer code uploaded by the tested user;

Build a broadcast module 803, construct answer release transactions based on answer-related data, and broadcast the answer release transactions to the blockchain network, so that each node that obtains the answer release transactions is based on the consensus mechanism between the nodes , Write the answer release transaction into the blockchain;

Wherein, the solution-related data includes a problem identification of the programming problem, the solution code, and a user identification of the user under test.

Based on the method shown in FIG. 2, the embodiment of the present specification also correspondingly provides a blockchain-based solution code verification device. As shown in FIG. 9, the device is in a blockchain network and stores corresponding programming problems. To answer the node of inspection data, the device includes:

The obtaining module 901 obtains the answer code corresponding to the programming question and the user ID of the user who is tested by uploading the answer code; the programming question is issued by the method shown in FIG. Published by the method shown;

The verification module 902 uses the stored verification data corresponding to the programming problem to verify the solution code;

Construct a broadcasting module 903, if the test passes, construct a result publishing transaction based on the result-related data, and broadcast the result publishing transaction to the blockchain network, so that each node that obtains the result publishing transaction is based on each node Between the consensus mechanism, write the result release transaction into the blockchain;

Wherein, the result-related data includes the title identification of the programming topic and the user identification.

Based on the method shown in FIG. 1, the embodiments of the present specification also correspondingly provide a blockchain-based programming topic publishing system, including a blockchain network composed of multiple nodes;

Based on the method shown in FIG. 2, the embodiment of this specification also correspondingly provides a blockchain-based solution code issuing system, including a blockchain network composed of multiple nodes;

Get a programming question at any node; the target node is any node in the blockchain network, and the programming question is published according to the method shown in Figure 1; provide the programming question to the tested user for answering , And receive the answer code uploaded by the tested user; based on the answer-related data, construct an answer release transaction, and broadcast the answer release transaction to the blockchain network; wherein, the answer-related data includes the programming topic Title identification, the answer code and the user identification of the tested user;

Based on the method shown in FIG. 3, the embodiment of this specification also correspondingly provides a blockchain-based solution code verification system, including a blockchain network composed of multiple nodes;

Check the node to obtain the answer code corresponding to the programming question and the user ID of the user under test who uploaded the answer code. The programming question is issued according to the method shown in FIG. 1 and the answer code is shown in FIG. 2 Issued by the method, the verification node is a node in the blockchain network that stores the solution verification data corresponding to the programming problem; use the stored solution verification data corresponding to the programming problem to verify the solution code; if If the test passes, the result release transaction is constructed based on the result-related data, and the result release transaction is broadcast to the blockchain network; wherein, the result-related data includes the title identification of the programming topic and the user identification;

FIG. 10 is a schematic structural diagram of a blockchain-based programming level testing system provided by an embodiment of the present specification. The system shown in FIG. 10 can be specifically used to implement a block chain-based programming question issuing system, answer code issuing system, and answer code checking system.

An embodiment of the present specification also provides a computer device, which includes at least a memory, a processor, and a computer program stored on the memory and executable on the processor, where the processor executes the program to implement FIG. 1 or FIG. 2 or The function of the method shown in Figure 3.

FIG. 11 shows a schematic diagram of a more specific hardware structure of a computing device provided by an embodiment of the present specification. The device may include: a processor 1010, a memory 1020, an input / output interface 1030, a communication interface 1040, and a bus 1050. The processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040 realize the communication connection between the devices within the device through the bus 1050.

The processor 1010 may be implemented by a general-purpose CPU (Central Processing Unit, central processing unit), a microprocessor, an application-specific integrated circuit (Application Specific Integrated Circuit, ASIC), or one or more integrated circuits, etc. Programs to implement the technical solutions provided by the embodiments of the present specification.

The memory 1020 may be implemented in the form of ROM (Read Only Memory), RAM (Random Access Memory, random access memory), static storage devices, and dynamic storage devices. The memory 1020 may store an operating system and other application programs. When the technical solutions provided by the embodiments of the present specification are implemented by software or firmware, related program codes are stored in the memory 1020 and are called and executed by the processor 1010.

The input / output interface 1030 is used to connect input / output modules to realize information input and output. The input / output / module can be configured as a component in the device (not shown in the figure), or can be externally connected to the device to provide corresponding functions. The input device may include a keyboard, mouse, touch screen, microphone, various sensors, etc., and the output device may include a display, a speaker, a vibrator, an indicator light, and the like.

The communication interface 1040 is used to connect a communication module (not shown in the figure) to implement communication interaction between the device and other devices. The communication module can realize communication through a wired method (such as USB, network cable, etc.), and can also implement communication through a wireless method (such as mobile network, WIFI, Bluetooth, etc.).

The bus 1050 includes a path for transferring information between various components of the device (for example, the processor 1010, the memory 1020, the input / output interface 1030, and the communication interface 1040).

It should be noted that although the above device only shows the processor 1010, the memory 1020, the input / output interface 1030, the communication interface 1040, and the bus 1050, in the specific implementation process, the device may also include the necessary to achieve normal operation Other components. In addition, those skilled in the art can understand that the above-mentioned device may also include only the components necessary for implementing the embodiments of the present specification, and does not necessarily include all the components shown in the figures.

Embodiments of the present specification also provide a computer-readable storage medium on which a computer program is stored, which when executed by a processor implements the functions of the method shown in FIG. 1 and / or FIG. 4.

Computer readable media, including permanent and non-permanent, removable and non-removable media, can store information by any method or technology. The information may be computer readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

It can be known from the description of the above implementation manners that those skilled in the art can clearly understand that the embodiments of this specification can be implemented by means of software plus a necessary general hardware platform. Based on this understanding, the technical solutions of the embodiments of the present specification can be embodied in the form of software products in essence or part of contributions to the existing technology, and the computer software products can be stored in a storage medium, such as ROM / RAM Magnetic disks, optical disks, etc., include several instructions to enable a computer device (which may be a personal computer, server, or network device, etc.) to perform the methods described in the embodiments of this specification or some parts of the embodiments.

The system, method, module or unit explained in the above embodiments may be implemented by a computer chip or entity, or by a product with a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or any combination of these devices.

The embodiments in this specification are described in a progressive manner. The same or similar parts between the embodiments can be referred to each other, and each embodiment focuses on the differences from other embodiments. In particular, for the device and device embodiments, since they are basically similar to the method embodiments, the description is relatively simple. For the related parts, refer to the description of the method embodiments. The method embodiments described above are only schematics, wherein the modules described as separate components may or may not be physically separated, and the functions of the modules may be the same when implementing the embodiment solutions of this specification Or multiple software and / or hardware. Part or all of the modules may also be selected according to actual needs to achieve the purpose of the solution of this embodiment. Those of ordinary skill in the art can understand and implement without paying creative labor.

The above is only a specific implementation of the embodiments of this specification. It should be pointed out that for those of ordinary skill in the art, without departing from the principles of the embodiments of this specification, several improvements and retouches can be made. These Improvements and retouching should also be regarded as the scope of protection of the embodiments of this specification.

Claims

A method for publishing programming questions based on blockchain, including:

The target node creates a programming topic to be released; the target node is any node in the blockchain network;

The target node constructs a topic publishing transaction based on topic related data, and broadcasts the topic publishing transaction to the blockchain network; the topic related data includes the programming topic;

For each node that obtains the topic release transaction, the node writes the topic release transaction into the blockchain based on the consensus mechanism between the nodes.
The method according to claim 1, wherein the topic-related data further includes a node identifier of the target node.
The method according to claim 1, further comprising: for each node that obtains the topic issue transaction, the node creates a topic storage address, and stores the topic-related data in the topic storage address.
The method according to claim 3, storing the title-related data in the title storage address, specifically including:

The title smart contract encapsulated with the relevant data of the title is stored in the title storage address.
A blockchain-based answer code publishing method, including:

The target node obtains the programming topic; the target node is any node in the blockchain network, and the programming topic is issued by the method according to any one of claims 1 to 4;

The target node provides the programming problem to the tested user for answering, and receives the answer code uploaded by the tested user;

The target node constructs an answer release transaction based on the answer-related data, and broadcasts the answer release transaction to the blockchain network; the answer-related data includes the title identification of the programming topic, the answer code, and the The user ID of the tested user;

For each node that obtains the answer release transaction, the node writes the answer release transaction into the blockchain based on the consensus mechanism between the nodes.
According to the method of claim 5, the target node obtains the programming topic, specifically including:

The target node reads the programming topic from any topic publishing transaction in the blockchain; or

The target node obtains the programming topic from any topic storage address.
The method of claim 6, if the target node reads a programming topic from any topic publishing transaction in the blockchain, the topic identification of the programming topic is the transaction hash of the topic publishing transaction;

If the target node obtains a programming topic from any topic storage address, the topic of the programming topic is identified as the storage address.
The method according to claim 5, further comprising: for each node that obtains the solution issuing transaction, the node creates a solution storage address, and stores the solution related data in the solution storage address.
The method of claim 8, storing the answer-related data in the answer storage address, specifically including:

The solution smart contract encapsulated with the solution related data is stored in the solution storage address.
A blockchain-based solution code verification method, including:

The verification node obtains the answer code corresponding to the programming question and the user ID of the user who is testing the uploading the answer code; the programming question is issued by the method of any one of claims 1 to 4, and the answer code According to the method of any one of claims 5 to 9, the verification node is a node in a blockchain network that stores answer verification data corresponding to the programming problem;

The verification node uses the stored solution verification data corresponding to the programming problem to verify the solution code;

If the verification passes, the verification node constructs a result publishing transaction based on the result-related data, and broadcasts the result publishing transaction to the blockchain network; User identification

For each node that obtains the result publishing transaction, the node writes the result publishing transaction into the blockchain based on the consensus mechanism between the nodes.
According to the method of claim 10, the verification node obtains the answer code corresponding to the programming problem and the user ID of the user under test uploading the answer code, specifically including:

The inspection node determines the question ID corresponding to the answer test data according to any stored answer test data;

From the query in the blockchain, find the answer publishing transaction that contains the question ID, and read the answer code and user ID from the answer publishing transaction; or query the answer storage address where the question ID is stored, and search from all Get the answer code and user ID in the answer storage address.
The method according to claim 10, wherein the result-related data further includes a test passed result or a test failed result.
The method of claim 10, further comprising: for each node that obtains the result publishing transaction, the node creates a result storage address, and stores the result related data in the result storage address.
The method of claim 13, storing the result-related data in the result storage address, specifically including:

Storing the result smart contract encapsulated with the result-related data in the result storage address.
The method of claim 13, further comprising:

For each node that obtains the result publishing transaction, if the node obtains other result publishing transactions associated with the result publishing transaction, the node writes the other result publishing transactions into the zone based on the consensus mechanism between the nodes Blockchain; the other result release transaction is constructed based on the user ID and other topic IDs;

as well as

The node issues a transaction based on the other results, and stores the other topic identifiers in the result storage address.
The method of claim 10, the number of check nodes is greater than 1;

The verification node obtains the answer code corresponding to the programming problem and the user ID of the user under test uploading the answer code, which specifically includes:

For each verification node, the verification node obtains the answer code corresponding to the programming problem and the user ID of the user under test uploading the answer code;

The verification node uses the stored solution verification data corresponding to the programming problem to verify the solution code, specifically including:

For each check node, the check node uses the stored answer test data corresponding to the programming problem to check the answer code;

If the verification passes, the verification node constructs a result release transaction based on the result-related data, and broadcasts the result release transaction to the blockchain network, specifically including:

For each verification node, if the verification node passes the answer code, it constructs a result release transaction based on the result-related data, and broadcasts the result release transaction to the blockchain network.
The method of claim 16, for each node that obtains the result publishing transaction, the node writes the result publishing transaction into the blockchain based on a consensus mechanism between the nodes, specifically including:

When the node determines that the number of obtained result publishing transactions is the specified number, based on the consensus mechanism between each node, any obtained result publishing transactions are written into the blockchain;

Wherein, the specified number is not greater than the number of inspection nodes.
The method according to claim 10, wherein the verification node is a node that creates the programming problem in the blockchain network.
A method for publishing programming questions based on blockchain, including:

The target node creates a programming topic to be released; the target node is any node in the blockchain network;

Based on the topic-related data, construct a topic issue transaction, and broadcast the topic issue transaction to the blockchain network; the topic-related data includes the programming topic, so that each node that obtains the topic issue transaction is based on The consensus mechanism between the nodes writes the issue publishing transaction into the blockchain.
A blockchain-based answer code publishing method, including:

The target node obtains the programming topic; the target node is any node in the blockchain network, and the programming topic is issued by the method according to any one of claims 1 to 4;

Providing the programming problem to the tested user for answering, and receiving the answer code uploaded by the tested user;

Based on the answer-related data, construct an answer release transaction, and broadcast the answer release transaction to the blockchain network, so that each node that obtains the answer release transaction will base the answer on the consensus mechanism between the nodes Post transactions into the blockchain;

Wherein, the solution-related data includes a problem identification of the programming problem, the solution code, and a user identification of the user under test.
A blockchain-based solution code verification method, including:

The verification node obtains the answer code corresponding to the programming question and the user ID of the user who is testing the uploading the answer code; the programming question is issued by the method of any one of claims 1 to 4, and the answer code According to the method of any one of claims 5 to 9, the verification node is a node in a blockchain network that stores answer verification data corresponding to the programming problem;

Using the stored answer verification data corresponding to the programming problem to verify the answer code;

If the test passes, based on the result-related data, construct a result publishing transaction, and broadcast the result publishing transaction to the blockchain network, so that each node that obtains the result publishing transaction is based on the consensus mechanism between the nodes , Write the result release transaction into the blockchain;

Wherein, the result-related data includes the title identification of the programming topic and the user identification.
A blockchain-based programming issue issuing device, the device is any node in a blockchain network, the device includes:

Create modules to create programming topics to be released;

Build a broadcast module, build a topic release transaction based on the topic-related data, and broadcast the topic release transaction to the blockchain network; the topic-related data includes the programming topic, so that each issue of the topic release transaction is obtained Each node writes the issue publishing transaction into the blockchain based on the consensus mechanism between each node.
A blockchain-based solution code issuing device, the device is any node in a blockchain network, the device includes:

An acquisition module to acquire programming questions; the programming questions are issued by the method of any one of claims 1 to 4;

The answering module provides the programming question to the tested user for answering, and receives the answer code uploaded by the tested user;

Build a broadcast module, build answer release transactions based on answer-related data, and broadcast the answer release transactions to the blockchain network, so that each node that obtains the answer release transactions is based on the consensus mechanism between the nodes, Write the answer release transaction into the blockchain;

Wherein, the solution-related data includes a problem identification of the programming problem, the solution code, and a user identification of the user under test.
An answer code verification device based on a blockchain. The device is a node in a blockchain network that stores answer verification data corresponding to a programming problem. The device includes:

An obtaining module, obtaining the answer code corresponding to the programming question and the user ID of the user under test uploading the answer code; the programming question is issued by the method according to any one of claims 1 to 4, and the answer The code is issued by the method of any one of claims 5-9;

A verification module, using the stored verification data corresponding to the programming problem to verify the solution code;

Build a broadcasting module, if the test passes, build a result publishing transaction based on the result-related data, and broadcast the result publishing transaction to the blockchain network, so that each node that obtains the result publishing transaction is based on the The consensus mechanism between the two, writes the result release transaction into the blockchain;

Wherein, the result-related data includes the title identification of the programming topic and the user identification.
A blockchain-based programming topic publishing system, including a blockchain network composed of multiple nodes;

Any node creates a programming topic to be released; based on the data related to the topic, constructs a topic release transaction, and broadcasts the topic release transaction to the blockchain network, and the topic related data includes the programming topic;

Each node that obtains the topic release transaction writes the topic release transaction into the blockchain based on the consensus mechanism between the nodes.
A blockchain-based answer code publishing system, including a blockchain network composed of multiple nodes;

Any node to obtain a programming topic; the target node is any node in the blockchain network, the programming topic is issued by the method according to any one of claims 1 to 4; the programming topic is provided Answer to the tested user and receive the answer code uploaded by the tested user; based on the relevant data of the answer, construct an answer publishing transaction and broadcast the answer publishing transaction to the blockchain network; wherein, the answer is relevant The data includes the title identification of the programming topic, the answer code and the user identification of the tested user;

Each node that obtains the answer release transaction writes the answer release transaction into the blockchain based on the consensus mechanism between the nodes.
A block-based answer code verification system, including a block chain network composed of multiple nodes;

A verification node to obtain the answer code corresponding to the programming question and the user ID of the user under test uploading the answer code, the programming question is issued by the method according to any one of claims 1 to 4, and the answer code is Issued by the method of any one of claims 5 to 9, the verification node is a node in the blockchain network that stores the answer verification data corresponding to the programming problem; using the stored data corresponding to the programming problem Answer verification data to verify the answer code; if the test passes, based on the result-related data, construct a result-publishing transaction and broadcast the result-publishing transaction to the blockchain network; where the result-related data includes all The title identification of the programming topic and the user identification;

Each node that obtains the result publishing transaction writes the result publishing transaction into the blockchain based on the consensus mechanism between the nodes.
A computer device, including a memory, a processor, and a computer program stored on the memory and executable on the processor, wherein when the processor executes the program, the program according to any one of claims 1 to 21 is implemented method.