CN115357548B - Block chain-based electronic contract query method, device, equipment and medium - Google Patents

Abstract

The embodiment of the disclosure discloses an electronic contract query method, device, equipment and medium based on a block chain, wherein the method comprises the following steps: and when the contract information identifier does not belong to a preset first query forbidding list, the query client identifier does not belong to a preset second query forbidding list, the contract information identifier belongs to a preset contract information identifier storage list, and the contract information has a contract file hash value identical to the target hash value, acquiring the target contract file from the block chain based on the contract file identifier corresponding to the contract file hash value identical to the target hash value. Therefore, the contract files corresponding to each signing stage in the signing process of the electronic contract can be inquired, whether the contract files can be inquired or not can be determined according to the contract information identification and the inquiry client identification, and the safety of the contract files is effectively improved.

Description

Blockchain-based electronic contract query method, device, equipment and medium

technical field

The present disclosure relates to blockchain technology and contract query technology, in particular to a blockchain-based electronic contract query method, device, equipment and medium.

Background technique

With the continuous development of blockchain technology, based on blockchain technology, the technology of signing and storing electronic contracts on the chain is also being more and more applied. In the prior art, it is often possible to query the final version of the electronic contract through the identification or contract number of the electronic contract, but it is impossible to query the intermediate electronic contract documents corresponding to the signing stage in the electronic contract signing process.

Contents of the invention

Embodiments of the present disclosure provide a blockchain-based electronic contract query method, device, device, and medium to solve the problem in the prior art that the contract documents corresponding to the signing stage in the electronic contract signing process cannot be queried.

An aspect of the embodiments of the present disclosure provides a blockchain-based electronic contract query method, including: a query terminal receiving an electronic contract query request sent by a query client, wherein the electronic contract query request includes: a query client ID, contract information ID, and target hash value; in response to determining that the contract information ID does not belong to a preset first prohibited query list, and that the querying client ID does not belong to a preset second prohibited query list, determine that the contract Whether the information identifier belongs to the preset contract information identifier storage list; in response to the contract information identifier belonging to the preset contract information identifier storage list, acquire the contract information identified by the contract information identifier, wherein the contract information includes: At least one contract file hash value and contract file identifiers respectively corresponding to each contract file hash value in the at least one contract file hash value; determine whether there is a contract with the same target hash value in the contract information File hash value; in response to the existence of a contract file hash value identical to the target hash value in the contract information, based on the contract file identifier corresponding to the contract file hash value identical to the target hash value, from Acquiring the target contract file from the block chain; feeding the target contract file back to the query client.

Optionally, in the method of any of the above-mentioned embodiments of the present disclosure, the contract information further includes: a contract status; the method further includes: determining whether the contract status is a contract completion status; in response to the contract status being Signing completion state, performing the operation of determining whether there is a contract file hash value identical to the target hash value in the contract information.

Optionally, in the method of any one of the above-mentioned embodiments of the present disclosure, the contract information includes: the generation time corresponding to each contract file hash value in the at least one contract file hash value; the method further includes: In response to the fact that there is no contract file hash value identical to the target hash value in the contract information, determine the contract file hash value corresponding to the generation time closest to the current time as the target contract file hash value; Based on the contract file identifier corresponding to the hash value of the target contract file, the target contract file is acquired from the block chain.

Optionally, in the method of any one of the above-mentioned embodiments of the present disclosure, the method further includes: the query terminal determining the contract information identifier to be added to the preset first prohibited query list as a new contract information identifier; Responding to the fact that the new contract information identifier is not included in the preset first forbidden query list, and the preset contract information identifier storage list includes the new contract information identifier, adding the new contract information identifier to to the preset first prohibited query list.

Optionally, in the method of any one of the above-mentioned embodiments of the present disclosure, the method further includes:

The query terminal receives the contract file list query request sent by the query client, wherein the contract file list query request includes: a contract file list identifier;

Determine whether the contract file list identifier belongs to the preset first prohibited query list;

Responding to the fact that the contract document list identifier does not belong to the preset first prohibited query list, based on the contract document list identifier, the contract document list identified by the contract document list identifier is obtained from the block chain;

The contract file list identified by the contract file list identifier is fed back to the query client.

