HK40090172A - A blockchain-based method, device and electronic equipment for document management - Google Patents

Description

A blockchain-based document management method, device, and electronic device

Technical Field

This invention relates to the field of blockchain technology, and in particular to a blockchain-based document management method, apparatus, and electronic device.

Background Technology

With the rapid development of internet technology, many companies need to handle a large number of internal or external paper documents.

Currently, all documents require certification or verification by administrative/management/professionals. The certification process involves many security issues, including the reliability of paper documents and the validity of handwritten signatures.

Summary of the Invention

Therefore, it is necessary to provide a blockchain-based document management method, device, and electronic device to address the aforementioned technical issues and ensure document security.

In a first aspect, embodiments of the present invention provide a blockchain-based document management method, the method comprising:

Receive documents sent by the creator;

The document is queried in the blockchain to obtain the first file record corresponding to it, and a second file record is generated, wherein the first file record includes a first signature and the second file record includes a second signature;

The second file record is uploaded to the blockchain, and the document is sent to the validator so that the validator can verify the second file record in the blockchain based on the document.

In some embodiments, prior to receiving the document sent by the creator, the method further includes:

Create a document;

Calculate the root hash value of the Merkle tree of the document, and set the document's identifier as the root hash value;

A first signature is generated on the root hash value using the creator's private key;

The first file record is obtained by combining the identification code, the root hash value, the creator's first signature, the creator's public key, and the document's metadata.

The first file record is uploaded to the blockchain, and the document is transmitted to the signer.

In some embodiments, querying the first file record corresponding to the document in the blockchain and generating the second file record includes:

Calculate the root hash value of the Merkle tree of the document;

The document's identifier is determined based on the root hash value;

Based on the identification code, query the first file record corresponding to the document in the blockchain;

If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the first file record on the blockchain, and the first signature verification is successful, then a second signature is generated on the root hash value of the Merkle tree in the first file record using the signer's private key.

The signer's second signature and the signer's public key are added to the first file record to generate a second file record.

In some embodiments, the verifier verifies the second document record in the blockchain based on the document, including:

Calculate the root hash value of the Merkle tree of the document;

The document's identifier is determined based on the root hash value;

Based on the identification code, query the second file record corresponding to the document in the blockchain;

If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the second file record on the blockchain, and both the first signature and the second signature are verified, then the document is verified.

In some embodiments, the method further includes:

The first document record is uploaded to the blockchain, and the document's identification code is transmitted to the signer.

In some embodiments, transmitting the document to the signer includes:

The creator uses an encryption key to encrypt the document, thus obtaining the encrypted document;

The encrypted document is then transmitted to the signer.

In some embodiments, the method further includes:

The identification code is obtained by using a label on a paper document, the label storing the document's identification code.

Secondly, embodiments of the present invention also provide a blockchain-based document management device, the device comprising:

The receiving module is used to receive documents sent by the creator.

The first generation module is used to query the first file record corresponding to the document in the blockchain and generate a second file record, wherein the first file record includes a first signature and the second file record includes a second signature;

The verification module is used to upload the second file record to the blockchain and send the document to the verifier so that the verifier can verify the second file record in the blockchain based on the document.

Thirdly, embodiments of the present invention also provide an electronic device, comprising:

At least one processor; and,

A memory communicatively connected to the at least one processor; wherein,

The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method described in the first aspect.

Fourthly, embodiments of the present invention also provide a non-volatile computer-readable storage medium storing computer-executable instructions that, when executed by a processor, cause the processor to perform the method described in the first aspect.

Compared with the prior art, the beneficial effects of the present invention are as follows: Unlike the prior art, in the blockchain-based document management method, apparatus, and electronic device embodiments of the present invention, the signer receives a document sent by the creator, then queries the blockchain for the first file record corresponding to the document, and generates a second file record. The first file record includes a first signature, and the second file record includes a second signature. Then, the signer sends the document to the verifier, who verifies the second file record in the blockchain based on the document. Thus, by having different users sign the document and upload the file record to the blockchain, the security of the document can be guaranteed.

Attached Figure Description

One or more embodiments are illustrated by way of example with reference numerals in the accompanying drawings. These illustrations do not constitute a limitation on the embodiments. Elements with the same reference numerals in the drawings are denoted as similar elements. Unless otherwise stated, the figures in the drawings are not to be limited by scale.

Figure 1 is a schematic diagram of the application scenario of the blockchain-based document management method in an embodiment of the present invention;

