Data management method, device and equipment based on block chain, medium and product

Abstract

The invention provides a block chain-based data management method, apparatus and device, a medium and a product. The method comprises the steps of obtaining a resource cross-chain display request; the resource cross-chain display request carries a resource identifier and a block chain identifier; responding to the resource cross-chain display request, obtaining first target resource data corresponding to the resource identifier, and determining a first hash value of the first target resource data; and sending the first hash value and the resource identifier to a node of a second block chain corresponding to the block chain identifier, so that the node of the second block chain obtains second target resource data corresponding to the resource identifier from the first block chain, and determines a second hash value of the second target resource data, and when the first hash value is matched with the second hash value, sending the second target resource data to the node of the second block chain. And displaying the second target resource data in the client of the second block chain. Through the embodiment of the invention, cross-chain display of the resource data can be conveniently realized.

Description

Technical Field

[0001] This application relates to the field of blockchain technology, and in particular, to a data management method, a data management device, a computing device, a computer-readable storage medium, and a computer program product based on blockchain. Background Art

[0002] With the advancement of digital construction, technology companies, cultural institutions, cultural property trading agencies, etc. have successively launched their own digital cultural and creative platforms, and issued digital resources in different forms such as digital copyrights and digital collections on the digital cultural and creative platforms. However, the data of each platform is not interoperable, and the owners of digital resources can only view the digital resources of their own platforms on each platform, thus resulting in the problem of digital resource islands, which makes it difficult to achieve unified management of digital resources. Currently, through cross-chain technology, the resource data of multiple platforms is uniformly transferred to a certain platform to display the resource data of multiple platforms on this platform, but this method has low efficiency and great operation difficulty. Therefore, how to conveniently perform cross-chain display of resource data has become a research hotspot. Summary of the Invention

[0003] This application provides a data management method, device, equipment, medium, and product based on blockchain, which can conveniently achieve cross-chain display of resource data.

[0004] On the one hand, this application provides a data management method based on blockchain, which is applied to a node of the first blockchain. The method includes:

[0005] Obtain a resource cross-chain display request; the resource cross-chain display request carries a resource identifier and a blockchain identifier;

[0006] Respond to the resource cross-chain display request, obtain first target resource data corresponding to the resource identifier, and determine a first hash value of the first target resource data;

[0007] Send the first hash value and the resource identifier to a node of the second blockchain corresponding to the blockchain identifier, so that the node of the second blockchain obtains second target resource data corresponding to the resource identifier from the first blockchain, and determines a second hash value of the second target resource data. When the first hash value matches the second hash value, display the second target resource data in the client of the second blockchain.

[0008] On the other hand, this application provides another data management method based on blockchain, which is applied to a node of the second blockchain. The method includes:

[0009] Receive the first hash value and resource identifier sent by a node of the first blockchain in response to a resource cross-chain display request; the resource cross-chain display request carries the resource identifier and the blockchain identifier, the first hash value is generated by the node of the first blockchain according to the first target resource data corresponding to the resource identifier, and the blockchain identifier matches the second blockchain;

[0010] Obtain the second target resource data corresponding to the resource identifier from the first blockchain, and determine the second hash value of the second target resource data;

[0011] Match the first hash value with the second hash value;

[0012] When the first hash value matches the second hash value, display the second target resource data in the client of the second blockchain.

[0013] On the other hand, the present application provides a blockchain-based data management device, which is applied to a node of the first blockchain. The device includes:

[0014] An acquisition module, configured to acquire a resource cross-chain display request; the resource cross-chain display request carries a resource identifier and a blockchain identifier;

[0015] A processing module, configured to respond to the resource cross-chain display request, acquire the first target resource data corresponding to the resource identifier, and determine the first hash value of the first target resource data;

[0016] A sending module, configured to send the first hash value and the resource identifier to a node of the second blockchain corresponding to the blockchain identifier, so that the node of the second blockchain acquires the second target resource data corresponding to the resource identifier from the first blockchain, and determines the second hash value of the second target resource data. When the first hash value matches the second hash value, display the second target resource data in the client of the second blockchain.

[0017] On yet another aspect, the present application provides another blockchain-based data management device, which is applied to a node of the second blockchain. The device includes:

[0018] A receiving module, configured to receive the first hash value and the resource identifier sent by a node of the first blockchain in response to a resource cross-chain display request; the resource cross-chain display request carries the resource identifier and the blockchain identifier, the first hash value is generated by the node of the first blockchain according to the first target resource data corresponding to the resource identifier, and the blockchain identifier matches the second blockchain;

[0019] An execution module, configured to obtain second target resource data corresponding to the resource identifier from the first blockchain, and determine a second hash value of the second target resource data;

[0020] The execution module is configured to match the first hash value and the second hash value;

[0021] A data display module, configured to display the second target resource data in a client of the second blockchain when the first hash value and the second hash value match.

[0022] Correspondingly, the present application provides a computing device, including a processor, a memory, and a network interface, where the above-mentioned processor, memory, and network interface are interconnected. Among them, the memory is used to store a computer program, the computer program includes program instructions, and the processor is configured to call the program instructions to implement the steps of the above-mentioned blockchain-based data management method.

[0023] Correspondingly, the present application provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program, the computer program includes program instructions, and the program instructions are executed by a processor to implement the steps of the above-mentioned blockchain-based data management method.

[0024] Correspondingly, the present application provides a computer program product, where the computer program product includes a computer program or computer instructions, and the computer program or computer instructions are executed by a processor to implement the steps of the above-mentioned blockchain-based data management method.

[0025] When the present application embodiment obtains a resource cross-chain display request carrying a resource identifier and a blockchain identifier, it obtains first target resource data corresponding to the resource identifier, calculates a first hash value of the first target resource data, and sends the first hash value and the resource identifier to a node of the second blockchain corresponding to the blockchain identifier. The node of the second blockchain obtains second target resource data corresponding to the resource identifier from the first blockchain, calculates a second hash value of the second target resource data, and after the first hash value and the second hash value are compared and are consistent, displays the second target resource data in the client of the second blockchain, thereby ensuring the authenticity and integrity of the obtained second target resource data. Compared with the method of uniformly transferring resource data of multiple platforms to a certain platform through cross-chain technology to achieve cross-platform display of resource data, the above method can improve the efficiency of cross-platform display of resource data and reduce the operation difficulty, thereby conveniently realizing cross-chain display of resource data, and at the same time realizing cross-chain verification of resource data. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] To more clearly illustrate the technical solutions of the embodiments of the present application, the accompanying drawings required for the description of the embodiments will be briefly introduced below. Obviously, for those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0027] Figure 1A It is a schematic diagram of the architecture of a blockchain-based data management system provided by an embodiment of the present application;

[0028] Figure 1B It is a schematic diagram of the structure of a blockchain provided by an embodiment of the present application;

[0029] Figure 1C It is a schematic diagram of the process of generating a new block provided by an embodiment of the present application;

[0030] Figure 2 It is a schematic diagram of the process flow of a blockchain-based data management method provided by an embodiment of the present application;

[0031] Figure 3 It is a schematic diagram of the process flow of another blockchain-based data management method provided by an embodiment of the present application;

[0032] Figure 4 It is a schematic diagram of the process flow of yet another blockchain-based data management method provided by an embodiment of the present application;

[0033] Figure 5 It is a schematic diagram of the data structure of an authorization credential provided by an embodiment of the present application;

[0034] Figure 6 It is a schematic block diagram of a blockchain-based data management device provided by an embodiment of the present application;

[0035] Figure 7 It is a schematic block diagram of another blockchain-based data management device provided by an embodiment of the present application;

[0036] Figure 8 It is a schematic block diagram of a computing device provided by an embodiment of the present application. Detailed implementation manners

[0037] Next, the technical solutions in the embodiments of the present application will be clearly and completely described in conjunction with the accompanying drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of the present application.

[0038] An embodiment of the present application proposes a blockchain-based data management method. When a node of the first blockchain receives a resource cross-chain display request, it determines whether there is an authorized binding relationship between the request initiator and the blockchain to which the resource needs to be displayed (such as the second blockchain). If there is an authorized binding relationship, the first hash value of the resource data to be cross-chain displayed (such as the first target resource data) is synchronized to the second blockchain. Then, a node of the second blockchain obtains the resource data to be verified (such as the second target resource data) from the first blockchain, and then compares the second hash value of the second target resource data with the obtained first hash value. If the comparison is consistent, the second target resource data is displayed in the client of the second blockchain. If there is no authorized binding relationship, the request initiator is allowed to perform an authorization binding operation to add a binding relationship, and then the same process as above is carried out, so as to conveniently realize cross-chain verification and cross-chain display of resource data. The present application will be described through the following embodiments.

[0039] Please refer to Figure 1A , which is a schematic diagram of the architecture of a blockchain-based data management system provided by an embodiment of the present application. The blockchain-based data management system includes a blockchain network 10, multiple nodes 101, and a client 102, where:

[0040] The blockchain network 10 refers to a network used for data sharing between nodes. The blockchain network may include multiple nodes 101, and among them, the multiple nodes 101 may include consensus nodes. During the normal operation of each node 101, it can receive input information and maintain the shared data (i.e., the blockchain) in the blockchain network based on the received input information. Among them, each node in the blockchain network stores an identical blockchain, and the blockchain includes a series of blocks (Block) that are sequentially connected in the order of generation time, such as Figure 1A the block 1, block M-1 shown in, etc. Once a new block is added to the blockchain, it will not be removed again. The block records the record data submitted by the nodes in the blockchain network. To ensure information intercommunication within the blockchain network, there may be information connections between each node, and point-to-point communication can be achieved between any two nodes. Specifically, point-to-point communication can be carried out through a wired communication link or a wireless communication link. For example, when any node in the blockchain network receives input information, other nodes obtain the input information according to the consensus algorithm and store the input information as data in the shared data, so that the data stored on all nodes in the blockchain network is consistent.

[0041] The client 102 can access the blockchain network and communicate with the nodes in the blockchain network. For example, it can send transaction data to the nodes and so on. Of course, in some possible implementation manners, the client 102 can also be one of the nodes in the blockchain network. The computing device where the client 102 is located can specifically be a smart phone, a tablet computer, a notebook computer, a desktop computer, an in-vehicle intelligent terminal, etc., which is not limited in the embodiments of the present application. The client 102 can be applied to the computing device of the request initiator for sending a cross-chain display request for resources (such as the client of the first blockchain), or can also be applied to the computing device of the target object for cross-chain displaying the second target resource data (such as the client of the second blockchain).

[0042] It should be noted that the blockchain network 10 can include a first blockchain network and a second blockchain network, and the first blockchain network is connected to the second blockchain network; the client 102 can include a first client and a second client. Based on this, the first blockchain network is like the first blockchain in the embodiment, the second blockchain network is like the second blockchain in the embodiment, the first client can refer to the client of the first blockchain, the first client is connected to the first blockchain, the second client can refer to the client of the second blockchain, and the second client is connected to the second blockchain.

[0043] It should be noted that any node in the blockchain in the embodiment (such as a node of the first blockchain or a node of the second blockchain) may be a receiving node, a processing node or a consensus node. Or there is also a possibility that any node is both a receiving node and a processing node, or there is also a possibility that any node is both a processing node and a consensus node, or there is also a possibility that any node is both a receiving node, a processing node and a consensus node, etc. The embodiments of the present application do not limit this.

[0044] It should be noted that Figure 1A the number of nodes shown is only illustrative. According to actual needs, any number of nodes can be deployed. The node can refer to any form of computing device accessing the network. For example, a server and an object terminal can both join and become nodes.

[0045] For each node in the blockchain network, there is a corresponding node identifier, and each node in the blockchain network can store the node identifiers of other nodes in the blockchain network, so as to broadcast the generated block to other nodes in the blockchain network according to the node identifiers of other nodes later. A node identifier list as shown in Table 1 below can be maintained in each node, and the node name and the node identifier are correspondingly stored in the node identifier list. Among them, the node identifier can be an Internet Protocol (IP) address and any other information that can be used to identify the node. The node identifiers in Table 1 are only examples.

[0046] Table 1

[0047] Node Name Node Identifier Node 1 000.000.000.00a Node 2 000.000.000.00b … … Node N 000.000.000.00c

[0048] Each node in the blockchain network stores an identical blockchain. The blockchain consists of multiple blocks. See Figure 1B , the blockchain consists of multiple blocks. The genesis block includes a block header and a block body. The block header stores the input information feature value, version number, timestamp, and difficulty value. The block body stores the input information. The next block of the genesis block uses the genesis block as the parent block. The next block also includes a block header and a block body. The block header stores the input information feature value of the current block, the block header feature value of the parent block, version number, timestamp, and difficulty value, and so on. This ensures that the block data stored in each block in the blockchain is associated with the block data stored in the parent block, guaranteeing the security of the input information in the block.

[0049] When generating each block in the blockchain, see Figure 1C , when the node where the blockchain is located receives the input information, it verifies the input information. After verification, it stores the input information in the memory pool and updates the hash tree used to record the input information. Then, it updates the timestamp to the time when the input information was received and tries different random numbers, performing eigenvalue calculations multiple times so that the calculated eigenvalue can satisfy the following formula:

[0050] SHA256(SHA256(version+prev_hash+merkle_root+ntime+nbits+x))<TARGET

[0051] Where SHA256 is the eigenvalue algorithm used to calculate the eigenvalue; version (version number) is the version information of the relevant block protocol in the blockchain; prev_hash is the block header feature value of the parent block of the current block; merkle_root is the eigenvalue of the input information; ntime is the update time of the updated timestamp; nbits is the current difficulty, which is a fixed value within a certain period of time and is determined again after exceeding the fixed time period; x is a random number; TARGET is the eigenvalue threshold, and this eigenvalue threshold can be determined based on nbits.

[0052] In this way, when a random number that satisfies the above formula is calculated, the information can be stored correspondingly to generate a block header and a block body, thus obtaining the current block. Subsequently, the node where the blockchain is located sends the newly generated block to other nodes in the blockchain network according to the node identifiers of other nodes in the blockchain network. Other nodes verify the newly generated block and add the newly generated block to the blockchain they store after the verification is completed.

[0053] Among them, smart contracts can run on the nodes of the blockchain network, and various transactions can be realized by calling these smart contracts. A smart contract is an immutable and automatically executable computer program running on the blockchain. A smart contract is the code implementation for execution when certain conditions are met. Developers can define the contract logic through programming languages, publish it to the blockchain (smart contract registration), trigger the execution according to the logic of the contract terms by calling keys or other events, complete the contract logic, and at the same time provide functions for upgrading and canceling smart contracts.

[0054] In a possible implementation, any node 101 in the blockchain network can obtain the transaction data of the client. The transaction data can carry the identity identifier of the client, and this identity identifier can be determined according to the identity certificate of the client. Node 101 can query the identity certificate of the client from the smart contract according to the identity identifier. If the identity certificate of the client is queried from the smart contract and it is determined according to the identity certificate that the client has the permission to perform the transaction operation corresponding to the transaction data for the blockchain, then node 101 can perform the transaction operation corresponding to the transaction data for the blockchain. It can use the mapping relationship between the identity identifier carried in the transaction data and the identity certificate recorded in the smart contract to determine the identity certificate corresponding to the client, and perform the transaction operation according to the permissions indicated in the identity certificate, thereby enhancing the security of data processing on the blockchain. Only carrying the identity identifier in the transaction data can reduce the data volume of the transaction data relative to carrying the complete identity certificate in the transaction data while ensuring that the corresponding identity certificate can be obtained, which is conducive to the rapid transmission of transaction data.

[0055] Generally, it is also necessary to generate a transaction block for the transaction data and chain the block (store the block on the blockchain). Since only the identity identifier is carried, the data volume of the transaction data can be reduced relative to carrying the complete identity certificate in the transaction data while ensuring that the corresponding identity certificate can be obtained, so as to achieve a certain degree of data compression, which can reduce the consumption of blockchain storage resources.

[0056] Embodiments of the present application can also be applied to the field of artificial intelligence. Artificial Intelligence (AI) uses digital computers or machines controlled by digital computers to simulate, extend, and expand human intelligence, and is a theory, method, technology, and application system that can perceive the environment, acquire knowledge, and use knowledge to obtain the best results. In other words, artificial intelligence is a comprehensive technology in computer science that attempts to understand the essence of intelligence and produce a new intelligent machine that can react in a way similar to human intelligence. Artificial intelligence also studies the design principles and implementation methods of various intelligent machines, enabling machines to have the functions of perception, reasoning, and decision-making.

[0057] Artificial intelligence technology is an interdisciplinary subject with a wide range of fields, including both hardware-level and software-level technologies. Artificial intelligence basic technologies generally include sensors, dedicated artificial intelligence chips, cloud computing, distributed storage, big data processing technology, pre-trained model technology, operation / interaction systems, mechatronics, etc. Among them, the pre-trained model, also known as the large model or the basic model, can be widely applied to downstream tasks in various major directions of artificial intelligence after fine-tuning. Artificial intelligence software technology mainly includes several major directions such as computer vision technology, speech processing technology, natural language processing technology, and machine learning / deep learning. The solution provided by the embodiments of the present application mainly relates to the computer vision technology under artificial intelligence technology, which will be described below:

[0058] Computer Vision Technology (CV) Computer vision is a science that studies how to enable machines to "see". More specifically, it refers to using cameras and computers to replace human eyes for tasks such as target recognition and measurement in machine vision, and further performing graphic processing to make the computer-processed images more suitable for human eye observation or transmission to instrument detection. As a scientific discipline, computer vision studies related theories and technologies and attempts to build artificial intelligence systems that can obtain information from images or multi-dimensional data. Large model technology has brought important changes to the development of computer vision technology. Pre-trained models in the visual field such as swin-transformer, ViT, V-MOE, and MAE can be quickly and widely applied to downstream specific tasks after fine-tuning. Computer vision technology usually includes technologies such as image processing, image recognition, image semantic understanding, image retrieval, OCR, video processing, video semantic understanding, video content / behavior recognition, three-dimensional object reconstruction, 3D technology, virtual reality, augmented reality, simultaneous localization and mapping, and also includes common biometric recognition technologies such as face recognition and fingerprint recognition. Specifically, the method proposed in this application realizes the display of second target resource data (such as digital collections) in the client of the second blockchain through computer vision technology. For example, through pictures or videos, 3D visualization, charts, virtual reality, augmented reality, etc., diverse visual displays can be made, making the display of digital collections more immersive and interactive.