An aspect of the embodiments of the present disclosure provides a block chain-based electronic contract query device, including: a first receiving module, used for the query terminal to receive the electronic contract query request sent by the query client, wherein the electronic contract The query request includes: a query client ID, a contract information ID, and a target hash value; a first determination module, configured to respond to determining that the contract information ID does not belong to a preset first prohibited query list, and the query client ID does not belong to the preset second prohibition query list, and determines whether the contract information identifier belongs to the preset contract information identifier storage list; the first acquisition module is configured to respond to the contract information identifier belonging to the preset contract information identifier storage list , to obtain the contract information identified by the contract information identifier, wherein the contract information includes: at least one hash value of a contract file and contracts respectively corresponding to the hash values of each contract file in the at least one hash value of a contract file File identification; a second determination module, configured to determine whether there is a contract file hash value identical to the target hash value in the contract information; a second acquisition module, configured to respond to the presence of the target hash value in the contract information The hash value of the contract file with the same target hash value, based on the contract file identification corresponding to the contract file hash value with the same target hash value, obtain the target contract file from the block chain; the first feedback module uses Then feed back the target contract file to the query client.

Optionally, in the device in any of the above-mentioned embodiments of the present disclosure, the contract information further includes: a contract status; the device further includes: a third determination module, configured to determine whether the contract status is a contract completion status; An executing module, configured to execute the operation of determining whether there is a contract file hash value identical to the target hash value in the contract information in response to the contract status being the contract completion status.

Optionally, in the device of any one of the above-mentioned embodiments of the present disclosure, the contract information includes: the generation time corresponding to each contract file hash value in the at least one contract file hash value; the device further includes: The fourth determination module is configured to determine the contract file hash value corresponding to the generation time closest to the current time as Hash value of the target contract file; a third acquiring module, configured to acquire the target contract file from the block chain based on the contract file identifier corresponding to the hash value of the target contract file.

An aspect of an embodiment of the present disclosure provides an electronic device, including: a memory for storing a computer program; a processor for executing the computer program stored in the memory, and when the computer program is executed, the method described above.

An aspect of the embodiments of the present disclosure provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, any one of the above-mentioned methods is implemented.

Embodiments of the present disclosure provide a blockchain-based electronic contract query method, device, device, and medium. When the contract information identifier does not belong to the preset first prohibited query list, the query client ID does not belong to the preset second prohibited query list. list, when the contract information identifier belongs to the preset contract information identifier storage list, and there is a contract file hash value that is the same as the target hash value in the contract information, the contract file corresponding to the contract file hash value that is the same as the target hash value ID, get the target contract file from the blockchain. Thus, the embodiments of the present disclosure not only realize the possibility of querying the contract documents corresponding to each signing stage in the signing process of the electronic contract, but also realize the possibility of determining whether the contract documents can be queried according to the contract information identifier and the query client identifier. Effectively improve the security of contract documents.

The technical solution of the present disclosure will be described in further detail below with reference to the drawings and embodiments.

Description of drawings

The accompanying drawings, which constitute a part of this specification, illustrate embodiments of the disclosure and, together with the description, serve to explain principles of the disclosure.

The present disclosure can be more clearly understood from the following detailed description with reference to the accompanying drawings, in which:

FIG. 1 is a schematic flow diagram of a blockchain-based electronic contract query method provided by an exemplary embodiment of the present disclosure;

FIG. 2 is a schematic flowchart of a blockchain-based electronic contract query method provided by another exemplary embodiment of the present disclosure;

FIG. 3 is a schematic flow diagram of a blockchain-based electronic contract query method provided by another exemplary embodiment of the present disclosure;

4 is a schematic flow diagram of a blockchain-based electronic contract query method provided by another exemplary embodiment of the present disclosure;

5 is a schematic flow diagram of a blockchain-based electronic contract query method provided by another exemplary embodiment of the present disclosure;

Fig. 6 is a schematic structural diagram of a blockchain-based electronic contract query device provided by an exemplary embodiment of the present disclosure;

Fig. 7 is a structural diagram of an electronic device provided by an exemplary embodiment of the present disclosure.

Detailed ways

Various exemplary embodiments of the present disclosure will now be described in detail with reference to the accompanying drawings. It should be noted that relative arrangements of components and steps, numerical expressions and numerical values set forth in these embodiments do not limit the scope of the present disclosure unless specifically stated otherwise.

Those skilled in the art can understand that terms such as "first" and "second" in the embodiments of the present disclosure are only used to distinguish different steps, devices or modules, etc. necessary logical sequence.

It should also be understood that in the embodiments of the present disclosure, "plurality" may refer to two or more than two, and "at least one" may refer to one, two or more than two.

It should also be understood that any component, data or structure mentioned in the embodiments of the present disclosure can generally be understood as one or more unless there is a clear limitation or a contrary suggestion is given in the context.

In addition, the term "and/or" in the present disclosure is only an association relationship describing associated objects, indicating that there may be three relationships, for example, A and/or B may indicate: A exists alone, and A and B exist simultaneously , there are three cases of B alone. In addition, the character "/" in the present disclosure generally indicates that the contextual objects are an "or" relationship.

