Method, device, computer equipment and storage medium for transmitting asset certification documents

Abstract

The present application relates to a method, apparatus, computer equipment, storage medium, and computer program product for transmitting an asset certification document, which can be applied in the field of information security technology and can balance data security and transmission efficiency during the transmission of the asset certification document. The method comprises: responding to a certification transmission message of an asset certification document of an account carried by a first node, determining a first block generated for the asset certification document from a blockchain, and verifying the asset certification document based on the file information of the asset certification document stored in the first block; if the verification passes, generating a second block based on the file information of the asset certification document; uplinking the second block to the blockchain, and sending the asset certification document to the second node when the certification transmission message indicates that the target transmission node of the asset certification document is a second node communicating with the current node, so that the second node verifies the obtained asset certification document based on the file information of the asset certification document stored in the second block.

Description

Technical Field

[0001] The present application relates to the field of information security technology, and in particular to a method, apparatus, computer equipment, storage medium, and computer program product for transmitting asset certification documents. Background Art

[0002] With the development of computer technology, when users handle business and provide asset proof documents, they often need to go to multiple different institutions to apply offline, which is time-consuming and laborious.

[0003] In related technologies, in order to increase the efficiency of transmitting asset certification documents between different institutions, some institutions will use guarantee centers to transmit asset certification documents between different institutions, that is, all asset certification documents are transmitted to the target institution through the guarantee center; or, they will directly establish transmission channels between different institutions to conduct point-to-point asset certification document transmission.

[0004] However, the former approach struggles to find a highly trusted guarantee center, and the risk of data tampering persists during the transmission of asset proof documents. The latter, on the other hand, requires establishing transmission channels with multiple institutions, and as the number of participating institutions increases, the system complexity rapidly increases. Consequently, these technologies struggle to balance both efficiency and data security when transmitting asset proof documents. Summary of the Invention

[0005] Based on this, it is necessary to provide a method, device, computer equipment, computer-readable storage medium and computer program product for transmitting asset proof documents that can balance the transmission efficiency and data security of asset proof documents in order to address the above technical problems.

[0006] In a first aspect, the present application provides a method for transmitting an asset certification document. The method comprises:

[0007] In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block;

[0008] If the verification passes, a second block is generated based on the file information of the asset certification file;

[0009] The second block is uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, the asset proof file is sent to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0010] In one embodiment, the asset certification document carries a three-dimensional code generated by the first node, and determining the first block generated by the asset certification document for the account from the blockchain includes:

[0011] Decoding the three-dimensional code carried by the asset certificate, and obtaining reference file information corresponding to the asset certificate document based on the decoding result;

[0012] comparing the reference file information with the file information in the asset proof file received by the current node, and generating a block index based on the file information in the asset proof file when the reference file information matches the file information in the asset proof file;

[0013] Based on the block index, obtain a first block generated for the asset certification file of the account in the blockchain.

[0014] In one embodiment, generating a block index based on the file information in the asset certification file includes:

[0015] Reading the account ID of the account from the file information in the asset certification document, and obtaining the generation time of the three-dimensional code from the decoding result;

[0016] A block index is generated based on the account identifier and the generation time of the three-dimensional code.

[0017] In one embodiment, sending the asset certification file to the second node includes:

[0018] Obtaining color parameters of the facial image of the account, and generating a three-dimensional code based on the color parameters of the facial image, file information of the asset certification document, and the current time;

[0019] The three-dimensional code is added to the asset certification document, and the asset certification document carrying the three-dimensional code is sent to the second node.

[0020] In one embodiment, the proof transmission message further carries a block access token provided by the first node, and before verifying the asset proof file based on the file information of the asset proof file stored in the first block, the process further includes:

[0021] Sending a request for viewing a first block in the blockchain to the blockchain platform; the request carries the block access token, and the verification request is used to instruct the blockchain platform to verify the access rights of the current node based on the block access token;

[0022] If the verification is passed, the blockchain platform returns the file information of the asset certification file stored in the first block.

[0023] In one embodiment, the second block on the blockchain is a block signed by a node key corresponding to the current node, and the node key is generated based on a key seed of the current node. The method further includes:

[0024] When the key seed is lost, searching for a first backup node storing a backup key seed of the current node from multiple nodes;

[0025] Sending a backup seed acquisition request carrying the node identity information corresponding to the current node to the first backup node; the backup seed acquisition request is used to trigger the first backup node to match the node identity information with the identity authentication information associated with the pre-stored backup key seed;

[0026] In a case where the node identity information matches the identity authentication information, the backup key seed returned by the first backup node is received.

[0027] In one embodiment, searching for a first backup node storing a backup key seed of the current node from a plurality of nodes includes:

[0028] Broadcast backup node query requests for the current node to multiple nodes;

[0029] Upon receiving a response message from the second backup node to the backup node query request, sending a backup relationship acquisition request carrying the node identity information corresponding to the current node to the second backup node; the backup relationship acquisition request is used to trigger the second backup node to match the node identity information with the identity authentication information associated with the pre-stored backup mapping relationship;

[0030] When the node identity information matches the identity authentication information, receiving the backup mapping relationship returned by the second backup node;

[0031] Based on the backup mapping relationship, a first backup node storing the backup key seed of the current node is determined.

[0032] In a second aspect, the present application also provides a device for transmitting asset certification documents. The device includes:

[0033] a verification module, configured to respond to a proof transmission message from the first node carrying an asset certification document of an account, determine a first block generated for the asset certification document of the account from the blockchain, and verify the asset certification document based on file information of the asset certification document stored in the first block;

[0034] A block generation module, configured to generate a second block based on the file information of the asset certification file if the verification passes;

[0035] A file transfer module is configured to upload the second block to the blockchain, and, when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, send the asset proof file to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0036] In a third aspect, the present application further provides a computer device. The computer device includes a memory and a processor, wherein the memory stores a computer program, and when the processor executes the computer program, the following steps are performed:

[0037] In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block;

[0038] If the verification passes, a second block is generated based on the file information of the asset certification file;

[0039] The second block is uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, the asset proof file is sent to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0040] In a fourth aspect, the present application further provides a computer-readable storage medium having a computer program stored thereon, which, when executed by a processor, implements the following steps:

[0041] In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block;

[0042] If the verification passes, a second block is generated based on the file information of the asset certification file;

[0043] The second block is uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, the asset proof file is sent to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0044] In a fifth aspect, the present application further provides a computer program product. The computer program product includes a computer program that, when executed by a processor, implements the following steps:

[0045] In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block;

[0046] If the verification passes, a second block is generated based on the file information of the asset certification file;