[0059] It can be understood that in the specific implementation of this application, relevant data such as cross-chain display requests for resources, target resource data (including first target resource data and second target resource data), and authorization binding information are involved. When the embodiments of this application apply the above data to specific products or technologies, object permission or consent is required, and the collection, use, and processing of relevant data need to comply with relevant laws, regulations, and standards in the relevant regions.

[0060] The implementation details of the technical solutions of the embodiments of this application will be elaborated in detail below:

[0061] Please refer to Figure 2 , Figure 2 which is a schematic flowchart of a blockchain-based data management method provided by the embodiments of this application. The data management method of the embodiments of this application can be applied to nodes of the first blockchain, and the first blockchain can be connected to the second blockchain. As Figure 2 shown, the blockchain-based data management method may include:

[0062] S201. Obtain a cross-chain display request for resources; the cross-chain display request for resources carries a resource identifier and a blockchain identifier.

[0063] A resource cross-chain display request may refer to a request for cross-chain display of specific resources. The resource cross-chain display request may be generated by a request initiator on the client of the first blockchain and sent to the nodes of the first blockchain. Cross-chain display may refer to displaying resources on one blockchain to other blockchains outside that blockchain. Resources may refer to digital assets of accounts on the blockchain, such as digital copyrights, digital collectibles, digital souvenirs, etc. in the account.

[0064] The resource cross-chain display request carries a resource identifier and a blockchain identifier. The resource identifier is the unique identifier of the resource, used to indicate which specific resource needs to be cross-chain displayed in the resource cross-chain display request; the blockchain identifier is the unique identifier of the blockchain, used to indicate which specific blockchain the resource needs to be cross-chain displayed to in the resource cross-chain display request.

[0065] S202. In response to the resource cross-chain display request, obtain the first target resource data corresponding to the resource identifier, and determine the first hash value of the first target resource data.

[0066] In the embodiments of the present application, the nodes of the first blockchain can obtain the resource data matching the resource identifier from the first blockchain through the resource identifier carried in the resource cross-chain display request, that is, the first target resource data. Then, the nodes of the first blockchain can perform hash calculation on the first target resource data to obtain the first hash value of the first target resource data.

[0067] S203. Send the first hash value and the resource identifier to the nodes of the second blockchain corresponding to the blockchain identifier, so that the nodes of the second blockchain obtain the second target resource data corresponding to the resource identifier from the first blockchain and determine the second hash value of the second target resource data. When the first hash value matches the second hash value, display the second target resource data on the client of the second blockchain.

[0068] In an embodiment of the present application, after the node of the first blockchain sends the first hash value and the resource identifier to the node of the second blockchain corresponding to the blockchain identifier, the node of the second blockchain obtains resource data matching the resource identifier from the first blockchain, that is, the second target resource data. However, the second target resource data obtained by the node of the second blockchain may be forged, incomplete, etc. Therefore, the node of the second blockchain can perform a hash calculation on the second target resource data to obtain a second hash value, and then match (i.e., compare) the second hash value with the obtained first hash value. If the first hash value matches the second hash value (i.e., the comparison is consistent), it indicates that the second target resource data obtained by the node of the second blockchain is exactly the same as the data that the node of the first blockchain hopes the node of the second blockchain to perform cross-chain display, thus ensuring the authenticity and integrity of the second target resource data. It should be noted that when the first hash value is the same as the second hash value, the second target resource data is also the same as the first target resource data. In the embodiment, the resource data finally displayed across the chain in the client of the second blockchain is limited by using the second target resource data, which is the resource data obtained by the node of the second blockchain according to the resource identifier.

[0069] When the first hash value matches the second hash value, the node of the second blockchain realizes the cross-chain display of the resource data by displaying the second target resource data that has passed the authenticity and integrity verification in the client of the second blockchain, improving the visibility of digital assets, facilitating the unified management of digital resources on different blockchains by resource owners, reducing the management difficulty of digital resources, and at the same time enhancing the user experience.

[0070] It should be noted that when the first hash value does not match the second hash value, it means that the second target resource data obtained by the node of the second blockchain is not authentic. Then, the display of the second target resource data in the client of the second blockchain can be rejected to avoid misleading the resource owner (such as the request initiator). At the same time, a first error message, such as "resource display exception", can also be displayed in the client of the second blockchain, thus enhancing the object experience of the resource owner. At the same time, a second error message can also be sent to the node of the first blockchain to prompt the node of the first blockchain to correct this exception, such as re-executing the steps and subsequent steps for responding to the cross-chain display request of the resource, and then attempting to display accurate resource data in the client of the second blockchain, which further enhances the object experience of the resource owner.

[0071] In a possible implementation, the node of the first blockchain may also store the first hash value and the resource identifier on the second blockchain corresponding to the blockchain identifier, and then the node of the second blockchain obtains the first hash value and the resource identifier from the second blockchain. The node of the second blockchain then obtains the second target resource data corresponding to the resource identifier from the first blockchain and determines the second hash value of the second target resource data. When the first hash value matches the second hash value, the second target resource data is displayed in the client of the second blockchain. This will not be elaborated in the embodiments of the present application.

[0072] The beneficial effects of the embodiments of the present application are as follows: When receiving a resource cross-chain display request carrying a resource identifier and a blockchain identifier, obtain the first target resource data corresponding to the resource identifier, calculate the first hash value of the first target resource data, and send the first hash value and the resource identifier to the node of the second blockchain corresponding to the blockchain identifier. The node of the second blockchain obtains the second target resource data corresponding to the resource identifier from the first blockchain and calculates the second hash value of the second target resource data. After the first hash value and the second hash value are compared and are consistent, the second target resource data is displayed in the client of the second blockchain, thereby ensuring the authenticity and integrity of the obtained second target resource data. Compared with the method of uniformly transferring the resource data of multiple platforms to a certain platform through cross-chain technology to achieve cross-platform display of resource data, the above method can improve the efficiency of cross-platform display of resource data and reduce the operation difficulty, so as to efficiently and conveniently achieve cross-chain display of resource data, and at the same time achieve cross-chain verification of resource data to ensure that the cross-chain displayed data is accurate.

[0073] In a possible implementation, the node of the first blockchain may also perform the following steps:

[0074] (1) Determine the request initiator corresponding to the resource cross-chain display request and obtain the authorization binding information of the request initiator.

[0075] The request initiator may send a resource cross-chain display request to the node of the first blockchain through the client of the first blockchain. The request initiator may refer to an account in the first blockchain.

[0076] The authorization binding information of the request initiator may refer to: a data structure that records the binding relationship between the request initiator and other authorized blockchains. One or more binding relationships may be recorded in the authorization binding information. The binding relationship can be regarded as the authorization relationship for resource cross-chain display between the request initiator and a certain blockchain. Any one of the binding relationships may include the blockchain identifier of the bound blockchain. Then this binding relationship indicates that this bound blockchain has authorized the request initiator to cross-chain display resources to this bound blockchain without the need for re-authorization binding operations.

[0077] In a possible implementation, the authorization binding information of the request initiating object may be data stored on the first blockchain, and the authorization binding information of the request initiating object may be uploaded to the first blockchain after the consensus nodes of the first blockchain pass the consensus on the authorization binding information, which ensures the authenticity of the authorization binding information and also realizes the traceability of the authorization binding information.

[0078] (2) If the authorization binding information indicates that there is a binding relationship between the second blockchain and the request initiating object, then perform the step of obtaining the first target resource data corresponding to the resource identifier.

[0079] In the embodiment of the present application, the nodes of the first blockchain analyze the binding relationship in the authorization binding information. If the analysis result indicates that there is a binding relationship between the second blockchain and the request initiating object, it means that the second blockchain has authorized the request initiating object to display the resource across the chain to the second blockchain, and there is no need to perform the authorization binding operation anymore. Then, the nodes of the first blockchain can perform the step of obtaining the first target resource data corresponding to the resource identifier (that is, perform step S202 and subsequent steps). The above method can ensure that the operation of resource cross-chain display is legal and is carried out under the authorization of the blockchain to which it needs to be displayed, thereby ensuring the security of resource cross-chain display.

[0080] (3) If the authorization binding information indicates that there is no binding relationship between the second blockchain and the request initiating object, then start the client of the second blockchain so that the request initiating object can perform the authorization binding operation through the client of the second blockchain.

[0081] The authorization binding operation may refer to the operation of establishing a binding relationship between the request initiating object and the second blockchain. The request initiating object can trigger the control for performing the authorization binding operation on the client of the second blockchain to start the authorization binding process. The authorization binding operation may at least include steps such as the second blockchain authenticating the identity of the request initiating object, granting permissions, and signing contracts to ensure legal and secure cross-chain interaction (such as resource cross-chain display) between the request initiating object and the second blockchain in the future.

[0082] (4) Receive the authorization binding request for the authorization binding operation returned by the client of the second blockchain.

[0083] In a possible implementation, during the process of the request initiating object performing an authorization binding operation through the client of the second blockchain, verification operations related to the authorization binding operation are carried out, such as whether the identity of the request initiating object is verified, whether the permissions submitted by the request initiating object are legal, whether the signed contract is correct, etc. After the above verification operations pass, the client of the second blockchain can return an authorization binding request for the authorization binding operation to the node of the first blockchain. The above method ensures that the authorization binding is verified by the second blockchain and the authorization binding is legal.

