Blockchain-based asset management method, system, electronic device and storage medium

Abstract

This application provides a blockchain-based asset management method, system, electronic device, and storage medium. The method binds a first non-fungible token (NFT) corresponding to the target user, a second NFT in the target virtual scenario, and a third NFT corresponding to the information of each digital asset of the target virtual avatar. The first NFT used for identity authentication and the third NFT used for virtual avatar asset management in the virtual scenario are combined to form a composable NFT. This allows the user to associate and manage multiple digital assets of their corresponding digital avatar in the virtual scenario in a unified manner.

Description

Technical Field

[0001] This application relates to the field of Internet technology, and in particular to a blockchain-based asset management method, system, electronic device, and storage medium. Background Technology

[0002] Non-fungible tokens (NFTs) are tokenized digital or real-world assets, possessing the characteristics of being non-fungible and indivisible. They are currently used in fields such as art collection, game items, domain names, identity authentication, copyright, and leasing. NFTs are issued on the blockchain and used to designate ownership of specific assets. Each NFT is associated with some unique data, typically some kind of digital content file (or a reference to it), and is managed by smart contracts.

[0003] Blockchain has three key characteristics: multi-party maintenance, immutability, and openness and transparency. It is a system that enables multiple people / things with little or no trust to collaborate according to established consensus rules, making it a good choice for establishing a distributed identity authentication system.

[0004] However, blockchain-based distributed identity systems have some unresolved issues: applicability, private key management (loss), and most blockchain identity authentication systems store data in third-party systems (e.g., wallets storing information are located in the memory of computers or servers).

[0005] Currently, some applications use ERC-721-based non-fungible tokens for identity verification. The ERC-721 protocol is the de facto standard for generating non-fungible tokens on the Ethereum blockchain and other blockchains. However, because ERC-721-based tokens can only be mapped to individual items (identities) and cannot be associated with other items (identities), it is impossible to associate and manage multiple digital avatars (corresponding accounts) of a real user existing in multiple virtual scenarios (metaverses). Summary of the Invention

[0006] To address the aforementioned issues, this application provides a blockchain-based asset management method, system, electronic device, and storage medium, which solves the technical problem in the prior art that a single user cannot manage multiple digital assets of multiple digital avatars.

[0007] In a first aspect, this application provides a blockchain-based asset management method, wherein the blockchain is configured with at least one user account and at least one virtual scenario account, the virtual scenario including at least one virtual avatar, and the method includes:

[0008] Receive non-fungible token requests from target users;

[0009] Based on the non-fungible token request, obtain the target user's identity authentication information;

[0010] Based on the target user's identity authentication information, a corresponding first non-fungible token is generated;

[0011] Based on the first non-fungible token of the target user, a second non-fungible token corresponding to the target virtual scene is generated; wherein, the target virtual scene includes a target virtual avatar corresponding to the target user;

[0012] Based on the second non-fungible token, obtain information on at least one digital asset corresponding to the target virtual avatar in the target virtual scene;

[0013] Based on the information of the at least one digital asset, a third non-fungible token is generated corresponding to the information of each digital asset of the target virtual avatar, and the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene, and the third non-fungible token are bound together.

[0014] According to an embodiment of this application, optionally, in the above-described blockchain-based asset management method, before the step of generating a corresponding first non-fungible token based on the target user's identity authentication information, the method further includes:

[0015] Based on the target user's identity authentication information, a public key and a private key pair are generated, and a wallet address is generated using the public key;

[0016] Bind the target user's identity authentication information to the wallet address;

[0017] The first non-fungible token is associated with the wallet address.

[0018] According to an embodiment of this application, optionally, in the above-described blockchain-based asset management method, the first non-fungible token, the second non-fungible token, and the third non-fungible token are encrypted using the private key.

[0019] According to an embodiment of this application, optionally, in the above-described blockchain-based asset management method, after the step of generating a corresponding first non-fungible token based on the target user's identity authentication information, the method further includes:

[0020] Based on the target user's identity authentication information, a verifiable credential is generated.

[0021] According to embodiments of this application, optionally, the above-described blockchain-based asset management method further includes:

[0022] Receive the target user's asset query request;

[0023] The asset query request and the verifiable credential are sent to the target virtual scene through the first non-fungible token, so that the target virtual scene can verify the verifiable credential;

[0024] When the first non-fungible token receives the verification result for the verifiable credential from the target virtual scene, it sends the public key and the asset information to be queried to the target virtual scene through the first non-fungible token.

[0025] The target virtual scene uses the received public key to decode the third non-fungible token of the asset to be queried, so as to read the information of the third non-fungible token of the asset to be queried.

[0026] According to embodiments of this application, optionally, the above-described blockchain-based asset management method further includes:

[0027] Receive owner query requests for the target digital assets in the target virtual scene;

[0028] Based on the query requests from all the parties, the third non-fungible token corresponding to the target digital asset is determined;

[0029] Based on the third non-fungible token corresponding to the target digital asset, sequentially search for the second non-fungible token and the first non-fungible token corresponding to the target digital asset;