It should also be understood that the description of the various embodiments in the present disclosure emphasizes the differences between the various embodiments, and the same or similar points can be referred to each other, and for the sake of brevity, details are not repeated here.

At the same time, it should be understood that, for the convenience of description, the sizes of the various parts shown in the drawings are not drawn according to the actual proportional relationship.

The following description of at least one exemplary embodiment is merely illustrative in nature and in no way intended as any limitation of the disclosure, its application or uses.

Techniques, methods and devices known to those of ordinary skill in the relevant art may not be discussed in detail, but where appropriate, such techniques, methods and devices should be considered part of the description.

It should be noted that like numerals and letters denote like items in the following figures, therefore, once an item is defined in one figure, it does not require further discussion in subsequent figures.

Embodiments of the present disclosure may be applied to electronic devices such as terminal devices, computer systems, servers, etc., which may operate with numerous other general purpose or special purpose computing system environments or configurations. Examples of well known terminal devices, computing systems, environments and/or configurations suitable for use with electronic devices such as terminal devices, computer systems, servers include, but are not limited to: personal computer systems, server computer systems, thin clients, thick client Computers, handheld or laptop devices, microprocessor-based systems, set-top boxes, programmable consumer electronics, networked personal computers, minicomputer systems, mainframe computer systems, and distributed cloud computing technology environments including any of the foregoing, etc.

Electronic devices such as terminal devices, computer systems, servers, etc. may be described in the general context of computer system-executable instructions, such as program modules, being executed by the computer system. Generally, program modules may include routines, programs, objects, components, logic, data structures, etc., that perform particular tasks or implement particular abstract data types. The computer system/server can be practiced in distributed cloud computing environments where tasks are performed by remote processing devices that are linked through a communications network. In a distributed cloud computing environment, program modules may be located in both local and remote computing system storage media including storage devices.

Fig. 1 shows a schematic flowchart of a blockchain-based electronic contract query method in an embodiment of the present disclosure. This embodiment can be applied to electronic equipment, as shown in Figure 1, the blockchain-based electronic contract query method of this embodiment includes the following steps:

Step S110, the inquiry terminal receives the electronic contract inquiry request sent by the inquiry client.

Wherein, the electronic contract query request includes: query client identification, contract information identification and target hash value.

The query terminal and the query client can be servers, computers, etc., and the query terminal is connected to the query client through communication, and the user can query the contract documents in the query terminal through the query client. The query client ID is used to uniquely identify a query client. The query client ID can be BID (Blockchain-based Identifier, blockchain-based identifier) or DID (Decentralized Identifier, decentralized identifier), etc.

The contract information identifier is used to uniquely identify a contract information, and the contract information identifier can be BID or DID. Each contract information corresponds to an electronic contract, and the contract information includes all relevant information of the electronic contract and all information of the contract documents corresponding to each signing stage in the signing process of the electronic contract; for example, the contract information may include: the contract documents corresponding to each signing stage The serial number of the electronic contract, the information of each signatory to the electronic contract, the signing date of the electronic contract, etc.

In an implementation manner, the query terminal may create a hash value lookup table in advance, and the hash value lookup table includes the hash values of each contract file and the signing stage corresponding to each contract file hash value. The user can query the contract file hash value of the contract file corresponding to the contract stage required by the query client in the hash value query table of the contract terminal, and determine the contract file hash value as the target hash value. Among them, the hash value of the contract file can be obtained by performing hash calculation on the abstract of the contract file, and the hash value of the contract file is called the contract file hash value of the contract file, and the contract file hash value is used to represent A characteristic or fingerprint of a contract document.

Step S120, in response to determining that the contract information identifier does not belong to the first preset prohibited query list and the query client identifier does not belong to the preset second prohibited query list, determine whether the contract information identifier belongs to the preset contract information identifier storage list.

Wherein, at the query terminal, the preset first prohibition query list includes multiple contract information identifiers, and when there is a contract information identifier identical to the contract information identifier in the electronic contract query request in the preset first prohibition query list, it can be determined that the electronic contract information identifier is the same as that in the electronic contract query request. The contract information identifier in the contract query request belongs to the preset first prohibited query list; otherwise, it can be determined that the contract information identifier in the electronic contract query request does not belong to the preset first prohibited query list.

The preset second prohibited query list includes a plurality of query client IDs, and when the same query client ID as the query client ID in the electronic contract query request exists in the preset second prohibited query list, the electronic contract query request can be determined The inquiring client identifier in the query request belongs to the preset second prohibited query list; otherwise, it can be determined that the query client identifier in the electronic contract query request does not belong to the preset second prohibited query list.