[0084] (5) Respond to the authorization binding request, add the binding relationship between the second blockchain and the request initiating object to the authorization binding information, and perform the step of obtaining the first target resource data corresponding to the resource identifier.

[0085] In the embodiment of the present application, after adding the binding relationship between the second blockchain and the request initiating object to the authorization binding information, the node of the first blockchain can perform the step of obtaining the first target resource data corresponding to the resource identifier (that is, perform step S202 and subsequent steps). The above method realizes the continuous update of the authorization binding information, ensures the accuracy of the authorized binding relationships stored in the authorization binding information. In the subsequent process, any node of the blockchain can determine whether to directly perform the step of obtaining the first target resource data corresponding to the resource identifier through the updated authorization binding information, or first notify the corresponding client to perform the corresponding authorization binding operation. The embodiment of the present application will not elaborate on this anymore.

[0086] Through the above steps (3)-(5), the continuous update of the authorization binding information is realized. Analyzing the authorized binding relationships of the request initiating object corresponding to the resource cross-chain display request based on the continuously updated authorization binding information helps to ensure that the resource data for cross-chain display has been legally authorized, guarantees the authenticity and integrity of the resource data, and ensures the security and credibility of cross-chain interaction.

[0087] In a possible implementation, the node of the first blockchain can obtain the authorization binding information of the request initiating object through the following steps:

[0088] (1) Obtain one or more candidate authorization credentials corresponding to the request initiating object from the first blockchain; the candidate authorization credentials are generated by the node of the first blockchain when responding to the authorization binding request returned by the client of any blockchain and are uploaded to the first blockchain.

[0089] In a possible implementation, the request initiating object can perform an authorization binding operation through the client of any blockchain. Then, the node of the first blockchain receives the authorization binding request for this authorization binding operation returned by the client of any blockchain. Finally, in response to the authorization binding request, the node of the first blockchain adds the binding relationship between any blockchain and the request initiating object to the authorization binding information. This step is also to generate a candidate authorization credential corresponding to this authorization binding operation and upload the generated candidate authorization credential to the first blockchain. For the specific implementation of adding the binding relationship between any blockchain and the request initiating object to the authorization binding information, reference can be made to the relevant description of adding the binding relationship between the second blockchain and the request initiating object to the authorization binding information in the subsequent embodiments, which will not be elaborated here.

[0090] In a possible implementation, one or more candidate authorization credentials corresponding to the request initiating object are stored on the first blockchain. After each authorization binding operation of the request initiating object is completed, a corresponding candidate authorization credential will be generated. For example, when the request initiating object sends a resource cross-chain display request to the node of the first client through the client of the first blockchain, and the blockchain identifier carried in the resource cross-chain display request indicates a new blockchain that has no binding relationship with the request initiating object, then the request initiating object will perform an authorization binding operation through the client of the new blockchain. After the authorization binding operation is completed, the node of the first blockchain will generate a candidate authorization credential corresponding to this authorization binding operation and upload this candidate authorization credential to the first blockchain. Among them, the generated candidate authorization credential includes the binding relationship between the new blockchain and the request initiating object.

[0091] (2) Determine the target authorization credential from one or more candidate authorization credentials; the on-chain time of the target authorization credential is later than the on-chain times of other candidate authorization credentials among the one or more candidate authorization credentials.

[0092] In the embodiments of this application, each candidate authorization credential corresponds to an on-chain time. The node of the first blockchain determines the candidate authorization credential with the latest on-chain time among the one or more candidate authorization credentials (that is, the candidate authorization credential that is newly uploaded) as the target authorization credential. That is to say, the candidate authorization credential with the latest on-chain time among the one or more candidate authorization credentials corresponding to the request initiating object can be used as the valid authorization credential of the request initiating object, while other candidate authorization credentials are invalid authorization credentials and are only suitable for tracing. This can avoid using expired or non-timely authorization credentials, thereby improving the accuracy and reliability of the obtained authorization binding information.

[0093] Exemplarily, there are two candidate authorization credentials corresponding to the request initiating object on the first blockchain, namely candidate authorization credential 1 and candidate authorization credential 2. Candidate authorization credential 1 is generated when the request initiating object performs the first authorization binding operation. For example, the request initiating object authorizes and binds with blockchain 2 so that the resource data of the request initiating object on blockchain 1 can be cross-chain displayed on blockchain 2. Candidate authorization credential 2 is generated when the request initiating object performs the second authorization binding operation. For example, the request initiating object authorizes and binds with blockchain 3 so that the resource data of the request initiating object on blockchain 1 can be cross-chain displayed on blockchain 3. The on-chain time of candidate authorization credential 2 is later than that of candidate authorization credential 1. Then, the target authorization credential can refer to the above-mentioned candidate authorization credential 2.

[0094] It should be noted that when the request initiating object registers its identity on the first blockchain, the initial authorization credential of the request initiating object can be generated by the nodes of the first blockchain and the initial authorization credential of the request initiating object is uploaded to the first blockchain. The initial authorization credential does not include binding records. The above initial authorization credential can be the candidate authorization credential that is the earliest to be uploaded among one or more candidate authorization credentials. For example, the initial authorization credential can refer to the above-mentioned candidate authorization credential 1. And the candidate authorization credential has undergone one authorization binding. Therefore, the number of binding records included in the initial authorization credential 2 can be 1.

[0095] (3) Determine the authorization binding information of the request initiating object from the target authorization credential.

[0096] Through the above steps (1)-(3), the nodes of the first blockchain can accurately identify valid authorization credentials from the first blockchain and extract authorization binding information from the valid authorization credentials, which ensures the accuracy and authenticity of the extracted authorization binding information.

[0097] In a possible implementation manner, the nodes of the first blockchain add the binding relationship between the second blockchain and the request initiating object to the authorization binding information, which can be implemented through the following steps:

[0098] (1) Generate a binding record according to the binding relationship between the second blockchain and the request initiating object.

[0099] (2) Add the binding record to the target authorization credential to obtain the updated target authorization credential.

[0100] (3) Upload the updated target authorization credential to the first blockchain; the updated target authorization credential on the first blockchain includes the updated authorization binding information.

[0101] In the above steps (1)-(3), the nodes of the first blockchain generate the corresponding binding relationship for this authorization binding, and then add the binding relationship to the valid authorization credential (i.e., the target authorization credential) of the request initiating object to obtain the updated target authorization credential. Then, the updated target authorization credential is uploaded to the first blockchain, thus realizing the continuous update of the authorization credential of the request initiating object on the chain, ensuring the traceability and immutability of the authorization binding information, and at the same time providing trusted authorization binding information for the access and verification of other blockchain nodes.

[0102] In a possible implementation, the nodes of the second blockchain can submit the identity ID of the request initiating object on the second blockchain to the nodes of the first blockchain through the cross-chain identity protocol, so that the nodes of the first blockchain can authorize and bind the request initiating object with the second blockchain.

[0103] In a possible implementation, the nodes of the first blockchain can also perform the following steps: store the first target resource data in the light node of the first blockchain, so that the nodes of the second blockchain can obtain the second target resource data corresponding to the resource identifier from the light node of the first blockchain.

[0104] Among them, the light node of the first blockchain refers to the lightweight node in the first blockchain. Compared with the full node, the light node does not need to store the data of the entire blockchain completely, but only needs to store the block header and part of the transaction data. By communicating with the full node or other light nodes, the light node can obtain the required blockchain data for verification and query operations. Storing the first target resource data in the light node of the first blockchain can reduce the response time when the second blockchain requests this data, and at the same time realizes the distributed storage of the data on the first blockchain, improving the stability and security of the data, thereby reducing the risk of data loss and tampering.

[0105] In a possible implementation, only the specified blockchain has the access right to read the first target resource data stored in the light node of the first blockchain. The light node of the first blockchain can include an access right judgment logic, and the access right judgment logic can be in the smart contract of the light node.

[0106] When the light node of the first blockchain receives a data acquisition request for the second target resource data from a node of the second blockchain, it acquires the authorization binding information of the request initiator. If the authorization binding information indicates that there is a binding relationship between the second blockchain and the request initiator, it sends the first target resource data corresponding to the resource identifier to the node of the second blockchain. When the authorization binding information indicates that there is no binding relationship between the second blockchain and the request initiator, it rejects the access of the node of the second blockchain. The above method restricts the light node of the first blockchain to only open the access permission of resource data to specified blockchain nodes, which helps to improve data security. Only the nodes of the second blockchain with a binding relationship can obtain the corresponding resource data, thus reducing the risk of unauthorized access. In addition, the above method can also effectively control the use of resources, reduce unnecessary data transmission, and improve the utilization efficiency of network resources.

[0107] Please refer to Figure 3 , Figure 3 FIG. is a schematic flowchart of another blockchain-based data management method provided by an embodiment of the present application. The data management method of the embodiment of the present application can be applied to a node of the second blockchain, and the first blockchain can be connected to the second blockchain. As Figure 3 shown, the blockchain-based data management method may include:

[0108] S301. Receive a first hash value and a resource identifier sent by a node of the first blockchain in response to a resource cross-chain display request; the resource cross-chain display request carries the resource identifier and the blockchain identifier, the first hash value is generated by the node of the first blockchain according to the first target resource data corresponding to the resource identifier, and the blockchain identifier matches the second blockchain.

[0109] S302. Obtain the second target resource data corresponding to the resource identifier from the first blockchain and determine the second hash value of the second target resource data.

[0110] S303. Match the first hash value with the second hash value.

