Electronic asset ownership confirmation processing methods, devices, electronic equipment and storage media

Abstract

This application provides a method, apparatus, electronic device, and storage medium for processing electronic asset ownership confirmation business. The method includes: first, obtaining an electronic asset ownership confirmation business processing request, which carries multiple electronic assets and the identity information of the corresponding owners for each electronic asset; then, determining a unique identifier for each electronic asset; then, generating a List collection using the unique identifiers and owner identity information for each electronic asset; then, generating a byte array by converting each object in the List collection into elements of a byte array; then, compressing the byte array using the Fan compression algorithm to obtain a compressed package; and finally, uploading the compressed package to the blockchain used for ownership confirmation by calling the Polkadot JS API. Therefore, this method only requires a single call to the Polkadot JS API to complete the data upload for multiple electronic assets, thus improving efficiency compared to existing technologies.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and more specifically, to methods, apparatus, electronic devices, and storage media for processing electronic asset ownership confirmation business. Background Technology

[0002] With the continuous development of internet technology, an increasing number of electronic assets have emerged, including ownership of images and online copyrights. It is often necessary to determine the ownership of these electronic assets, thus giving rise to rights confirmation platforms. Users can typically upload their electronic assets to the rights confirmation platform in advance, which then processes the rights confirmation process. This includes uploading relevant information about the electronic assets to a blockchain used for rights confirmation. Subsequently, during the rights confirmation process, the relevant information stored on the blockchain can be used to confirm the ownership of the electronic assets.

[0003] Currently, asset ownership confirmation platforms typically upload relevant information about digital assets to the blockchain by calling the Polkadot JS API. However, due to its inherent characteristics, the Polkadot JS API can only upload information for one digital asset at a time. Therefore, when processing ownership confirmation for multiple digital assets, it is necessary to call the Polkadot JS API multiple times to upload the relevant information for each digital asset to the blockchain separately, resulting in low efficiency. Summary of the Invention

[0004] The purpose of this application is to provide a method, apparatus, electronic device, and storage medium for processing electronic asset ownership confirmation business, in order to solve the problems in the prior art.

[0005] The first aspect of this application provides a method for processing electronic asset ownership confirmation business, including:

[0006] Obtain an electronic asset ownership confirmation business processing request, wherein the electronic asset ownership confirmation business processing request carries multiple electronic assets and the identity information of the owner corresponding to each electronic asset;

[0007] Determine a unique identifier for each electronic asset;

[0008] A List collection is generated using the unique identifier and owner identity information corresponding to each electronic asset, wherein each object in the List collection is the unique identifier and owner identity information of the corresponding electronic asset.

[0009] A byte array is generated by converting each object in the List collection into an element of a byte array.

[0010] The byte array is compressed using the Fan compression algorithm to obtain a compressed package;

[0011] The compressed package is uploaded to the blockchain used for rights confirmation by calling the Polkadot JS API.

[0012] In one embodiment, the compressed package includes compressed data and a data offset; and the method further includes:

[0013] The blockchain uses the data offset to decompress the compressed data to obtain the byte array;

[0014] The List collection is regenerated using the byte array;

[0015] For each object in the List collection, determine whether the electronic asset meets the preset rights confirmation conditions based on the unique identifier of the electronic asset corresponding to the object and the identity information of the owner;

[0016] If the electronic asset meets the preset rights confirmation conditions, the unique identifier and ownership information of the electronic asset will be stored in the blockchain; or,

[0017] If the electronic asset does not meet the preset rights confirmation conditions, the unique identifier and owner's identity information of the electronic asset will not be stored in the blockchain.

[0018] In one embodiment, if the electronic asset does not meet the preset ownership conditions, the method further includes: recording the file name of the electronic asset in a hash table.

[0019] In one embodiment, the method further includes: sending the hash table back to the client.

[0020] In one embodiment, obtaining an electronic asset ownership confirmation business processing request specifically includes: obtaining the electronic asset ownership confirmation business processing request sent by the client from the message queue.

[0021] In one embodiment, determining the unique identifier corresponding to each electronic asset specifically includes: determining the unique identifier corresponding to each electronic asset through the distributed file system IPFS.

[0022] A second aspect of this application provides an electronic asset ownership confirmation processing device, comprising:

[0023] The request acquisition unit acquires an electronic asset ownership confirmation business processing request, which carries multiple electronic assets and the identity information of the owner corresponding to each electronic asset.