[0047] The second block is uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, the asset proof file is sent to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0048] The above-mentioned asset certification document transmission method, apparatus, computer equipment, storage medium and computer program product, in response to a proof transmission message of an asset certification document of an account carried by a first node, the current node can determine the first block generated for the asset certification document of the account from the blockchain, and verify the asset certification document based on the file information of the asset certification document stored in the first block; if the verification passes, a second block can be generated based on the file information of the asset certification document, the second block can be chained in the blockchain, and when the proof transmission message indicates that the target transmission node of the asset certification document is a second node communicating with the current node, the asset certification document is sent to the second node, so that the second node verifies the asset certification document obtained by the second node based on the file information of the asset certification document stored in the second block. In the present application, on the one hand, the decentralized and tamper-proof characteristics of the blockchain can be utilized. After the current node obtains the asset file transmitted by other nodes, the asset proof file can be verified using the information stored in the corresponding block in the blockchain to ensure the credibility of the file, and a new block can be generated to generate an tamper-proof file transfer record, which is convenient for subsequent nodes that obtain the asset proof file to perform file verification. On the other hand, when the first node and the second node do not communicate, the current node can forward the asset proof file to avoid establishing a new transmission channel again; thus, the solution of the present application takes into account both data security and transmission efficiency during the transmission of the asset proof file. BRIEF DESCRIPTION OF THE DRAWINGS

[0049] Figure 1 A diagram illustrating an application environment of a method for transmitting an asset certification document in one embodiment;

[0050] Figure 2 A flowchart of a method for transmitting an asset certification document in one embodiment is shown;

[0051] Figure 3 is a schematic diagram of a storage structure of a block in one embodiment;

[0052] Figure 4 A schematic diagram of the structure of a blockchain in one embodiment;

[0053] Figure 5 is a flowchart of a step of determining a first block in one embodiment;

[0054] Figure 6 A schematic diagram of an asset certification file transmission architecture according to one embodiment;

[0055] Figure 7 1. A flowchart of another method for transmitting an asset certification document in one embodiment;

[0056] Figure 8ais a maximum flow graph in one embodiment;

[0057] Figure 8b is another maximum flow graph in one embodiment;

[0058] Figure 8c is another maximum flow graph in one embodiment;

[0059] Figure 9 A schematic diagram of data cross-backup at each node in one embodiment;

[0060] Figure 10 This is a structural block diagram of a device for transmitting asset certification documents in one embodiment;

[0061] Figure 11 FIG. 1 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0062] In order to make the purpose, technical solutions and advantages of this application more clear, the following further describes this application in detail with reference to the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain this application and are not intended to limit this application.

[0063] It should be noted that the asset certification document transmission method, device, computer equipment, storage medium and computer program product provided in this application can be applied to the field of information security technology and other related fields.

[0064] The asset certification document transmission method provided in the embodiment of the present application can be applied to Figure 1 In the application environment shown, multiple nodes may be included in the application environment, each node may communicate with one or more other nodes in the multiple nodes through a network, and each node may correspond to one or more institutions (such as business outlets).

[0065] Nodes can be terminals or servers. Terminals can be, but are not limited to, various personal computers and laptops. Servers can be implemented as independent servers or server clusters consisting of multiple servers. Furthermore, nodes can also have corresponding data storage modules for storing data that the nodes need to process, such as asset certification documents obtained by the nodes. The data storage module can be integrated into the node or deployed in the cloud or other network servers.

[0066] In one embodiment, Figure 2 As shown, a method for transmitting asset certification documents is provided, which is applied to Figure 1 Take any node in as an example to illustrate, including the following steps:

[0067] S210, in response to the proof transmission message of the first node carrying the asset proof document of the account, determining the first block generated for the asset proof document of the account from the blockchain, and verifying the asset proof document based on the file information of the asset proof document stored in the first block.

[0068] As an example, the asset certification document may include the following document information: the account's certificate type, certificate number, account's Chinese name, account's English name, and the asset information corresponding to the account.

[0069] In a specific implementation, the current node can communicate with other nodes through the network. For the sake of distinction, in this embodiment, the other node that carries the asset certification document and transmits it to the current node is referred to as the first node.

[0070] In an optional embodiment, the first node or another node (such as the current node) can generate an asset certification document for the account. Specifically, after the user logs in to the system through the account, the user can send an asset certification generation request to the corresponding node (such as the first node or another node). In response to the asset certification generation request, the node can obtain the asset information of the account, such as reading the asset information of the account from the data storage module. Then, the asset certification document can be generated based on the asset information of the account, and the asset certification document can be transmitted to the corresponding target transmission node according to the certification document transmission request of the account.

[0071] In this embodiment, the first node can send a proof transmission message carrying the account's asset proof document to the current node, and transmit the asset proof document via the proof transmission message. The asset proof document obtained by the first node can be received from another node, or generated by the first node in response to an asset proof generation request from the account. After generating the asset proof document, the first node can provide the account with download or confirmation of the generated asset proof document. After verification, the account can authorize the node that generated the asset proof document to send the asset proof document to other nodes.

[0072] Furthermore, after the node obtains the account's asset certification document, if the node determines that the asset certification document it obtained has passed verification, it can generate a corresponding block after verification and upload it to the blockchain. If the asset certification document was generated by the node, it can directly confirm that the newly generated asset certification document has passed verification and directly create a corresponding block in the blockchain. In this embodiment, to facilitate distinction from other blocks later described, the block currently queried by the node can be referred to as the first block.

[0073] Then, after the current node obtains the certificate file transmission message sent by the first node, it can read the asset certificate file provided by the first node from the certificate file, and determine the first block generated in advance for the asset certificate file of the account from the blockchain (also known as the transmission chain), and verify the asset certificate file currently transmitted by the first node based on the file information of the asset certificate stored in the first block. Specifically, after the first block determines that the asset certificate file has passed the verification, the first node can store the file information of the asset certificate file verified by the first node in the first block. Based on the immutability of the blockchain, the current node can verify the currently received asset certificate file based on the information verified by the first node in the first block, and determine whether the asset certificate file provided by the first node matches the asset certificate file verified by the first node.

[0074] S220: If the verification passes, a second block is generated based on the file information of the asset certification file.

[0075] If the verification is confirmed to be successful, it can be determined that the asset proof document transmitted by the first node to the current node matches the asset proof document verified by the first node and the relevant information uploaded to the chain, and thus it can be determined that the currently obtained asset proof document is credible. The current node can generate a corresponding block based on the file information of the received asset proof document. For ease of distinction, the block generated by the current node can be called the second block.

[0076] In an optional embodiment, the storage structure of the block can be as follows Figure 3 As shown, it includes block data and transport stream data.