[0111] S304. When the first hash value and the second hash value match, display the second target resource data in the client of the second blockchain.

[0112] Among them, the specific implementation manners and related concepts of steps S301-S304 can be referred to the relevant descriptions in the foregoing embodiments, and will not be elaborated here.

[0113] The beneficial effects of the embodiments of the present application are as follows: After the nodes of the second blockchain receive the first hash value and the resource identifier sent by the nodes of the first blockchain in response to the resource cross-chain display request, they obtain the second target resource data corresponding to the resource identifier from the first blockchain, calculate the second hash value of the second target resource data, and by comparing the first hash value with the second hash value, when the comparison is consistent, display the second target resource data in the client of the second blockchain, thereby ensuring the authenticity and integrity of the obtained second target resource data.

[0114] In a possible implementation, the nodes of the second blockchain can display the second target resource data in the client of the second blockchain in the following manner:

[0115] 1. Picture or video display: If the second target resource data is a digital collectible of the image or video type, it can be directly displayed in the client in the form of a picture or video. This method usually involves operations such as zooming in, zooming out, and fast-forwarding of the image or video, and may require providing interactive controls to support the user's interactive experience.

[0116] 2. 3D visualization display: If the second target resource data is such as a three-dimensional digital collectible, a three-dimensional digital artwork, etc., three-dimensional visualization technology can be used to present it in the form of a three-dimensional model in the client of the second blockchain, and users can browse it through interactive methods such as mouse, gestures, or touch screen.

[0117] 3. Chart display: For data such as digital collectibles and data related to digital collectibles, the data can be displayed in the form of charts, such as statistics of post-collection quantities, charts of price trends, etc. These charts can help users more intuitively understand the characteristics and changing trends of the data.

[0118] 4. Virtual Reality (VR) / Augmented Reality (AR) display: Through virtual reality or augmented reality technology, a more immersive and interactive digital collectible display can be achieved in the client.

[0119] Through the above methods, a diverse visual display of the second target resource data is achieved in the client of the second blockchain.

[0120] In a possible implementation, after the nodes of the first blockchain obtain the resource cross-chain display request, they store the first target resource data in the light nodes of the first blockchain. Based on this, the nodes of the second blockchain can obtain the second target resource data corresponding to the resource identifier from the first blockchain through the following steps:

[0121] (1) Send a data acquisition request for the second target resource data corresponding to the resource identifier to the lightweight node of the first blockchain, so that the lightweight node of the first blockchain responds to the data acquisition request, obtains the authorization binding information of the request initiator object corresponding to the resource cross-chain display request, and analyzes the binding relationship included in the authorization binding information to obtain an analysis result.

[0122] (2) Receive the first target resource data corresponding to the resource identifier returned by the lightweight node of the first blockchain to determine that the second target resource data corresponding to the resource identifier has been obtained; the first target resource data is sent by the lightweight node of the first blockchain when the analysis result indicates that the authorization binding information includes the binding relationship between the second blockchain and the request initiator object.

[0123] In the above steps (1)-(2), the node of the second blockchain needs to send a data acquisition request for the second target resource data to the lightweight node of the first blockchain. The lightweight node of the first blockchain will determine whether the node of the second blockchain has access rights to the first target resource data stored on the lightweight node through the authorization binding information of the request initiator object. When the authorization binding information includes the binding relationship between the second blockchain and the request initiator object, it is considered to have access rights; when the authorization binding information does not include the binding relationship between the second blockchain and the request initiator object, it is considered not to have access rights. The above method helps to protect the security of the data on the lightweight node of the first blockchain and restricts the access of unauthorized nodes to the data on the lightweight node of the first blockchain.

[0124] In a possible implementation, after the node of the first blockchain obtains the resource cross-chain display request, it stores the first signature corresponding to the first target resource data in the lightweight node of the first blockchain, and sends the second signature corresponding to the first hash value to the node of the second blockchain. That is to say, after the node of the first blockchain obtains the resource cross-chain display request, it can store the first target resource data and the first signature corresponding to the first target resource data in the lightweight node of the first blockchain, so that the node of the second blockchain can verify the authenticity and integrity of the first target resource data obtained from the lightweight node through the first signature. The node of the first blockchain can also send the first hash value and the second signature corresponding to the first hash value to the node of the second blockchain, so that the node of the second blockchain can verify the authenticity and integrity of the obtained first hash value through the second signature.

[0125] Based on this, the node of the second blockchain can also perform the following steps:

[0126] (1) Obtain the public key, the first signature, and the second signature of the node of the first blockchain.

[0127] (2) Perform the first signature verification process using the public key, the first signature, and the second target resource data. When the first signature verification process passes, perform the second signature verification process using the public key, the second signature, and the first hash value.

[0128] In a possible implementation, the first signature verification process can be implemented in the following way: decrypt the first signature using the public key to obtain the first hash value; perform a hash operation on the second target resource data using the same hash algorithm as the decryption operation to obtain the second hash value. If the first hash value is the same as the second hash value, the first signature verification process passes; if the first hash value is different from the second hash value, the first signature verification process fails.

[0129] In a possible implementation, the second signature verification process can be implemented in the following way: decrypt the second signature using the public key to obtain the third hash value; perform a hash operation on the first hash value using the same hash algorithm as the decryption operation to obtain the fourth hash value. If the third hash value is the same as the fourth hash value, the second signature verification process passes; if the third hash value is different from the fourth hash value, the second signature verification process fails.

[0130] (3) When the second signature verification process passes, execute the step of determining the second hash value of the second target resource data.

[0131] In the above steps (1)-(3), the nodes of the second blockchain perform signature verification processes on the obtained second target resource data and the first hash value respectively, so as to verify the integrity and authenticity of the obtained second target resource data and the first hash value. After the signature verification processes for both the second target resource data and the first hash value pass, then perform the subsequent steps of hash value matching, which can ensure that the resource data displayed across chains is accurate.

[0132] The first blockchain in the data management method based on blockchain provided by the embodiments of this application can be an open chain (such as the trustSQL blockchain), and is implemented relying on the smart contracts and light nodes provided by the open chain. The second blockchain can be a third-party consortium chain. Generally, a consortium chain is jointly maintained and managed by multiple participants, such as local data exchanges, etc. Each participant has its own node in the consortium chain and participates in the consensus process of the chain. At the same time, each participant runs its own centralized platform for displaying, trading, etc. of resource data (such as digital assets).

[0133] This application realizes an interactive mode for cross-platform interoperability of digital assets, breaking the limitation that digital assets can only be displayed on the corresponding centralized platform. The core logic of the above blockchain-based data management method is as follows: Through smart contracts and light nodes, the digital asset data that needs to be cross-chain displayed is synchronized to the light nodes, and the third-party consortium chain verifies the data on the light nodes. After the verification passes, the third-party consortium chain displays it, so as to realize the verification and display of cross-chain information while maintaining the sovereignty independence between the open chain and other consortium chains.

[0134] Please refer to Figure 4 , Figure 4 FIG. is a schematic flowchart of another blockchain-based data management method provided by an embodiment of this application. The data management method of the embodiment of this application is described by the interaction between the first blockchain and the second blockchain. The blockchain-based data management method may include:

[0135] S401. A request initiating object initiates a resource cross-chain display request. Among them, the resource cross-chain display request carries a resource identifier and a blockchain identifier.

[0136] The request initiating object owns resources on the first blockchain, such as digital assets. The request initiating object can initiate a resource cross-chain display request through the client of the first blockchain. When initiating a resource cross-chain display request, it can select the second blockchain to which the digital assets need to be displayed. The above blockchain identifier is used to indicate the second blockchain.

[0137] After step S401, according to the authorization binding information of the request initiating object, it can be determined whether the request initiating object is performing resource cross-chain display for the second blockchain for the first time. That is to say, when the authorization binding information of the request initiating object indicates that there is no binding relationship between the second blockchain and the request initiating object, it is determined that it is the first time to perform resource cross-chain display for the second blockchain, and then subsequent step S402 and subsequent steps are performed. And when it is determined that it is not the first time to perform resource cross-chain display for the second blockchain, that is, the authorization binding information of the request initiating object indicates that there is a binding relationship between the second blockchain and the request initiating object, subsequent step S406 and subsequent steps are directly performed.

[0138] S402. The client of the first blockchain starts the client of the second blockchain.

[0139] S403. The request initiating object performs an authorization binding operation through the client of the second blockchain.

[0140] After the request initiating object logs in to the second blockchain, it performs an authorization binding operation.

[0141] S404. Perform blockchain - uploading processing on the authorized binding information. The blockchain - uploading processing may include uploading the authorized binding information to the second blockchain (such as nodes of the second blockchain), and uploading the authorized binding information to the first blockchain (such as nodes of the first blockchain, where the nodes may refer to the core nodes of the first blockchain).

[0142] S405. The nodes of the second blockchain perform cross - chain binding.

[0143] The cross - chain binding may refer to adding the binding relationship between the second blockchain and the request - initiating object to the authorized binding information of the request - initiating object, and the authorized binding information is stored on the first blockchain. The cross - chain binding may submit the binding relationship between the second blockchain and the request - initiating object to the core node of the first blockchain based on the cross - chain identity protocol to complete the binding.

[0144] S406. The core node of the first blockchain calculates the first hash value of the resource data and performs a signature operation.