[0030] Based on the binding relationship between the target user's identity authentication information and the wallet address, the identity information of the target user corresponding to the target digital asset is determined through the wallet address corresponding to the first non-fungible token, so as to obtain the identity authentication information of the owner of the target digital asset.

[0031] According to embodiments of this application, optionally, the above-described blockchain-based asset management method further includes:

[0032] Receive an asset transfer request sent by the target user for the target digital asset in the target virtual scene;

[0033] According to the asset transfer request, the third non-fungible token corresponding to the target digital asset is transferred to the second non-fungible token corresponding to another virtual scene, so as to transfer the target digital asset to the other virtual scene.

[0034] Secondly, this application provides a blockchain-based asset management device, the device comprising:

[0035] The receiving module is used to receive non-fungible token requests from target users;

[0036] The identity authentication module is used to obtain the user's identity authentication information based on the non-fungible token request;

[0037] The first creation module is used to generate a corresponding first non-fungible token based on the user's identity authentication information;

[0038] The second creation module is used to generate a second non-fungible token for the user in the target virtual scene based on the user's first non-fungible token.

[0039] The asset acquisition module is used to acquire at least one digital asset information corresponding to the user's target virtual avatar in the target virtual scene based on the second non-fungible token.

[0040] The third creation module is used to generate at least one third non-fungible token corresponding to the information of each digital asset of the target virtual avatar based on the information of the at least one digital asset, and to bind the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene and the third non-fungible token.

[0041] Thirdly, this application provides a blockchain-based asset management system, characterized in that it includes:

[0042] Blockchain;

[0043] At least one user's account is set up on the blockchain;

[0044] At least one account for a virtual scenario is set up on the blockchain; wherein each virtual scenario includes at least one virtual avatar, each virtual avatar has at least one digital asset, and each user corresponds to at least one virtual avatar;

[0045] The first non-fungible token corresponds one-to-one with the user;

[0046] The second non-fungible token is bound to the first non-fungible token and corresponds one-to-one with the virtual scene;

[0047] The third non-fungible token is bound to the second non-fungible token and corresponds one-to-one with the digital asset.

[0048] Fourthly, this application provides an electronic device, characterized in that it includes a memory and a controller, wherein the memory stores a program that, when executed by the controller, performs a blockchain-based asset management method as described in any one of the first aspects.

[0049] Fifthly, this application provides a storage medium storing a computer program that can be executed by one or more processors and can be used to implement the blockchain-based asset management method as described in any of the first aspects.

[0050] Compared with the prior art, one or more embodiments of the above solutions may have the following advantages or beneficial effects:

[0051] This application provides a blockchain-based asset management method, system, electronic device, and storage medium. The method includes generating a first non-fungible token (NFT) based on the identity authentication information of a target user; generating a second NFT corresponding to a target virtual scene based on the first NFT of the target user; wherein the target virtual scene includes a target virtual avatar corresponding to the target user; obtaining information on at least one digital asset corresponding to the target virtual avatar in the target virtual scene based on the second NFT; generating a third NFT corresponding to the information of each digital asset of the target virtual avatar based on the information of the at least one digital asset; and binding the first NFT corresponding to the target user, the second NFT in the target virtual scene, and the third NFT. The first non-fungible token (root NFT) used for identity authentication, the second non-fungible token (bulk NFT) used for all assets of a corresponding user in a virtual scenario (metaverse), and the third non-fungible token (sub-NFT) used for a single digital asset in the corresponding virtual scenario (metaverse) are combined to form a composable non-fungible token. This allows users to associate and manage multiple digital assets of their digital avatar in the corresponding virtual scenario in a unified manner. Attached Figure Description

[0052] The present application will be described in more detail below based on embodiments and with reference to the accompanying drawings:

[0053] Figure 1 A schematic diagram of the structure of a blockchain-based asset management system provided in this application embodiment;

[0054] Figure 2 A flowchart illustrating a blockchain-based asset management method provided in this application embodiment;

[0055] Figure 3Another schematic diagram of a blockchain-based asset management method provided for an embodiment of this application;

[0056] Figure 4 Another schematic diagram of a blockchain-based asset management method provided for an embodiment of this application;

[0057] Figure 5 A schematic diagram of the structure of a blockchain-based asset management device provided in this application embodiment;

[0058] In the accompanying drawings, the same parts are referred to by the same reference numerals, and the drawings are not drawn to scale. Detailed Implementation

[0059] The following detailed description of the embodiments of this application, in conjunction with the accompanying drawings, will provide a thorough understanding of how this application uses technical means to solve technical problems and achieve corresponding technical effects, enabling its implementation. The embodiments of this application and the various features within them can be combined with each other without conflict, and all resulting technical solutions are within the protection scope of this application.

[0060] Furthermore, numerous specific details are set forth in the following description for purposes of explanation, in order to provide a thorough understanding of the embodiments of the invention. However, it will be apparent to those skilled in the art that the invention may be practiced without the specific details herein or the particular methods described.

[0061] Before blockchain, the identity federation stored trust certificates from multiple Certificate Service Providers (CSPs) for users and selected the appropriate certificate when logging into different online services. Users registered once with their chosen CSP, generating an online trust certificate managed by the CSP for identity authentication. When a user wished to access another service provider, they were redirected to their preferred CSP to authenticate using the aforementioned certificate. The CSP then displayed the authentication status to the currently accessing service provider, and the user was granted access to the corresponding service.