[0024] The identifier determination unit is used to determine the unique identifier corresponding to each electronic asset.

[0025] The collection generation unit is used to generate a List collection by using the unique identifier and owner identity information corresponding to each electronic asset, wherein each object in the List collection is the unique identifier and owner identity information of the corresponding electronic asset;

[0026] The array generation unit is used to generate a byte array by converting each object in the List collection into an element of a byte array.

[0027] A compression unit is used to compress the byte array using the Fan compression algorithm to obtain a compressed package;

[0028] The upload unit is used to upload the compressed package to the blockchain used for rights confirmation by calling the Polkadot JS API.

[0029] In one embodiment, the compressed package includes compressed data and a data offset; and the apparatus further includes:

[0030] A decompression unit is used by the blockchain to decompress the compressed data using the data offset to obtain the byte array;

[0031] The second set generation unit is used to regenerate the List set using the byte array;

[0032] The judgment unit is used to determine, for each object in the List collection, whether the electronic asset meets the preset rights confirmation conditions based on the unique identifier of the electronic asset corresponding to the object and the identity information of the owner;

[0033] A storage unit is configured to store the unique identifier and owner's identity information of the electronic asset in the blockchain when the electronic asset meets the preset ownership confirmation conditions; or, if the electronic asset does not meet the preset ownership confirmation conditions, not store the unique identifier and owner's identity information of the electronic asset in the blockchain.

[0034] A third aspect of this application provides an electronic device, including:

[0035] Memory, used to store computer programs;

[0036] A processor for executing the method described in any one of the embodiments of the present application.

[0037] A fourth aspect of this application provides a storage medium comprising: a program, which, when run on an electronic device, enables the electronic device to execute any method described in any of the method embodiments of this application.

[0038] The electronic asset ownership confirmation process method provided in this application first obtains an electronic asset ownership confirmation request. This request carries multiple electronic assets and the identity information of the corresponding owners for each electronic asset. Then, a unique identifier is determined for each electronic asset. A List collection is then generated using the unique identifier and owner information of each electronic asset. Each object in this List collection represents the unique identifier and owner information of the corresponding electronic asset. A byte array is then generated by converting each object in the List collection into an element of a byte array. This byte array is then compressed using the Fan compression algorithm to obtain a compressed package. Finally, the compressed package is uploaded to the blockchain used for ownership confirmation by calling the Polkadot JS API. Therefore, this method only requires a single call to the Polkadot JS API to complete the data upload for multiple electronic assets, which improves efficiency compared to existing technologies. Attached Figure Description

[0039] To more clearly illustrate the technical solutions of the embodiments of this application, the accompanying drawings used in the embodiments of this application will be briefly introduced below. It should be understood that the following drawings only show some embodiments of this application and should not be regarded as a limitation of the scope. For those skilled in the art, other related drawings can be obtained based on these drawings without creative effort.

[0040] Figure 1 A schematic diagram of the specific structure of an electronic device provided in an embodiment of this application;

[0041] Figure 2 A schematic diagram illustrating the interaction between an electronic device and a terminal, provided as an embodiment of this application;

[0042] Figure 3 A schematic diagram of the specific process of electronic asset ownership confirmation business provided for an embodiment of this application;

[0043] Figure 4 This is a schematic diagram of the specific structure of an electronic asset ownership confirmation processing device provided in an embodiment of this application. Detailed Implementation

[0044] The technical solutions of the embodiments of this application will now be described with reference to the accompanying drawings. In the description of this application, terms such as "first," "second," and "third" are used only for distinguishing descriptions and should not be construed as indicating or implying relative importance or order.

[0045] As mentioned earlier, current rights confirmation platforms typically upload information about digital assets to the blockchain by calling the Polkadot JS API. However, due to its inherent characteristics, the Polkadot JS API can only upload information for one digital asset at a time. Therefore, when processing rights confirmation for multiple digital assets, it is necessary to call the Polkadot JS API multiple times to upload the information for each digital asset to the blockchain separately, resulting in low efficiency.