[0145] In a possible implementation, the core node of the first blockchain may obtain the resource data corresponding to the resource identifier from the first blockchain and calculate the first hash value of the resource data.

[0146] In a possible implementation, the signature operation may include two parts: the first signature corresponding to the resource data, and the second signature corresponding to the first hash value. Exemplarily, after the node of the first blockchain obtains a resource cross - chain display request, it may store the first target resource data and the first signature corresponding to the first target resource data in the light node of the first blockchain, so that the node of the second blockchain can verify the authenticity and integrity of the first target resource data obtained from the light node through the first signature. The node of the first blockchain may also send the first hash value and the second signature corresponding to the first hash value to the node of the second blockchain, so that the node of the second blockchain can verify the authenticity and integrity of the obtained first hash value through the second signature.

[0147] S407. The core node of the first blockchain synchronizes the resource data to the light node.

[0148] S408. The core node of the first blockchain synchronizes the first hash value to the second blockchain.

[0149] S409. The node of the second blockchain calculates the second hash value of the light - node data and matches it with the first hash value.

[0150] S410. When the match is consistent, display the resource data on the client of the second blockchain.

[0151] Through the above steps S401-S410, cross-chain display of resource data is conveniently realized, and cross-chain verification of resource data is also realized to ensure that the data displayed across the chain is accurate. The specific implementation of steps S401-S410 can be found in the relevant description in the above embodiments, which will not be repeated here.

[0152] In a possible implementation, the authorization binding information of the request initiating object can be obtained from the target authorization credential of the request initiating object, and the target authorization credential is the candidate authorization credential with the latest chain time among one or more candidate authorization credential stored on the chain by the request initiating object. See Figure 5 , Figure 5 This is a schematic diagram of the data structure of an authorization credential provided in an embodiment of the present application.

[0153] Among them, the authorization certificate may include three parts. The first part is the identity of the request initiating object on the first blockchain (such as ID1). The object is uniquely identified in the blockchain network through the identity, and the request initiating object is associated with the information in the authorization certificate for easy indexing.

[0154] The second part is the attribute information of the object initiating the request, such as the registration name, registration time, account related information, etc.

[0155] The third part is the authorization binding information, including the binding record generated by the request initiator after each authorization binding operation is completed. Each binding record can include the binding relationship between the request initiator and a blockchain. The authorization binding information on the chain can be used to understand the authorization binding process of the object and ensure the traceability of the authorization binding information.

[0156] For example, each binding record may include the target blockchain, operation type, and occurrence time corresponding to the current authorization binding event. The operation types of the authorization binding event may include adding binding, unbinding, freezing binding, etc. Frozen binding is usually temporary and can be restored by unfreezing. For example, when there are security issues or suspicious operations on the object, the binding can be frozen to prevent further abnormal operations on the object. Figure 5 The authorization binding information in may mean that the object with identity ID1 is bound to blockchain 2 at time T2, bound to blockchain 3 at time T3, bound to blockchain 4 at time T4, and unbound from blockchain 3 at time T5. At this time, the blockchains that are bound to the object also include: blockchain 2 and blockchain 4. Then, the object can display the resource data on blockchain 1 to blockchain 2 or blockchain 4 across chains, but not to blockchain 3.

[0157] After each authorization binding operation of the request initiating object is completed, first obtain the latest authorized credential uploaded to the chain corresponding to the request initiating object from the chain, then add the binding record corresponding to the current authorization binding operation to the above-mentioned latest authorized credential uploaded to the chain to obtain an updated authorized credential, and perform an on-chain process on the updated authorized credential, such as uploading it to one or both of the first blockchain and the second blockchain.

[0158] Exemplarily, after the request initiating object performs the first authorization binding operation and completes it, the authorization binding information in the generated authorized credential only contains the first binding record, and this binding record may refer to: the object with the identity identifier ID1 is bound to the blockchain 2 at time T2.

[0159] Exemplarily, when the request initiating object registers on the first blockchain, an initial authorized credential can be generated and an on-chain process is performed on the initial authorized credential. The authorization binding information in the initial authorized credential does not contain binding records.

[0160] Through the above embodiments, the problem of digital asset islands can be effectively solved, which will help build a digital cultural and creative alliance chain system that can be interconnected and maintain sovereign independence, contribute to building an efficient and trustworthy digital cultural and creative ecological environment, and promote the healthy development of the digital cultural and creative industry. From the perspective of the owner of digital assets, it can also help the owner better manage and operate their digital assets.

[0161] Please refer to Figure 6 , which is a schematic block diagram of a blockchain-based data management device provided by an embodiment of the present application. The data management device described in this embodiment can be applied to a computing device, for example, it can be applied to a node of the first blockchain. The data management device includes:

[0162] An obtaining module 601, configured to obtain a resource cross-chain display request; the resource cross-chain display request carries a resource identifier and a blockchain identifier;

[0163] A processing module 602, configured to respond to the resource cross-chain display request, obtain first target resource data corresponding to the resource identifier, and determine a first hash value of the first target resource data;

[0164] A sending module 603, configured to send the first hash value and the resource identifier to a node of the second blockchain corresponding to the blockchain identifier, so that the node of the second blockchain obtains second target resource data corresponding to the resource identifier from the first blockchain and determines a second hash value of the second target resource data. When the first hash value matches the second hash value, display the second target resource data in the client of the second blockchain.

[0165] In a possible implementation, the above-mentioned processing module 602 is further configured to:

[0166] Determine the request initiator corresponding to the above-mentioned cross-chain display request for resources, and obtain the authorization binding information of the above-mentioned request initiator;

[0167] If the above-mentioned authorization binding information indicates that there is a binding relationship between the second blockchain and the above-mentioned request initiator, then execute the step of obtaining the first target resource data corresponding to the above-mentioned resource identifier.

[0168] In a possible implementation, when the above-mentioned processing module 602 is used, it is specifically configured to:

[0169] If the above-mentioned authorization binding information indicates that there is no binding relationship between the second blockchain and the above-mentioned request initiator, then start the client of the second blockchain, so that the above-mentioned request initiator performs an authorization binding operation through the client of the second blockchain;

[0170] Receive the authorization binding request for the above-mentioned authorization binding operation returned by the client of the second blockchain;

[0171] In response to the above-mentioned authorization binding request, add the binding relationship between the second blockchain and the above-mentioned request initiator to the above-mentioned authorization binding information, and execute the step of obtaining the first target resource data corresponding to the above-mentioned resource identifier.

[0172] In a possible implementation, when the above-mentioned processing module 602 is used to obtain the authorization binding information of the above-mentioned request initiator, it is specifically configured to:

[0173] Obtain one or more candidate authorization certificates corresponding to the above-mentioned request initiator from the first blockchain; the above-mentioned candidate authorization certificates are generated by the nodes of the first blockchain in response to the authorization binding request returned by the client of any blockchain and uploaded to the first blockchain;

[0174] Determine the target authorization certificate from the above-mentioned one or more candidate authorization certificates; the on-chain time of the above-mentioned target authorization certificate is later than the on-chain time of other candidate authorization certificates among the above-mentioned one or more candidate authorization certificates;

[0175] Determine the authorization binding information of the above-mentioned request initiator from the above-mentioned target authorization certificate.

[0176] In a possible implementation, when the above-mentioned processing module 602 is used to add the binding relationship between the second blockchain and the above-mentioned request initiator to the above-mentioned authorization binding information, it is specifically configured to:

[0177] Generate a binding record according to the binding relationship between the second blockchain and the above-mentioned request initiator;

[0178] Add the above binding record to the above target authorization credential to obtain an updated target authorization credential;

[0179] Upload the updated target authorization credential to the first blockchain; the updated target authorization credential on the first blockchain includes updated authorization binding information.

[0180] In a possible implementation, the processing module 602 is further configured to:

[0181] Store the first target resource data in the light node of the first blockchain, so that the nodes of the second blockchain can obtain the second target resource data corresponding to the resource identifier from the light node of the first blockchain;

[0182] Wherein, when the light node of the first blockchain receives a data acquisition request for the second target resource data from the node of the second blockchain, it acquires the authorization binding information of the request initiator object. If the authorization binding information indicates that there is a binding relationship between the second blockchain and the request initiator object, it sends the first target resource data corresponding to the resource identifier to the node of the second blockchain.

[0183] Please refer to Figure 7 , which is a schematic block diagram of another blockchain-based data management device provided by an embodiment of the present application. The data management device described in this embodiment can be applied to a computing device, for example, it can be applied to the nodes of the second blockchain. The data management device includes:

[0184] A receiving module 701, configured to receive a first hash value and a resource identifier sent by a node of the first blockchain in response to a resource cross-chain display request; the resource cross-chain display request carries the resource identifier and a blockchain identifier, the first hash value is generated by the node of the first blockchain according to the first target resource data corresponding to the resource identifier, and the blockchain identifier matches the second blockchain;

[0185] An execution module 702, configured to obtain the second target resource data corresponding to the resource identifier from the first blockchain and determine a second hash value of the second target resource data;

[0186] The execution module 702 is configured to match the first hash value with the second hash value;

[0187] A data display module 703, configured to display the second target resource data in the client of the second blockchain when the first hash value matches the second hash value.

[0188] In a possible implementation, after the node of the first blockchain obtains the above-mentioned cross-chain display request for resources, it stores the above-mentioned first target resource data in the light node of the first blockchain;