[0062] The ERC-721 standard defines the minimum interface that a smart contract must implement, which includes token-related management, holding, and trading functions, such as token name, identifier, symbol, total token supply, balance of a specific token, querying the owner of a token, approving the acquisition of ownership, ownership transfer, and obtaining token metadata.

[0063] Example 1

[0064] Figure 1The schematic diagram of a blockchain-based asset management system provided in this application embodiment includes: a blockchain 10, at least one user account 30, at least one virtual scene account 40, a first non-fungible token, a second non-fungible token, and a third non-fungible token.

[0065] At least one user account 30 and at least one virtual scenario account 40 are set on the blockchain 10.

[0066] Blockchain 10 packages multiple transaction data and hashes their contents together with the hash value of the previous block on the chain to generate a new block, thereby constructing and maintaining an immutable distributed ledger. It stores at least one user's account 30 and at least one virtual scenario (i.e., the metaverse) account 40.

[0067] Each virtual scene includes at least one virtual avatar, each virtual avatar has at least one digital asset, and each user corresponds to at least one of the virtual avatars. That is, the virtual avatar can be understood as a digital avatar of a user in the virtual scene, such as a digital avatar of a user in virtual scenes using virtual reality technology (virtual reality (VR), augmented reality (AR), mixed reality (MR) and extended reality (XR)), game technology (game engine, game code, multimedia resources), and AI artificial intelligence technology.

[0068] In this embodiment, the first non-fungible token, the second non-fungible token, and the third non-fungible token are all non-fungible tokens (NFTs) generated based on Blockchain 10.

[0069] The first nonfungible token, the second nonfungible token, and the third nonfungible token constitute a composable nonfungible token 20.

[0070] The first non-fungible token corresponds to the user's account, and there is a one-to-one correspondence between the first non-fungible token and the user.

[0071] The second non-fungible token corresponds to an account in the virtual scenario, and there is a one-to-one correspondence between the second non-fungible token and the virtual scenario. The second non-fungible token is bound to the first non-fungible token. This can be understood as the owner of the second non-fungible token being the first non-fungible token.

[0072] The third non-fungible token (NFT) corresponds to the digital asset of a virtual avatar in the virtual scenario, with a one-to-one correspondence between the third NFT and the digital asset of the virtual avatar. The third NFT is bound to the second NFT. This can be understood as the owner of the third NFT being the second NFT. The third NFT conforms to the ERC-721 standard.

[0073] The digital assets mentioned above can be understood as the digital assets of a user's digital identity in virtual scenarios such as virtual reality technology (virtual reality (VR), augmented reality (AR), mixed reality (MR) and extended reality (XR)), game technology (game engine, game code, multimedia resources) and AI artificial intelligence technology, such as digital assets like the skin of a game character.

[0074] The first nonfungible token is used to store and manage real user identities.

[0075] The third non-fungible token represents the user's digital identity and digital assets in a virtual scenario (metaverse).

[0076] Furthermore, since a user can have digital avatars in multiple virtual scenarios, one first non-fungible token can correspond to multiple second non-fungible tokens. And since a user's digital avatar in a virtual scenario can have multiple digital assets, one second non-fungible token can correspond to multiple third non-fungible tokens.

[0077] Therefore, the first non-fungible token can be seen as the root NFT, the second non-fungible token can be seen as a batch of asset NFTs, and the third non-fungible token can be seen as a single asset NFT (sub-NFT). The corresponding NFT distribution structure diagram is shown below. Figure 1 As shown.

[0078] The parent node of the third nonfungible token (individual asset NFT) points to the second nonfungible token (bulk asset NFT), and the parent node of the second nonfungible token (bulk asset NFT) points to the first nonfungible token (root NFT).

[0079] A first non-fungible token (root NFT) can be associated with one or more third non-fungible tokens (individual asset NFTs). The first non-fungible token (root NFT) can be viewed as a composable non-fungible token, representing a user's total assets across multiple virtual scenarios. The first non-fungible token (root NFT) is used to store and manage the real user's identity, while the third non-fungible tokens (individual asset NFTs) represent the user's digital identity and digital identity assets in the metaverse.

[0080] The second type of non-fungible token (bulk asset NFT) is also a composable non-fungible token that represents all or a single asset of a user in a virtual scenario (metaverse).

[0081] By using a first non-fungible token (root NFT), a second non-fungible token (bulk asset NFT), and a third non-fungible token (sub-NFT), the association and unified management of digital assets are achieved, enhancing the user experience.

[0082] This application provides a blockchain-based asset management system, comprising: a blockchain 10, at least one user account 30, at least one virtual scenario account 40, a first non-fungible token (NFT), a second NFT, and a third NFT. The first NFT (root NFT) used for identity authentication, the second NFT (batch NFT) used for all assets of the corresponding user in a virtual scenario (metaverse), and the third NFT (sub-NFT) used for a single digital asset in the corresponding virtual scenario (metaverse) are combined to form a composable NFT. This allows users to associate and manage multiple digital assets of their digital avatars in their corresponding virtual scenarios in a unified manner.