The preset contract information identifier storage list includes a plurality of contract information identifiers, and when the same contract information identifier as the contract information identifier in the electronic contract query request exists in the preset contract information identifier storage list, the contract in the electronic contract query request can be determined The information identifier belongs to the preset contract information identifier storage list; otherwise, it can be determined that the contract information identifier in the electronic contract query request does not belong to the preset contract information identifier storage list.

In one implementation, in response to determining that the contract information identifier belongs to the preset first prohibited query list, and/or the query client identifier belongs to the preset second prohibited query list, the query terminal ends the query process and sends a query message to the query client Query failure message.

Step S130, in response to the contract information identifier belonging to the preset contract information identifier storage list, acquire the contract information identified by the contract information identifier.

Wherein, at the query terminal, the contract information includes: at least one contract file hash value and contract file identifiers respectively corresponding to each contract file hash value in the at least one contract file hash value. The contract document may be a process contract document generated at the signing stage in the signing process of the electronic contract. The contract information identifier may include a storage address of the contract information identified by the contract information identifier, and the contract information identified by the contract information identifier may be acquired through the storage address included in the contract information identifier. The contract document identifier is used to uniquely identify a contract document, and the contract document identifier may include a storage address of the contract document identified by the contract document identifier. The contract document identifier can be BID or DID, etc.

In an implementation manner, in response to the contract information identifier not belonging to the preset storage list of contract information identifiers, the query terminal sends a query failure message to the query client.

Exemplarily, enterprise A and enterprise B sign an electronic contract, and the electronic contract signing process may include three signing stages, namely: the initial stage, the signature stage, and the completion stage; (Communication connection between the signing system and the query terminal) Upload the contract template, the signing system will add the enterprise information of enterprise A and enterprise B to the contract template, generate an initial contract, the initial contract is the contract document corresponding to the initial stage, when enterprise A and enterprise B After the initial contract is signed, the contract to be verified is obtained. The contract to be verified is the contract document corresponding to the signature stage. The signature of the contract to be verified is verified. When the verification is passed, an electronic contract is generated, and the electronic contract is the contract document corresponding to the completion stage. By performing hash calculation on the contract files corresponding to each signing stage, the contract file hash value of the contract file corresponding to each signing stage can be obtained, and at the same time, the contract file identifier of the contract file at each signing stage can be generated, and the contract files of each signing stage The contract file hash value and contract file ID are recorded in the contract information.

Step S140, determining whether there is a contract file hash value identical to the target hash value in the contract information.

Wherein, querying the terminal compares the hash value of the contract file in the contract information with the target hash value, and determines whether there is a contract file hash value identical to the target hash value in the contract information.

Step S150, in response to the existence of a contract file hash value identical to the target hash value in the contract information, the target contract file is obtained from the blockchain based on the contract file identification corresponding to the contract file hash value identical to the target hash value .

Wherein, the contract file hash value and the contract file identifier of the same contract file correspond to each other. The target contract file is the contract file identified by the contract file identifier corresponding to the contract file hash value identical to the target hash value.

Blockchain (Block Chain) is a chained data structure that combines data blocks in a sequential manner in chronological order, and cryptographically ensures that data cannot be tampered with and cannot be forged. Distributed ledgers. Based on the storage address of the contract file included in the contract file identifier, the contract file identified by the contract file identifier corresponding to the contract file hash value that is the same as the target hash value can be obtained on the blockchain, and the contract file is determined as target contract document.

Step S160, feeding back the target contract file to the query client.

Wherein, the query terminal sends the target contract file to the query client.

In the embodiment of the present disclosure, when the contract information identifier does not belong to the preset first forbidden query list, the query client identifier does not belong to the preset second forbidden query list, the contract information identifier belongs to the preset contract information identifier storage list, and the contract information When there is a contract file hash value identical to the target hash value, the target contract file is obtained from the blockchain based on the contract file identifier corresponding to the contract file hash value identical to the target hash value. As a result, it is not only realized that the contract documents corresponding to each signing stage in the electronic contract signing process can be queried, but also it can be determined whether the contract documents can be queried according to the contract information identification and the query client identification, which effectively improves the Security of Contract Documents.

In an optional embodiment, the contract information in the disclosed embodiment also includes: contract status; as shown in Figure 2, the blockchain-based electronic contract query method in the disclosed embodiment also includes the following steps:

Step S210, determine whether the contract status is the contract completion status.

Among them, at the query terminal, the contract status is used to determine whether the signing process of the electronic contract is completed. For example, the contract status may include: a contracting status and a contracting status. The signing completion state is used to indicate that the signing process of the electronic contract has been completed, and the signing state is used to indicate that the signing process of the electronic contract is in progress.