[0046] In view of this, embodiments of this application provide a method, apparatus, electronic device, and storage medium for processing electronic asset ownership confirmation business, which can be used to process ownership confirmation business for multiple electronic assets in batches, thereby improving efficiency. Figure 1 The image shows an electronic device 1 provided in this embodiment. The electronic device 1 includes at least one processor 11 and a memory 12. Figure 1 Taking a processor as an example, the processor 11 and memory 12 can be connected via bus 10. The memory 12 stores instructions that can be executed by the processor 11. The instructions are executed by the processor 11 to enable the electronic device 1 to perform all or part of the processes of the methods in the embodiments described below. In practical applications, the electronic device 1 can be a laptop computer, a desktop computer, a server composed of such computers, or a server cluster, etc.

[0047] like Figure 2 As shown, electronic device 1, acting as the server of the rights confirmation platform, can also connect to one or more clients 2. In this case, electronic device 1 can communicate with each client 2 separately. The terminal can be a user's mobile phone, laptop, desktop computer, etc. In one embodiment, when a user needs to upload multiple electronic assets to the rights confirmation platform, they can send an electronic asset rights confirmation service processing request to electronic device 1 through client 2.

[0048] like Figure 3 The diagram shown is a flowchart illustrating an electronic asset ownership confirmation process according to an embodiment of this application. Some or all of the steps in this method can be performed by… Figure 1 The electronic device 1 shown acts as the server of the rights confirmation platform, and the method includes the following steps:

[0049] Step S31: Obtain the electronic asset ownership confirmation business processing request, which carries multiple electronic assets and the identity information of the owner corresponding to each electronic asset.

[0050] In practical applications, when a user needs to upload multiple electronic assets to the ownership confirmation platform, they can send an electronic asset ownership confirmation processing request to the server through the client, thereby enabling the server to receive the electronic asset ownership confirmation processing request. Therefore, the method for obtaining the electronic asset ownership confirmation processing request in step S31 can be that the server directly receives the electronic asset ownership confirmation processing request sent by the user through the client.

[0051] It should be noted that since the server is usually connected to multiple clients, if multiple different users send electronic asset ownership confirmation requests to the server through multiple clients in a short period of time, the server may receive multiple electronic asset ownership confirmation requests in a short period of time, which will greatly increase the computing pressure on the server and affect the operation of the server.

[0052] Therefore, in one embodiment, a message queue can be pre-built, such as a Kafka message queue. Electronic asset ownership confirmation requests sent by various clients can be added to this message queue sequentially according to the order of their sending time. The server can then retrieve these requests from the message queue. Compared to the server directly receiving electronic asset ownership confirmation requests sent by users through clients, this method, by first adding the requests to the message queue and then retrieving them from the queue, allows the server to retrieve requests according to its processing efficiency even if multiple different clients send such requests within a short period, thus reducing the server's computational load.

[0053] The electronic asset ownership confirmation business processing request obtained in step S31 carries multiple electronic assets and the identity information of the owner corresponding to each electronic asset. The owner's identity information reflects the owner's identity, such as the owner's name, ID number, user account, IP address on the network, etc.

[0054] Of course, in addition to carrying multiple electronic assets and the identity information of the owners of each electronic asset, the electronic asset ownership confirmation request can usually also carry other information, including the description information of each electronic asset. This description information is used to describe the basic information of the electronic asset, such as the name, purpose, and generation time of the electronic asset.

[0055] Step S32: Determine the unique identifier corresponding to each electronic asset.

[0056] After receiving the electronic asset ownership confirmation business processing request, the server can extract the electronic assets and the identity information of the owners of each electronic asset carried in the electronic asset ownership confirmation business processing request. Then, in step S32, each electronic asset can be used to determine the unique identifier corresponding to each electronic asset. This unique identifier can be used to uniquely represent the corresponding electronic asset. For example, the unique identifier can be the information digest of the corresponding electronic asset. Therefore, one approach is to use a hash algorithm to calculate the information digest of each electronic asset, and then use the calculated information digest as the unique identifier corresponding to the electronic asset.

[0057] Another way to determine the unique identifier for each electronic asset is through the InterPlanetary File System (IPFS). For example, each electronic asset can be uploaded to IPFS, and then IPFS can be used to determine the unique identifier for each electronic asset. Alternatively, IPFS can be pre-built according to relevant specifications, and then used to determine the unique identifier for each electronic asset.

[0058] Step S33: Generate a List collection using the unique identifier and owner information corresponding to each electronic asset.