[0083] Example 2

[0084] Figure 2 This is a flowchart illustrating a blockchain-based asset management method provided in an embodiment of this application. The blockchain is configured with at least one user account and at least one virtual scenario account, and the virtual scenario includes at least one virtual avatar.

[0085] Please see Figure 2 This embodiment provides a blockchain-based asset management method, including:

[0086] Step S110: Receive nonfungible token requests from the target user.

[0087] The fungible token request is initiated by the target user through their account on the blockchain.

[0088] Step S120: Obtain the identity authentication information of the target user based on the non-fungible token request.

[0089] This can be understood as meaning that only certified and legitimate users can proceed with the subsequent steps, and the user's identity verification information may include ID card information.

[0090] Step S130: Generate a corresponding first non-fungible token based on the identity authentication information of the target user.

[0091] This can be understood as the first non-fungible token corresponding to the user's account, with each user having a one-to-one correspondence between the first non-fungible token and the user.

[0092] In some cases, the following steps are included before step S130:

[0093] S122: Generate a public key and a private key pair based on the target user's identity authentication information, and generate a wallet address using the public key;

[0094] S124: Bind the target user's identity authentication information to the wallet address; wherein, the first non-fungible token is associated with the wallet address.

[0095] Each digital wallet has a wallet address, which uniquely identifies the wallet on the blockchain. The address is generated by calculating the public key, similar to a bank card number.

[0096] The user's identity authentication information is bound to their wallet address. Users can make transactions through their wallets, such as generating tokens, making payments, transferring funds, purchasing, and trading.

[0097] This can be understood as the blockchain storing the user's real identity and its mapping relationship with the wallet address, and the first non-fungible token is used to store and manage the real user identity.

[0098] The private key is held by the key pair owner and cannot be published, while the public key is published by the key pair holder to others.

[0099] The first non-fungible token is generated by a smart contract on the blockchain.

[0100] A smart contract is a piece of code written on the blockchain. Once an event triggers a clause in the contract, the code executes automatically. In other words, it executes as soon as the conditions are met, without requiring human intervention. Its code is used to generate, manage, trade, use, and destroy tokens.

[0101] The activation of the smart contract can be achieved by calling the API (Application Programming Interface) on the target blockchain through the digital wallet corresponding to the target user account.

[0102] In some cases, after step S130, the method further includes generating a verifiable credential based on the target user's identity authentication information.

[0103] This can be understood as follows: after a user's identity is verified by a trusted third party, a verifiable credential is generated and stored in the first non-fungible token.

[0104] The verifiable credential may include information such as a declaration, credential identification code, issuer signature, and credential metadata.

[0105] In the subsequent verification process, information such as the declaration, credential identification code, issuer signature, and credential metadata can be used to answer whether the credential is valid and the authenticity of the subject is proven by whether it is in a standard data request format, has been effectively signed, and has not been tampered with.

[0106] Step S140: Generate a second non-fungible token corresponding to the target virtual scene based on the first non-fungible token of the target user; wherein the target virtual scene includes a target virtual avatar corresponding to the target user.

[0107] After the first non-fungible token is generated, it can be determined which virtual scenarios the target user is associated with, that is, which virtual scenarios the target user has a virtual avatar in. The virtual scenarios associated with the target user are the aforementioned target virtual scenarios.

[0108] The generated second non-fungible token corresponds one-to-one with the target virtual scene.

[0109] A user can have virtual avatars (i.e., digital avatars) in multiple virtual scenarios, so a user can be associated with multiple virtual scenarios simultaneously. Therefore, the first non-fungible token corresponds to a second non-fungible token in multiple target virtual scenarios (virtual scenarios associated with the target user). It can be understood that the owner of the second non-fungible token is the first non-fungible token.

[0110] Step S150: Based on the second non-fungible token, obtain information on at least one digital asset corresponding to the target virtual avatar in the target virtual scene.

[0111] The digital assets mentioned above can be understood as the digital assets of a user's digital identity in virtual scenarios such as virtual reality technology (virtual reality (VR), augmented reality (AR), mixed reality (MR) and extended reality (XR)), game technology (game engine, game code, multimedia resources) and AI artificial intelligence technology, such as digital assets like the skin of a game character.

[0112] Furthermore, a user's digital avatar in a virtual scenario can possess multiple digital assets.

[0113] Step S160: Based on the information of the at least one digital asset, generate a third non-fungible token corresponding to the information of each digital asset of the target virtual avatar, and bind the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene, and the third non-fungible token.

[0114] After obtaining the information of the digital assets corresponding to the target virtual avatar, at least one third non-fungible token is generated that corresponds to the information of each digital asset of the target virtual avatar.

[0115] The third non-fungible token (NFT) corresponds to the digital asset of a virtual avatar in the virtual scenario, with a one-to-one correspondence between the third NFT and the digital asset of the virtual avatar. The third NFT is bound to the second NFT. This can be understood as the owner of the third NFT being the second NFT. The third NFT conforms to the ERC-721 standard.

[0116] This can be understood as the third non-fungible token representing the user's digital identity and digital assets in a virtual scenario (metaverse).