Figure 2 is a flowchart illustrating a blockchain-based document management method in one embodiment of the present invention;

Figure 3 is a schematic diagram of the process of a creator creating a document in one embodiment of the present invention;

Figure 4 is a schematic diagram of the process of generating a second file record in one embodiment of the present invention;

Figure 5 is a schematic diagram of the process for verifying the second file record in one embodiment of the present invention;

Figure 6 is a schematic diagram of the structure of a blockchain-based document management device in one embodiment of the present invention;

Figure 7 is a schematic diagram of the hardware structure of an electronic device in one embodiment of the present invention.

Detailed Implementation

To make the objectives, technical solutions, and advantages of the embodiments of the present invention clearer, the technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

It should be noted that, unless otherwise specified, the various features in the embodiments of this invention can be combined with each other, all of which are within the protection scope of this invention. Furthermore, although functional modules are divided in the device schematic diagram and a logical order is shown in the flowchart, in some cases, the steps shown or described can be executed in a different order than the module division in the device or the order in the flowchart. Moreover, the terms "first," "second," and "third" used in this invention do not limit the data or execution order, but only distinguish identical or similar items with essentially the same function and effect.

To facilitate understanding of this invention, the concepts involved in this invention will be explained below.

Digital signature schemes: Digital signatures are schemes used to prove and verify the authenticity of digital information. Digital signatures are based on public-key cryptography and private-key cryptography. The public key can be freely published, but the private key is kept secret only by the user. Let sign: (sk, m) → δ be the signature algorithm. Using the private key sk to sign the message digest m, a digital signature δ is formed. The verifier or receiver can execute the verification algorithm, using the public key (pk, m, δ) to decrypt the digital signature and check its validity. With the help of the public key pk, the verifier can determine whether the digital signature δ matches the message digest m. RSA encryption algorithm and ECDSA elliptic curve signature algorithm are popular digital signature schemes in most systems on the market.

Merkle Tree: A Merkle tree, also known as a hash tree, is a tree-like data structure. It allows users to perform hash function calculations on multiple data items and output a single value, the root hash, as the representative. Let V = { _v1 , _v2 , ..., _vn } be the sequence of values. We use MTree: V → (tree, root) to represent the construction algorithm of the Merkle tree. Inputting V will produce the structure tree and the root hash value root. Merkle trees also provide an efficient way to prove and verify membership while protecting privacy. The proof algorithm can be represented as prove: (tree, v) → proofs. Where proofs = { _h1 , _h2 , ..., _hm } are values relative to the value v. The root hash value can be recalculated and verified using the verify algorithm. The verify algorithm is then expressed as: verify: (v, proofs, root) → accept/reject. When the values proofs and v can be reassembled to form a hash tree with the root hash value root, it will accept the result.

Changes during implementation can be verified through numerical values and metrics. Proof drills and verification drills are represented as provedx:(tree, idx)→proofs and verifyIdx(v, idx, proofs, root)→accept/reject, respectively. Here, idx is the metric of v in V.

The blockchain-based document management method provided in this embodiment of the invention is applicable to the application scenario shown in Figure 1, which includes a creator, at least one signer, and a verifier. Figure 1 exemplarily shows a creator 10, a signer 20, and a verifier 30, wherein the signer 20 is communicatively connected to both the creator 10 and the verifier 30.

Creator 10 creates a document and sends it to signer 20, while simultaneously uploading the corresponding file record to the blockchain. The file record includes the document's identifier, metadata, root hash value, creator's public key, and creator's signature. Signer 20 receives the document from creator 10, queries the block for the corresponding file record, generates its own signature based on the creator's file record, and adds its own public key to the file record, thus forming a new file record. This new file record includes the document's identifier, metadata, root hash value, creator's public key, creator's signature, and the signer's public key and signature. Signer 20 uploads the new file record to the blockchain and simultaneously sends the document to verifier 30. Verifier 30 receives the document from signer 20 and verifies the new file record in the blockchain based on the document.

It should be noted that the method provided in this embodiment of the invention can be further extended to other suitable application scenarios, and is not limited to the application scenario shown in Figure 1. In actual application, the application scenario may include more or fewer creators, signers and verifiers.

As shown in Figure 2, the blockchain-based document management method provided in this embodiment of the invention includes:

Step 202: Receive the document sent by the creator.

The signer receives the document from the creator via a secure transfer.

In some embodiments, as shown in Figure 3, before the signer receives the document sent by the creator, the creator first needs to create the document, the method of which includes:

Step 302, create a document.

Step 304: Calculate the root hash value of the Merkle tree of the document, and set the document's identifier as the root hash value.

Specifically, the creator first needs to register in a blockchain-based document verification and management system (dBC system), creating their own public and private keys. The creator's public key is stored in the blockchain, while the private key is kept secret. After the creator's public and private keys are created, they proceed to create the document. The creator calculates the root hash value of the document's Merkle tree and sets the document's identifier ID to the calculated root hash value. For example, let doc = {d, _a1 , _a2 , ..., _an } represent a document with an attachment list. The creator calculates the root hash value of the document's Merkle tree using root←MTree(doc) and sets the document's identifier ID = root.

Step 306: Generate the first signature on the root hash value using the creator's private key.

After the creator sets the document's identifier as the root hash value, they can use their registered private key to sign the root hash value, forming the first signature. For example, continuing the previous example, the creator uses δ _creator← sign(sk _creator , root) to generate the signature δ _creator on the root hash value root.

Step 308: Combine the identification code, the root hash value, the creator's first signature, the creator's public key, and the document's metadata to obtain the first file record.

Step 310: Upload the first file record to the blockchain and transmit the document to the signer.

In this embodiment of the invention, the first file record includes the document's identifier ID, the document's metadata meta, the root hash value root, the creator's first signature δ _creator , and the creator's registered public key pk _creator . All of the above information is combined to obtain the first file record. For example, the first file record can be, for instance, rec = (ID, root, δ _creator , pk _creator , meta). Specifically, the creator uploads the first file record to the blockchain and simultaneously transmits the document to the signer via a secure means.

In some embodiments, as one implementation of step 310, the method includes: the creator encrypting the document using an encryption key to obtain an encrypted document; and transmitting the encrypted document to the signer.

In this embodiment of the invention, to ensure document security, the creator can encrypt the created document using an encryption key before transmitting it to the signer. Specifically, when the creator chooses to encrypt the file doc using an encryption key, they must first generate a file encryption key and a decryption key K _doc , and then encrypt the ciphertext C _doc using C _doc ← Enc(k _doc , doc). The Merkle root hash value and signature are preset as root ← MTree(doc) and δ _creator ← sign(sk _creator , root). After the document is encrypted, it will be in ciphertext C _doc format when transferred or stored, rather than in plain text format, thus ensuring document security. If the recipient needs the decryption key to view the original document, it must be transmitted through a secure key transmission mechanism. The secure key transmission mechanism is as follows: the recipient obtains the decryption key K _doc through a secure channel, and the recipient retrieves the decryption key K _doc from a lockable NFC tag on the paper document. After receiving the ciphertext C _doc , the verifier and signer can decrypt the original doc using doc←Dec(k _doc , c _doc ). After decryption, they can perform document checks as usual.

Step 204: Query the first file record corresponding to the document in the blockchain and generate a second file record, wherein the first file record includes a first signature and the second file record includes a second signature.

The second document record is generated based on the first document record, which includes a first signature, and the second document record includes a second signature. Specifically, after receiving the document from the creator via a secure means, the signer queries the blockchain for the corresponding first document record, thereby generating the second document record based on the first document record.

In some embodiments, as shown in FIG4, as a specific implementation of step 204, the method includes:

Step 402: Calculate the root hash value of the Merkle tree of the document.

Step 404: Determine the document's identifier based on the root hash value.

Step 406: Based on the identification code, query the first file record corresponding to the document in the blockchain.

In this embodiment of the invention, the signer calculates the root hash value of the Merkle tree of the document and searches the blockchain based on the root hash value to find the document's identifier. Since the creator sets the document's identifier as the root hash value of the Merkle tree, the document's identifier ID can be determined simply by determining the root hash value. Specifically, the signer uses the identifier ID to query the first file record in the blockchain, i.e., rec = (ID, root, δ _creator , pk _creator , meta).

Step 408: If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the first file record on the blockchain, and the first signature verification is successful, then a second signature is generated on the root hash value of the Merkle tree in the first file record using the signer's private key.

In this embodiment of the invention, the signer needs to check the validity of the root hash value and the creator's signature. Specifically, the signer needs to ensure that the root hash value of the document's Merkle tree is equal to the root hash value of the Merkle tree in the first file record stored on the blockchain, and that the first signature verification passes before the signer will proceed with the signing.