[0077] The block data can be used to record attribute data in the file information corresponding to the asset certification document. For example, the attribute data may include: the account name in Chinese, the account name in English, the certificate type, the certificate number, the QR code, and the node that currently owns the asset certification document. The node that currently owns the asset certification document may be the node that obtained the asset certification document. If the asset certification document is transmitted to another node, for example, the asset certification document of an account is transmitted from the first node to the current node, the node that currently owns the asset certification document is the current node, and the first node is not considered the node that currently owns the asset certification document.

[0078] Transaction flow data can record data related to the transmission of asset proof documents. Exemplarily, the transaction flow data can include at least one of the following: the node identifier of the previous node and the node identifier of the next node, wherein the previous node can be the node that provides the asset proof document to the current node, and the next node can be the node that receives the asset proof document provided by the current node; the first block has no previous node, and the last block has no next node.

[0079] S230, uploading the second block to the blockchain, and sending the asset certification file to the second node when the proof transmission message indicates that the target transmission node of the asset certification file is the second node communicating with the current node, so that the second node verifies the asset certification file obtained by the second node based on the file information of the asset certification file stored in the second block.

[0080] Specifically, after the current node generates the second block, the second block can be uploaded to the blockchain. It can be understood that the node can generate the corresponding block and upload it to the blockchain after the asset proof document is verified. The number of times the asset proof document is transmitted (including the block generated by the node that first obtains or generates the asset proof document) is the number of blocks that can be generated, so that the transmission process of the asset proof document can be traced through the blockchain, such as Figure 4 As shown in the figure, the blockchain can include multiple blocks after being put on the chain. Each block records the relevant records of the corresponding node obtaining the asset proof document. When tracing the transmission process of the asset proof document, it can be based on Figure 4 Follow the arrow direction to search forward or backward for the node where the asset proof file has been transferred.

[0081] In addition, after receiving the proof transmission message, the current node can also read the target transmission node of the asset proof file from the proof transmission message. The target transmission node can be the node indicated by the first node to finally obtain the asset proof file.

[0082] If the proof transmission message indicates that the target transmission node of the asset proof document is the current node, the current node can store the asset proof document and provide the asset proof document after receiving the relevant business request.

[0083] If the target transmission node of the asset proof document indicated by the proof transmission message is a node other than the current node and the first node, the current node can continue to transmit the asset proof document. For the sake of distinction, the other node to obtain the asset proof document indicated by the proof transmission message is called the second node.

[0084] In actual applications, if the first node can communicate with the current node, but there are other nodes that are not communicating, such as the second node, the first node can determine an intermediate node between the first node and the second node, and the intermediate node can transmit the asset proof transmission file obtained by the first node to the second node. For example, the first node can determine an intermediate node that can communicate with the second node from the multiple nodes it communicates with, such as the current node in this embodiment. Then, if the current node determines that the target transmission node indicated by the proof transmission message is the second node, the current node can send the obtained asset proof file to the second node. After receiving the asset proof file transmitted by the current node, the second node can verify the asset proof file currently obtained by the second node based on the file information of the asset proof file stored in the second block in the blockchain.

[0085] In the above-mentioned method for transmitting an asset proof document, in response to a proof transmission message from a first node carrying an asset proof document of an account, the current node may determine a first block generated for the asset proof document of the account from the blockchain, and verify the asset proof document based on the file information of the asset proof document stored in the first block; if the verification passes, a second block may be generated based on the file information of the asset proof document, the second block may be uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof document is a second node communicating with the current node, the asset proof document may be sent to the second node, so that the second node verifies the asset proof document obtained by the second node based on the file information of the asset proof document stored in the second block. In the present application, on the one hand, the decentralized and tamper-proof characteristics of the blockchain can be utilized. After the current node obtains the asset file transmitted by other nodes, the asset proof file can be verified using the information stored in the corresponding block in the blockchain to ensure the credibility of the file, and a new block can be generated to generate an tamper-proof file transfer record, which is convenient for subsequent nodes that obtain the asset proof file to perform file verification. On the other hand, when the first node and the second node do not communicate, the current node can forward the asset proof file to avoid establishing a new transmission channel again; thus, the solution of the present application takes into account both data security and transmission efficiency during the transmission of the asset proof file.

[0086] In one embodiment, the asset certification document sent by the first node to the current node also carries a 3D code generated by the first node. For example, the 3D code can be a curved 3D code. Figure 5 As shown, S210 determines the first block generated by the asset certification document for the account from the blockchain, which may include the following steps:

[0087] S510, decoding the three-dimensional code carried by the asset certificate, and obtaining reference file information corresponding to the asset certificate document based on the decoding result.

[0088] In a specific implementation, after obtaining the asset certification document provided by the first node, the current node can read the 3D code contained in the asset certification document and decode the 3D code. The 3D code can be generated by the first node based on the file information in the asset certification document it obtained. Furthermore, after the current node completes decoding the 3D code, it can obtain the file information of the asset certification document contained in the 3D code based on the decoding result, and use this file information as reference file information corresponding to the asset certification document.

[0089] S520 , comparing the reference file information with the file information in the asset proof file received by the current node, and generating a block index based on the file information in the asset proof file when the reference file information matches the file information in the asset proof file.

[0090] As an example, a block index may be index information used to find a corresponding block in a blockchain.

[0091] Then, each current node can compare the reference file information obtained after decoding the three-dimensional code with the plain text of the asset certification file transmitted by the first node, that is, the file information in the asset certification file, to determine whether the two match.

[0092] If the reference file information matches the file information in the asset proof file, it can be determined that the asset proof file sent by the first node to the current node has not been tampered with, and then a block index can be generated based on the file information in the asset proof file.

[0093] If the reference file information does not match the file information in the asset proof file, it can be determined that the asset proof file sent by the first node to the current node has been modified during transmission and the file information is unreliable, and corresponding information can be fed back to the first node.

[0094] S530: Based on the block index, obtain a first block generated by the asset certification file for the account in the blockchain.

[0095] After obtaining the block index, the current node can determine the first block generated by the first node for the asset certification file of the account from the blockchain based on the block index.

[0096] Compared with the traditional transmission mode, the asset proof document only contains the personal asset information of the account, which is easy to be tampered with during the file transmission process. In this embodiment, a three-dimensional code generated based on the file information in the asset proof document can be added to the asset proof document. The anti-tampering feature of the three-dimensional code is used to prevent the file information corresponding to the three-dimensional code from being tampered with during the transmission process. Then, the current node can verify the file information in the asset proof document based on the reference file information obtained after decoding the three-dimensional code, effectively improving the security of the asset proof document transmission process and preventing the asset proof document from being tampered with.

[0097] In one embodiment, S520 generates a block index based on the file information in the asset certification file, which may include the following steps:

[0098] The account ID of the account is read from the file information in the asset proof file, and the generation time of the QR code is obtained from the decoding result; based on the account ID and the generation time of the QR code, a block index is generated.