[0117] Since a user's digital avatar in a virtual scenario can possess multiple digital assets, a user's digital avatar in a virtual scenario can correspond to multiple third-party non-fungible tokens.

[0118] The NFT distribution structure obtained after binding the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene, and the third non-fungible token is shown in the diagram below. Figure 1 As shown.

[0119] Since a user can have digital avatars in multiple virtual scenarios, one primary non-fungible token can correspond to multiple secondary non-fungible tokens. And since a user's digital avatar in a virtual scenario can have multiple digital assets, one secondary non-fungible token can correspond to multiple tertiary non-fungible tokens.

[0120] Therefore, the first non-fungible token can be regarded as the root NFT, the second non-fungible token can be regarded as a batch asset NFT, and the third non-fungible token can be regarded as a separate asset NFT (sub-NFT).

[0121] The parent node of the third nonfungible token (individual asset NFT) points to the second nonfungible token (bulk asset NFT), and the parent node of the second nonfungible token (bulk asset NFT) points to the first nonfungible token (root NFT).

[0122] A first non-fungible token (root NFT) can be associated with one or more third non-fungible tokens (individual asset NFTs). The first non-fungible token (root NFT) can be viewed as a composable non-fungible token, representing a user's total assets across multiple virtual scenarios. The first non-fungible token (root NFT) is used to store and manage the real user's identity, while the third non-fungible tokens (individual asset NFTs) represent the user's digital identity and digital identity assets in the virtual scenario (metaverse).

[0123] The second type of non-fungible token (bulk asset NFT) is also a composable non-fungible token that represents all or a single asset of a user in a virtual scenario (metaverse).

[0124] By using the first non-fungible token (root NFT) and the second non-fungible token (bulk asset NFT), the association and unified management of digital assets are achieved, improving the user experience.

[0125] The first non-fungible token, the second non-fungible token, and the third non-fungible token are encrypted using the private key.

[0126] In some cases, as in this embodiment, such as Figure 3 As shown, the above method may further include:

[0127] Step S210: Receive the target user's asset query request;

[0128] Step S220: Send the asset query request and the verifiable credential to the target virtual scene through the first non-fungible token, so that the target virtual scene can verify the verifiable credential;

[0129] Step S230: When the first non-fungible token receives the verification result for the verifiable credential from the target virtual scene, the public key and the asset information to be queried are sent to the target virtual scene through the first non-fungible token;

[0130] Step S240: Using the public key received by the target virtual scene, decode the third non-fungible token of the asset to be queried to read the information of the third non-fungible token of the asset to be queried.

[0131] This can be understood as follows: When a user wants to view their associated digital asset token information in a virtual scenario, they first send the asset query request and the verifiable credential to the target virtual scenario. Upon receiving this, the virtual scenario verifies the validity of the verifiable credential and the authenticity of the user entity corresponding to the first non-fungible token. After successful verification, the virtual scenario sends the public key and the asset information to be queried to the target virtual scenario. Upon receiving this, the target virtual scenario uses the received public key to decode the third non-fungible token (encrypted with a private key during generation) of the asset to be queried. After successful decoding, the information of the third non-fungible token (a separate asset NFT) of the asset to be queried can be read.

[0132] The information of the asset to be queried may be the asset information required by the virtual scene (metaverse) for the digital avatar to be displayed and active in the metaverse. For example, if an activity requires a certain skin, then this skin is the asset to be queried.

[0133] The first non-fungible token (root NFT) receives and sends its own metadata and / or the corresponding metaverse bulk asset NFT metadata and / or its individual asset NFTs, as well as the required public key to the metaverse.

[0134] Metaverse uses the public key it receives to decode the data and read the information of the third non-fungible token (individual asset NFT) of the asset to be queried.

[0135] Each operation in the above query steps will have a timestamp for easy recording in the background.

[0136] In some cases, as in this embodiment, such as Figure 4 As shown, the above method may further include:

[0137] Step S310: Receive a query request for the owner of the target digital asset in the target virtual scene;

[0138] Step S320: Based on the query request from all owners, determine the third non-fungible token corresponding to the target digital asset;

[0139] Step S330: Based on the third non-fungible token corresponding to the target digital asset, sequentially search for the second non-fungible token and the first non-fungible token corresponding to the target digital asset;

[0140] Step S340: Based on the binding relationship between the target user's identity authentication information and the wallet address, determine the identity information of the target user corresponding to the target digital asset through the wallet address corresponding to the first non-fungible token, so as to obtain the identity authentication information of the owner of the target digital asset.

[0141] This can be understood as follows: the parent node of the third non-fungible token corresponding to the target digital asset corresponds to the second non-fungible token, and the parent node of the second non-fungible token corresponds to the first non-fungible token. Therefore, based on the third non-fungible token corresponding to the target digital asset, the second non-fungible token and the first non-fungible token corresponding to the target digital asset are searched sequentially. Since a wallet address corresponding to the identity authentication information of the target user is generated when the first non-fungible token corresponding to each user is generated, the identity information of the target user corresponding to the target digital asset can be determined through the wallet address corresponding to the first non-fungible token, based on the binding relationship between the identity authentication information of the target user and the wallet address. Thus, the identity authentication information of the owner of the target digital asset can be obtained.