Step S220, in response to the fact that the contract status is the contract completion status, perform an operation of determining whether there is a contract file hash value identical to the target hash value in the contract information.

Wherein, at the inquiry terminal, when the contract status is the contract completion status, step S140 and the operations after step S140 are performed.

In an optional embodiment, the contract information in the embodiment of the present disclosure includes: the generation time corresponding to each contract file hash value in at least one contract file hash value; as shown in FIG. 3 , the zone-based The electronic contract query method of the block chain also includes the following steps:

Step S310, in response to there is no contract file hash value identical to the target hash value in the contract information, determine the contract file hash value corresponding to the generation time closest to the current time as the target contract file hash value.

Wherein, at the query terminal, each contract file hash value corresponds to the generation time of the contract file hash value.

In an implementation manner, the generation time with the smallest time interval from the current time may be determined as the generation time closest to the current time. For example, the current time can be July 15, 2021, the generation time A is July 5, 2021, and the generation time B is July 6, 2021, then the generation time B is the closest generation time to the current time, and the The hash value of the contract file corresponding to the generation time B is determined as the hash value of the target contract file.

Step S320, based on the contract file identifier corresponding to the hash value of the target contract file, the target contract file is obtained from the blockchain.

Wherein, at the query terminal, the contract file identified by the contract file identifier corresponding to the hash value of the target contract file is determined as the target contract file.

In one implementation, the contract file identifier corresponding to the hash value of the target contract file is determined as the target contract file identifier, based on the target contract file identifier, the contract file identified by the target contract file identifier is obtained on the blockchain, and the The contract document is determined as the target contract document.

In the embodiment of the present disclosure, when there is no contract file hash value identical to the target hash value in the contract information, the contract file identified by the contract file identifier corresponding to the target contract file hash value can be used as the target contract file to realize When the contract documents corresponding to the required signing stage cannot be queried, the latest contract documents in the signing process are sent to the query client, which effectively improves the user experience.

In an optional embodiment, as shown in FIG. 4, the blockchain-based electronic contract query method of the embodiment of the present disclosure further includes the following steps:

Step S410, the query terminal determines the contract information identifier to be added to the preset first prohibited query list as a newly added contract information identifier.

Wherein, at the query terminal, when it is necessary to prevent any piece of contract information from being queried by the query client, the contract information identifier of the contract information can be added to the preset first prohibited query list.

Step S420, in response to the fact that the new contract information identifier is not included in the preset first prohibited query list, and the preset contract information identifier storage list contains the newly added contract information identifier, adding the newly added contract information identifier to the preset first prohibited query list.

Wherein, when the preset first prohibited query list does not contain the same contract information identifier as the newly added contract information identifier, and the preset contract information identifier storage list contains the same contract information identifier as the newly added contract information identifier, the new contract information identifier will be added The contract information identifier is added to the preset first prohibited query list.

In an optional embodiment, as shown in Figure 5, the blockchain-based electronic contract query method of the disclosed embodiment further includes the following steps:

Step S510, the inquiry terminal receives the contract document list inquiry request sent by the inquiry client.

Wherein, the contract file list query request includes: a contract file list identifier. The contract file list includes a plurality of contract file hash values. The contract file list identifier can be BID or DID, etc. The contract file list identifier may include a storage address of the contract file list identified by the contract file list identifier.

In step S520, it is determined whether the contract file list identifier belongs to the preset first prohibited query list.

Wherein, at the inquiry terminal, the preset first prohibited query list includes a plurality of contract file list identifiers, when there is a contract file list identifier identical to the contract file list identifier in the contract file list query request in the preset first prohibited query list , it can be determined that the contract document list identifier in the contract document list query request belongs to the preset first prohibited query list; otherwise, it can be determined that the contract document list identifier in the contract document list query request does not belong to the preset first prohibited query list.

Step S530, in response to the fact that the contract file list identifier does not belong to the preset first prohibited query list, based on the contract file list identifier, the contract file list identified by the contract file list identifier is obtained from the blockchain.

Wherein, at the query terminal, the contract document list identified by the contract document list identifier can be obtained from the block chain according to the storage address of the contract document list included in the contract document list identifier.

Step S540, feeding back the contract file list identified by the contract file list identifier to the query client.

Wherein, the query terminal feeds back the contract file list identified by the contract file list identifier to the query client.

Fig. 6 shows a block diagram of a blockchain-based electronic contract query device in an embodiment of the present disclosure. As shown in Figure 6, the electronic contract query device based on block chain in this embodiment includes:

The first receiving module 610 is used for the query terminal to receive the electronic contract query request sent by the query client, wherein the electronic contract query request includes: query client identification, contract information identification and target hash value;