[0099] In related technologies, QR codes are mainly bound and associated with specific items. There is only one QR code throughout the entire life cycle of an item from its creation to its disappearance. However, the application and transmission of asset proof documents can be triggered based on relevant account behaviors. It is possible to trigger the generation of asset proof documents multiple times within a period of time or transmit asset proof documents at different nodes. If, when transmitting proof documents, multiple nodes only generate one QR code for the same asset proof document of the same account, it is easy to cause confusion when searching for asset proof documents.

[0100] Based on this, the QR code can carry the corresponding generation time, such as timestamp information. The current node can obtain the generation time of the QR code from the decoding result by decoding the QR code. In addition, the current node can also read the account ID (such as the ID number) of the account from the file information of the received asset proof document, and then generate a block index based on the account ID and the generation time of the QR code.

[0101] Specifically, a block index is generated based on the account identifier and the generation time of the QR code. For example, the ID type, ID number, user Chinese name, user English name and timestamp are concatenated together (such as in the form of "ID type#ID number#Chinese name#English name#timestamp") as a block index. When querying, whether it is a random search or a query of other transaction blocks based on a certain transaction block, it is very efficient and can quickly locate the block to be accessed from a large number of blocks, thereby improving the search efficiency.

[0102] Compared with traditional blockchain products such as Bitcoin, which use transaction addresses as indexes, each transaction is completed by querying the transaction addresses corresponding to all exchanges the payer has participated in to calculate whether the balance of the payer's account is sufficient to pay. The block index obtained by this application in the above way helps the current node to locate the corresponding block in the transmission process more quickly from a large number of blocks, thereby improving retrieval efficiency.

[0103] In this embodiment, a block index can be generated based on the generation time and account ID of the account obtained after decoding the three-dimensional code, so that the current node can quickly and accurately locate the blocks corresponding to the asset proof documents of the same account that flow through multiple nodes at different times from the blockchain, thereby improving retrieval efficiency and providing a basis for obtaining relevant verification information of the asset proof documents and improving verification speed.

[0104] In one embodiment, S230 sending the asset certification document to the second node may include the following steps:

[0105] Obtain the color parameters of the facial image of the account, and generate a three-dimensional code based on the color parameters of the facial image, the file information of the asset proof document and the current time; add the three-dimensional code to the asset proof document, and send the asset proof document carrying the three-dimensional code to the second node.