[0142] This can be understood as follows: from the first non-fungible token (root NFT), you can find all the leaf nodes in its tree, which is the third non-fungible token (individual asset NFT), and thus you can obtain information about any digital assets owned by each user.

[0143] From any third non-fungible token (a standalone asset NFT, a leaf node), you can obtain its parent first non-fungible token (the root NFT), which means you can obtain the identity information of the owner of any asset.

[0144] In some cases, the method described above in this embodiment may further include:

[0145] Step S410: Receive an asset transfer request from the target user for the target digital asset in the target virtual scene;

[0146] Step S420: According to the asset transfer request, transfer the third non-fungible token corresponding to the target digital asset to the second non-fungible token corresponding to another virtual scene, so as to transfer the target digital asset to the other virtual scene.

[0147] This can be understood as follows: based on the user's request, one or more third non-fungible tokens (individual asset NFTs) can be transferred to second non-fungible tokens (bulk asset NFTs) corresponding to other virtual scenarios, so that the corresponding digital assets can be used in other virtual scenarios (metaverse).

[0148] In addition, a second non-fungible token (bulk asset NFT) can be replicated, allowing users to own the same assets in different metaverses, simplifying the process of users generating assets.

[0149] This application provides a blockchain-based asset management method. The method includes generating a first non-fungible token (NFT) based on the identity authentication information of a target user; generating a second NFT corresponding to a target virtual scene based on the first NFT of the target user; wherein the target virtual scene includes a target virtual avatar corresponding to the target user; obtaining information on at least one digital asset corresponding to the target virtual avatar in the target virtual scene based on the second NFT; generating a third NFT corresponding to the information of each digital asset of the target virtual avatar based on the information of the at least one digital asset; and binding the first NFT of the target user, the second NFT in the target virtual scene, and the third NFT. The first NFT used for identity authentication (root NFT), the second NFT used for all assets of the corresponding user in a certain virtual scene (metaverse) (batch NFT), and the third NFT used for a single digital asset in the corresponding virtual scene (metaverse) (sub-NFT) are combined to form a composable NFT. This allows users to associate and manage multiple digital assets of their corresponding digital avatars in virtual scenarios.

[0150] Example 3

[0151] Figure 5 Please refer to the schematic diagram of a blockchain-based asset management device provided in this application embodiment. Figure 5 This embodiment provides a blockchain-based asset management device 100, including a receiving module 110, an identity authentication module 120, a first creation module 130, a second creation module 140, an asset acquisition module 150, and a third creation module 160.

[0152] The receiving module 110 is used to receive non-fungible token requests from target users;

[0153] The identity authentication module 120 is used to obtain the user's identity authentication information based on the non-fungible token request;

[0154] The first creation module 130 is used to generate a corresponding first non-fungible token based on the user's identity authentication information.

[0155] The second creation module 140 is used to generate a second non-fungible token for the user in the target virtual scene based on the user's first non-fungible token.

[0156] The asset acquisition module 150 is used to acquire at least one digital asset information corresponding to the user's target virtual avatar in the target virtual scene based on the second non-fungible token.

[0157] The third creation module 160 is used to generate at least one third non-fungible token corresponding to the information of each digital asset of the target virtual avatar based on the information of the at least one digital asset, and to bind the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene and the third non-fungible token.

[0158] Optionally, in the aforementioned blockchain-based asset management device 100, the first creation module 130 is further used for:

[0159] Based on the target user's identity authentication information, a corresponding first non-fungible token and a pair of public and private keys are generated, and a wallet address is generated using the public key;

[0160] The target user's identity authentication information is bound to the wallet address.

[0161] Optionally, in the blockchain-based asset management device 100 described above, the second non-fungible token and the third non-fungible token are encrypted using the private key.

[0162] Optionally, in the aforementioned blockchain-based asset management device 100, the first creation module 130 is further used for:

[0163] Based on the target user's identity authentication information, a verifiable credential is generated.

[0164] Optionally, in the blockchain-based asset management device 100 described above, the receiving module 110 is also used to receive the asset query request from the target user;

[0165] The above-mentioned device also includes:

[0166] The verification module is used to send the asset query request and the verifiable credential to the target virtual scene through the first non-fungible token, so that the target virtual scene can verify the verifiable credential;

[0167] The sending module is used to send the public key and the asset information to be queried to the target virtual scene through the first non-fungible token when the first non-fungible token receives the verification result of the verifiable credential from the target virtual scene.

[0168] The decoding module is used to decode the third non-fungible token of the asset to be queried by using the public key received by the target virtual scene, so as to read the information of the third non-fungible token of the asset to be queried.

[0169] Optionally, in the blockchain-based asset management device 100 described above, the receiving module 110 is further configured to receive query requests from the owner of the target digital asset in the target virtual scene.

[0170] Also includes:

[0171] The first determining module is used to determine the third non-fungible token corresponding to the target digital asset based on the query request from the owner.

[0172] The search module is used to sequentially search for the second non-fungible token and the first non-fungible token corresponding to the target digital asset based on the third non-fungible token corresponding to the target digital asset.