Specifically, the signer determines whether the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the first document record stored in the blockchain. If they are equal, the signer uses the creator's public key for verification, that is, to determine whether the root hash value of the document's Merkle tree and the creator's public key can be reassembled to form the first signature. If they can be used, the first signature verification is successful. After successful verification, the signer uses their private key to generate a second signature based on the root hash value of the Merkle tree in the first document record. If neither of the above two conditions is met, or only one condition is met, it means that the document verification fails, and the signer can refuse to sign, at which point the signing process will be stopped. It should be noted that the order of checking the root hash value and the signature validity can be set according to needs and is not limited to the limitations of this embodiment. The root hash value can be checked first, followed by the signature, or the signature can be checked first, followed by the root hash value.

Step 410: Add the signer's second signature and the signer's public key to the first file record to generate a second file record.

Specifically, after generating a second signature on the root hash value of the Merkle tree in the first document record, the signer can add the second signature and their own public key to the first document record to generate a second document record. For example, the signer's second signature could be δ _signer , and the signer's public key could be pk _signer . The signer adds δ _signer and pk _signer to the first document record, resulting in the second document record rec = (ID, root, δ _creator , pk _creator , δ _signer , pk _signer , meta). That is, the second document record includes the document identifier, metadata, root hash value, first signature, creator's public key, signer's public key, and second signature.

Step 206: Upload the second file record to the blockchain and send the document to the verifier so that the verifier can verify the second file record in the blockchain based on the document.

Specifically, the signer uploads the second document record to the blockchain and simultaneously transmits the document to the verifier via a secure means, so that the verifier can verify the second document record in the blockchain based on the document.

In this embodiment of the invention, the signer receives a document sent by the creator, then queries the blockchain for the first file record corresponding to the document and generates a second file record. The signer then sends the document to the verifier, who verifies the second file record in the blockchain based on the document. Thus, by having different users sign the document and upload the file record to the blockchain, the security of the document can be guaranteed.

In some embodiments, as shown in FIG5, as one implementation of step 206, the method includes:

Step 502: Calculate the root hash value of the Merkle tree of the document.

Step 504: Determine the document's identifier based on the root hash value.

Step 506: Based on the identification code, query the second file record corresponding to the document in the blockchain.

In this embodiment of the invention, after receiving the document transmitted securely by the signer, the verifier calculates the root hash value of the document's Merkle tree and searches the blockchain based on the root hash value to obtain the document's identifier. Since the creator sets the document's identifier as the root hash value of the Merkle tree, the document's identifier ID can be determined simply by determining the root hash value. Specifically, the verifier uses the identifier ID to query the second file record in the blockchain, i.e., rec = (ID, root, δ _creator , pk _creator , δ _signer , pk _signer , meta).

Step 508: If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the second file record on the blockchain, and both the first signature and the second signature are verified, then the document is verified.

In this embodiment of the invention, the verifier is responsible for checking the validity of the root hash value and all signatures. Specifically, the verifier needs to check whether the root hash value of the document's Merkle tree is equal to the root hash value of the Merkle tree in the second file record stored on the blockchain, and also needs to check the validity of the first and second signatures, i.e., whether the first and second signatures pass verification. If any of the above verifications fail, the document will be automatically rejected by the verifier. Conversely, if all verifications pass, the document passes verification.

Specifically, the verifier checks if the root hash value of the document's Merkle tree is equal to the root hash value of the Merkle tree in the second document record stored in the blockchain. If they are equal, the verifier uses the creator's public key to verify whether the root hash value of the document's Merkle tree and the creator's public key can be reassembled to form the first signature. If the first signature can be reassembled, the verifier continues to use the signer's public key to verify whether the root hash value of the document's Merkle tree and the signer's public key can be reassembled to form the second signature. If the second signature can be assembled, the document passes verification. If none of the above three conditions are met, or only one or two conditions are met, the document fails verification.

In some embodiments, the method further includes: uploading the first document record to a blockchain, and transmitting the document's identifier to the signer.

In this embodiment of the invention, to improve data liquidity, after creating a document, the creator uploads the corresponding first file record to the blockchain, but does not transmit the document to the signer. Instead, the signer transmits the document's identification code to the signer. The signer can then use the identification code to directly download the document from the blockchain. Similarly, the signer does not transmit the document to the verifier, but instead transmits the identification code to the verifier, who can also use the identification code to download the document from the blockchain.

Optionally, in some other embodiments, the method further includes: obtaining the identification code through a label on a paper document, the label storing the document's identification code.