[0059] In this List collection, each object represents the unique identifier and ownership information of the corresponding electronic asset. For example, after determining the unique identifier for each electronic asset through step S32, in step S33, a List collection can be constructed first. Then, for each electronic asset, its unique identifier and ownership information can be added to the List collection as objects. The List collection can be constructed using relevant functions in the programming languages ​​Rust and TypeScript.

[0060] Step S34: Generate a byte array by converting each object in the List collection into an element of a byte array.

[0061] After generating the List collection through step S33 above, since the List collection in the programming languages ​​Rust and TypeScript is also an array from the underlying data level, we can use an iterator to sequentially obtain each object from the List collection, and add each obtained object as an element in the byte array, and finally generate the required byte array.

[0062] Step S35: Compress the byte array using the Fan compression algorithm to obtain a compressed package.

[0063] The Fan compression algorithm is used to compress the byte array. The resulting compressed package includes compressed data and a data offset. The compressed data is the data obtained by compressing the byte array. The data offset is used to describe the offset of the compressed data relative to the byte array. The compressed data can be decompressed using the data offset to obtain the byte array again.

[0064] In practical applications, since each element in the byte array corresponds to a unique identifier and owner's identity information for each electronic asset, the data volume of the byte array is also large when there are many electronic assets, making it difficult to upload to the blockchain. Therefore, in step S35, the byte array is compressed using the Fan compression algorithm to reduce the amount of data to be uploaded and improve upload efficiency.

[0065] Of course, in practical applications, other compression algorithms besides Fan compression can be used to compress byte arrays, but these compression algorithms are usually insufficient for byte array compression compared to Fan compression. Therefore, in step S35, Fan compression is used for compression.

[0066] Step S36: Upload the compressed package to the blockchain used for rights confirmation by calling the Polkadot JS API.

[0067] After obtaining the compressed package through step S35, in step S36, the compressed package can be uploaded to the blockchain by calling the Polkadot JS API. Specifically, the Polkadot JS API is the API interface in Polkadot JS used for uploading data. Since only the compressed package is being uploaded, only one call to the Polkadot JS API is needed to complete the upload, which improves efficiency compared to existing technologies.

[0068] It should be noted that since a single call to the Polkadot JS API can only upload data to the blockchain once, existing technologies require multiple calls to the Polkadot JS API to upload the relevant information for each electronic asset, resulting in low efficiency. However, the method provided in this application only requires a single call to the Polkadot JS API to complete the upload, thus achieving relatively higher efficiency. Furthermore, since the method involves the unique identifiers and ownership information of multiple electronic assets, the amount of data to be uploaded may be large. The method provided in this application first generates a List collection, then converts it into a byte array, and then uses the Fan compression algorithm to compress it, thereby reducing the amount of data to be uploaded and enabling a quick data upload with a single call to the Polkadot JS API.

[0069] Furthermore, existing technologies require multiple calls to the Polkadot JS API to upload information for each of the multiple electronic assets. This method is not only inefficient, but also suffers from the inherent characteristics of Polkadot JS. Since these multiple consecutive calls are atomic operations, if the upload of any electronic asset fails, the process is rolled back, and the upload attempt restarts from the first electronic asset. In contrast, the method provided in this application only calls the Polkadot JS API once to complete the data upload, significantly reducing the possibility of rollback and thus further improving efficiency.

[0070] Of course, after uploading the compressed package to the blockchain through the above step S36, the method may also include the blockchain performing data storage steps. Specifically, the blockchain may use the data offset in the compressed package to decompress the compressed data in the compressed package to obtain the byte array again, and then use the byte array to regenerate the List collection. For example, the List collection may be regenerated by converting the elements in the byte array back into objects in the List collection.

[0071] After regenerating the List collection, since each object in the List collection represents the unique identifier and owner information of the corresponding electronic asset, it is possible to determine whether each electronic asset meets the preset rights confirmation conditions based on its unique identifier and owner information. These preset rights confirmation conditions may include verifying the legality and completeness of the owner information, the legality of the unique identifier, and the legality of the electronic asset itself. These preset rights confirmation conditions are typically pre-defined based on the type of electronic asset. Thus, if the electronic asset meets the preset rights confirmation conditions, its unique identifier and owner information can be stored on the blockchain; if the electronic asset does not meet the preset rights confirmation conditions, these conditions may not be stored on the blockchain.

[0072] For example, for each object in the List collection, the object can be retrieved in turn, and then the electronic asset can be determined to meet the preset rights confirmation conditions based on the unique identifier of the electronic asset and the identity information of the owner. If it meets the conditions, it is stored in the blockchain; otherwise, it is not stored in the blockchain.