The first determination module 620 is configured to determine whether the contract information identifier does not belong to the preset first prohibited query list and the query client identifier does not belong to the preset second prohibited query list in response to determining that the contract information identifier does not belong to the preset second prohibited query list. Belongs to the default contract information identifier storage list;

The first acquiring module 630 is configured to acquire the contract information identified by the contract information identifier in response to the contract information identifier belonging to the preset contract information identifier storage list, wherein the contract information includes: at least one contract document a hash value and a contract file identifier respectively corresponding to each contract file hash value in the at least one contract file hash value;

The second determining module 640 is configured to determine whether there is a contract file hash value identical to the target hash value in the contract information;

The second obtaining module 650 is configured to, in response to the contract file hash value identical to the target hash value existing in the contract information, based on the contract file corresponding to the contract file hash value identical to the target hash value Identify, obtain the target contract file from the blockchain;

The first feedback module 660 is configured to feed back the target contract file to the query client.

In one embodiment, the contract information further includes: contract status; the device further includes:

The third determination module 670 (not shown in the figure), is used to determine whether the contract status is a contract completion status;

Executing module 680 (not shown in the figure), configured to perform the step of determining whether there is a contract file hash value identical to the target hash value in the contract information in response to the contract status being the contract completion status. operate.

In one embodiment, the contract information includes: the generation time corresponding to each contract file hash value in the at least one contract file hash value; the device further includes:

The fourth determination module 690 (not shown in the figure) is configured to, in response to the fact that there is no contract file hash value identical to the target hash value in the contract information, set the The hash value of the contract file is determined as the hash value of the target contract file;

The third obtaining module 700 (not shown in the figure) is configured to obtain the target contract file from the block chain based on the contract file identifier corresponding to the hash value of the target contract file.

In one embodiment, the block chain-based electronic contract query device in the embodiment of the present disclosure also includes:

The fifth determining module 710 (not shown in the figure), is used for the query terminal to determine the contract information identifier to be added to the preset first forbidden query list as a newly added contract information identifier;

An updating module 720 (not shown in the figure), configured to respond to the fact that the new contract information identifier is not included in the preset first prohibition query list, and the preset contract information identifier storage list includes the newly added contract information identifier. A contract information identifier, adding the newly added contract information identifier to the preset first prohibited query list.

In one embodiment, the block chain-based electronic contract query device in the embodiment of the present disclosure also includes:

The second receiving module 730 (not shown in the figure), is used for the query terminal to receive the contract file list query request sent by the query client, wherein the contract file list query request includes: contract file list identifier;

A sixth determining module 740 (not shown in the figure), configured to determine whether the contract file list identifier belongs to the preset first prohibited query list;

The fourth obtaining module 750 (not shown in the figure), is configured to respond to that the contract file list identification does not belong to the preset first prohibited query list, based on the contract file list identification, from the block chain Obtain the contract document list identified by the contract document list identifier;

The second feedback module 760 (not shown in the figure) is configured to feed back the contract file list identified by the contract file list identifier to the query client.

In addition, an embodiment of the present disclosure also provides an electronic device, including: a memory configured to store a computer program;

The processor is configured to execute the computer program stored in the memory, and when the computer program is executed, implement the blockchain-based electronic contract query method described in any of the above-mentioned embodiments of the present disclosure.

Fig. 7 is a schematic structural diagram of an application embodiment of the electronic device of the present disclosure. As shown in Figure 7, an electronic device includes one or more processors and memory.

The processor may be a central processing unit (CPU) or other form of processing unit having data processing capabilities and/or instruction execution capabilities, and may control other components in the electronic device to perform desired functions.

The memory may include one or more computer program products, which may include various forms of computer-readable storage media, such as volatile memory and/or non-volatile memory. The volatile memory may include, for example, a random access memory (RAM) and/or a cache memory (cache). The non-volatile memory may include, for example, a read-only memory (ROM), a hard disk, a flash memory, and the like. One or more computer program instructions can be stored on the computer-readable storage medium, and the processor can execute the program instructions to realize the blockchain-based electronic contract query of the various embodiments of the present disclosure described above method and/or other desired functionality.

In an example, the electronic device may further include: an input device and an output device, and these components are interconnected through a bus system and/or other forms of connection mechanisms (not shown).

In addition, the input device may also include, for example, a keyboard, a mouse, and the like.

The output device can output various information to the outside, including determined distance information, direction information, and the like. The output devices may include, for example, displays, speakers, printers, and communication networks and their connected remote output devices, among others.

Of course, for simplicity, only some of the components related to the present disclosure in the electronic device are shown in FIG. 7 , and components such as bus, input/output interface, etc. are omitted. In addition, the electronic device may also include any other suitable components according to specific applications.

