Blockchain-based information management method, device, equipment and medium
By using digital certificates and public keys to encrypt cross-chain transmission of target information on the blockchain, the risk of tampering due to offline confirmation in cross-blockchain information management is resolved, achieving secure management of multiple nodes and security and immutability of data transmission.
Patent Information
- Application Number
- CN202411212788.2
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-30
- Publication Date
- 2025-10-21
- Estimated Expiration
- 2044-08-30
AI Technical Summary
Existing technologies for cross-blockchain information management are at risk of being tampered with during offline confirmation, and the lack of oversight of each party signing in their respective blockchains makes it difficult to achieve secure management of multi-party confirmation and multi-party signature.
The target information is generated on the target blockchain by the target node and encrypted using the digital certificate and public key in the configuration file. The target information is transmitted across chains and is only decrypted and signed by the associated node to ensure data security and immutability.
It enables cross-blockchain multi-node target information security management, ensuring the security and immutability of data during transmission, and supports multi-party confirmation and multi-party signature.
Smart Images

Figure CN119089471B_ABST
Abstract
Description
Technical Field
[0001] The embodiments of the present application relate to the field of information management technology, and in particular to a blockchain-based information management method, apparatus, device, and medium. Background Art
[0002] Blockchain technology is a distributed, shared database characterized by unforgeability, traceability, transparency, and collective maintenance. Smart contracts are a core blockchain technology, serving as a bridge between application terminals and the blockchain system.
[0003] In order to achieve cross-chain information management (multi-party confirmation and multi-party signature) between relative nodes of multiple different blockchains, the currently commonly used method is offline confirmation, and then each party signs and uploads it in its own blockchain. However, this method has the risk of tampering during offline confirmation, and signing in each blockchain is not conducive to management, and the signature is not supervised. Summary of the Invention
[0004] The following is a summary of the subject matter described in detail herein. This summary is not intended to limit the scope of the claims.
[0005] This application aims to at least solve the technical problems existing in the prior art. To this end, this application proposes a blockchain-based information management method, device, equipment and medium that can achieve secure management of target information across multiple nodes of the blockchain.
[0006] A first aspect of an embodiment of the present application provides a blockchain-based information management method for setting a target smart contract on a target blockchain, the method comprising:
[0007] Obtaining a configuration file and target information generated by a target node corresponding to the target blockchain, wherein the configuration file includes digital certificates corresponding to multiple associated nodes associated with the target information, the digital certificate of the target node, a first digital signature obtained by digitally signing the target information, and a public key corresponding to the target blockchain;
[0008] Obtaining a second digital signature generated by the private key of the target blockchain from the associated smart contract on the associated blockchain corresponding to each of the associated nodes;
[0009] Decrypting the second digital signature according to the public key corresponding to the target blockchain and then verifying it. If the verification passes, generating multiple copies of the target information corresponding to the target information, and encrypting each copy of the target information using the public key in the digital certificate corresponding to each of the associated nodes to obtain an encrypted file;
[0010] Sending each encrypted file to the corresponding associated smart contract, so that the encrypted file is sent to the corresponding associated node through the associated smart contract, and the associated node decrypts the encrypted file according to the corresponding private key and verifies it. After the verification is passed, the target information copy is digitally signed with the corresponding private key to obtain a third digital signature, and the target information copy carrying the third digital signature is sent to the associated smart contract, and the associated smart contract stores the target information copy carrying the third digital signature in a block of the associated blockchain;
[0011] The target information carrying the first digital signature is stored in a block of the target blockchain.
[0012] The present application embodiment provides a blockchain-based information management method. In order to achieve the secure management (multi-party confirmation and multi-party signature) of target information across multiple nodes of the blockchain, the method uploads the target file and configuration file to the target blockchain where the target node is located, and determines the transmission authority of the target information between multiple blockchains through the configuration file, so that smart contracts of different chains can transmit target information to each other and the target information can flow across chains. Moreover, when the target information flows across chains, it is encrypted with a key, and only the associated nodes can decrypt and sign it, ensuring the security and non-tamperability of the data.
[0013] In some embodiments of the present application, the process of generating the first digital signature includes:
[0014] The target node performs hash processing on the target information to obtain a first hash value;
[0015] The target node digitally signs the first hash value according to the corresponding private key to obtain a first digital signature;
[0016] Before the associated smart contract on the associated blockchain corresponding to each of the associated nodes is digitally signed using the private key of the target blockchain, the method further includes:
[0017] Decrypting the first digital signature according to the public key in the digital certificate of the target node to obtain a second hash value;
[0018] If the second hash value is not equal to the first hash value, the target information is returned to the target node.
[0019] In some embodiments of the present application, before sending the encrypted file to the associated node through the associated smart contract, the method further includes:
[0020] Sending the first digital signature to the associated smart contract;
[0021] The associated smart contract storing the target information copy carrying the third digital signature in a block of the associated blockchain includes:
[0022] The associated smart contract generates a block of the associated blockchain by using the target information carrying the third digital signature and the copy of the target information carrying the first digital signature.
[0023] In some embodiments of the present application, after the associated smart contract stores the copy of the target information carrying the third digital signature in a block of the associated blockchain, the method further includes:
[0024] receiving a copy of the target information carrying the third digital signature sent by the associated smart contract;
[0025] Generate a block of the target blockchain using the copy of the target information carrying the third digital signature and the target information carrying the first digital signature.
[0026] In some embodiments of the present application, both the target blockchain and the associated blockchain are consortium chains.
[0027] In some embodiments of the present application, the configuration file is stored in the target blockchain.
[0028] In some embodiments of the present application, before obtaining the configuration file and the target information generated by the target node corresponding to the target blockchain, the method further includes:
[0029] The target node applies to a CA organization for the public key and private key of the target node and the plurality of associated nodes.
[0030] A second aspect of an embodiment of the present application provides a blockchain-based information management device, the device comprising:
[0031] an information receiving unit, configured to obtain a configuration file and target information generated by a target node corresponding to a target blockchain, wherein the configuration file includes digital certificates corresponding to multiple associated nodes associated with the target information, a digital certificate of the target node, a first digital signature obtained by digitally signing the target information, and a public key corresponding to the target blockchain;
[0032] a signature receiving unit, configured to obtain a second digital signature generated by the private key of the target blockchain from the associated smart contract on the associated blockchain corresponding to each of the associated nodes;
[0033] a first processing unit, configured to decrypt and verify the second digital signature according to the public key corresponding to the target blockchain; if the verification passes, generate multiple copies of the target information corresponding to the target information, and encrypt each copy of the target information using the public key in the digital certificate corresponding to each of the associated nodes to obtain an encrypted file;
[0034] a second processing unit, configured to send each encrypted file to the corresponding associated smart contract, so that the encrypted file is sent to the corresponding associated node through the associated smart contract, and the associated node decrypts the encrypted file according to the corresponding private key and verifies it. After the verification is passed, the associated node digitally signs the target information copy with the corresponding private key to obtain a third digital signature, and sends the target information copy carrying the third digital signature to the associated smart contract, so that the associated smart contract stores the target information copy carrying the third digital signature in a block of the associated blockchain;
[0035] A data uploading unit is used to store the target information carrying the first digital signature in a block of the target blockchain.
[0036] The third aspect of an embodiment of the present application provides an electronic device, comprising at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the blockchain-based information management method.
[0037] A fourth aspect of an embodiment of the present application provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the blockchain-based information management method.
[0038] It can be understood that the beneficial effects of the second to fourth aspects compared with the relevant technologies are the same as the beneficial effects of the first aspect compared with the relevant technologies. Please refer to the relevant description in the first aspect and no further details will be given here. BRIEF DESCRIPTION OF THE DRAWINGS
[0039] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the following briefly introduces the drawings required for use in the embodiments or related technical descriptions. Obviously, the drawings described below are only some embodiments of the embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative labor.
[0040] Figure 1 This is a flowchart of a blockchain-based information management method provided by an embodiment of the present application;
[0041] Figure 2 This is a structural diagram of a blockchain-based information management device provided by one embodiment of the present application;
[0042] Figure 3 This is a schematic diagram of the structure of an electronic device provided by an embodiment of the present application. DETAILED DESCRIPTION
[0043] 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.
[0044] It should be noted that although the device schematics illustrate functional module divisions and the flowcharts illustrate logical sequences, in certain circumstances, the steps shown or described may be performed in a sequence that differs from the module divisions in the device or the sequence in the flowcharts. The terms "first," "second," and so on, in the specification, claims, and drawings, are used to distinguish similar items and are not necessarily used to describe a specific sequence or precedence.
[0045] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as those commonly understood by those skilled in the art to which this application pertains. The terms used herein are for the purpose of describing the embodiments of this application only and are not intended to limit this application.
[0046] like Figure 1 One embodiment of the present application provides a blockchain-based information management method for setting a target smart contract on a target blockchain, the method comprising steps S110 to S150:
[0047] Step S110, obtain a configuration file and target information generated by a target node corresponding to the target blockchain, wherein the configuration file contains digital certificates corresponding to multiple associated nodes associated with the target information, the digital certificate of the target node, a first digital signature obtained after digitally signing the target information, and a public key corresponding to the target blockchain.
[0048] Step S120: Obtain a second digital signature generated by the private key of the target blockchain for the associated smart contract on the associated blockchain corresponding to each associated node.
[0049] Step S130: Decrypt the second digital signature and verify it according to the public key corresponding to the target blockchain. If the verification is successful, generate multiple copies of the target information corresponding to the target information, and encrypt each copy of the target information using the public key in the digital certificate corresponding to each associated node to obtain an encrypted file.
[0050] In step S140, each encrypted file is sent to the corresponding associated smart contract, so that the encrypted file is sent to the corresponding associated node through the associated smart contract, and the associated node decrypts the encrypted file according to the corresponding private key and verifies it. After the verification is passed, the target information copy is digitally signed with the corresponding private key to obtain a third digital signature, and the target information copy carrying the third digital signature is sent to the associated smart contract, and the associated smart contract stores the target information copy carrying the third digital signature in the block of the associated blockchain.
[0051] Step S150: Store the target information carrying the first digital signature in a block of the target blockchain.
[0052] In the embodiment of the present application, the target node refers to the node where the target information is generated, and the node can be a terminal that can access the block.
[0053] Target information includes, but is not limited to, key documents such as bidding documents, contracts, flyers, and invoices. Bidding documents will be used as an example later. A copy of target information is a photocopy of the target information, which is the same material.
[0054] An associated node associated with target information refers to a node that jointly confirms and signs the target information with the target node. For example, companies A, B, and C jointly implement a project, and the bidding documents require joint confirmation and signature by the three companies. Company A generates the bidding documents through terminal A, and the terminal A corresponding to company A is the target node. Company B confirms and signs through terminal B, and company C confirms and signs through terminal C. Then terminals B and C are the associated nodes corresponding to the target information.
[0055] The blockchain to which the associated node is connected is called the associated blockchain, and the blockchain to which the target node is connected is called the target blockchain. For example, there are three blockchains, blockchain 1, blockchain 2, and blockchain 3. Terminal A is connected to blockchain 1, terminal B is only connected to blockchain 2, and terminal C is only connected to blockchain 3. If blockchain 1 is the target blockchain, then 2 to 3 are all associated blockchains.
[0056] Digital certificates and digital signatures are not introduced here.
[0057] Smart contracts are specialized protocols used to create contracts on blockchains. They are self-executing contracts. A target smart contract is a smart contract on a target blockchain, while a linked smart contract is a smart contract on a linked blockchain. Cross-chain smart contract services enable data transfer between target and linked smart contracts.
[0058] The purpose of this embodiment is to enable multiple nodes in different blockchains to verify and sign the target information and generate blocks in the blockchain. The implementation process of this embodiment is as follows:
[0059] In step S110, the target node first generates target information and uploads it to the target blockchain. The target smart contract on the target blockchain then receives the target information and obtains a configuration file, which is stored in the target blockchain in advance. The configuration file includes:
[0060] 1. The digital signature of the target node (i.e., the first digital signature): the target node signs the target information using its own private key to prove to other associated nodes that the target node has confirmed and signed the target information.
[0061] 2. The target node’s digital certificate is used by the target smart contract to identify the target node and receive the public key included in the digital certificate. The public key is mainly used to verify the target node’s digital signature so that the target smart contract can determine the authenticity of the signature.
[0062] 3. The associated node's digital certificate is used by the target smart contract to identify the associated node and the public key included in the received digital certificate. The public key is mainly used to encrypt the target information copy to protect the target information copy (to prevent malicious nodes from tampering with the target information copy). Only the corresponding node holding the private key corresponding to the public key can decrypt and obtain the target information copy.
[0063] 4. The target blockchain's public key is primarily used by the target smart contract to decrypt the second digital signature sent from other associated smart contracts. The second digital signature is a signature file generated by the associated node signing the target blockchain's address. The private key used for this signature is the target blockchain's private key. This signature can be sent in advance by the smart contract after the target and associated nodes confirm the agreement. The target smart contract can decrypt the second digital signature. The presence of the target blockchain's public key in the configuration file and the receipt of the second digital signature sent by the associated blockchain prove that the target and associated nodes have reached an agreement (or pre-negotiated) using the corresponding smart contract and blockchain (because the target and associated nodes are connected to different blockchains). If no agreement is reached, the target blockchain's public key will not be present in the configuration file, the private key will not be transmitted in advance, and the target information cannot be confirmed and signed by different nodes in different blockchains.
[0064] In step S130, the second digital signature of the target blockchain's public key is first verified, that is, decrypted and then compared. If the verification is passed, multiple copies of the target information are made. For example, if there are three signatories, two copies of the file are required. The target information copies are then encrypted. Since the first smart contract is impartial, it will not tamper with the target information. However, the target information copies need to be uploaded to other nodes in other blockchains, so they need to be encrypted to prevent tampering by other nodes. Public keys can be used for encryption here, because digital certificates contain the public keys of the associated nodes. The target information copies are encrypted using the public key, and verification can only be performed if and only if the associated node holds the corresponding private key.
[0065] In step S140, the encrypted copy of the information is sent to the associated node via the associated smart contract. Note that because the configuration file contains a digital certificate that provides a unique identity, the target smart contract can send the digital certificate to the associated smart contract when the encrypted copy of the information is sent. Upon receiving the encrypted copy of the information, the associated node can first decrypt it using its own private key, verify that the target copy of the information is correct, and then digitally sign it using its own private key. After signing, the target copy of the information is uploaded to the associated smart contract, which then generates the block.
[0066] It is important to note that the target node and the associated node communicate the specific content of the target information in advance, so that after receiving the copy of the target information, the content can be verified. Signing the target information on the blockchain provides a tamper-proof environment.
[0067] In step S150, the target information carrying the first signature is uploaded to the blockchain to generate a block.
[0068] The beneficial effects of this embodiment include:
[0069] To achieve secure management (multi-party confirmation and multi-party signature) of target information across multiple nodes across blockchains, this method involves the target node uploading a target file and configuration file to its target blockchain. This configuration file determines the transmission permissions for target information between multiple blockchains, enabling smart contracts on different chains to transfer target information to each other and allowing target information to flow across chains. Furthermore, when target information flows across chains, it is encrypted using a key, and only connected nodes can decrypt and sign it, ensuring data security and immutability.
[0070] In some embodiments of the present application, the process of generating the first digital signature includes:
[0071] The target node performs hash processing on the target information to obtain a first hash value;
[0072] The target node digitally signs the first hash value according to the corresponding private key to obtain a first digital signature;
[0073] Before the associated smart contract on the associated blockchain corresponding to each associated node is digitally signed using the private key of the target blockchain, the method further includes:
[0074] Decrypt the first digital signature according to the public key in the digital certificate of the target node to obtain a second hash value;
[0075] If the second hash value is not equal to the first hash value, the target information is returned to the target node.
[0076] There is a situation where the target node forges a digital signature. If there is a problem with the digital signature uploaded by the target node, the target information will be returned to avoid uploading the wrong digital signature and ensure fairness to multiple associated nodes.
[0077] In some embodiments of the present application, before sending the encrypted file to the associated node through the associated smart contract, the method further includes:
[0078] Sending the first digital signature to the associated smart contract;
[0079] The associated smart contract stores a copy of the target information carrying the third digital signature in a block of the associated blockchain, including:
[0080] The associated smart contract generates a block of the associated blockchain using the target information carrying the third digital signature and the copy of the target information carrying the first digital signature.
[0081] In this embodiment, the target node can view the signatures of the associated nodes through the target blockchain to ensure that each associated node has confirmed the target information and obtained the corresponding signature, which is convenient for verification.
[0082] In some embodiments of the present application, after the associated smart contract stores the copy of the target information carrying the third digital signature in a block of the associated blockchain, the method further includes:
[0083] Receive a copy of the target information with a third digital signature sent by the associated smart contract;
[0084] The target information copy carrying the third digital signature and the target information carrying the first digital signature are used to generate a block of the target blockchain.
[0085] In this embodiment, each associated node can view the signatures of other associated nodes including the target node on the corresponding blockchain to ensure that each associated node has confirmed the target information and obtained the signature for easy verification.
[0086] In some embodiments of the present application, both the target blockchain and the associated blockchain are consortium chains.
[0087] In some embodiments of the present application, a configuration file is stored in a target blockchain. The configuration file includes digital certificates corresponding to multiple associated nodes associated with the target information, the digital certificate of the target node, and a first digital signature obtained by digitally signing the target information, which can be uploaded by the target node.
[0088] In some embodiments of the present application, before obtaining the configuration file and the target information generated by the target node corresponding to the target blockchain, the method further includes:
[0089] The target node applies to the CA for the public and private keys of the target node and multiple associated nodes. The CA is a trustworthy organization.
[0090] In some embodiments of the present application, the following examples are provided:
[0091] The bidding documents are implemented by company terminal A (i.e., target node), company terminal B (i.e., associated node), and company terminal C (i.e., associated node). The three companies reach an agreement in advance:
[0092] Confirm the contents of the bidding documents; send the private key of Company A's blockchain 1 to other blockchains through a smart contract.
[0093] In step (1), Company Terminal A requests the digital certificates corresponding to Company Terminal A, Company Terminal B, and Company Terminal C from the CA. The private keys are stored by each company. The digital certificates contain the public keys, and the private keys can be uploaded by each company to the corresponding blockchain.
[0094] In step (2), company terminal A generates a bidding document (i.e., target information), hashes the bidding document using a private key, obtains a first digital signature, and uploads the bidding document, the first digital signature, and the digital certificate to blockchain 1.
[0095] In step (3), company terminal B generates a second digital signature b using the address of blockchain 1 as basic information and the private key of blockchain 1 as encryption key through the smart contract in blockchain 2, and then signs the basic information to obtain the second digital signature b, and sends the second digital signature b to the smart contract in blockchain 1.
[0096] In step (4), the company terminal C generates a second digital signature c through the smart contract in blockchain 3, using the address of blockchain 1 as the basic information and the private key of blockchain 1 as the encryption key, and then signs the basic information to obtain the second digital signature c, and sends the second digital signature c to the smart contract in blockchain 1.
[0097] In step (5), the blockchain 1 smart contract uses the public key of blockchain 1 stored in advance to decrypt the second digital signature b of step (3) and the digital signature c of step (4) and verify them.
[0098] Step (6), after the verification in step (5) is successful, two copies of the tender document are generated, and then the two copies of the tender document are encrypted respectively using the public key in the digital integer.
[0099] In step (7), the encrypted copy of the bidding document carrying the digital certificate of company terminal B is sent to the smart contract of blockchain 2, and the encrypted copy of the bidding document carrying the digital certificate of company terminal C is sent to the smart contract of blockchain 3.
[0100] In step (8), the smart contract of blockchain 2 sends the encrypted copy of the bidding document to company terminal B, which decrypts the encrypted copy of the bidding document using the corresponding private key to obtain a copy of the bidding document, and digitally signs the copy of the bidding document using the private key to obtain a third digital signature b, and sends the copy of the bidding document carrying the third digital signature b to blockchain 1 and blockchain 3.
[0101] The smart contract of blockchain 2 stores two copies of the bidding document with the third digital signature and the bidding document with the first digital signature in block 2 of the blockchain.
[0102] In step (9), the smart contract of blockchain 3 sends the encrypted file to company terminal C, which decrypts the encrypted file using the corresponding private key to obtain a copy of the bidding document, digitally signs the copy of the bidding document using the private key, and sends the copy of the bidding document carrying the third digital signature c to blockchain 1 and blockchain 2.
[0103] The smart contract of blockchain 3 stores two copies of the bidding document carrying the third digital signature and the bidding document carrying the first digital signature in the block of blockchain 3.
[0104] In step (10), the smart contract of blockchain 1 stores two copies of the bidding document carrying the third digital signature and the bidding document carrying the first digital signature in block 1 of the blockchain.
[0105] To achieve secure management (multi-party confirmation and multi-party signature) of target information across multiple nodes across blockchains, this method involves the target node uploading a target file and configuration file to its target blockchain. This configuration file determines the transmission permissions for target information between multiple blockchains, enabling smart contracts on different chains to transfer target information to each other and allowing target information to flow across chains. Furthermore, when target information flows across chains, it is encrypted using a key, and only connected nodes can decrypt and sign it, ensuring data security and immutability.
[0106] like Figure 2 As shown, one embodiment of the present application provides a blockchain-based information management device, the device comprising:
[0107] The information receiving unit 1100 is used to obtain a configuration file and target information generated by a target node corresponding to a target blockchain, wherein the configuration file includes digital certificates corresponding to multiple associated nodes associated with the target information, a digital certificate of the target node, a first digital signature obtained by digitally signing the target information, and a public key corresponding to the target blockchain;
[0108] The signature receiving unit 1200 is used to obtain a second digital signature generated by the private key of the target blockchain from the associated smart contract on the associated blockchain corresponding to each associated node;
[0109] The first processing unit 1300 is configured to decrypt and verify the second digital signature using the public key corresponding to the target blockchain. If the verification is successful, multiple copies of the target information are generated, and each copy of the target information is encrypted using the public key in the digital certificate corresponding to each associated node to obtain an encrypted file.
[0110] The second processing unit 1400 is configured to send each encrypted file to a corresponding associated smart contract, so that the encrypted file is sent to the corresponding associated node through the associated smart contract. The associated node decrypts the encrypted file using the corresponding private key and verifies the encrypted file. After the verification is successful, the associated node digitally signs the target information copy using the corresponding private key to obtain a third digital signature, and sends the target information copy carrying the third digital signature to the associated smart contract. The associated smart contract stores the target information copy carrying the third digital signature in a block of the associated blockchain.
[0111] The data upload unit 1500 is used to store the target information carrying the first digital signature in a block of the target blockchain.
[0112] It should be noted that the blockchain-based information management device provided in this embodiment and the above-mentioned blockchain-based information management method are based on the same embodiment concept, so the relevant content of the above-mentioned blockchain-based information management method is also applicable to the content of the blockchain-based information management system, so it will not be repeated here.
[0113] like Figure 3 , an embodiment of the present application further provides an electronic device, the electronic device comprising:
[0114] at least one memory;
[0115] at least one processor;
[0116] at least one program;
[0117] The program is stored in the memory, and the processor executes at least one program to implement the blockchain-based information management method implemented in the present disclosure.
[0118] The electronic device may be any intelligent terminal including a mobile phone, a tablet computer, a personal digital assistant (PDA), a car computer, etc.
[0119] The electronic device according to the embodiment of the present application is described in detail below.
[0120] The processor 1600 may be implemented as a general-purpose central processing unit (CPU), a microprocessor, an application-specific integrated circuit (ASIC), or one or more integrated circuits, and is configured to execute relevant programs to implement the technical solutions provided by the embodiments of the present invention.
[0121] Memory 1700 can be implemented in the form of a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). Memory 1700 can store an operating system and other application programs. When the technical solutions provided in the embodiments of this specification are implemented through software or firmware, the program code is stored in memory 1700 and is called by processor 1600 to execute the blockchain-based information management method of the embodiments of the present invention.
[0122] Input / output interface 1800, used for information input and output;
[0123] Communication interface 1900, used to implement communication interaction between this device and other devices, which can be achieved through wired means (such as USB, network cable, etc.) or wireless means (such as mobile network, WiFi, Bluetooth, etc.);
[0124] Bus 2000 , which transmits information between various components of the device (e.g., processor 1600 , memory 1700 , input / output interface 1800 , and communication interface 1900 );
[0125] The processor 1600 , the memory 1700 , the input / output interface 1800 , and the communication interface 1900 are connected to each other in communication within the device via the bus 2000 .
[0126] An embodiment of the present invention also provides a storage medium, which is a computer-readable storage medium. The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the above-mentioned blockchain-based information management method.
[0127] The memory, as a non-transient computer-readable storage medium, can be used to store non-transient software programs and non-transient computer executable programs. In addition, the memory may include a high-speed random access memory and may also include a non-transient memory, such as at least one disk storage device, a flash memory device, or other non-transient solid-state storage device. In some embodiments, the memory may optionally include a memory remotely arranged relative to the processor, and these remote memories may be connected to the processor via a network. Examples of the above-mentioned network include, but are not limited to, the Internet, an intranet, a local area network, a mobile communication network, and combinations thereof.
[0128] The embodiments described in the present invention are intended to more clearly illustrate the technical solutions of the embodiments of the present invention and do not constitute a limitation on the technical solutions provided by the embodiments of the present invention. Those skilled in the art will appreciate that with the evolution of technology and the emergence of new application scenarios, the technical solutions provided by the embodiments of the present invention are equally applicable to similar technical problems.
[0129] Those skilled in the art will understand that the technical solutions shown in the figures do not constitute a limitation on the embodiments of the present invention, and may include more or fewer steps than shown in the figures, or a combination of certain steps, or different steps.
[0130] The device embodiments described above are merely illustrative. The units described as separate components may or may not be physically separate, i.e., they may be located in one place or distributed across multiple network units. Some or all of the modules may be selected based on actual needs to achieve the objectives of this embodiment.
[0131] Those skilled in the art will appreciate that all or some of the steps in the methods, systems, and functional modules / units in the devices disclosed above may be implemented as software, firmware, hardware, or appropriate combinations thereof.
[0132] The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or sequential order. It should be understood that the data used in this way can be interchangeable where appropriate, so that the embodiments of the present application described herein can be implemented in an order other than those illustrated or described herein. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.
[0133] It should be understood that in this application, "at least one (item)" means one or more, and "plurality" means two or more. "And / or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and / or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character " / " generally indicates that the previous and next associated objects are in an "or" relationship. "At least one of the following items" or similar expressions refers to any combination of these items, including any combination of single items or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.
[0134] In the several embodiments provided in this application, it should be understood that the disclosed devices and methods can be implemented in other ways. For example, the device embodiments described above are merely schematic. For example, the division of units is only a logical function division. In actual implementation, there may be other division methods, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some interfaces, indirect coupling or communication connection of devices or units, which can be electrical, mechanical or other forms.
[0135] Units described as separate components may or may not be physically separate, and 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 these units may be selected to achieve the purpose of this embodiment according to actual needs.
[0136] In addition, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or each unit may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.
[0137] If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application, or the part that contributes to the prior art, or all or part of the technical solution can be embodied in the form of a software product, which is stored in a storage medium and includes multiple instructions for enabling an electronic device (which can be a personal computer, server, or network device, etc.) to execute all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes various media that can store programs, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disk.
[0138] Obviously, those skilled in the art may make various changes and modifications to the present invention without departing from the spirit and scope of the present invention. Thus, if such changes and modifications fall within the scope of the claims and their equivalents, the present invention is intended to include such changes and modifications.
Claims
1. A blockchain-based information management method, characterized in that: For setting a target smart contract on a target blockchain, the method comprises: Obtaining a configuration file and target information generated by a target node corresponding to the target blockchain, wherein the configuration file includes digital certificates corresponding to multiple associated nodes associated with the target information, the digital certificate of the target node, a first digital signature obtained by digitally signing the target information, and a public key corresponding to the target blockchain; Obtaining a second digital signature generated by the private key of the target blockchain from the associated smart contract on the associated blockchain corresponding to each of the associated nodes; Decrypting the second digital signature according to the public key corresponding to the target blockchain and then verifying it. If the verification passes, generating multiple copies of the target information corresponding to the target information, and encrypting each copy of the target information using the public key in the digital certificate corresponding to each of the associated nodes to obtain an encrypted file; Sending each encrypted file to the corresponding associated smart contract, so that the encrypted file is sent to the corresponding associated node through the associated smart contract, and the associated node decrypts the encrypted file according to the corresponding private key and verifies it. After the verification is passed, the target information copy is digitally signed with the corresponding private key to obtain a third digital signature, and the target information copy carrying the third digital signature is sent to the associated smart contract, and the associated smart contract stores the target information copy carrying the third digital signature in a block of the associated blockchain; The target information carrying the first digital signature is stored in a block of the target blockchain.
2. The information management method based on blockchain according to claim 1, characterized in that: The generation process of the first digital signature includes: The target node performs hash processing on the target information to obtain a first hash value; The target node digitally signs the first hash value according to the corresponding private key to obtain a first digital signature; Before the associated smart contract on the associated blockchain corresponding to each of the associated nodes is digitally signed using the private key of the target blockchain, the method further includes: Decrypting the first digital signature according to the public key in the digital certificate of the target node to obtain a second hash value; If the second hash value is not equal to the first hash value, the target information is returned to the target node.
3. The information management method based on blockchain according to claim 1 is characterized in that: Before sending the encrypted file to the associated node through the associated smart contract, the method further includes: Sending the first digital signature to the associated smart contract; The associated smart contract storing the target information copy carrying the third digital signature in a block of the associated blockchain includes: The associated smart contract generates a block of the associated blockchain by using the target information carrying the third digital signature and the copy of the target information carrying the first digital signature.
4. The information management method based on blockchain according to claim 1, characterized in that: After the associated smart contract stores the copy of the target information carrying the third digital signature in a block of the associated blockchain, the method further includes: receiving a copy of the target information carrying the third digital signature sent by the associated smart contract; Generate a block of the target blockchain using the copy of the target information carrying the third digital signature and the target information carrying the first digital signature.
5. The information management method based on blockchain according to claim 1, characterized in that: The target blockchain and the associated blockchain are both consortium chains.
6. The information management method based on blockchain according to claim 1, characterized in that: The configuration file is stored in the target blockchain.
7. The information management method based on blockchain according to claim 1, characterized in that: Before obtaining the configuration file and the target information generated by the target node corresponding to the target blockchain, the method further includes: The target node applies to a trusted organization for the public key and the private key of the target node and the plurality of associated nodes.
8. An information management device based on blockchain, characterized in that: The device comprises: an information receiving unit, configured to obtain a configuration file and target information generated by a target node corresponding to a target blockchain, wherein the configuration file includes digital certificates corresponding to multiple associated nodes associated with the target information, a digital certificate of the target node, a first digital signature obtained by digitally signing the target information, and a public key corresponding to the target blockchain; a signature receiving unit, configured to obtain a second digital signature generated by the private key of the target blockchain from the associated smart contract on the associated blockchain corresponding to each of the associated nodes; a first processing unit, configured to decrypt and verify the second digital signature according to the public key corresponding to the target blockchain; if the verification passes, generate multiple copies of the target information corresponding to the target information, and encrypt each copy of the target information using the public key in the digital certificate corresponding to each of the associated nodes to obtain an encrypted file; a second processing unit, configured to send each encrypted file to the corresponding associated smart contract, so that the encrypted file is sent to the corresponding associated node through the associated smart contract, and the associated node decrypts the encrypted file according to the corresponding private key and verifies it. After the verification is passed, the associated node digitally signs the target information copy with the corresponding private key to obtain a third digital signature, and sends the target information copy carrying the third digital signature to the associated smart contract, so that the associated smart contract stores the target information copy carrying the third digital signature in a block of the associated blockchain; A data uploading unit is used to store the target information carrying the first digital signature in a block of the target blockchain.
9. An electronic device, characterized in that: It includes at least one control processor and a memory for communicating with the at least one control processor; the memory stores instructions that can be executed by the at least one control processor, and the instructions are executed by the at least one control processor to enable the at least one control processor to execute the blockchain-based information management method according to any one of claims 1 to 7.
10. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores computer-executable instructions, and the computer-executable instructions are used to enable a computer to execute the blockchain-based information management method according to any one of claims 1 to 7.
Citation Information
Patent Citations
Application configuration file management method and device
WO2020233373A1
Service processing system and method based on blockchain
WO2020244231A1