[0106] In actual applications, the current node can obtain the facial image of the account (such as the user's avatar or the facial image in the ID card) and determine the color parameters of the facial image. For example, the color parameters of the facial image may include the pixel values ​​corresponding to each pixel point in the facial image.

[0107] The current node can then generate a 3D code based on the color parameters of the facial image, the file information in the asset proof document, and the current time, combined with a preset 3D code generation algorithm. For example, a curved 3D code can be generated using elements such as the account's Chinese name, English name, ID type, ID number, user profile picture, current timestamp, and account asset information (such as asset size). The currently generated 3D code can then be added to the asset proof document, and the asset proof document carrying the 3D code generated by the current node can be sent to the second node.

[0108] In this embodiment, on the one hand, compared with traditional QR codes, color dimension parameters related to the facial image of the account can be added during the generation of the 3D code, thereby increasing the difficulty of cracking the 3D code and preventing the 3D code from being imitated; on the other hand, by generating a 3D code based on a timestamp and related file information and adding it to the asset proof file, the 3D code can carry a time attribute. When the node that subsequently obtains the asset proof file verifies the asset proof and decodes the 3D code, it can distinguish the 3D codes generated at different times and locate the corresponding blocks by obtaining the generation time in the 3D code, thereby better ensuring the uniqueness of the asset proof files received by different nodes and the uniqueness of the corresponding generated blocks during the transmission of the asset proof files.

[0109] In one embodiment, the proof transmission message sent by the first node to the current receiving node also carries a block access token provided by the first node. Before verifying the asset proof file based on the file information of the asset proof file stored in the first block, the method may further include the following steps:

[0110] A request for viewing the first block in the blockchain is sent to the blockchain platform; the request carries the block access token, and the verification request is used to instruct the blockchain platform to verify the access rights of the current node based on the block access token verification; if the verification passes, the blockchain platform returns the file information of the asset certification file stored in the first block.

[0111] In a specific implementation, the current node can read the block access token provided by the first node from the proof transmission message sent by the first node. The token can also be called a verification token.

[0112] Specifically, a block access token can be generated when a first node initiates a secured transaction against the current node. A secured transaction can be understood as a transmission protocol in which the first node provides asset proof documents to the current node and ensures the authenticity of the asset proof documents. Secured transactions are generated based on blockchain smart contracts, which include arbitration and transmission rules. Once finalized, the contract cannot be tampered with, ensuring the reliability of the secured transaction during the transmission of asset proof documents. After initiating the secured transaction, the first node can associate the generated block access token with the asset proof documents and send it to the current node.

[0113] After receiving the block access token, the current node can send a request to the blockchain platform to view the first block in the blockchain. This request carries the block access token provided by the first node. The blockchain platform can then verify whether the current node has access rights to the first block based on the block access token carried in the request.

[0114] Specifically, if the verification passes, the current node can determine, on the one hand, that the first node is the creator of the first block and that the node currently holding the asset certification document is the first node. It can also be determined that the current node has access rights to browse the data in the first block. If the verification fails, the block access token provided by the first node fails to enable the current node to successfully view the contents of the first block. It can then be determined that the creator of the first block is not the first node, and that the node currently holding the asset certification document is not the first node. The current node can then return corresponding feedback information to the first node.

[0115] If the verification passes, the current node can receive the asset proof document stored in the first block from the blockchain platform and use the returned asset proof document information to verify the asset proof document sent by the first block. In addition, the current node can also confirm the secured transaction initiated by the first node.

[0116] In an optional embodiment, considering the security and privacy of data storage, the file information of the asset proof file stored in the blockchain can be a value encrypted using a preset encryption algorithm (such as the result obtained by encryption based on the MD5 algorithm). The plaintext data is not directly obtained from the blockchain. When the current node obtains the encrypted file information of the asset proof file stored in the first block, the same encryption algorithm can be used to encrypt the plaintext file information in the asset proof file provided by the first node, and the current encryption result (such as the MD5 value) is compared with the encrypted value obtained from the first block. If the two are consistent, it can be determined that the file information in the asset proof file provided by the first node is consistent with the encrypted file information stored in the blockchain, and it is determined that the current asset proof file has passed the verification; if the two are inconsistent, it can be determined that the asset proof file received by the current node has been tampered with. In this way, it is also possible to check whether the MD5 values ​​of other blocks in the blockchain are the same, thereby preventing internal data tampering within the organization.

[0117] If the current node also performs verification in conjunction with the QR code carried by the asset proof document, the current node can perform three verifications on the asset proof document provided by the first node. The first verification is the QR code verification, which can be used to determine whether the asset proof document obtained by the current node is the same as the asset proof document transmitted to the current node by the first node, and whether the asset proof document has been tampered with by other third parties during the transmission from the first node to the current node; the second verification is the traceability verification, which can be used to verify whether the first node currently owns the asset proof document. The final verification results of the first two verifications can be shown in the following table:

[0118] Serial number 3D code verification results Traceability results Verification results 1 Fake No ownership Fake 2 real No ownership Fake 3 Fake Ownership Fake 4 real Ownership real

[0119] The third verification can be understood as verifying whether the file information of the asset proof document on the chain of the first node is consistent with the file information of the asset proof document actually provided by the first node to the current node.

[0120] In this embodiment, by providing a block access token to the current node, and then providing the current node with relevant information stored in the first block when the block access token is verified, only nodes with relevant access rights can view and confirm the block content, which can effectively prevent account information leakage and improve data security during the transmission of asset proof documents.

[0121] In one embodiment, the second block added to the blockchain is a block signed by a node key corresponding to the current node, and the node key is generated based on a key seed of the current node. The method may further include the following steps:

[0122] S610: When the key seed is lost, search for a first backup node that stores a backup key seed of the current node from multiple nodes.

[0123] The backup key seed may be the same key seed as the key seed used by the current node.

[0124] In a specific implementation, when it is determined that the key seed is lost, the current node can search for a backup node that stores the backup key seed of the current node from multiple nodes. For the sake of distinction, this backup node can also be called the first backup node.

[0125] Specifically, key seeds can be backed up crosswise between multiple nodes, and each node stores no more than a preset number of backup key seeds corresponding to other nodes. For example, the maximum number of backup key seeds that can be stored by each node is 1. It will be understood that in this embodiment, the backup key seeds of multiple nodes are not stored simultaneously in the same node.

[0126] S620, sending a backup seed acquisition request carrying the node identity information corresponding to the current node to the first backup node; the backup seed acquisition request is used to trigger the first backup node to match the node identity information with the identity authentication information associated with the pre-stored backup key seed.

[0127] After determining the first backup node, the current node may send a backup seed acquisition request carrying the node identity information corresponding to the current node to the first backup node, wherein the node identity information used in the process of obtaining the backup key seed may also be referred to as the first node identity information.

[0128] After receiving the backup seed acquisition request, the first backup node can read the node identity information corresponding to the first backup node from the backup seed acquisition request, and obtain the identity authentication information associated with the pre-stored backup key seed. For the sake of distinction, the identity authentication information can also be referred to as the first identity authentication information; and then the node identity information carried in the request can be matched with the identity authentication information, for example, to determine whether the node identity information carried in the backup seed acquisition request is consistent with the identity authentication information.

[0129] S630: When the node identity information matches the identity authentication information, receive the backup key seed returned by the first backup node.

[0130] If the first backup node determines that the node identity information matches the pre-stored identity authentication information, it can return the backup key seed to the current node, so that the current node obtains its corresponding backup key seed; if the first backup node determines that the node identity information does not match the pre-stored identity authentication information, the first backup node can refuse to respond to the current node's backup seed acquisition request and does not return the backup key seed to the current node.

[0131] In this embodiment, the backup key seeds of multiple nodes can be backed up in advance on different nodes. When the key seed of the current node is lost, the first backup node storing the backup key seed can be searched from the multiple nodes and the backup key seed can be obtained from the first backup node. On the one hand, the backup key seed can be obtained in time when the key seed is lost, ensuring the normal uplink of the asset certification file transmission data. On the other hand, by backing up the backup key seeds on different nodes, problems such as key seed loss or leakage caused by centralized backup of key seeds in traditional technologies can be avoided, thereby improving the security of key seed backup.

[0132] In one embodiment, S610 searches for a first backup node storing a backup key seed of the current node from multiple nodes, and may include the following steps:

[0133] S710: Broadcast a backup node query request for the current node to multiple nodes.

[0134] Specifically, when the current node determines that the key seed is in a lost state, it can send a backup node query request to multiple nodes in the network in a broadcast manner.

[0135] S720, after receiving a response message from the second backup node to the backup node query request, send a backup relationship acquisition request carrying the node identity information corresponding to the current node to the second backup node; the backup relationship acquisition request is used to trigger the second backup node to match the node identity information with the identity authentication information associated with the pre-stored backup mapping relationship.

[0136] As an example, the backup mapping relationship may be used to determine a node storing a backup key seed.

[0137] After the current node broadcasts the backup node query request, if the node that receives the request determines that it stores the backup mapping relationship corresponding to the current node, the node can feedback the corresponding response message to the current node. In order to distinguish it from other nodes, the node that responds to the backup node query request and stores the backup mapping relationship of the current node can be called the second backup node.

[0138] Furthermore, the current node can determine that its backup mapping relationship is stored in the second backup node based on the response message, and send a backup relationship acquisition request carrying the node identity information corresponding to the current node to the second backup node, wherein the node identity information carried in the backup relationship acquisition request can also be referred to as the second node identity information, and the second node identity information can be different from the first node identity information. For example, the second node identity information can be the verification information used when obtaining the backup mapping relationship, and the first node identity information can be the verification information used when obtaining the backup key seed.

[0139] After receiving the backup relationship acquisition request, the second backup node can obtain the identity authentication information associated with the pre-stored backup mapping relationship, which can also be called second identity authentication information, and then match the node identity information carried in the backup relationship acquisition request with the identity authentication information.

[0140] S730: When the node identity information matches the identity authentication information, receive the backup mapping relationship returned by the second backup node.

[0141] If the second backup node determines that the node identity information matches the pre-stored identity authentication information, it can return the backup mapping relationship to the current node, so that the current node obtains its corresponding backup mapping relationship; if the second backup node determines that the node identity information does not match the pre-stored identity authentication information, the second backup node can refuse to respond to the current node's backup relationship acquisition request and not return the backup mapping relationship to the current node.

[0142] S740: Determine a first backup node that stores the backup key seed of the current node based on the backup mapping relationship.

[0143] The first backup node and the second backup node are different nodes.

[0144] After obtaining the backup mapping relationship, the current node can read the first backup node storing the backup key seed of the current node from the backup mapping relationship.

[0145] In this embodiment, the backup mapping relationship and the backup key seed can be stored in different nodes respectively. The current node obtains the backup mapping relationship and the backup key seed respectively through two authentications, which can improve the storage security of the backup key seed and avoid leakage.

[0146] In order to enable those skilled in the art to better understand the above steps, the embodiments of the present application are illustrated below through some examples, but it should be understood that the embodiments of the present application are not limited thereto.

[0147] In practical applications, an asset certification document transmission system consisting of a terminal, a node, and a blockchain platform can be provided. Users can use the terminal to log in to their corresponding account and apply for asset certification documents from the node. The terminal can be equipped with a personal user operation module that can be used by individual users to apply for asset certification documents, download asset certification documents, and authorize the node to send asset certification documents. The personal user operation module can be implemented through a mobile HTML5 (i.e., H5) page for user login authentication and the viewing, downloading, and uploading of asset data. It provides the function of interacting with the user asset data security transmission system. Compared with the offline processing of cross-border user data interaction in related technologies, it can provide users with an online operation channel, solving the problems of time-consuming and labor-intensive offline processing.

[0148] The node can be deployed with a node processing module and a key seed backup module. The node processing module can be used to generate asset proof documents for individual users, generate QR codes, upload relevant information of the asset proof documents to the chain, generate block access tokens, and transmit the asset proof documents to the next node; the key seed backup module can be used to back up the key seed of the node.

[0149] The blockchain platform can deploy a blockchain processing module and a key seed backup module. The blockchain processing module can be used to store asset certification documents and generate secured transactions; the key seed backup module sends the backup key seeds to different nodes for cross-backup.

[0150] Regarding the transmission process of asset certification documents, such as Figure 6 As shown, it can be divided into two stages, including the business preparation stage and the business processing stage. In the business preparation stage, individual users can register an account through the H5 page of the individual user operation module. After registration, the account information will be retained in the node processing module for authentication.

[0151] Furthermore, node registration can be performed. Each node can register as a blockchain user through the interface provided by the blockchain processing module. The blockchain processing module generates a private key file for the node, produces a key seed, and backs up the key seed to other nodes through the key seed backup module. After receiving the key seed and private key corresponding to the node, the key seed backup module can randomly generate a backup mapping table. This backup mapping table can record the backup mapping relationships corresponding to different nodes. The key seed backup module can then encrypt the backup key seed with the private key according to the backup mapping table and store it on the backup node. It can also encrypt the backup mapping relationships of other institutions that currently need to be stored and store them on the backup node.

[0152] During the business processing phase, individual users initiate an application and log in through the H5 page of the individual user operation module. The organization processing module receives the login request and authenticates the logged-in user. Figure 7 As shown, users can initiate an asset proof file query on the node on the H5 page through the logged-in account. The node processing module receives the user's application to generate an asset proof, uploads the asset proof file to the transmission chain (i.e., blockchain), and the blockchain processing module creates a new block of asset proof and returns the asset proof file data for the account to download.

[0153] Among them, a corresponding curved three-dimensional code will be attached to the asset proof document as the unique identifier of the file; customers can trigger the download of the asset proof document to the terminal for viewing on the H5 page. After confirmation, the asset proof document can be uploaded to the institution processing module through the file upload interface in the H5 page.

[0154] When processing an asset proof document transfer transaction, a node can generate a guarantee transaction for the asset proof document transfer after receiving an application from an account to send an asset proof document through the node processing module, and transfer the asset proof document to other nodes.

[0155] When transmitting asset proof documents between nodes, if the target transmission node is Node B, which has a transmission channel with Node A, Node B will verify the file information in the asset proof document using the QR code on the document after receiving it. Node B can also obtain the block index based on the QR code decoding result and the account information corresponding to the account, and verify the authenticity of the block index on the chain. If the authenticity is passed, the asset proof document transmission is completed by confirming the guarantee transaction on the transmission chain, and a new block is generated.

[0156] If the target transmission node to be transmitted is Node C, and there is no transmission channel between Node A and Node B, but there is a transmission channel between Node C, Node A will first transmit the asset proof document to Node B. After Node B receives the asset proof document and confirms the guarantee transaction and generates a new block, it will re-initiate the guarantee transaction with Node C and transmit the asset proof document to Node C. After receiving the file, Node C can use the QR code to verify and trace the source. After confirming that it is correct, it confirms the guarantee transaction generated by Node B and completes the asset proof document transmission.

[0157] For key seed backup, the blockchain platform can pre-generate a backup relationship table, which includes the backup mapping relationships corresponding to multiple nodes. Specifically, the backup relationship table can generate backup relationships through network flow graphs and maximum flow algorithms, such as Figure 8a As shown, it is the network flow diagram of each node backing up the key seed. Figure 8a The network flow diagram shown shows multiple possible backup nodes for each node. The left side represents the source node, also known as the source node, which represents the node that needs to store the key seed; the right side represents the sink node, also known as the backup node, which represents the node that stores the backup key seeds of other nodes.

[0158] When backing up the key seed, each backup node only stores the backup key seed of one other node. Figure 8a The numbers on the connectors represent the flow capacity, or the number of backup key seeds stored by the node. To achieve a complete mapping, each backup node stores a copy of the backup key seeds of every other node. This means that if the source node flow is 1, the incoming node flow should also be 1. At this point, the network flow graph reaches maximum flow.

[0159] Figure 8a The amplitude network flow graph is a complete maximum flow graph synthesized by all mapping relationships, but when different mapping rules are used, the maximum flow graph is also different. Figure 8b and Figure 8c The maximum flow graphs corresponding to different mapping rules are shown respectively. After all mapping relationships are obtained to form a backup mapping relationship table, when selecting the backup node corresponding to the key seed of each node, one of the backup mapping relationships will be randomly selected from the backup relationship table to determine the backup node corresponding to the node.

[0160] According to the backup mapping table, each node can store not only the secret key seed of the node, but also the secret key seeds of other nodes (i.e. backup key seeds), the backup mapping relationship owener:des and the identity authentication information C i owner(owner is the node that provides identity authentication information) The backup key seed and backup mapping relationship stored in the same node belong to two different nodes respectively; the identity authentication information may include the identity authentication information C used to obtain the backup mapping relationship. 1 owner And the identity authentication information C used to obtain the backup key seed 2 owner .

[0161] The following combination Figure 8b The maximum flow graph and Figure 9 Explain and explain the parameters first: KR owner KU is the private key registered by the corresponding node owner on the blockchain platform. owner For KR owner The public key generated by the elliptic algorithm; S owner is the key seed of the corresponding node owner; E KU owner’ S owner’ The encrypted backup key seed for other nodes owner'; owner':E KUowner’ (owner”) indicates that the backup identifier is owner', and stores the encrypted backup mapping relationship of other nodes owner', which points to the node owner"; E SHA256 (C 1 owner ) indicates obtaining the identity authentication information of the backup mapping relationship, E SHA256 (C 2 owner ) indicates obtaining the identity authentication information of the backup key seed, and the corresponding identity authentication information C can be respectively obtained by using the SHA256 algorithm. i owner Obtained after processing.

[0162] against Figure 8b and Figure 9 The data stored in the A node may include:

[0163] KR A KU A S A E KUC (S C )

[0164]

[0165] KR A KU is the private key generated when node A registers and logs in to the blockchain platform. A It's KR A The public key generated by the elliptic algorithm; SA is the key seed of node A; E KUC S C The encrypted backup key seed for node C; D:E KUD (C) indicates that the backup ID of node A is D, and stores the encrypted backup mapping relationship used by node D to determine the storage location of the backup key seed; E SHA256 (C 1 D ) indicates obtaining the identity authentication information of the backup mapping relationship of the D node; E SHA256 (C 2 C ) indicates obtaining the identity authentication information of the backup key seed of node C.

[0166] When the key seed of node A is lost, the key seed backup module can restore KR through the user password of node A. A and KU A , and communicates with the backup ID D node A by broadcasting messages and sends identity authentication information C 1 A After the identity authentication is passed, node A can obtain the encrypted backup mapping relationship from node D.

[0167] After obtaining the encrypted backup mapping relationship E KUA (B), through KR A After decryption, the backup key seed of A is backed up in node B, and then node A can communicate with node B and send identity authentication information C 2 A Node B passes E SHA256 (C 2 A ) After verification, return to E KUA S A Node A obtains the encrypted backup key seed through KR A Decrypt to get the secret key seed.

[0168] It should be understood that, although the various steps in the flowcharts involved in the various embodiments described above are displayed in sequence according to the instructions of the arrows, these steps are not necessarily executed in sequence in the order indicated by the arrows. Unless otherwise specified herein, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a portion of the steps in the flowcharts involved in the various embodiments described above can include multiple steps or multiple stages, and these steps or stages are not necessarily executed and completed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a portion of steps or stages in other steps.

[0169] Based on the same inventive concept, embodiments of the present application also provide an asset certification document transmission device for implementing the aforementioned asset certification document transmission method. The solution provided by this device is similar to the solution described in the aforementioned method. Therefore, the specific limitations of the embodiments of the asset certification document transmission device provided below can be found in the above-mentioned limitations of the asset certification document transmission method and will not be further elaborated here.

[0170] In one embodiment, Figure 10 As shown, a device for transmitting asset certification documents is provided, comprising:

[0171] Verification module 1001 is configured to respond to a proof transmission message from a first node carrying an asset certification document of an account, determine a first block generated for the asset certification document of the account from the blockchain, and verify the asset certification document based on the file information of the asset certification document stored in the first block;

[0172] A block generation module 1002 is configured to generate a second block based on the file information of the asset certification file if the verification passes;

[0173] The file transfer module 1003 is configured to upload the second block to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is the second node communicating with the current node, send the asset proof file to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0174] In one embodiment, the asset certification document carries a three-dimensional code generated by the first node, and the verification module 1001 includes:

[0175] A decoding submodule, configured to decode the three-dimensional code carried by the asset certificate and obtain reference file information corresponding to the asset certificate document based on the decoding result;

[0176] an index acquisition module, configured to compare the reference file information with the file information in the asset proof file received by the current node, and generate a block index based on the file information in the asset proof file when the reference file information matches the file information in the asset proof file;

[0177] A block query module is used to obtain a first block generated by the asset certification file for the account in the blockchain based on the block index.

[0178] In one embodiment, the index acquisition module is used to:

[0179] Reading the account ID of the account from the file information in the asset certification document, and obtaining the generation time of the three-dimensional code from the decoding result;

[0180] A block index is generated based on the account identifier and the generation time of the three-dimensional code.

[0181] In one embodiment, the file transfer module 1003 is configured to:

[0182] Obtaining color parameters of the facial image of the account, and generating a three-dimensional code based on the color parameters of the facial image, file information of the asset certification document, and the current time;

[0183] The three-dimensional code is added to the asset certification document, and the asset certification document carrying the three-dimensional code is sent to the second node.

[0184] In one embodiment, the proof transmission message also carries a block access token provided by the first node, and the verification module 1001 is further configured to:

[0185] Sending a request for viewing a first block in the blockchain to the blockchain platform; the request carries the block access token, and the verification request is used to instruct the blockchain platform to verify the access rights of the current node based on the block access token;