In addition to the methods and devices described above, embodiments of the present disclosure may also be computer program products, which include computer program instructions that, when executed by a processor, cause the processor to perform the functions described in the foregoing sections of this specification. Steps in the blockchain-based electronic contract query method of various embodiments of the present disclosure.

The computer program product can be written in any combination of one or more programming languages to execute the program codes for performing the operations of the embodiments of the present disclosure, and the programming languages include object-oriented programming languages, such as Java, C++, etc. , also includes conventional procedural programming languages, such as the "C" language or similar programming languages. The program code may execute entirely on the user's computing device, partly on the user's device, as a stand-alone software package, partly on the user's computing device and partly on a remote computing device, or entirely on the remote computing device or server to execute.

In addition, the embodiments of the present disclosure may also be a computer-readable storage medium, on which computer program instructions are stored, and the computer program instructions, when executed by a processor, cause the processor to execute the method according to the present invention described in the above part of this specification. The steps in the blockchain-based electronic contract query method of various embodiments are disclosed.

The computer readable storage medium may employ any combination of one or more readable media. The readable medium may be a readable signal medium or a readable storage medium. The readable storage medium may include, but not limited to, electronic, magnetic, optical, electromagnetic, infrared, or semiconductor systems, devices, or devices, or any combination thereof. More specific examples (non-exhaustive list) of readable storage media include: electrical connection with one or more conductors, portable disk, hard disk, random access memory (RAM), read only memory (ROM), erasable programmable read-only memory (EPROM or flash memory), optical fiber, portable compact disk read-only memory (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the above.

Those of ordinary skill in the art can understand that all or part of the steps for realizing the above-mentioned method embodiments can be completed by hardware related to program instructions, and the aforementioned program can be stored in a computer-readable storage medium. When the program is executed, the It includes the steps of the above method embodiments; and the aforementioned storage medium includes: ROM, RAM, magnetic disk or optical disk and other various media that can store program codes.

The basic principles of the present disclosure have been described above in conjunction with specific embodiments, but it should be pointed out that the advantages, advantages, effects, etc. mentioned in the present disclosure are only examples rather than limitations, and these advantages, advantages, effects, etc. Various embodiments of the present disclosure must have. In addition, the specific details disclosed above are only for the purpose of illustration and understanding, rather than limitation, and the above details do not limit the present disclosure to be implemented by using the above specific details.

Each embodiment in this specification is described in a progressive manner, each embodiment focuses on the difference from other embodiments, and the same or similar parts of each embodiment can be referred to each other. As for the system embodiment, since it basically corresponds to the method embodiment, the description is relatively simple, and for the related parts, please refer to the part of the description of the method embodiment.

The block diagrams of devices, devices, devices, and systems involved in the present disclosure are only illustrative examples and are not intended to require or imply that they must be connected, arranged, and configured in the manner shown in the block diagrams. As will be appreciated by those skilled in the art, these devices, devices, devices, systems may be connected, arranged, configured in any manner. Words such as "including", "comprising", "having" and the like are open-ended words meaning "including but not limited to" and may be used interchangeably therewith. As used herein, the words "or" and "and" refer to the word "and/or" and are used interchangeably therewith, unless the context clearly dictates otherwise. As used herein, the word "such as" refers to the phrase "such as but not limited to" and can be used interchangeably therewith.

The methods and apparatus of the present disclosure may be implemented in many ways. For example, the methods and apparatuses of the present disclosure may be implemented by software, hardware, firmware or any combination of software, hardware, and firmware. The above sequence of steps for the method is for illustration only, and the steps of the method of the present disclosure are not limited to the sequence specifically described above unless specifically stated otherwise. Furthermore, in some embodiments, the present disclosure can also be implemented as programs recorded in recording media, the programs including machine-readable instructions for realizing the method according to the present disclosure. Thus, the present disclosure also covers a recording medium storing a program for executing the method according to the present disclosure.

It should also be pointed out that, in the devices, equipment and methods of the present disclosure, each component or each step can be decomposed and/or reassembled. These decompositions and/or recombinations should be considered equivalents of the present disclosure.

The above description of the disclosed aspects is provided to enable any person skilled in the art to make or use the present disclosure. Various modifications to these aspects will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other aspects without departing from the scope of the present disclosure. Thus, the present disclosure is not intended to be limited to the aspects shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

The foregoing description has been presented for purposes of illustration and description. Furthermore, this description is not intended to limit the disclosed embodiments to the forms disclosed herein. Although a number of example aspects and embodiments have been discussed above, those skilled in the art will recognize certain variations, modifications, changes, additions and sub-combinations thereof.

Claims (10)

1. An electronic contract query method based on a block chain is characterized by comprising the following steps:

the method comprises the following steps that an inquiry terminal receives an electronic contract inquiry request sent by an inquiry client, wherein the electronic contract inquiry request comprises the following steps: inquiring client identification, contract information identification and target hash value;

in response to determining that the contract information identifier does not belong to a preset first prohibited query list and the query client identifier does not belong to a preset second prohibited query list, determining whether the contract information identifier belongs to a preset contract information identifier storage list;

responding to the contract information identification belonging to the preset contract information identification storage list, and acquiring contract information identified by the contract information identification, wherein the contract information comprises: at least one contract file hash value and a contract file identifier corresponding to each contract file hash value in the at least one contract file hash value respectively;

determining whether a contract file hash value identical to the target hash value exists in the contract information;

in response to the contract information having the contract file hash value identical to the target hash value, acquiring a target contract file from a block chain based on a contract file identifier corresponding to the contract file hash value identical to the target hash value;

and feeding the target contract document back to the query client.

2. The method of claim 1, wherein the contract information further comprises: contract status; the method further comprises the following steps:

determining whether the contract state is a contract completion state;

and in response to that the contract state is a contract completion state, executing the operation of determining whether a contract file hash value identical to the target hash value exists in the contract information.

3. The method of claim 1, wherein the contract information comprises: generating time corresponding to each contract file hash value in the at least one contract file hash value respectively; the method further comprises the following steps:

determining a contract file hash value corresponding to generation time closest to the current time as a target contract file hash value in response to the contract information that the contract file hash value same as the target hash value does not exist;

and acquiring the target contract file from the block chain based on the contract file identifier corresponding to the hash value of the target contract file.

4. The method of claim 1, further comprising:

the inquiry terminal determines the contract information identifier to be added into the preset first prohibited inquiry list as a newly added contract information identifier;

and in response to that the preset first query forbidding list does not contain the newly added contract information identification and the preset contract information identification storage list contains the newly added contract information identification, adding the newly added contract information identification into the preset first query forbidding list.

5. The method of any of claims 1-4, further comprising:

the query terminal receives a contract document list query request sent by the query client, wherein the contract document list query request comprises: contract document list identification;

determining whether the contract file list identification belongs to the preset first query forbidding list;

responding to the fact that the contract file list identification does not belong to the preset first query forbidden list, and acquiring a contract file list identified by the contract file list identification from the block chain based on the contract file list identification;

and feeding back the contract document list identified by the contract document list identification to the query client.

6. An electronic contract inquiry apparatus based on a block chain, comprising:

a first receiving module, configured to receive, by a query terminal, an electronic contract query request sent by a query client, where the electronic contract query request includes: inquiring a client identification, a contract information identification and a target hash value;

the first determining module is used for determining whether the contract information identifier belongs to a preset contract information identifier storage list or not in response to the fact that the contract information identifier does not belong to a preset first prohibited query list and the query client identifier does not belong to a preset second prohibited query list;

a first obtaining module, configured to obtain, in response to that the contract information identifier belongs to the preset contract information identifier storage list, contract information identified by the contract information identifier, where the contract information includes: at least one contract file hash value and a contract file identifier corresponding to each contract file hash value in the at least one contract file hash value respectively;

a second determining module, configured to determine whether a contract file hash value identical to the target hash value exists in the contract information;

a second obtaining module, configured to, in response to a contract file hash value that is the same as the target hash value existing in the contract information, obtain a target contract file from a block chain based on a contract file identifier corresponding to the contract file hash value that is the same as the target hash value;

and the first feedback module is used for feeding the target contract file back to the query client.

7. The apparatus of claim 6, wherein the contract information further comprises: contract status; the device further comprises:

a third determining module, configured to determine whether the contract status is a contract completion status;

and the execution module is used for responding to the contract state as a contract completion state and executing the operation of determining whether the contract information has the contract file hash value which is the same as the target hash value.

8. The apparatus of claim 6, wherein the contract information comprises: the generation time corresponding to each contract file hash value in the at least one contract file hash value is respectively; the device further comprises:

a fourth determining module, configured to determine, in response to that there is no contract file hash value that is the same as the target hash value in the contract information, a contract file hash value corresponding to a generation time closest to a current time as a target contract file hash value;

a third obtaining module, configured to obtain the target contract file from the block chain based on a contract file identifier corresponding to the hash value of the target contract file.

9. An electronic device, comprising:

a memory for storing a computer program;

a processor for executing a computer program stored in the memory, and when executed, implementing the method of any of the preceding claims 1-5.

10. A computer-readable storage medium, on which a computer program is stored, which, when being executed by a processor, carries out the method of any one of the preceding claims 1 to 5.

Images