[0189] When the above-mentioned execution module 702 is used to obtain the second target resource data corresponding to the above-mentioned resource identifier from the above-mentioned first blockchain, it is specifically used for:

[0190] Send a data acquisition request for the second target resource data corresponding to the above-mentioned resource identifier to the light node of the first blockchain, so that the light node of the first blockchain responds to the data acquisition request, obtains the authorization binding information of the request initiator object corresponding to the above-mentioned cross-chain display request for resources, and analyzes the binding relationship included in the above-mentioned authorization binding information to obtain an analysis result;

[0191] Receive the first target resource data corresponding to the above-mentioned resource identifier returned by the light node of the first blockchain to determine that the second target resource data corresponding to the above-mentioned resource identifier is obtained; the above-mentioned first target resource data is sent by the light node of the first blockchain when the above-mentioned analysis result indicates that the above-mentioned authorization binding information includes the binding relationship between the second blockchain and the above-mentioned request initiator object.

[0192] In a possible implementation, after the node of the first blockchain obtains the above-mentioned cross-chain display request for resources, it stores the first signature corresponding to the above-mentioned first target resource data in the light node of the first blockchain, and sends the second signature corresponding to the above-mentioned first hash value to the node of the second blockchain;

[0193] The above-mentioned execution module 702 is further used for:

[0194] Obtain the public key, the above-mentioned first signature, and the above-mentioned second signature of the node of the first blockchain;

[0195] Perform a first signature verification process using the above-mentioned public key, the above-mentioned first signature, and the above-mentioned second target resource data. When the first signature verification process passes, perform a second signature verification process using the above-mentioned public key, the above-mentioned second signature, and the above-mentioned first hash value;

[0196] When the second signature verification process passes, execute the step of determining the second hash value of the above-mentioned second target resource data.

[0197] It should be noted that the functions of the functional modules of the data management device in the embodiments of the present application can be specifically implemented according to the methods in the above-mentioned method embodiments, and the specific implementation process can refer to the relevant descriptions of the above-mentioned method embodiments, which will not be elaborated here.

[0198] In a feasible embodiment, the blockchain-based data management device provided by the embodiments of the present application can be implemented in software. The blockchain-based data management device can be stored in a memory, which can be software in the form of a program and a plug-in, and includes a series of units, including a processing unit and a communication unit; wherein, the processing unit and the communication unit are used to implement the blockchain-based data management method provided by the embodiments of the present application.

[0199] In other feasible embodiments, the blockchain-based data management device provided by the embodiments of the present application can also be implemented in a combination of software and hardware. As an example, the blockchain-based data management device provided by the embodiments of the present application can be a processor in the form of a hardware decoding processor, which is programmed to execute the blockchain-based data management method provided by the embodiments of the present application. For example, the processor in the form of a hardware decoding processor can adopt one or more application-specific integrated circuits (ASICs), DSPs, programmable logic devices (PLDs), complex programmable logic devices (CPLDs), field-programmable gate arrays (FPGAs) or other electronic components.

[0200] Please refer to Figure 8 , which is a schematic block diagram of a computing device provided by the embodiments of the present application. The computing device described in this embodiment includes: a processor 801, a memory 802, and a network interface 803. Data can be exchanged between the above-mentioned processor 801, memory 802, and network interface 803. For example, they are connected through one or more communication buses, and the communication buses are used to implement the communication connection between these components.

[0201] The above-mentioned processor 801 can be a central processing unit (CPU), and this processor can also be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), off-the-shelf programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or this processor can also be any conventional processor, etc.

[0202] The above-mentioned memory 802 may include a read-only memory and a random-access memory, and provide program instructions and data to the processor 801. The memory 802 may include a volatile memory, such as a random-access memory (RAM); the memory 802 may also include a non-volatile memory, such as a flash memory, a solid-state drive (SSD), etc.; the memory 802 may further include a combination of the above-mentioned types of memories. In a feasible embodiment, the computing device may be applied to an embodiment. When the above-mentioned processor 801 calls the above-mentioned program instructions, it is used to perform the following operations:

[0203] Obtain a resource cross-chain display request; the resource cross-chain display request carries a resource identifier and a blockchain identifier;

[0204] In response to the resource cross-chain display request, obtain first target resource data corresponding to the resource identifier, and determine a first hash value of the first target resource data;

[0205] Send the first hash value and the resource identifier to a node of a second blockchain corresponding to the blockchain identifier, so that the node of the second blockchain obtains second target resource data corresponding to the resource identifier from the first blockchain, and determines a second hash value of the second target resource data. When the first hash value matches the second hash value, display the second target resource data in a client of the second blockchain.

[0206] In a possible implementation manner, the above-mentioned processor 801 is further used for:

[0207] Determine a request initiator corresponding to the resource cross-chain display request, and obtain authorization binding information of the request initiator;

[0208] If the authorization binding information indicates that there is a binding relationship between the second blockchain and the request initiator, perform the step of obtaining the first target resource data corresponding to the resource identifier.

[0209] In a possible implementation manner, when the above-mentioned processor 801 is used, it is specifically used for:

[0210] If the authorization binding information indicates that there is no binding relationship between the second blockchain and the request initiator, start the client of the second blockchain, so that the request initiator performs an authorization binding operation through the client of the second blockchain;

[0211] Receive the authorization binding request for the above authorization binding operation returned by the client of the second blockchain;

[0212] In response to the above authorization binding request, add the binding relationship between the second blockchain and the request initiating object to the above authorization binding information, and execute the step of obtaining the first target resource data corresponding to the above resource identifier.

[0213] In a possible implementation manner, when the above processor 801 is used to obtain the authorization binding information of the above request initiating object, it is specifically used for:

[0214] Obtain one or more candidate authorization credentials corresponding to the above request initiating object from the above first blockchain; the above candidate authorization credentials are generated by the nodes of the above first blockchain when responding to the authorization binding request returned by the client of any blockchain and are chained to the above first blockchain;

[0215] Determine the target authorization credential from the above one or more candidate authorization credentials; the chaining time of the above target authorization credential is later than the chaining times of other candidate authorization credentials among the above one or more candidate authorization credentials;

[0216] Determine the authorization binding information of the above request initiating object from the above target authorization credential.

[0217] In a possible implementation manner, when the above processor 801 is used to add the binding relationship between the second blockchain and the above request initiating object to the above authorization binding information, it is specifically used for:

[0218] Generate a binding record according to the binding relationship between the second blockchain and the above request initiating object;

[0219] Add the above binding record to the above target authorization credential to obtain an updated target authorization credential;

[0220] Chain the above updated target authorization credential to the above first blockchain; the updated target authorization credential on the above first blockchain includes the updated authorization binding information.

[0221] In a possible implementation manner, the above processor 801 is further used for:

[0222] Store the above first target resource data in the light node of the above first blockchain, so that the nodes of the above second blockchain can obtain the second target resource data corresponding to the above resource identifier from the light node of the above first blockchain;

[0223] Among them, when the light node of the first blockchain receives a data acquisition request for the second target resource data from a node of the second blockchain, it acquires the authorization binding information of the request initiator object. If the authorization binding information indicates that there is a binding relationship between the second blockchain and the request initiator object, it sends the first target resource data corresponding to the resource identifier to the node of the second blockchain.

[0224] In a feasible embodiment, the computing device can be applied to another embodiment. When the processor 801 invokes the above program instructions, it is used to perform the following operations:

[0225] Receive the first hash value and the resource identifier sent by the node of the first blockchain in response to the resource cross-chain display request; the resource cross-chain display request carries the resource identifier and the blockchain identifier, the first hash value is generated by the node of the first blockchain according to the first target resource data corresponding to the resource identifier, and the blockchain identifier matches the second blockchain;

[0226] Obtain the second target resource data corresponding to the resource identifier from the first blockchain, and determine the second hash value of the second target resource data;

[0227] Match the first hash value with the second hash value;

[0228] When the first hash value and the second hash value match, display the second target resource data in the client of the second blockchain.

[0229] In a possible implementation manner, after the node of the first blockchain obtains the resource cross-chain display request, it stores the first target resource data in the light node of the first blockchain;

[0230] When the processor 801 is used to obtain the second target resource data corresponding to the resource identifier from the first blockchain, it is specifically used for:

[0231] Send a data acquisition request for the second target resource data corresponding to the resource identifier to the light node of the first blockchain, so that the light node of the first blockchain responds to the data acquisition request, acquires the authorization binding information of the request initiator object corresponding to the resource cross-chain display request, and analyzes the binding relationship included in the authorization binding information to obtain an analysis result;

[0232] Receive the first target resource data corresponding to the resource identifier returned by the light node of the first blockchain, so as to determine that the second target resource data corresponding to the resource identifier is obtained; the first target resource data is sent by the light node of the first blockchain when the analysis result indicates that the authorization binding information includes the binding relationship between the second blockchain and the request initiating object.

[0233] In a possible implementation manner, after the node of the first blockchain obtains the resource cross-chain display request, store the first signature corresponding to the first target resource data in the light node of the first blockchain, and send the second signature corresponding to the first hash value to the node of the second blockchain;

[0234] The above-mentioned processor 801 is further configured to:

[0235] Obtain the public key, the first signature, and the second signature of the node of the first blockchain;

[0236] Perform a first signature verification process using the public key, the first signature, and the second target resource data. When the first signature verification process passes, perform a second signature verification process using the public key, the second signature, and the first hash value;