[0186] If the verification is passed, the blockchain platform returns the file information of the asset certification file stored in the first block.

[0187] In one embodiment, the second block on the blockchain is a block signed by a node key corresponding to the current node, the node key is generated based on a key seed of the current node, and the apparatus further includes:

[0188] A first backup node search module is configured to search for a first backup node storing a backup key seed of a current node from a plurality of nodes when the key seed is lost;

[0189] a backup seed acquisition module, configured to send a backup seed acquisition request carrying node identity information corresponding to the current node to the first backup node; the backup seed acquisition request is configured to trigger the first backup node to match the node identity information with identity authentication information associated with the pre-stored backup key seed;

[0190] The backup seed receiving module is configured to receive the backup key seed returned by the first backup node when the node identity information matches the identity authentication information.

[0191] In one embodiment, the first backup node search module is configured to:

[0192] Broadcast backup node query requests for the current node to multiple nodes;

[0193] Upon receiving a response message from the second backup node to the backup node query request, sending a backup relationship acquisition request carrying the node identity information corresponding to the current node to the second backup node; the backup relationship acquisition request is used to trigger the second backup node to match the node identity information with the identity authentication information associated with the pre-stored backup mapping relationship;

[0194] When the node identity information matches the identity authentication information, receiving the backup mapping relationship returned by the second backup node;

[0195] Based on the backup mapping relationship, a first backup node storing the backup key seed of the current node is determined.

[0196] Each module in the aforementioned asset certification document transmission device may be implemented in whole or in part through software, hardware, or a combination thereof. Each module may be embedded in or independent of a processor within a computer device in hardware form, or may be stored in a computer device memory in software form, so that the processor can call and execute the corresponding operations of each module.

[0197] In one embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as follows: Figure 11 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, abbreviated as I / O) and a communication interface. The processor, memory and input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and computer program in the non-volatile storage medium. The database of the computer device is used to store asset certification documents. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for transmitting an asset certification document is implemented.

[0198] Those skilled in the art will understand that Figure 11The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than shown in the figure, or combine certain components, or have a different component arrangement.

[0199] In one embodiment, a computer device is provided, including a memory and a processor, wherein a computer program is stored in the memory, and when the processor executes the computer program, the following steps are implemented:

[0200] In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block;

[0201] If the verification passes, a second block is generated based on the file information of the asset certification file;

[0202] The second block is uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, the asset proof file is sent to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0203] In one embodiment, when the processor executes the computer program, the steps in the other embodiments described above are also implemented.