[0073] Additionally, a hash table can be pre-built to record the file name of an electronic asset if it does not meet the preset ownership verification conditions. Furthermore, after determining whether each object in the List collection meets the preset ownership verification conditions, uploading those that meet the conditions to the blockchain and not uploading those that do not, the hash table can be fed back to the client. This allows users to use the hash table to determine which electronic assets failed to upload.

[0074] In practical applications, the blockchain can also be subscribed to via Polkadot JS. After uploading the compressed package to the blockchain used for rights confirmation through step S36 above, the blockchain can send feedback information to Polkadot JS indicating upload failure if it determines that the electronic asset does not meet the preset rights confirmation conditions, based on the unique identifier and owner's identity information of the electronic asset corresponding to the object in the List collection. This will inform which electronic assets failed to upload.

[0075] Based on the same inventive concept as the electronic asset ownership confirmation processing method provided in the embodiments of this application, the embodiments of this application also provide an electronic asset ownership confirmation processing device. For any unclear aspects of this device embodiment, please refer to the corresponding content of the method embodiment. Figure 4The diagram shown illustrates the specific structure of the device 40, which includes: a request acquisition unit 401, an identifier determination unit 402, a set generation unit 403, an array generation unit 404, a compression unit 405, and an upload unit 406, wherein:

[0076] The request acquisition unit 401 acquires an electronic asset ownership confirmation business processing request, which carries multiple electronic assets and the identity information of the owner corresponding to each electronic asset.

[0077] 0 Identifier Determination Unit 402 is used to determine the unique identifier corresponding to each electronic asset;

[0078] The collection generation unit 403 is used to generate a List collection by using the unique identifier and owner identity information corresponding to each electronic asset, wherein each object in the List collection is the unique identifier and owner identity information of the corresponding electronic asset;

[0079] The array generation unit 404 is used to generate a byte array by converting each object in the List collection into an element of a byte array.

[0080] Compression unit 405 is used to compress the byte array using the Fan compression algorithm to obtain a compressed package;

[0081] Upload unit 406 is used to upload the compressed package to the blockchain used for rights confirmation by calling the Polkadot JS API.

[0082] The device 40 provided in the embodiments of this application adopts the same inventive concept as the electronic asset ownership confirmation business processing method provided in the embodiments of this application. Under the premise that the method can solve the technical problem, the device 40 can also solve the technical problem, which will not be elaborated here.

[0083] Furthermore, in practical applications, the technical effects achieved by combining this device 40 with specific hardware devices, cloud technologies, etc., are also within the scope of protection of this application. For example, the use of distributed systems...

[0084] The different units in the device 40 are deployed in a distributed cluster in a group manner, thereby improving efficiency, etc.

[0085] The compressed package includes compressed data and data offset; and the device 40 may further include: a decompression unit, a second set generation unit, a judgment unit, and a storage unit, wherein:

[0086] A decompression unit is used by the blockchain to decompress the compressed data using the data offset to obtain the byte array;

[0087] The second set generation unit is used to regenerate the List set using the byte array;

[0088] The judgment unit is used to determine, for each object in the List collection, whether the electronic asset meets the preset rights confirmation conditions based on the unique identifier of the electronic asset corresponding to the object and the identity information of the owner;

[0089] A storage unit is configured to store the unique identifier and owner's identity information of the electronic asset in the blockchain when the electronic asset meets the preset ownership confirmation conditions; or, if the electronic asset does not meet the preset ownership confirmation conditions, not store the unique identifier and owner's identity information of the electronic asset in the blockchain.

[0090] If the electronic asset does not meet the preset ownership conditions, the device 40 may further include a recording unit for recording the file name of the electronic asset into a hash table.

[0091] The device 40 may also include a feedback unit for feeding back the hash table to the client.

[0092] The request acquisition unit 401 may specifically include a request acquisition subunit, used to acquire the electronic asset ownership confirmation business processing request sent by the client from the message queue.

[0093] The identifier determination unit 402 may specifically include an identifier determination subunit, which is used to determine the unique identifier corresponding to each electronic asset through the distributed file system IPFS.