In this embodiment of the invention, attaching the tag to a paper document facilitates the binding of the paper document and its digitization. When the document is created, the identification ID is stored in the tag. Therefore, signers and verifiers can retrieve the document and signature in the blockchain through the tag on the paper document. To prevent the tag from being modified, a lockable NFC tag can be used.

Accordingly, this embodiment of the invention provides a blockchain-based document management device 600, as shown in FIG6. The device 600 includes:

The receiving module 602 is used to receive the document sent by the creator;

The first generation module 604 is used to query the first file record corresponding to the document in the blockchain and generate a second file record, wherein the first file record includes a first signature and the second file record includes a second signature;

The verification module 606 is used to upload the second file record to the blockchain and send the document to the verifier so that the verifier can verify the second file record in the blockchain based on the document.

In this embodiment of the invention, a receiving module receives a document sent by the creator, then queries the blockchain for the first file record corresponding to the document, and a generating module generates a second file record. The first file record includes a first signature, and the second file record includes a second signature. The second file record is then uploaded to the blockchain, and the document is sent to a verifier so that the verifier can verify the second file record in the blockchain based on the document through a verification module. Thus, by having different users sign the document and upload the file record to the blockchain, the security of the document can be guaranteed.

Optionally, in other embodiments of the device, as shown in FIG6, the device 600 further includes:

Create module 608 for creating documents;

The calculation module 610 is used to calculate the root hash value of the Merkle tree of the document and set the identification code of the document as the root hash value;

The second generation module 612 is used to generate a first signature on the root hash value using the creator's private key;

The combination module 614 is used to combine the identification code, the root hash value, the creator's first signature, the creator's public key, and the document's metadata to obtain a first file record;

The first file record is uploaded to the blockchain, and the document is transmitted to the signer.

Optionally, in other embodiments of the device, as shown in FIG6, the device 600 further includes:

The first transmission module 618 is used to upload the first file record to the blockchain and transmit the document's identification code to the signer.

Optionally, in other embodiments of the device, as shown in FIG6, the device 600 further includes:

The encryption module 620 is used by the creator to encrypt the document using an encryption key to obtain an encrypted document;

The second transmission module 622 is used to transmit the encrypted document to the signer.

Optionally, in other embodiments of the device, the first generation module 604 is specifically used for:

Calculate the root hash value of the Merkle tree of the document;

The document's identifier is determined based on the root hash value;

Based on the identification code, query the first file record corresponding to the document in the blockchain;

If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the first file record on the blockchain, and the first signature verification is successful, then a second signature is generated on the root hash value of the Merkle tree in the first file record using the signer's private key.

The signer's second signature and the signer's public key are added to the first file record to generate a second file record.

Alternatively, in other embodiments of the device, the verification module 606 is specifically used for:

Calculate the root hash value of the Merkle tree of the document;

The document's identifier is determined based on the root hash value;

Based on the identification code, query the second file record corresponding to the document in the blockchain;

If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the second file record on the blockchain, and both the first signature and the second signature are verified, then the document is verified.

It should be noted that the aforementioned blockchain-based document management device can execute the blockchain-based document management method provided in the embodiments of the present invention, and possesses the corresponding functional modules and beneficial effects of the method. Technical details not described in detail in the embodiments of the blockchain-based document management device can be found in the blockchain-based document management method provided in the embodiments of the present invention.

Figure 7 is a schematic diagram of the hardware structure of an electronic device provided in an embodiment of the present invention. As shown in Figure 7, the electronic device 700 includes:

One or more processors 702 and a memory 704 are provided. Figure 7 shows an example of one processor 702. The processor 702 can be a central processing unit (CPU), a graphics processing unit (GPU), or a processor that integrates the functions of both a CPU and a GPU.

The processor 702 and the memory 704 can be connected via a bus or other means. Figure 7 shows an example of a connection via a bus.

The memory 704, as a non-volatile computer-readable storage medium, can be used to store non-volatile software programs, non-volatile computer-executable programs, and modules, such as the program instructions/modules corresponding to the blockchain-based document management method in this embodiment of the invention. The processor 702 executes various functional applications and data processing of the electronic device by running the non-volatile software programs, instructions, and modules stored in the memory 704, thereby realizing the blockchain-based document management method in the above embodiment.