[0173] The second determining module is used to determine the identity information of the target user corresponding to the target digital asset based on the binding relationship between the target user's identity authentication information and the wallet address, through the wallet address corresponding to the first non-fungible token, so as to obtain the identity authentication information of the owner of the target digital asset.

[0174] Optionally, in the blockchain-based asset management device 100 described above, the receiving module 110 is further configured to receive an asset transfer request sent by the target user for the target digital asset in the target virtual scene.

[0175] Also includes:

[0176] The transfer module is used to transfer the third non-fungible token corresponding to the target digital asset to the second non-fungible token corresponding to another virtual scene according to the asset transfer request, so as to transfer the target digital asset to the other virtual scene.

[0177] Specific implementations of the blockchain-based asset management method based on the above modules have been detailed in Implementation Example 2 and will not be repeated here.

[0178] Example 4

[0179] This embodiment provides an electronic device, which may be a mobile phone, computer, or tablet computer, etc., including a memory and a processor. The memory stores a calculator program, which, when executed by the processor, implements the blockchain-based asset management method as described in Embodiment 2. It is understood that the electronic device may also include an input / output (I / O) interface and communication components.

[0180] The processor is used to execute all or part of the steps in the blockchain-based asset management method as described in Embodiment 2. The memory is used to store various types of data, which may include, for example, instructions for any application or method in the electronic device, as well as application-related data.

[0181] The processor may be implemented as an Application Specific Integrated Circuit (ASIC), Digital Signal Processor (DSP), Digital Signal Processing Device (DSPD), Programmable Logic Device (PLD), Field Programmable Gate Array (FPGA), controller, microcontroller, microprocessor, or other electronic components, and is used to execute the blockchain-based asset management method in Embodiment 2 above.

[0182] The memory can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read-Only Memory (EPROM), Programmable Read-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0183] Example 5

[0184] This embodiment also provides a computer-readable storage medium, such as flash memory, hard disk, multimedia card, card-type memory (e.g., SD or DX memory), random access memory (RAM), static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, disk, optical disk, server, app store, etc., which stores a computer program. When the computer program is executed by a processor, it can implement the following method steps:

[0185] Step S110: Receive nonfungible token requests from the target user;

[0186] Step S120: Obtain the identity authentication information of the target user based on the non-fungible token request;

[0187] Step S130: Generate a corresponding first non-fungible token based on the identity authentication information of the target user;

[0188] Step S140: Generate a second non-fungible token for the target user in the target virtual scene based on the first non-fungible token of the target user;

[0189] Step S150: Based on the second non-fungible token, obtain information on at least one digital asset corresponding to the target virtual avatar of the target user in the target virtual scene;

[0190] Step S160: Based on the information of the at least one digital asset, generate at least one third non-fungible token corresponding to the information of each digital asset of the target virtual avatar, and bind the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene, and the third non-fungible token.

[0191] For a detailed description of the above method steps, please refer to Example 2. This example will not be repeated here.

[0192] In summary, this application provides a blockchain-based asset management method, system, electronic device, and storage medium. The method includes generating a first non-fungible token (NFT) based on the identity authentication information of the target user; generating a second NFT corresponding to a target virtual scene based on the first NFT of the target user; wherein the target virtual scene includes a target virtual avatar corresponding to the target user; obtaining information on at least one digital asset corresponding to the target virtual avatar in the target virtual scene based on the second NFT; generating a third NFT corresponding to the information of each digital asset of the target virtual avatar based on the information of the at least one digital asset; and binding the first NFT corresponding to the target user, the second NFT in the target virtual scene, and the third NFT. The first non-fungible token (root NFT) used for identity authentication, the second non-fungible token (bulk NFT) used for all assets of a corresponding user in a virtual scenario (metaverse), and the third non-fungible token (sub-NFT) used for a single digital asset in the corresponding virtual scenario (metaverse) are combined to form a composable non-fungible token. This allows users to associate and manage multiple digital assets of their digital avatar in the corresponding virtual scenario in a unified manner.

[0193] It should be noted that, in this document, the terms "comprising," "including," or any other variations thereof are intended to cover non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements includes not only those elements but also other elements not expressly listed, or elements inherent to such a process, method, article, or apparatus. Unless otherwise specified, an element defined by the phrase "comprising one..." does not exclude the presence of other identical elements in the process, method, article, or apparatus that includes said element.

[0194] Although the embodiments disclosed in this application are as described above, the content is merely for the purpose of facilitating understanding of this application and is not intended to limit this application. Any person skilled in the art to which this application pertains may make any modifications and changes in the form and details of the implementation without departing from the spirit and scope disclosed in this application; however, the scope of patent protection of this application shall still be determined by the scope defined in the appended claims.

Claims