[0204] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the following steps are implemented:

[0205] In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block;

[0206] If the verification passes, a second block is generated based on the file information of the asset certification file;

[0207] The second block is uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, the asset proof file is sent to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0208] In one embodiment, when the computer program is executed by a processor, the steps in the other embodiments described above are also implemented.

[0209] In one embodiment, a computer program product is provided, comprising a computer program, which, when executed by a processor, implements the following steps:

[0210] In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block;

[0211] If the verification passes, a second block is generated based on the file information of the asset certification file;

[0212] The second block is uploaded to the blockchain, and when the proof transmission message indicates that the target transmission node of the asset proof file is a second node communicating with the current node, the asset proof file is sent to the second node, so that the second node verifies the asset proof file obtained by the second node based on the file information of the asset proof file stored in the second block.

[0213] In one embodiment, when the computer program is executed by a processor, the steps in the other embodiments described above are also implemented.

[0214] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with the relevant laws, regulations and standards of relevant countries and regions.

[0215] Those skilled in the art will appreciate that all or part of the processes in the above-mentioned embodiment methods can be implemented by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to memory, database or other media used in the embodiments provided in this application may include at least one of non-volatile and volatile memory. Non-volatile memory may include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory may include random access memory (RAM) or external cache memory, etc. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in the various embodiments provided herein may include at least one of a relational database and a non-relational database. Non-relational databases may include, but are not limited to, distributed databases based on blockchains. The processor involved in the various embodiments provided herein may be, but are not limited to, a general-purpose processor, a central processing unit, a graphics processing unit, a digital signal processor, a programmable logic unit, a data processing logic unit based on quantum computing, and the like.

[0216] The technical features of the above embodiments can be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.

[0217] The above-described embodiments merely represent several implementation methods of the present application. While the descriptions are relatively specific and detailed, they should not be construed as limiting the scope of the present application. It should be noted that a person of ordinary skill in the art may make various modifications and improvements without departing from the spirit of the present application, and these modifications and improvements fall within the scope of protection of the present application. Therefore, the scope of protection of the present application shall be determined by the appended claims.

Claims

1. A method for transmitting an asset certification document, characterized in that: The method comprises: In response to a proof transmission message from the first node carrying the asset certification document of the account, determining a first block generated for the asset certification document of the account from the blockchain, and verifying the asset certification document based on file information of the asset certification document stored in the first block; If the verification passes, a second block is generated based on the file information of the asset certification file; The second block is uploaded to the blockchain, and when the certification transmission message indicates that the target transmission node of the asset certification document is a second node communicating with the current node, the asset certification document is sent to the second node, so that the second node verifies the asset certification document obtained by the second node based on the file information of the asset certification document stored in the second block, and the first node and the second node are not in communication with each other; The asset certification document carries a three-dimensional code generated by the first node, and determining the first block generated for the asset certification document of the account from the blockchain includes: Decoding the three-dimensional code carried by the asset certificate, and obtaining reference file information corresponding to the asset certificate document based on the decoding result; comparing the reference file information with the file information in the asset proof file received by the current node, and generating a block index based on the file information in the asset proof file when the reference file information matches the file information in the asset proof file; Based on the block index, obtain a first block generated for the asset certification file of the account in the blockchain.

2. The method according to claim 1, characterized in that The generating of a block index based on the file information in the asset certification file includes: Reading the account ID of the account from the file information in the asset certification document, and obtaining the generation time of the three-dimensional code from the decoding result; A block index is generated based on the account identifier and the generation time of the three-dimensional code.

3. The method according to claim 1, characterized in that The sending the asset certification document to the second node includes: Obtaining color parameters of the facial image of the account, and generating a three-dimensional code based on the color parameters of the facial image, file information of the asset certification document, and the current time; The three-dimensional code is added to the asset certification document, and the asset certification document carrying the three-dimensional code is sent to the second node.

4. The method according to claim 1, wherein The proof transmission message also carries a block access token provided by the first node. Before verifying the asset proof file based on the file information of the asset proof file stored in the first block, the process further includes: Sending a request for viewing a first block in the blockchain to the blockchain platform; the request carries the block access token, and the request is used to instruct the blockchain platform to verify the access rights of the current node based on the block access token; If the verification is passed, the blockchain platform returns the file information of the asset certification file stored in the first block.

5. The method according to claim 1, characterized in that The second block on the blockchain is a block signed by a node key corresponding to the current node, where the node key is generated based on a key seed of the current node. The method further includes: When the key seed is lost, searching for a first backup node storing a backup key seed of the current node from multiple nodes; Sending a backup seed acquisition request carrying the node identity information corresponding to the current node to the first backup node; the backup seed acquisition request is used to trigger the first backup node to match the node identity information with the identity authentication information associated with the pre-stored backup key seed; In a case where the node identity information matches the identity authentication information, the backup key seed returned by the first backup node is received.

6. The method according to claim 5, characterized in that The step of searching for a first backup node storing a backup key seed of the current node from a plurality of nodes includes: Broadcast backup node query requests for the current node to multiple nodes; Upon receiving a response message from the second backup node to the backup node query request, sending a backup relationship acquisition request carrying the node identity information corresponding to the current node to the second backup node; the backup relationship acquisition request is used to trigger the second backup node to match the node identity information with the identity authentication information associated with the pre-stored backup mapping relationship; When the node identity information matches the identity authentication information, receiving the backup mapping relationship returned by the second backup node; Based on the backup mapping relationship, a first backup node storing the backup key seed of the current node is determined.

7. A device for transmitting asset certification documents, characterized in that: The device comprises: a verification module, configured to respond to a proof transmission message from the first node carrying an asset certification document of an account, determine a first block generated for the asset certification document of the account from the blockchain, and verify the asset certification document based on file information of the asset certification document stored in the first block; A block generation module, configured to generate a second block based on the file information of the asset certification file if the verification passes; a file transmission module configured to upload the second block to the blockchain and, if the certification transmission message indicates that the target transmission node for the asset certification file is a second node in communication with the current node, transmit the asset certification file to the second node, so that the second node verifies the asset certification file obtained by the second node based on the file information of the asset certification file stored in the second block, without any communication connection between the first node and the second node; The asset certification document carries a three-dimensional code generated by the first node, and the verification module is specifically used to: Decoding the three-dimensional code carried by the asset certificate, and obtaining reference file information corresponding to the asset certificate document based on the decoding result; comparing the reference file information with the file information in the asset proof file received by the current node, and generating a block index based on the file information in the asset proof file when the reference file information matches the file information in the asset proof file; Based on the block index, obtain a first block generated for the asset certification file of the account in the blockchain.

8. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 6 are implemented.

9. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

10. A computer program product comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images