The memory 704 may include a program storage area and a data storage area. The program storage area may store the operating system and applications required for at least one function; the data storage area may store data created for use by the blockchain-based document management device. Furthermore, the memory 704 may include high-speed random access memory and may also include non-volatile memory, such as at least one disk storage device, flash memory device, or other non-volatile solid-state storage device. In some embodiments, the memory 704 may optionally include memory remotely located relative to the processor 702, and these remote memories can be connected to the blockchain-based document management device via a network. Examples of such networks include, but are not limited to, the Internet, corporate intranets, local area networks, mobile communication networks, and combinations thereof.

This invention also provides a non-volatile computer-readable storage medium storing computer-executable instructions. When these computer-executable instructions are executed by one or more processors, they enable the one or more processors to execute the blockchain-based document management method in any of the above method embodiments.

The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs.

Through the above description of the embodiments, those skilled in the art can clearly understand that each embodiment can be implemented using software and a general-purpose hardware platform, or of course, using hardware. Those skilled in the art will understand that all or part of the processes in the above embodiments can be implemented by a computer program instructing related hardware. The program can be stored in a computer-readable storage medium, and when executed, it can include the processes of the embodiments of the above methods. The storage medium can be a magnetic disk, optical disk, read-only memory (ROM), or random access memory (RAM), etc.

Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention, and not to limit them; under the concept of the present invention, the technical features of the above embodiments or different embodiments can also be combined, the steps can be implemented in any order, and there are many other variations of different aspects of the present invention as described above, which are not provided in detail for the sake of brevity; although the present invention has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features; and these modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the scope of the technical solutions of the embodiments of the present invention.

Claims (10)

1. A blockchain-based document management method, characterized in that the method includes: Receive documents sent by the creator; The document is queried in the blockchain to obtain the first file record corresponding to it, and a second file record is generated, wherein the first file record includes a first signature and the second file record includes a second signature; The second file record is uploaded to the blockchain, and the document is sent to the validator so that the validator can verify the second file record in the blockchain based on the document. 2. The method according to claim 1, characterized in that, before receiving the document sent by the creator, the method further includes: Create a document; Calculate the root hash value of the Merkle tree of the document, and set the document's identifier as the root hash value; A first signature is generated on the root hash value using the creator's private key; The first file record is obtained by combining the identification code, the root hash value, the creator's first signature, the creator's public key, and the document's metadata. The first file record is uploaded to the blockchain, and the document is transmitted to the signer. 3. The method according to claim 2, characterized in that, querying the first file record corresponding to the document in the blockchain and generating the second file record includes: Calculate the root hash value of the Merkle tree of the document; The document's identifier is determined based on the root hash value; Based on the identification code, query the first file record corresponding to the document in the blockchain; If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the first file record on the blockchain, and the first signature verification is successful, then a second signature is generated on the root hash value of the Merkle tree in the first file record using the signer's private key. The signer's second signature and the signer's public key are added to the first file record to generate a second file record. 4. The method according to claim 3, wherein the verifier verifies the second document record in the blockchain based on the document, comprising: Calculate the root hash value of the Merkle tree of the document; The document's identifier is determined based on the root hash value; Based on the identification code, query the second file record corresponding to the document in the blockchain; If the root hash value of the Merkle tree of the document is equal to the root hash value of the Merkle tree in the second file record on the blockchain, and both the first signature and the second signature are verified, then the document is verified. 5. The method according to claim 1, characterized in that the method further comprises: The first document record is uploaded to the blockchain, and the document's identification code is transmitted to the signer. 6. The method according to claim 2, wherein transmitting the document to the signer comprises: The creator uses an encryption key to encrypt the document, thus obtaining the encrypted document; The encrypted document is then transmitted to the signer. 7. The method according to any one of claims 1-6, characterized in that the method further comprises: The identification code is obtained by using a label on a paper document, the label storing the document's identification code. 8. A blockchain-based document management device, characterized in that the device comprises: The receiving module is used to receive documents sent by the creator. The first generation module is used to query the first file record corresponding to the document in the blockchain and generate a second file record, wherein the first file record includes a first signature and the second file record includes a second signature; The verification module is used to upload the second file record to the blockchain and send the document to the verifier so that the verifier can verify the second file record in the blockchain based on the document. 9. An electronic device, characterized in that it comprises: At least one processor; and, A memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor to enable the at least one processor to perform the method according to any one of claims 1-7. 10. A non-volatile computer-readable storage medium, characterized in that the computer-readable storage medium stores computer-executable instructions that, when executed by a processor, cause the processor to perform the method as described in any one of claims 1-7.