[0237] When the second signature verification process passes, execute the step of determining the second hash value of the second target resource data.

[0238] In a specific implementation, the processor 801, the memory 802, and the network interface 803 described in the embodiments of the present application may execute the implementation manners described in the related embodiments of the data management method provided by the embodiments of the present application Figure 2 、 Figure 3 or Figure 4 the implementation manners described in the related embodiments of the data management device provided by the embodiments of the present application, which will not be elaborated herein. Figure 6 or Figure 7 The implementation manners described in the related embodiments of the present application will not be elaborated herein.

[0239] In several embodiments provided by the present application, it should be understood that the disclosed methods, devices, and systems can be implemented in other ways. For example, the device embodiments described above are only illustrative; for example, the division of the units is only a logical function division, and there may be other division methods in actual implementation; for example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point, the displayed or discussed mutual coupling or direct coupling or communication connection may be through some interfaces, and the indirect coupling or communication connection of the device or unit may be in an electrical, mechanical or other form.

[0240] An embodiment of the present application also provides a computer-readable storage medium, in which program instructions are stored, and when the program is executed, it may include some or all of the steps of the blockchain-based data management method in the above embodiment.

[0241] It should be noted that, for the foregoing method embodiments, for the sake of simple description, they are all expressed as a series of action combinations. However, those skilled in the art should know that the present application is not limited by the described action sequence, because according to the present application, some steps can be performed in other sequences or simultaneously. Secondly, those skilled in the art should also know that the embodiments described in the specification are all preferred embodiments, and the actions and modules involved are not necessarily essential to the present application.

[0242] In the embodiments of the present application, the term "module" or "unit" refers to a computer program with a predetermined function or a part of a computer program, which works together with other related parts to achieve a predetermined goal, and can be fully or partially implemented by using software, hardware (such as a processing circuit or a memory), or a combination thereof. Similarly, one processor (or multiple processors or memories) can be used to implement one or more modules or units. In addition, each module or unit can be a part of the overall module or unit that includes the function of the module or unit.

[0243] It should be noted that the descriptions such as "first" and "second" involved in the embodiments of the present application are only for descriptive purposes, and cannot be understood as indicating or implying their relative importance or implicitly indicating the quantity of the indicated technical features. Therefore, the technical features defined with "first" and "second" may explicitly or implicitly include at least one of the features.

[0244] Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above embodiments can be completed by instructing relevant hardware through a program, and the program can be stored in a computer-readable storage medium. The storage medium may include: a flash drive, a read-only memory (ROM), a random access memory (RAM), a magnetic disk, or an optical disc, etc.

[0245] An embodiment of the present application also provides a computer program product, which includes a computer program or computer instructions, and the computer program or computer instructions are stored in a computer-readable storage medium. The processor of the server reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, so that the server executes the steps performed in the above method embodiments.

[0246] The above has introduced in detail a blockchain-based data management method, apparatus, device, and medium provided by the embodiments of the present application. Specific examples are used herein to elaborate on the principles and implementation manners of the present application. The description of the above embodiments is only used to help understand the method and its core idea of the present application; at the same time, for those of ordinary skill in the art, according to the idea of the present application, there will be changes in the specific implementation manners and application scopes. In summary, the content of this specification should not be construed as a limitation on the present application.

Claims

1. A data management method based on blockchain, characterized in that: Applied to a node of a first blockchain, the method comprises: Obtain a resource cross-chain display request; the resource cross-chain display request carries a resource identifier and a blockchain identifier; In response to the resource cross-chain display request, obtain first target resource data corresponding to the resource identifier, and determine a first hash value of the first target resource data; The first hash value and the resource identifier are sent to a node of a second blockchain corresponding to the blockchain identifier, so that the node of the second blockchain obtains the second target resource data corresponding to the resource identifier from the first blockchain and determines a second hash value of the second target resource data. When the first hash value matches the second hash value, the second target resource data is displayed in a client of the second blockchain.

2. The method according to claim 1, characterized in that The method further comprises: Determine the request initiating object corresponding to the resource cross-chain display request, and obtain the authorization binding information of the request initiating object; If the authorization binding information indicates that there is a binding relationship between the second blockchain and the request initiating object, the step of obtaining the first target resource data corresponding to the resource identifier is performed.

3. The method according to claim 2, characterized in that The method further comprises: If the authorization binding information indicates that there is no binding relationship between the second blockchain and the request initiating object, starting the client of the second blockchain so that the request initiating object performs an authorization binding operation through the client of the second blockchain; Receiving an authorization binding request for the authorization binding operation returned by the client of the second blockchain; In response to the authorization binding request, the binding relationship between the second blockchain and the request initiating object is added to the authorization binding information, and the step of obtaining the first target resource data corresponding to the resource identifier is performed.

4. The method according to claim 3, characterized in that The obtaining the authorization binding information of the request initiating object includes: Obtain one or more candidate authorization credentials corresponding to the request initiator from the first blockchain; the candidate authorization credentials are generated by the node of the first blockchain when responding to the authorization binding request returned by the client of any blockchain and uploaded to the first blockchain; Determine a target authorization credential from the one or more candidate authorization credentials; the on-chain time of the target authorization credential is later than the on-chain time of other candidate authorization credentials in the one or more candidate authorization credentials; The authorization binding information of the request initiating object is determined from the target authorization credential.

5. The method according to claim 4, characterized in that The adding the binding relationship between the second blockchain and the request initiating object to the authorization binding information includes: Generate a binding record according to the binding relationship between the second blockchain and the request initiating object; Adding the binding record to the target authorization credential to obtain an updated target authorization credential; The updated target authorization certificate is chained to the first blockchain; the updated target authorization certificate on the first blockchain includes the updated authorization binding information.

6. The method according to any one of claims 2 to 5, characterized in that: The method further comprises: Storing the first target resource data in the light node of the first blockchain, so that the node of the second blockchain obtains the second target resource data corresponding to the resource identifier from the light node of the first blockchain; Among them, when the light node of the first blockchain receives the data acquisition request for the second target resource data from the node of the second blockchain, it obtains the authorization binding information of the request initiating object; if the authorization binding information indicates that the second blockchain has a binding relationship with the request initiating object, the first target resource data corresponding to the resource identifier is sent to the node of the second blockchain.

7. A data management method based on blockchain, characterized in that: Applied to a node of a second blockchain, the method comprises: Receive a first hash value and a resource identifier sent by a node of the first blockchain in response to a resource cross-chain display request; the resource cross-chain display request carries the resource identifier and the blockchain identifier, the first hash value is generated by the node of the first blockchain according to the first target resource data corresponding to the resource identifier, and the blockchain identifier matches the second blockchain; Obtaining second target resource data corresponding to the resource identifier from the first blockchain, and determining a second hash value of the second target resource data; matching the first Hash value with the second Hash value; When the first hash value matches the second hash value, the second target resource data is displayed in the client of the second blockchain.

8. The method according to claim 7, characterized in that After the node of the first blockchain obtains the resource cross-chain display request, the node stores the first target resource data in the light node of the first blockchain; The obtaining, from the first blockchain, second target resource data corresponding to the resource identifier includes: Sending a data acquisition request for the second target resource data corresponding to the resource identifier to the light node of the first blockchain, so that the light node of the first blockchain responds to the data acquisition request, obtains the authorization binding information of the request initiating object corresponding to the resource cross-chain display request, and analyzes the binding relationship included in the authorization binding information to obtain an analysis result; Receive the first target resource data corresponding to the resource identifier returned by the light node of the first blockchain to determine that the second target resource data corresponding to the resource identifier is obtained; the first target resource data is sent by the light node of the first blockchain when the analysis result indicates that the authorization binding information includes the binding relationship between the second blockchain and the request initiating object.

9. The method according to claim 8, characterized in that After the node of the first blockchain obtains the resource cross-chain display request, the node stores the first signature corresponding to the first target resource data to the light node of the first blockchain, and sends the second signature corresponding to the first hash value to the node of the second blockchain; Wherein, the method further comprises: Obtaining a public key of a node of the first blockchain, the first signature, and the second signature; Performing a first signature verification process using the public key, the first signature, and the second target resource data, and when the first signature verification process passes, performing a second signature verification process using the public key, the second signature, and the first hash value; When the second signature verification process passes, the step of determining a second hash value of the second target resource data is performed.

10. A data management device based on blockchain, characterized in that: The device includes a module for implementing the blockchain-based data management method as described in any one of claims 1-6, or includes a module for implementing the blockchain-based data management method as described in any one of claims 7-9.

11. A computing device, characterized in that: The invention comprises a processor, a memory and a network interface, wherein the processor, the memory and the network interface are interconnected, wherein the memory is used to store a computer program, and the computer program comprises program instructions, and the processor is configured to call the program instructions to implement the blockchain-based data management method as described in any one of claims 1 to 6, or to implement the blockchain-based data management method as described in any one of claims 7 to 9.

12. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program, which includes program instructions. When the program instructions are executed by a processor, a computing device having the processor implements the blockchain-based data management method as described in any one of claims 1 to 6, or implements the blockchain-based data management method as described in any one of claims 7 to 9.

13. A computer program product, characterized in that The computer program product includes a computer program or computer instructions. When the computer program or computer instructions are executed by a processor, the blockchain-based data management method as described in any one of claims 1 to 6 is implemented, or the blockchain-based data management method as described in any one of claims 7 to 9 is implemented.

Images