[0094] This invention also provides a storage medium, comprising: a program, which, when run on an electronic device, enables the electronic device to execute all or part of the processes of the methods described in the above embodiments. The storage medium may be a disk, optical disk, read-only memory (ROM), random access memory (RAM), flash memory, hard disk drive (HDD), or solid-state drive (SSD), etc. The storage medium may also include combinations of the above types of memory.

[0095] Although embodiments of the invention have been described in conjunction with the accompanying drawings, those skilled in the art can make various modifications and variations without departing from the spirit and scope of the invention, and such modifications and variations all fall within the scope defined by the appended claims.

Claims

1. A method for processing electronic asset ownership confirmation business, characterized in that, include: Obtain an electronic asset ownership confirmation business processing request, wherein the electronic asset ownership confirmation business processing request carries multiple electronic assets and the identity information of the owner corresponding to each electronic asset; Determine a unique identifier for each electronic asset; A List collection is generated using the unique identifier and owner identity information corresponding to each electronic asset, wherein each object in the List collection is the unique identifier and owner identity information of the corresponding electronic asset. A byte array is generated by converting each object in the List collection into an element of a byte array. The byte array is compressed using the Fan compression algorithm to obtain a compressed package; The compressed package is uploaded to the blockchain used for rights confirmation by calling the Polkadot JS API, which is the API interface in Polkadot JS used for uploading data.

2. The method according to claim 1, characterized in that, The compressed package includes compressed data and data offset; and the method further includes: The blockchain uses the data offset to decompress the compressed data to obtain the byte array; The List collection is regenerated using the byte array; For each object in the List collection, determine whether the electronic asset meets the preset rights confirmation conditions based on the unique identifier of the electronic asset corresponding to the object and the identity information of the owner; If the electronic asset meets the preset rights confirmation conditions, the unique identifier and owner's identity information of the electronic asset will be stored in the blockchain, or... If the electronic asset does not meet the preset rights confirmation conditions, the unique identifier and owner's identity information of the electronic asset will not be stored in the blockchain.

3. The method according to claim 2, characterized in that, If the electronic asset does not meet the preset ownership conditions, the method further includes: recording the file name of the electronic asset in a hash table.

4. The method according to claim 3, characterized in that, The method further includes: sending the hash table back to the client.

5. The method according to claim 4, characterized in that, Obtaining the electronic asset ownership confirmation business processing request specifically includes: obtaining the electronic asset ownership confirmation business processing request sent by the client from the message queue.

6. The method according to claim 1, characterized in that, Determine the unique identifier for each electronic asset, specifically by using the distributed file system IPFS to determine the unique identifier for each electronic asset.

7. An electronic asset ownership confirmation processing device, characterized in that, include: The request acquisition unit acquires an electronic asset ownership confirmation business processing request, which carries multiple electronic assets and the identity information of the owner corresponding to each electronic asset. The identifier determination unit is used to determine the unique identifier corresponding to each electronic asset. The collection generation unit is used to generate a List collection by using the unique identifier and owner identity information corresponding to each electronic asset, wherein each object in the List collection is the unique identifier and owner identity information of the corresponding electronic asset; The array generation unit is used to generate a byte array by converting each object in the List collection into an element of a byte array. A compression unit is used to compress the byte array using the Fan compression algorithm to obtain a compressed package; The upload unit is used to upload the compressed package to the blockchain used for rights confirmation by calling the Polkadot JS API, wherein the Polkadot JS API is the API interface in Polkadot JS used for uploading data.

8. The apparatus according to claim 7, characterized in that, The compressed package includes compressed data and data offset; and the device further includes: A decompression unit is used by the blockchain to decompress the compressed data using the data offset to obtain the byte array; The second set generation unit is used to regenerate the List set using the byte array; The judgment unit is used to determine, for each object in the List collection, whether the electronic asset meets the preset rights confirmation conditions based on the unique identifier of the electronic asset corresponding to the object and the identity information of the owner; The storage unit is used to store the unique identifier and owner's identity information of the electronic asset to the blockchain when the electronic asset meets the preset ownership confirmation conditions, or not to store the unique identifier and owner's identity information of the electronic asset to the blockchain when the electronic asset does not meet the preset ownership confirmation conditions.

9. An electronic device, characterized in that, include: Memory, used to store computer programs; A processor for performing the method as described in any one of claims 1 to 6.

10. A storage medium, characterized in that, Includes: a program that, when run on an electronic device, enables the electronic device to perform the method as described in any one of claims 1 to 6.

Images