1. A blockchain-based asset management method, characterized in that, The blockchain is configured with at least one user account and at least one virtual scenario account, the virtual scenario including at least one virtual avatar, and the method includes: Receive non-fungible token requests from target users; Based on the non-fungible token request, obtain the target user's identity authentication information; Based on the target user's identity authentication information, a corresponding first non-fungible token is generated; Based on the first non-fungible token of the target user, a second non-fungible token corresponding to the target virtual scene is generated; wherein, the target virtual scene includes a target virtual avatar corresponding to the target user; the second non-fungible token corresponds one-to-one with the virtual scene; Based on the second non-fungible token, obtain information on at least one digital asset corresponding to the target virtual avatar in the target virtual scene; Based on the information of the at least one digital asset, a third non-fungible token is generated corresponding to the information of each digital asset of the target virtual avatar, and the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene, and the third non-fungible token are bound together. The method further includes: Receive an asset transfer request sent by the target user for the target digital asset in the target virtual scene; According to the asset transfer request, the third non-fungible token corresponding to the target digital asset is transferred to the second non-fungible token corresponding to another virtual scene, so as to transfer the target digital asset to the other virtual scene; Wherein, the owner of the second non-fungible token is the first non-fungible token, and the owner of the third non-fungible token is the second non-fungible token; The method further includes: Based on the target user's identity authentication information, a public key and a private key pair are generated, and a wallet address is generated using the public key; Bind the target user's identity authentication information to the wallet address; The first non-fungible token is associated with the wallet address.

2. The method according to claim 1, characterized in that, The first non-fungible token, the second non-fungible token, and the third non-fungible token are encrypted using the private key.

3. The method according to claim 2, characterized in that, After generating the corresponding first non-fungible token based on the target user's identity authentication information, the method further includes: Based on the target user's identity authentication information, a verifiable credential is generated.

4. The method according to claim 3, characterized in that, Also includes: Receive the target user's asset query request; The asset query request and the verifiable credential are sent to the target virtual scene through the first non-fungible token, so that the target virtual scene can verify the verifiable credential; When the first non-fungible token receives the verification result for the verifiable credential from the target virtual scene, it sends the public key and the asset information to be queried to the target virtual scene through the first non-fungible token. The target virtual scene uses the public key it receives to decode the third non-fungible token of the asset to be queried, so as to read the information of the third non-fungible token of the asset to be queried.

5. The method according to claim 1, characterized in that, The method further includes: Receive owner query requests for the target digital assets in the target virtual scene; Based on the query requests from all the parties, the third non-fungible token corresponding to the target digital asset is determined; Based on the third non-fungible token corresponding to the target digital asset, sequentially search for the second non-fungible token and the first non-fungible token corresponding to the target digital asset; Based on the binding relationship between the target user's identity authentication information and the wallet address, the identity information of the target user corresponding to the target digital asset is determined through the wallet address corresponding to the first non-fungible token, so as to obtain the identity authentication information of the owner of the target digital asset.

6. A blockchain-based asset management device, characterized in that, The apparatus for performing the method as described in any one of claims 1-5 includes: The receiving module is used to receive non-fungible token requests from target users and to receive asset transfer requests sent by the target users for target digital assets in the target virtual scene. The identity authentication module is used to obtain the user's identity authentication information based on the non-fungible token request; The first creation module is used to generate a corresponding first non-fungible token based on the user's identity authentication information; The second creation module is used to generate a second non-fungible token for the user in the target virtual scene based on the user's first non-fungible token; the second non-fungible token corresponds one-to-one with the virtual scene; The asset acquisition module is used to acquire at least one digital asset information corresponding to the user's target virtual avatar in the target virtual scene based on the second non-fungible token. The third creation module is used to generate at least one third non-fungible token corresponding to the information of each digital asset of the target virtual avatar based on the information of the at least one digital asset, and to bind the first non-fungible token corresponding to the target user, the second non-fungible token in the target virtual scene and the third non-fungible token. The transfer module is used to transfer the third non-fungible token corresponding to the target digital asset to the second non-fungible token corresponding to another virtual scene according to the asset transfer request, so as to transfer the target digital asset to the other virtual scene; The owner of the second non-fungible token is the first non-fungible token, and the owner of the third non-fungible token is the second non-fungible token.

7. A blockchain-based asset management system, characterized in that, The system for performing the method as described in any one of claims 1-5 includes: Blockchain; At least one user's account is set up on the blockchain; At least one account for a virtual scenario is set up on the blockchain; wherein each virtual scenario includes at least one virtual avatar, each virtual avatar has at least one digital asset, and each user corresponds to at least one virtual avatar; The first non-fungible token is associated with the user's wallet address; the wallet address corresponds one-to-one with the user's identity authentication information. The second non-fungible token is bound to the first non-fungible token and corresponds one-to-one with the virtual scene; The third non-fungible token is bound to the second non-fungible token and corresponds one-to-one with the digital asset; after the digital asset is transferred from the current target virtual scene to another virtual scene, the third non-fungible token corresponding to the digital asset is transferred from the second non-fungible token corresponding to the target virtual scene to the second non-fungible token corresponding to the other virtual scene. The owner of the third nonfungible token is the second nonfungible token.

8. An electronic device, characterized in that, It includes a memory and a controller, wherein the memory stores a program that, when executed by the controller, performs the blockchain-based asset management method as described in any one of claims 1 to 5.

9. A storage medium, characterized in that, The computer program stored in the storage medium, when executed by one or more processors, implements the blockchain-based asset management method as described in any one of claims 1 to 5.

Images