Digital asset processing method, electronic device, storage medium, and program product

Abstract

The application provides a digital asset processing method, an electronic device, a storage medium and a program product; the method comprises the following steps: in response to a digital asset processing operation triggered by a user in a metaverse space for at least one blockchain, acquiring first event information corresponding to the digital asset processing operation; the metaverse space comprises a plurality of blockchains, and the plurality of blockchains interact with each other through a cross-chain bridge; the first event information comprises a global identity of the user, at least one blockchain identifier, and a set of permission verification (VC) credentials of the user; the global identity is a unified identity for identifying the identity of the user by the plurality of blockchains; the set of VC credentials comprises a VC credential issued in advance to the user by a blockchain corresponding to the at least one blockchain identifier; by using the global identity and the set of VC credentials, the cross-chain bridge is used to process the digital asset in the corresponding blockchain, and a digital asset processing result is obtained. The method can improve the processing efficiency of the digital asset.

Description

Technical Field

[0001] This application relates to blockchain technology, and more particularly to a digital asset processing method, electronic device, storage medium, and program product. Background Technology

[0002] Digital assets, such as NFTs (Non-Fungible Tokens) and FTs (Fungible Tokens), refer to assets deployed through contracts that possess uniqueness, transparency, immutability, and non-tradability on the blockchain.

[0003] Currently, the mainstream methods for processing digital assets primarily operate on a single blockchain. This involves assigning a user identifier to each blockchain. Users use these identifiers to process corresponding digital assets on their respective blockchains. For example, in a futuristic universe, there are blockchains A, B, and C. Users are issued user identifiers 1 (for blockchain A), 2 (for blockchain B), and 3 (for blockchain C). A user can access blockchain A using user identifier 1 and perform the creation of digital assets within blockchain A. If cross-blockchain processing is required, such as transferring a user's digital assets from blockchain A to blockchain B, the user must first destroy the digital assets on blockchain A using user identifier 1, and then create new digital assets on blockchain B using user identifier 2.

[0004] However, this method of processing digital assets requires querying a large number of user identifiers to access the corresponding blockchain. Furthermore, digital assets on a chain are fixedly associated with user identifiers, and users cannot interact with other blockchains through user identifiers on a particular blockchain, resulting in very low efficiency in processing digital assets. Summary of the Invention

[0005] This application provides a digital asset processing method, an electronic device, a computer-readable storage medium, and a computer program product, which can improve the processing efficiency of digital assets.

[0006] This application provides a digital asset processing method, the method including: In response to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, the system obtains the first event information corresponding to the digital asset processing operation. The metaverse space includes multiple blockchains, which interact with each other through cross-chain bridges. The first event information includes the user's global identity identifier, at least one blockchain identifier, and the user's permission verification VC credential set. The global identity identifier is a unified identifier used by multiple blockchains to identify the user. The VC credential set includes VC credentials pre-issued to the user by the blockchain corresponding to at least one blockchain identifier, and the VC credentials serve as proof of the user's permissions within the corresponding blockchain. By using a global identity identifier and VC credential set, digital assets are processed within the corresponding blockchain using a cross-chain bridge to obtain the digital asset processing results.

[0007] In the above scheme, the metaverse space also includes an identity chain; the identity chain is used to issue global identity tokens to users. Prior to responding to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, the method further includes: In response to a user's identity registration operation within the metaverse space, the identity chain is invoked to issue a global identity identifier to the user; In response to a user's registration operation for a digital asset storage unit on any blockchain within the metaverse space, the corresponding blockchain is invoked to allocate a digital asset storage unit to the user and associate the digital asset storage unit with a global identity identifier. In response to a user's VC application for any blockchain within the metaverse space, based on the global identity identifier and the address of the digital asset storage unit associated with the global identity identifier on the corresponding blockchain, the corresponding blockchain is invoked to issue the corresponding blockchain VC certificate to the user.

[0008] In the above scheme, at least one blockchain identifier includes the source chain identifier of the source chain and the target chain identifier of the target chain; the VC credential set includes a first VC credential pre-issued to the user by the source chain and a second VC credential pre-issued to the user by the target chain. By leveraging a global identity identifier and VC credential set, and utilizing cross-chain bridges, digital assets can be processed within the corresponding blockchain, including: The first event information is forwarded to the source chain via a cross-chain bridge; The source chain is invoked to verify the global identity identifier and the first VC credential in the first event information, respectively; If the verification is successful, the source chain will be invoked to lock the digital asset associated with the source address, and the source chain will be invoked to generate the second event information; the second event information includes at least the global identity identifier and the second VC certificate; the source address is the address of the digital asset storage unit of the global identity identifier on the source chain; The second event information is forwarded to the target chain via a cross-chain bridge; The target chain is invoked to verify the global identity identifier and the second VC credential respectively; If the verification is successful, the target chain will be invoked to perform an addition operation on the digital assets associated with the target address; the amount of newly added digital assets in the target chain is equal to the amount of digital assets locked in the source chain; the target address is the address of the digital asset storage unit of the global identity identifier on the target chain.

[0009] In the above scheme, the second event information also includes a first VC certificate, a first signature, and a first identifier; the first signature is the signature signed by the operation of locking the corresponding digital asset in the source chain; the first identifier indicates whether the digital asset associated with the preset address in the source chain is in a locked state; The second event information is forwarded to the target chain via a cross-chain bridge, including: The first identifier, first signature, global identity identifier, first VC credential, and second VC credential are verified separately through a cross-chain bridge. If the verification passes, the second event information is forwarded to the target chain via a cross-chain bridge.

[0010] In the above scheme, after calling the target chain to perform a new operation on the digital asset associated with the target address, the method also includes: The target chain is invoked to generate third event information corresponding to the digital asset; the third event information includes at least a second identifier; the second identifier indicates whether the addition operation of the digital asset associated with the target address has been completed within the target chain. The third event information is forwarded to the source chain via a cross-chain bridge; The source chain is invoked to verify the second identifier in the third event information; If the second identifier indicates that the target chain has completed the addition operation of the digital asset associated with the target address, then the calling source chain will destroy the digital asset locked in the source chain or keep it in a locked state.

[0011] In the above scheme, forwarding the second event information to the target chain via a cross-chain bridge includes: The second event information is converted into standard event information in a standard format through a cross-chain bridge, and then the standard event information is converted into a fourth event information that conforms to the data format of the target chain. The fourth event information is forwarded to the target chain via a cross-chain bridge.

[0012] In the above scheme, at least one blockchain identifier includes the target chain identifier of the target chain; the VC credential set includes third VC credentials pre-issued to users by the target chain; By using a global identity identifier and VC credential set, and leveraging a cross-chain bridge, digital assets are processed within the corresponding blockchain to obtain the processing results, including: Invoke the cross-chain bridge to forward the first event information to the target chain; The target chain is invoked to verify the global identity and the third-party VC credential respectively; If the verification passes, the target chain is invoked to process the digital asset associated with the target address; the target address is the address of the digital asset storage unit on the target chain where the global identity is located.

[0013] This application provides an electronic device, which includes: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in memory, implements the digital asset processing method provided in the embodiments of this application.

[0014] This application provides a computer-readable storage medium storing a computer program or computer-executable instructions for implementing the digital asset processing method provided in this application when executed by a processor.

[0015] This application provides a computer program product, including a computer program or computer-executable instructions. When the computer program or computer-executable instructions are executed by a processor, they implement the digital asset processing method provided in this application.

[0016] The solution in this application embodiment responds to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, obtaining first event information corresponding to the digital asset processing operation. The metaverse space includes multiple blockchains, which interact with each other via cross-chain bridges. The first event information includes the user's global identity identifier, at least one blockchain identifier, and the user's permission verification VC credential set. The global identity identifier is a unified identifier used by multiple blockchains to identify the user's identity. The VC credential set includes VC credentials pre-issued to the user by the blockchain corresponding to at least one blockchain identifier; the VC credential is proof of the user's permissions within the corresponding blockchain. Using the global identity identifier and the VC credential set, the cross-chain bridge is used to process the digital asset within the corresponding blockchain, resulting in a digital asset processing result. Throughout this process, there is no need to query for the corresponding user identifier from a large number of user identifiers, nor is it necessary to perform digital asset processing operations separately for each blockchain. Instead, based on the global identity identifier and the VC credential set, the cross-chain bridge can be used to process the digital asset in one go within the corresponding blockchain, achieving the effect that digital assets and user identity data can directly interact between multiple blockchains. The entire digital asset processing process is simple, time-saving, and its processing efficiency is greatly improved. Attached Figure Description

[0017] Figure 1 This is a schematic diagram of the architecture of the digital asset processing system provided in the embodiments of this application; Figure 2 This is a first flowchart illustrating the digital asset processing method provided in this application embodiment; Figure 3 This is a schematic diagram illustrating the interaction between the identity chain, blockchain A, and the user through the VC certificate of blockchain A, as provided in this application embodiment.

[0018] Figure 4 This is a schematic diagram of the cross-chain bridge structure provided in the embodiments of this application; Figure 5 This is a second flowchart illustrating the digital asset processing method provided in the embodiments of this application; Figure 6 This is a hardware structure diagram of the electronic device provided in the embodiments of this application.

[0019] It should be noted that the terms "first" and "second" mentioned above are only used to distinguish between different options and do not represent the degree of superiority or inferiority of the options or their priority in the implementation process. Detailed Implementation

[0020] To make the objectives, technical solutions, and advantages of this application clearer, the application will be further described in detail below with reference to the accompanying drawings. The described embodiments should not be regarded as limitations on this application. All other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.

[0021] First, it should be noted that all information collected in this application is collected only when the user is aware of the information collection and has given their authorization and consent.

[0022] Secondly, some basic terms used in this application will be explained: 1. NFT: Non-fungible token, meaning a non-fungible token, is essentially a digital asset deployed through blockchain contract nodes. It possesses uniqueness, transparency, immutability, and non-tradeability on the blockchain. In practical applications, NFTs can be items in the form of photographs, videos, music, etc.

[0023] 2. Blockchain (BC): A distributed ledger technology with characteristics such as decentralization and immutability. Different blockchains are usually isolated from each other.

[0024] 3. Metaverse (MVS): A broad and persistent online virtual space realized through virtual reality (VR), augmented reality (AR), and the internet, existing in parallel with the real world. It can be understood as a virtual world constructed by humans using digital technology, mapping to or transcending the real world, and capable of interacting with it. It integrates various new technologies, such as extended reality, digital twins, and blockchain, to provide immersive experiences, generate mirror images of the real world, and build an economic system, closely merging the virtual and real worlds in economic, social, and identity systems.

[0025] 4. Interoperability Bridge (IB): This is an infrastructure protocol that connects two or more heterogeneous blockchains. Its core function is to break down the interaction barriers between different public chains, consortium chains, sidechains, and Layer 2 blockchains, enabling cross-chain transfer of digital assets and solving the blockchain silo problem. In this application, it is responsible for transmitting event data between the metaverse space and multiple blockchains. Its main function is to ensure the secure, intact, and real-time transmission of data between the metaverse space and multiple blockchains.

[0026] 5. Digital Identity (DID): A digital identity without a centralized authority providing ultimate assurance, it is an extension and expansion of the concept of user profiling. It allows users to create and control their own identities without relying on any centralized institution.

[0027] 6. Verifiable Credential (VC): It is a standardized decentralized digital identity data format. It is a digital cryptographic carrier of real-world paper documents (such as ID cards, academic certificates, and qualification certificates). It can securely, privately, and verifiably prove the identity, attributes, qualifications, and authorization information of the subject.

[0028] 7. A digital asset storage unit is the basic unit for distinguishing different assets in a digital asset system. Every user who has registered in the metaverse space can apply for a digital asset storage unit on its blockchain.

[0029] The current mainstream methods for processing digital assets primarily operate on a single blockchain. This involves assigning a user identifier to each blockchain, which serves as proof of the user's identity on that blockchain. Users then use their user identifiers to process corresponding digital assets on their respective blockchains. For example, in a futuristic universe, there are blockchains A, B, and C. Users are issued user identifiers 1 (for blockchain A), 2 (for blockchain B), and 3 (for blockchain C). To process digital assets on a single blockchain, a user can access blockchain A using user identifier 1 and perform a new digital asset creation operation within blockchain A. Similarly, a user can access blockchain B using user identifier 2 and perform a digital asset destruction operation within blockchain B. If cross-blockchain processing is required, such as transferring digital assets from blockchain A to blockchain B, the user must first perform a digital asset destruction operation on blockchain A using user identifier 1, and then perform a digital asset creation operation on blockchain B using user identifier 2.

[0030] This method of handling digital assets leads to severe interoperability limitations: an on-chain NFT and user identity data ID cannot directly interact with other blockchains, resulting in extremely low efficiency for cross-chain transfers of digital assets. Furthermore, even when performing digital asset processing operations within a single blockchain, it requires querying a large number of user identifiers to access the corresponding blockchain, making its efficiency within a single blockchain also low. Therefore, it is clear that the current processing efficiency of digital assets is low, whether for cross-chain transfers or single-chain processing.

[0031] In view of the shortcomings of the above-mentioned related technologies, this application provides a digital asset processing method that can improve the processing efficiency of digital assets. To illustrate the technical solution of this application, specific embodiments are described below.

[0032] This application provides a digital asset processing method applied to a metaverse space 101, which communicates bidirectionally with a terminal 102 via a network. The metaverse space 101 includes multiple blockchains 103, which interact with each other via cross-chain bridges 104. The terminal 102 is equipped with an interactive interface 105 for the metaverse space 101.

[0033] like Figure 1As shown, a user triggers a digital asset processing operation on at least one blockchain 103 on the interactive interface 105 of terminal 102. For example, the reward for completing a task in the metaverse space 101 is a digital collectible. If the user completes the task on the interactive interface 105 of the mobile phone, it is considered that the user has triggered a digital asset processing operation on at least one blockchain 103 in the metaverse space 101. Alternatively, if a user wants to transfer digital assets from a digital asset storage unit of one blockchain to a digital asset storage unit of another blockchain on the interactive interface 105 of the mobile phone, the user can fill in the corresponding blockchain identifier in the digital asset transfer area of ​​the interactive interface and trigger the digital asset transfer control. At this time, it is considered that the user has triggered a digital asset processing operation on at least one blockchain 103 in the metaverse space 101.

[0034] When a user triggers a digital asset processing operation on at least one blockchain 103 within the metaverse space 101, the terminal 102 responds to the triggering operation and generates first event information corresponding to the digital asset processing operation based on the user's global identity identifier, the identifier of at least one blockchain associated with the triggered digital asset processing operation, and the user's permission verification VC credential set. Here, the global identity identifier is a unified identifier used by multiple blockchains to identify the user; the VC credential set includes VC credentials pre-issued to the user by the blockchain corresponding to at least one blockchain identifier, and the VC credential serves as proof of the user's permissions within the corresponding blockchain.

[0035] Terminal 102 uploads the first event information corresponding to the digital asset processing operation to Metaverse Space 101. Metaverse Space 101 obtains the first event information corresponding to the digital asset processing operation; using the global identity identifier and VC credential set, it processes the digital asset within the corresponding blockchain through cross-chain bridge 104 to obtain the digital asset processing result. Further, based on the digital asset processing result, Metaverse Space 101 displays the asset information display sub-interface of the corresponding blockchain in the interactive interface 105.

[0036] Figure 2 A flowchart of a digital asset processing method provided in this application embodiment, taking the application of the method to the metaverse space 101 as an example, the digital asset processing method provided in this application includes the following steps: S201, in response to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, obtain the first event information corresponding to the digital asset processing operation.

[0037] The metaverse space comprises multiple blockchains that interact with each other via cross-chain bridges. The first event information includes the user's global identity identifier, at least one blockchain identifier, and the user's VC (Virtual Certificate) credential set for permission verification. The global identity identifier is a unified identifier across multiple blockchains; for example, it could be a digital identity (DID) mentioned in a signature. The VC credential set includes VC credentials pre-issued to the user by the blockchain corresponding to at least one blockchain identifier; these VC credentials serve as proof of the user's permissions within the corresponding blockchain.

[0038] Digital assets refer to digitized assets that exist in binary form, possess economic value, and can be clearly owned or controlled. Digital assets are diverse in type. For example, based on their interchangeability, they can be categorized into NFTs, FTs, etc. NFTs include, but are not limited to, cryptocurrencies, platform universal points, and equity, while NTs include, but are not limited to, digital artworks, collectibles, game equipment, tickets, and membership cards. Furthermore, digital assets can be classified according to their field into the following six categories, including, but not limited to: 1. Cryptocurrencies; 2. Digital currencies; 3. Digital content and intellectual property: ebooks, music, movies, software, design documents, domain names, website content, virtual game items, etc.; 4. Data assets: customer databases, market research data, user behavior analysis, machine learning models, etc.; 5. Digital financial assets: electronic stocks, digital bonds, etc.; 6. Digital identity credentials: verifiable digital identity information, academic certificates, qualification certificates, etc.

[0039] When a user triggers a digital asset processing operation on at least one blockchain through the terminal's interactive interface, such as purchasing a digital asset on a specific blockchain within the metaverse space, or completing a task within the metaverse space that rewards a digital asset on a specific blockchain, it is considered that the user has triggered a digital asset creation operation for that blockchain within the metaverse space. Similarly, clicking the delete operation on a digital asset on a specific blockchain within the metaverse space is considered a digital asset destruction operation for that blockchain within the metaverse space. Furthermore, if a user enters the source chain identifier in the digital asset transfer area of ​​the interactive interface and the target chain identifier in the digital asset transfer area, and then triggers the digital asset transfer control, it is considered that the user has triggered a cross-chain transfer operation for the digital asset between the source and target chains within the metaverse space. These digital asset creation, destruction, and cross-chain transfer operations can all be collectively referred to as digital asset processing operations.

[0040] Specifically, the terminal features an interactive interface for the Metaverse Space. Users log in to the Metaverse Space through this interface, and the terminal obtains the user's global identity. The interface also includes sub-interfaces for digital asset storage units. Each sub-interface contains multiple digital asset storage units, each associated with the user's global identity. Each storage unit corresponds to one or more digital assets. Users can click on a sub-interface within the digital asset storage unit to browse their one or more digital assets under that storage unit for each blockchain. Essentially, each blockchain's corresponding digital asset storage unit can be displayed as an account within its sub-interfaces, allowing users to clearly see their one or more digital assets within that blockchain through their corresponding blockchain account.

[0041] When a user triggers a digital asset processing operation on at least one blockchain within the metaverse space, the terminal responds to the triggering operation and identifies at least one blockchain identifier associated with the triggered digital asset processing operation. The terminal queries the blockchains corresponding to the at least one blockchain identifier to find the VC credentials issued to the user, and combines these VC credentials into the user's VC credential set. Further, based on the global identity identifier obtained when the user logs in, the at least one blockchain identifier associated with the triggered digital asset processing operation, and the user's permission verification VC credential set, the terminal generates first event information corresponding to the digital asset processing operation.

[0042] The terminal uploads the first event information corresponding to the digital asset processing operation to the metaverse space, and the metaverse space obtains the first event information corresponding to the digital asset processing operation.

[0043] In some embodiments, before responding to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, the metaverse space can issue a global identity identifier to the user, which can be recognized by multiple blockchains. Furthermore, each blockchain can also issue a specific VC credential to the user individually. This VC credential can be identified by the blockchain that issued it to determine whether its internal permission data conforms to the permissions of the corresponding blockchain, thus determining whether the user's digital asset processing operation can be executed on that blockchain. For example, if the permission data within the VC credential indicates that the user cannot process the digital asset corresponding to a certain digital asset identifier on that blockchain, then when the user accesses that blockchain through the VC credential, the blockchain will refuse to execute the user's digital asset processing operation.

[0044] In some embodiments, the first event information may further include the operation type of the digital asset processing operation, which includes, but is not limited to, digital asset creation, cross-chain transfer, and destruction operations. The number of corresponding blockchain identifiers may differ depending on the operation type of the digital asset processing operation. For example, when the operation type is a digital asset creation or destruction operation, the corresponding number of blockchain identifiers is 1; when the operation type is a cross-chain transfer operation, the corresponding number of blockchain identifiers is 2.

[0045] Furthermore, when the operation type of digital asset processing is a digital asset creation operation or a digital asset destruction operation, the corresponding blockchain identifier is the identifier of the blockchain that performs the digital asset creation operation or the digital asset destruction operation; when the operation type of digital asset processing is a cross-chain transfer operation of digital assets, the first event information includes at least one blockchain identifier, including the source chain identifier that performs the digital asset transfer-out operation and the target chain identifier corresponding to the digital asset transfer-in operation. The first event information not only includes these two blockchain identifiers, but also needs to mark each blockchain identifier as either a digital asset transfer-in party or a digital asset transfer-out party.

[0046] In some embodiments, a user may have more than one digital asset within each blockchain's digital asset storage unit. To distinguish the digital assets requiring digital asset processing operations, the first event information also includes a digital asset identifier. Subsequent processing of the digital asset refers to processing the digital asset corresponding to the digital asset identifier. For example, the digital asset identifier could be an identifier for an electronic certificate, and subsequent processing of the digital asset refers to processing the electronic certificate.

[0047] In some embodiments, the first event information also includes an operation timestamp of the user triggering the digital asset processing operation. Based on the operation timestamp, it can be determined whether the digital asset can be processed within the corresponding blockchain. For example, if a school sets that the balance in a water card cannot be changed from 0:00 to 6:00, and the operation timestamp in the first event information is 0:50, it is determined that the balance in the water card cannot be changed on the school's corresponding blockchain. Therefore, the first event information is invalid and cannot trigger the digital asset processing operation on the corresponding blockchain.

[0048] In some embodiments, the first event information includes one or more of the following: operation type of digital asset processing operation, digital asset identifier, user's global identity identifier, at least one blockchain identifier, user's permission verification VC credential set, and operation timestamp of user triggering digital asset processing operation. Based on this first event information, it is possible to comprehensively and accurately determine whether digital asset processing can be performed, and to accurately perform digital asset processing within the corresponding blockchain.

[0049] In some embodiments, a VC credential contains the user's identity information and related permissions on the corresponding blockchain, such as digital asset management permissions and digital asset transfer permissions. A VC credential may contain the following components: 1. Voucher Identifier: Used to uniquely identify this VC voucher.

[0050] 2. Certificate issuer: The entity or system responsible for issuing the VC certificate, currently mainly referring to the contract node corresponding to the blockchain.

[0051] 3. Holder: The holder of this VC credential, i.e., the user's global identity identifier.

[0052] 4. Declaration: Declaration regarding user identity or permissions. For example, this declaration can declare the digital asset identifier of a user that can be processed on a certain blockchain, or the operation type permissions for specific digital asset processing operations of a user that can be processed on a certain blockchain. In addition, it can declare the digital asset management permissions of a user on a certain blockchain, etc., without limitation.

[0053] 5. Certificate Metadata: This includes information such as the creation time and expiration time of the VC certificate. When the timestamp of the operation triggering the digital asset processing is later than the expiration time of the VC certificate, the blockchain corresponding to the VC certificate cannot identify its first event information and cannot execute the corresponding digital asset processing operation.

[0054] 6. Certificate Status: Describes the current status of the VC certificate, such as valid status or revoked status. When a VC certificate is revoked, the corresponding blockchain cannot identify its first event information, and therefore cannot perform the corresponding digital asset processing operations.

[0055] S202 uses a global identity identifier and VC credential set to process digital assets within the corresponding blockchain via a cross-chain bridge, and obtains the digital asset processing result.

[0056] Specifically, the metaverse space forwards the first event information to the cross-chain bridge. The cross-chain bridge has data forwarding capabilities; it can not only be used for data interaction between multiple blockchains, but also forward the first event information from the metaverse space to the corresponding blockchain. Then, based on the global identity identifier and VC credential set, the corresponding blockchain is invoked to process digital assets within the blockchain, obtaining the digital asset processing result.

[0057] In some embodiments, calling the corresponding blockchain to process digital assets based on the global identity identifier and VC certificate set means calling the corresponding blockchain to verify the global identity identifier and VC certificate set. If both the global identity identifier and VC certificate set are verified, then the corresponding blockchain is called to process the digital assets.

[0058] It should be noted that, in order to improve the accuracy of digital asset processing, each blockchain corresponding to each blockchain identifier included in the first event information needs to perform a verification operation. For example, if a digital asset is added within blockchain A, then blockchain A needs to verify the global identity identifier and the VC certificate issued to the user by blockchain A in the VC certificate set. Similarly, if a cross-chain transfer of digital assets is performed between blockchain A and blockchain B, then blockchain A needs to verify the global identity identifier and the VC certificate issued to the user by blockchain A in the VC certificate set, and blockchain B also needs to verify the global identity identifier and the VC certificate issued to the user by blockchain B in the VC certificate set.

[0059] In some embodiments, calling the corresponding blockchain to verify the global identity identifier and VC credential set can be to verify whether the global identity identifier is the same as any global identity identifier registered in the identity chain, and to verify whether the VC credential in the VC credential set corresponding to the blockchain is a standard VC credential stored in the blockchain that matches the user's global identity identifier.

[0060] In other embodiments, a user's global identity can be bound to standard user information and stored in an identity chain within the metaverse space. The first event information obtained by the blockchain contains not only the user's global identity but also the user information bound to that global identity. When the corresponding blockchain is invoked to verify the global identity, it can also verify whether the user information matches the standard user information bound to that global identity in the identity chain. If they do not match, it indicates that the user information in the first event information is counterfeit, and the global identity fails verification. If they match, the global identity passes verification. In practical applications, user information can be the user's name, facial image, etc., and is not limited here. For example, a user's global identity can be bound to the user's standard facial image and stored in the identity chain within the metaverse space. After the corresponding blockchain obtains the global identity and facial image from the first event information, it determines whether the user's facial image matches the standard facial image corresponding to that global identity in the identity chain. If they do not match, the global identity fails verification; if they match, the global identity passes verification.

[0061] In other embodiments, the corresponding blockchain is invoked to verify the global identity identifier and VC credential set. This can also be to verify whether the data format of the global identity identifier and VC credential set is compliant, such as whether the first digit of the global identity identifier is 1, whether the global identity identifier has expired, whether the VC credential in the VC credential set has expired, and whether the VC credential has the operation permissions that match the operation type.

[0062] In other embodiments, to improve the security of the first event information transmission and the accuracy of verification, when generating the first event information corresponding to the digital asset processing operation, the terminal can also encrypt the first event information using the private key corresponding to the global identity identifier. The metaverse space then calls the corresponding blockchain to verify the global identity identifier and the VC credential set. Alternatively, the terminal can call the corresponding blockchain to decrypt the encrypted first event information using the public key corresponding to the global identity identifier before verifying the global identity identifier and the VC credential set. The public key corresponding to the global identity identifier can be distributed to multiple blockchains within the metaverse space after the user registers their identity with the identity chain, or it can be read by the corresponding blockchain from the identity chain's database.

[0063] In some embodiments, the first event information may also include the operation type of the digital asset processing operation. If the operation type is a digital asset addition operation within a single blockchain, wherein the digital asset addition operation refers to adding a user's digital asset on the target chain, then the digital asset processing is performed within the corresponding blockchain using a cross-chain bridge, including: using the cross-chain bridge to forward the first event information to the target chain and calling the target chain to perform the digital asset addition operation.

[0064] If the operation type of digital asset processing is a digital asset destruction operation within a single blockchain, where the digital asset destruction operation refers to destroying a user's digital asset on the target chain, then the digital asset processing is performed within the corresponding blockchain using a cross-chain bridge, including: using the cross-chain bridge to forward the first event information to the target chain and calling the target chain to perform the digital asset destruction operation.

[0065] In some embodiments, the first event information may also include the operation type of digital asset processing operation. If the operation type is a cross-chain transfer operation of digital assets, where the cross-chain transfer operation of digital assets refers to transferring a user's digital assets from the source chain to the target chain, then a cross-chain bridge is used to process the digital assets between the source chain and the target chain. For example, the first event information is first forwarded to the source chain using a cross-chain bridge, and after the digital asset locking operation is performed on the source chain, a second event information related to the locking operation of the source chain is generated on the source chain. Then, the second event information is forwarded to the target chain using a cross-chain bridge, and a new digital asset operation is performed on the target chain.

[0066] In some embodiments, after the first event information is forwarded to the cross-chain bridge in the metaverse space, the cross-chain bridge can be invoked to verify the authenticity of the first event information. If the verification is successful, the first event information in the metaverse space can be forwarded to the corresponding blockchain.

[0067] Specifically, when the digital asset processing operation is a cross-chain transfer operation, verifying the authenticity of the first event information means verifying whether the digital asset processing operation actually occurred on the source chain and the target chain. This can be determined by verifying whether the digital asset transferor in the first event information is the source chain identifier and whether the digital asset transferee in the first event information is the target chain identifier. If the digital asset transferor in the first event information is the source chain identifier and the digital asset transferee is the target chain identifier, then the authenticity of the first event information is verified.

[0068] When a digital asset processing operation is performed within a single blockchain, verifying the authenticity of the first event information means verifying whether the digital asset processing operation actually occurred on the target chain. This can be determined by verifying whether the blockchain identifier in the first event information is the target chain identifier. If the blockchain identifier in the first event information is the target chain identifier, then the authenticity of the first event information is verified.

[0069] Furthermore, for both cross-chain transfer operations and digital asset processing operations within a single blockchain, the verification methods for the authenticity of the first event information can also include: the terminal holding the private key corresponding to its own global identity identifier; the terminal generating a hash digest of the first event information and using the private key to generate a digital signature from the digest; sending the first event information, digital signature, and global identity identifier together to the metaverse space; the metaverse space sending the received information to the cross-chain bridge; the cross-chain bridge querying the corresponding public key bound to the global identity identifier, generating a hash digest of the first event information, using the public key to perform an inverse operation on the digital signature to restore the original hash digest of the terminal, and comparing whether the hash digest newly generated by the cross-chain bridge is consistent with the restored original hash digest; if they are consistent, it means that the first event information has not been tampered with during transmission, and the triggering object of the first event information is the user corresponding to the global identity identifier; therefore, the authenticity of the first event information is verified.

[0070] In some embodiments, after processing digital assets within the corresponding blockchain using a cross-chain bridge and obtaining the digital asset processing result, the digital asset processing result can be directly associated with the digital asset storage unit on the corresponding blockchain with a global identity identifier. It can be understood that the digital asset storage unit can actually be displayed on the user's terminal in the form of an account, that is, the user can clearly see the increase, decrease or transfer of digital assets on the account of the corresponding blockchain.

[0071] In the above scheme, in response to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, the system obtains the first event information corresponding to the digital asset processing operation. The metaverse space includes multiple blockchains, which interact with each other via cross-chain bridges. The first event information includes the user's global identity identifier, at least one blockchain identifier, and the user's permission verification VC credential set. The global identity identifier is a unified identifier used by multiple blockchains to identify the user. The VC credential set includes VC credentials pre-issued to the user by the blockchain corresponding to at least one blockchain identifier; these VC credentials serve as proof of the user's permissions within the corresponding blockchain. Using the global identity identifier and the VC credential set, the cross-chain bridge is used to process the digital asset within the corresponding blockchain, yielding the processing result. Throughout this process, there is no need to query for the corresponding user identifier from a large number of user identifiers, nor is it necessary to perform digital asset processing operations separately for each blockchain. Instead, based on the global identity identifier and the VC credential set, the cross-chain bridge can be used to process the digital asset in one go within the corresponding blockchain, achieving the effect that digital assets and user identity data can directly interact between multiple blockchains. The entire digital asset processing process is simple, time-saving, and its processing efficiency is greatly improved.

[0072] In other embodiments of this application, the metaverse space also includes an identity chain; the identity chain is used to issue global identity identifiers to users; Prior to responding to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, the method further includes: In response to a user's identity registration operation within the metaverse space, the identity chain is invoked to issue a global identity identifier to the user; in response to a user's registration operation for a digital asset storage unit on any blockchain within the metaverse space, the corresponding blockchain is invoked to allocate a digital asset storage unit to the user and associate the digital asset storage unit with the global identity identifier; in response to a user's VC application operation on any blockchain within the metaverse space, based on the global identity identifier and the address of the digital asset storage unit associated with the global identity identifier on the corresponding blockchain, the corresponding blockchain is invoked to issue a VC certificate for the user.

[0073] A digital asset storage unit is a unit used to store digital assets, and each digital asset storage unit has a corresponding global identity identifier. Each blockchain has multiple digital asset storage units. In practical applications, a digital asset storage unit can be considered as a user's account. The digital assets are still stored within the corresponding blockchain, and the concept of digital asset storage units is used to allocate digital assets within the corresponding blockchain to the users corresponding to those storage units.

[0074] Specifically, since the user's digital asset processing process needs to be implemented through a global identity identifier and a VC credential set, and the user's digital asset processing process is to process the digital assets associated with the address of the user's digital asset storage unit on the blockchain, before the metaverse space responds to the user's digital asset processing operation triggered by at least one blockchain within the metaverse space, it is also necessary to issue a global identity identifier, a digital asset storage unit, and a VC credential set to the user. In addition, the user's global identity identifier can be bound to the user's digital asset storage unit on each blockchain in order to manage and verify the user's identity on the blockchain, while realizing identity-related permission control and operation.

[0075] More specifically, firstly, the user triggers an identity registration operation within the interactive interface of the metaverse space displayed on the terminal. The terminal uploads the identity registration request corresponding to this operation to the metaverse space. The metaverse space receives the user's identity registration request within the metaverse space and calls the identity chain to issue a global identity identifier to the user. This global identity identifier is a unique and decentralized identity identifier for the user within the metaverse space. Regardless of which blockchain, the user's identity can be identified through this global identity identifier. This global identity identifier can be stored in the identity chain for subsequent verification.

[0076] After obtaining their corresponding global identity, users can register their own digital asset storage units on various blockchains to index their own digital assets. That is, when a user triggers a digital asset storage unit registration operation for any blockchain within the interactive interface of the metaverse space displayed on the terminal, the terminal uploads the digital asset storage unit registration request corresponding to the digital asset storage unit registration operation to the metaverse space. The metaverse space receives the user's digital asset storage unit registration request within the metaverse space, calls the corresponding blockchain to issue a digital asset storage unit to the user, and then associates the digital asset storage unit with the global identity. In other words, a digital asset storage unit is issued to the user within the corresponding blockchain, and this digital asset storage unit can be associated with the user's digital assets within that blockchain.

[0077] To improve the reliability of digital asset processing within the metaverse space, it is necessary not only to identify users using their global identity but also to determine whether users have the authority to perform a specific operation on the corresponding blockchain. Therefore, given a user's global identity and multiple digital asset storage units corresponding to different blockchains, the user can trigger a VC application operation for any blockchain within the metaverse space's interactive interface displayed on the terminal. The terminal uploads the VC application request to the metaverse space, which contains the user's global identity and the address of the digital asset storage unit associated with that global identity on the corresponding blockchain. The metaverse space receives the user's VC application request and, based on the global identity and the associated digital asset storage unit address, issues a VC certificate to the user on the corresponding blockchain. This VC certificate serves as proof of the user's authority within that blockchain. Furthermore, the corresponding blockchain can record the issued VC certificate and associate it with the corresponding global identity for storage.

[0078] In some embodiments, during the process of issuing a global identity token to a user by invoking the identity chain, the metaverse space needs to verify the user's identity registration request. Generally, the identity registration request contains the user's ordinary identity token. The metaverse space needs to call the identity chain based on this identity token to query whether the identity token has a previous record of being blocked due to violations. In addition, the identity chain of the metaverse space can also communicate with a reliable third-party identity authority to ensure that the user corresponding to the identity token has no bad records in real life.

[0079] In some embodiments, during the process of invoking the corresponding blockchain to allocate digital asset storage units to users, the digital asset storage unit registration request obtained by the metaverse space contains the user's global identity identifier. The metaverse space calls the corresponding blockchain to verify this global identity identifier. If the verification is successful, the corresponding blockchain is invoked to allocate digital asset storage units to the user. The means of invoking the corresponding blockchain to verify the global identity identifier include: matching the obtained global identity identifier with multiple registered global identity identifiers stored in the identity chain to verify whether the global identity identifier is any of the registered global identity identifiers in the identity chain. If there is a registered global identity identifier in the identity chain that is the same as the obtained global identity identifier, it indicates that the blockchain's verification of the global identity identifier is successful, and the corresponding blockchain can be invoked to allocate digital asset storage units to the user.

[0080] In some embodiments, before issuing VC credentials to users, the blockchain also needs to register its identity. Specifically, the person in charge of the blockchain triggers the identity registration operation within the interactive interface of the metaverse space displayed on their terminal. The terminal uploads the identity registration request, which contains the corresponding blockchain identifier, to the metaverse space. The metaverse space receives the blockchain's identity registration request and invokes the identity chain to issue a global identity identifier to the blockchain corresponding to that identifier. After the metaverse space issues a global identity identifier to the blockchain, the blockchain can then join the VC credential issuance hall within the metaverse space, enabling it to issue VC credentials to users.

[0081] In some embodiments, based on the global identity identifier in the VC application request and the address of the digital asset storage unit associated with the global identity identifier on the corresponding blockchain, the corresponding blockchain is invoked to issue a VC credential to the user. This includes: invoking the corresponding blockchain to verify the global identity identifier in the VC application request and the address of the digital asset storage unit associated with the global identity identifier on the corresponding blockchain; if the global identity identifier in the VC application request matches any global identity identifier registered in the identity chain, and the address matches the address of any digital asset storage unit associated with the corresponding blockchain, then the corresponding blockchain is invoked to allocate a VC credential to the user.

[0082] In some embodiments, the VC application request may also include one or more of the user's permission scope within the corresponding blockchain, the VC certificate's validity period, and security authentication information. It should be noted that the permission scope, VC certificate's validity period, and other information included in the VC application request can be configured by the user in the VC application request, or can be determined randomly or according to a preset rule by the corresponding blockchain when generating the VC certificate.

[0083] The user's permission scope within the corresponding blockchain is used to restrict the user's execution permissions within the corresponding blockchain. For example, the user's permission scope within the corresponding blockchain may be related to the digital asset identifier, that is, it may include whether the user can perform processing operations on the digital asset corresponding to a certain digital asset identifier on the corresponding blockchain. The user's permission scope within the corresponding blockchain may also be related to the operation type of the digital asset processing operation, that is, it may include whether the user can perform digital asset processing operations corresponding to a certain operation type on the corresponding blockchain, etc., without being limited here.

[0084] The VC certificate expiration period is used to limit the validity period of the generated VC certificate. When this expiration period is exceeded, the corresponding blockchain cannot verify the VC certificate.

[0085] Security authentication information can be used to determine whether a user's VC application request is complete and transmitted correctly. In other words, upon receiving a VC application request, the metaverse space not only verifies the global identity identifier and the address of the digital asset storage unit associated with that global identity identifier on the corresponding blockchain, but also verifies the security authentication information. After successful verification, the corresponding blockchain authorizes the user with the blockchain's VC credential.

[0086] The security authentication information can be signature-based authentication information. This signature-based authentication information refers to a piece of authentication information generated by the terminal using its own global identity identifier's private key after hashing the digital asset information. This data can also be encrypted using an encryption algorithm to form encrypted authentication information. This digital asset information is metadata during digital asset processing, such as the digital asset identifier to be authorized and the quantity of digital assets held corresponding to that identifier.

[0087] The blockchain verifies the signature authentication information as follows: It uses the public key corresponding to the global identity identifier to perform an inverse operation on the decrypted signature authentication information, obtaining a hash digest of the restored authentication information. Simultaneously, the VC application certificate also contains digital asset information. The blockchain generates a hash digest of the digital asset processing information and compares it with the restored hash digest. If they match, it indicates that the digital asset information has not been tampered with, and the signature authentication information is verified successfully. The public key corresponding to the global identity identifier can be distributed to multiple blockchains within the metaverse space after the user registers their identity with the identity chain, or it can be retrieved from the database of the corresponding blockchain.

[0088] Among them, the security authentication information can also be a CMAC (Cipher-based Message Authentication Code) tag. The blockchain and the user's terminal share a set of AES (Advanced Encryption Standard) keys. The digital asset information is segmented and sent into the AES key for iterative calculation, outputting a CMAC tag. The digital asset information and the CMAC tag are then sent together to the metaverse space.

[0089] The blockchain verifies the encrypted information as follows: the blockchain in the metaverse space recalculates the CMAC tag of the digital asset information based on the corresponding AES key, and then compares the two CMAC tags. If they match, it means that the data has not been tampered with and the key held by the terminal is legitimate, and the verification of the signature authentication information is successful.

[0090] In some embodiments, when a user presents a VC certificate corresponding to the blockchain within the metaverse space, the blockchain can verify the VC certificate to determine whether it can perform cross-chain transfer, addition, or destruction operations on the digital assets in the digital asset storage unit associated with the global identity identifier on the corresponding blockchain.

[0091] In some embodiments, the user's VC application request may also include the expiration date of the user's global identity. If the user triggers the VC application request later than the expiration date of the user's global identity, the VC application request triggered by the user is invalid.

[0092] In some embodiments, from Figure 3 As can be seen, the Identity Chain is responsible for providing a user's global identity identifier when issuing and verifying VC credentials on Blockchain A. Blockchain A can issue VC credentials to users when they apply for them, and it can also verify the VC credentials presented by users when they perform digital asset processing operations. The Identity Chain, Blockchain A, and users interact through the VC credentials of Blockchain A to achieve reliable application and use of VC credentials.

[0093] In the above embodiments, before responding to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, it is necessary to assign the user a corresponding global identity identifier, a digital asset storage unit on the corresponding blockchain, and a VC certificate for the corresponding blockchain. This ensures that when the user subsequently triggers a digital asset processing operation within the metaverse space, any blockchain can verify a unified global identity identifier to determine whether the user has the authority to process the digital assets associated with the digital storage unit within that blockchain. Therefore, based on the permission mapping mechanism between the global identity identifier and the VC certificate, centralized control of multi-chain assets by the metaverse identity can be achieved, solving the ownership authentication problem in the metaverse space.

[0094] In other embodiments of this application, at least one blockchain identifier includes the source chain identifier of the source chain and the target chain identifier of the target chain; the VC credential set includes a first VC credential pre-issued to the user by the source chain and a second VC credential pre-issued to the user by the target chain. By leveraging a global identity identifier and VC credential set, and utilizing cross-chain bridges, digital assets can be processed within the corresponding blockchain, including: The first event information is forwarded to the source chain via a cross-chain bridge; the source chain is then invoked to verify the global identity identifier and the first VC credential in the first event information; if the verification is successful, the source chain is invoked to lock the digital asset associated with the source address and generate the second event information; the second event information is forwarded to the target chain via a cross-chain bridge; the target chain is invoked to verify the global identity identifier and the second VC credential; if the verification is successful, the target chain is invoked to perform an add operation on the digital asset associated with the target address.

[0095] The second event information includes at least a global identity identifier and a second VC certificate; the source address is the address of the digital asset storage unit of the global identity identifier on the source chain; the amount of newly added digital assets in the target chain is equal to the amount of locked digital assets in the source chain; and the target address is the address of the digital asset storage unit of the global identity identifier on the target chain.

[0096] In this cross-chain transfer operation, the source chain is the blockchain that actively transfers digital assets. The target chain is the blockchain that passively receives the digital assets transferred from the source chain. In other words, the cross-chain transfer operation is used to transfer digital assets from the source chain to the target chain.

[0097] Specifically, this embodiment describes a cross-chain transfer operation of digital assets performed by a user on two blockchains. This operation can be divided into a digital asset locking operation on the source chain and a digital asset addition operation on the target chain. These two stages can be linked through a cross-chain bridge. For example, transferring digital assets from blockchain A to blockchain B can be divided into a digital asset locking operation on blockchain A and a digital asset addition operation on blockchain B.

[0098] More specifically, when a user's cross-chain transfer operation of digital assets between two blockchains within the metaverse space is captured, the metaverse space responds to the user's cross-chain transfer operation by acquiring the first event information corresponding to the operation. This first event information includes the user's global identity identifier, the source chain's source chain identifier, the target chain's target chain identifier, and the user's permission verification VC credential set. This VC credential set contains a first VC credential pre-issued to the user by the source chain and a second VC credential pre-issued to the user by the target chain. The first event information also identifies the source chain as the digital asset transferee and the target chain as the digital asset transferor.

[0099] The metaverse space sends the first event information to the cross-chain bridge; the cross-chain bridge forwards the first event information to the source chain; the source chain locks the digital assets associated with the source address and generates the second event information, which includes relevant information about the digital asset transfer, such as the second VC certificate, digital asset identifier, digital asset metadata, the amount of digital assets locked in the source chain, and the user's global identity identifier, and forwards the second event information to the target chain; the target chain performs a new asset operation on the digital assets associated with the target address; during this process, it is necessary to control the amount of new digital assets in the target chain to be equal to the amount of digital assets locked in the source chain, so as to ensure that the total amount of digital assets in the metaverse space remains unchanged.

[0100] Furthermore, there may be instances of impersonation or unauthorized processing within the metaverse space. Therefore, all corresponding blockchains need to verify the received event information before processing it.

[0101] Specifically, after forwarding the first event information to the source chain, the metaverse space needs to verify whether the source chain can process the first event information. That is, it calls the source chain to verify the global identity identifier and the first VC certificate in the first event information respectively. If the verification is successful, it means that the source chain can process the first event information. At this time, the source chain is called to lock the digital assets associated with the source address.

[0102] The method for calling the source chain to verify the global identity identifier and the first VC credential in the first event information may include: determining whether the global identity identifier matches any global identity identifier registered in the identity chain, and whether the first VC credential matches the standard VC credential associated with the user identity identifier stored in the source chain; if the global identity identifier matches any global identity identifier registered in the identity chain, and the first VC credential matches the standard VC credential associated with the user identity identifier stored in the source chain, then calling the source chain to lock the digital asset associated with the source address.

[0103] The method of calling the source chain to verify the global identity identifier and the first VC credential in the first event information may also include: calling the source chain to verify the data format in the global identity identifier and the first VC credential in the first event information. If the data format is consistent with the preset format, the verification is passed. For example, whether the first digit of the global identity identifier is 1, whether the global identity identifier has expired, whether the first VC credential has expired, and whether the first VC credential has the operation permissions that match the operation type.

[0104] The first event information also includes user information bound to the global identity identifier. The method of calling the source chain to verify the global identity identifier and the first VC credential in the first event information may also include: verifying whether the user information is consistent with the standard user information bound to the global identity identifier in the identity chain. If they are inconsistent, it means that the user information in the first event information is fake information and the global identity identifier fails the verification. If they are consistent, the global identity identifier passes the verification.

[0105] After forwarding the second event information to the target chain through the cross-chain bridge, the metaverse space also needs to verify whether the target chain can process the second event information. That is, it calls the target chain to verify the global identity identifier and the second VC certificate in the second event information respectively. If the verification is successful, it means that the target chain can process the second event information. At this time, the target chain is called to perform a new operation on the digital asset associated with the target address.

[0106] The method for calling the target chain to verify the global identity identifier and the second VC credential in the second event information may include: determining whether the global identity identifier matches any global identity identifier registered in the identity chain, and whether the second VC credential matches the standard VC credential associated with the user identity identifier stored in the target chain. If the global identity identifier matches any global identity identifier registered in the identity chain, and the second VC credential matches the standard VC credential associated with the user identity identifier stored in the target chain, then the target chain is called to perform an add operation on the digital asset associated with the target address.

[0107] Similarly, the method of calling the target chain to verify the global identity identifier and the second VC credential in the second event information can also include the target chain verifying the user information bound to the global identity identifier in the second event information, and verifying the data format in the global identity identifier and the second VC credential. This is similar to the method of calling the source chain to verify the global identity identifier and the first VC credential in the first event information, and will not be elaborated here.

[0108] In some embodiments, calling the source chain to lock the digital asset associated with the source address means transferring the digital asset associated with the source address to the address of a specified locking contract and marking the digital asset as pending transfer.

[0109] In some embodiments, the second event information generated in the source chain further includes a first identifier, which indicates whether the digital asset associated with the preset address in the source chain is in a locked state. If the digital asset associated with the preset address in the source chain is in a locked state, the first identifier is 1; if the digital asset associated with the preset address in the source chain is not in a locked state, the first identifier is 0.

[0110] In some embodiments, during the process of forwarding the second event information to the target chain via the cross-chain bridge, the cross-chain bridge can also verify the legality of the digital assets locked in the second event information, the legality of the cross-chain transfer operation, and the authenticity of the global identity identifier.

[0111] This verification process can be implemented through PoS (Proof of Stake) or DPoS (Delegated Proof of Stake) consensus mechanisms. Specifically, the second event information undergoes PoS / DPoS consensus verification within the source chain to generate a valid block header with a consensus signature. After the second event information is sent to the cross-chain bridge, the cross-chain bridge verifies whether the consensus signature of the block header is accurate, thereby determining the legality of the locked digital assets and the legality of the cross-chain transfer operation. At the same time, the cross-chain bridge can also verify whether the global identity identifier is any global identity identifier registered in the identity chain to verify the authenticity of the global identity identifier.

[0112] Furthermore, the verification process for the legality of locked digital assets can also query the source chain to check whether the digital asset identifier in the received second event information is the same as the locked digital asset in the source chain, whether the digital asset identifier of the locked digital asset is a legitimate digital asset identifier, and whether the digital asset identifier of the locked digital asset has indeed been transferred to the designated address and has not been destroyed or locked repeatedly in advance. The verification process for the legality of cross-chain transfer operations can be based on the first VC certificate and the second VC certificate to verify whether the user can perform the corresponding digital asset processing operation in the corresponding blockchain. For example, the validity period and permissions in the first VC certificate and the second VC certificate can be used to verify whether the user can perform the corresponding digital asset processing operation in the corresponding blockchain.

[0113] In some embodiments, each node of the cross-chain bridge performs hash digest processing on the second event information and signs it using the private key corresponding to the global identity identifier, thereby obtaining a signature set corresponding to all nodes of the cross-chain bridge. The second event information and the signature set are then sent together to the contract node of the target chain. The contract node of the target chain verifies the signature set; that is, the contract node of the target chain iterates through each signature, performs an inverse operation on the signature set using the public key corresponding to the global identity identifier, restores a hash digest, and re-hash digests the second event information. It then determines whether the two hash digests are consistent. If they are consistent, the signature corresponding to that node is determined to be valid. Furthermore, the ratio between the total number of valid signatures and the number of nodes of the cross-chain bridge is checked to see if it is greater than a preset threshold. If it is greater, it is confirmed that all signatures sign the same locked data of digital asset, and there is no tampering or replacement of the message. At this point, the smart contract of the target chain performs the add operation on the digital asset associated with the target address.

[0114] In the above embodiments, during the cross-chain processing of digital assets using a cross-chain bridge, the global identity identifier and the first VC certificate in the first event information are verified by calling the source chain, and the global identity identifier and the second VC certificate are verified by calling the target chain. Only when both the global identity identifier and the corresponding VC certificate are verified can the target chain perform subsequent operations, making the digital asset processing between the source chain and the target chain more secure.

[0115] In other embodiments of this application, the second event information also includes a first VC certificate, a first signature, and a first identifier; the first signature is a signature signed by the source chain to lock the corresponding digital asset; the first identifier indicates whether the digital asset associated with the preset address in the source chain is in a locked state; The second event information is forwarded to the target chain via a cross-chain bridge, including: The first identifier, first signature, global identity identifier, first VC credential, and second VC credential are verified through a cross-chain bridge. If the verification is successful, the second event information is forwarded to the target chain through the cross-chain bridge.

[0116] Specifically, after the source chain locks the digital asset associated with the source address, it generates second event information. This second event information includes at least a global identity identifier, a second VC certificate, a first VC certificate, a first signature, and a first identifier. The metaverse space sends this second event information to the cross-chain bridge, which verifies it. Specifically, the cross-chain bridge verifies the first identifier, the first signature, the global identity identifier, the first VC certificate, and the second VC certificate. If the first identifier indicates that the corresponding digital asset is locked, the first signature indicates that the digital asset operation is correct, the global identity identifier matches any registered global identity identifier in the identity chain, the second VC certificate matches the standard VC certificate corresponding to the global identity identifier of the stored source chain, and the first VC certificate matches the standard VC certificate corresponding to the global identity identifier of the stored target chain, then the second event information is forwarded to the target chain via the cross-chain bridge.

[0117] In some embodiments, the process by which the cross-chain bridge verifies the second event information is essentially a verification of the legality of the locked digital assets, the legality of the transfer operation, and the authenticity of the global identity identifier.

[0118] Specifically, the legitimacy of locked digital assets can be verified using one or more of the following methods.

[0119] Verification criteria: The second event information generated when the source chain locks the corresponding digital asset also includes the first identifier, digital asset identifier, metadata hash, the address of the source chain's contract node, the block hash of the operation to lock the digital asset, and Merkel proof. The cross-chain bridge's verification node obtains the digital asset transfer receipt and logs for the locked digital asset through the source chain's light node or RPC (Remote Procedure Call) interface.

[0120] Verification steps: ① Verify whether the locked digital assets have been confirmed by the source chain consensus (reaching finality, such as the number of BFT (Byzantine Fault Tolerance) confirmations or PBFT (Practical Byzantine Fault Tolerance) confirmations in blockchain). ② Verify whether the locked digital assets have indeed been transferred to the address of the specified locking contract and have not been destroyed or locked repeatedly in advance; this can be verified through the first identifier.

[0121] ③ Verify that the metadata of the locked digital assets (such as name, attributes, URI (Uniform Resource Identifier)) conforms to the standards of digital assets supported by the target chain (such as ACS (AElfContract Standard, an AElf blockchain contract specification)) to prevent cross-chain minting of illegal digital assets.

[0122] ④ The Merkel proof serves as proof of the operation of locking the corresponding digital asset on the source chain. The cross-chain bridge verifies the Merkel proof to determine whether the operation of locking the corresponding digital asset on the source chain is genuine. If each node in the cross-chain bridge determines that the operation of locking the corresponding digital asset on the source chain is genuine, the cross-chain bridge will proceed. Failure handling: If any of the above verification conditions fail, the cross-chain bridge will refuse to forward the second event information to the target chain and will record the exception log.

[0123] The legitimacy of a transfer operation can be verified using one or more of the following methods.

[0124] Verification criteria: The second event information includes the user's first VC certificate, second VC certificate, operation timestamp, operation type (such as cross-chain transfer), and the first signature of the operation to lock the corresponding digital asset on the source chain.

[0125] Verification steps: ① Verify whether the first signature was signed by the private key corresponding to the global identity identifier of the holder when locking the digital asset in the source chain; ② Verify the validity of the first VC certificate: Check whether the certificate issuer (the contract node of the source chain) is trustworthy, whether the certificate has expired, the certificate status (check whether the first VC certificate has been revoked through the global identity identifier or the certificate status contract), and whether the certificate statement contains the permission to transfer digital assets. ③ Verify the validity of the second VC certificate: Confirm whether the user's global identity has a legal digital asset storage unit on the target chain, whether the certificate statement contains digital asset transfer permissions, and whether the second VC certificate has not expired or been revoked; ④ Verify that the operation type matches the scope of permissions declared in the first VC certificate and the second VC certificate (e.g., only allowing the transfer of a specific set of digital assets). ⑤ Verify that the operation timestamp is within the allowed time window configured in the cross-chain bridge to prevent replay attacks.

[0126] Failure handling: If any of the above verification conditions are not met, the cross-chain bridge will refuse to forward the second event information to the target chain and will record the exception log.

[0127] In some embodiments, such as Figure 4As shown, the entire cross-chain bridge also belongs to a decentralized network, containing a set of validator nodes, relay nodes, observer nodes, gateway nodes, and audit nodes. The source chain has a first contract node, and the target chain has a second contract node. The gateway node set includes at least the first gateway node set corresponding to the source chain and the second gateway node set corresponding to the target chain. These nodes collaborate to achieve cross-chain asset and data transmission and management, and their node functions are as follows: Verification Node Set: Verifies the authenticity and legality of received event information through PoS or DPoS consensus mechanisms, and verifies that the global identity identifier matches any global identity identifier registered in the identity chain.

[0128] Relay node set: Responsible for listening to and transmitting cross-chain event information. They monitor cross-chain transfer operations on the source chain and transmit cross-chain transfer-related event information to the target chain to trigger corresponding operations on the target chain.

[0129] Observer node set: Responsible for monitoring specific event information on the blockchain (such as the source chain and the target chain) and reporting it to other nodes or systems. The observer node set does not directly participate in the execution of cross-chain transfer operations, but plays the role of monitoring and verifying the state changes of cross-chain transfer operations.

[0130] The first and second gateway node sets are the entry points connecting the corresponding blockchains. During cross-chain transfer operations, the first gateway node set is responsible for handling the locking and unlocking of digital assets across chains. The second gateway node set receives event information from the source chain and executes corresponding operations on the target chain.

[0131] Audit node set: responsible for reviewing and verifying the legality and correctness of cross-chain bridge operations. They can independently recalculate or verify relevant information of cross-chain transfer operations to ensure that there are no improper operations or errors.

[0132] First and second contract nodes: Execute predefined logic to ensure the automation and security of cross-chain transfer operations. They collaborate with other node types (such as validator nodes and gateway nodes) to complete the core functions of the cross-chain bridge; their contract nodes are not deployed independently.

[0133] When the overall structure of this cross-chain bridge is applied to the cross-chain asset transfer operation in this embodiment, each node in the cross-chain bridge performs the following steps: The contract node of the source chain is used to receive the first event information sent by the first gateway node set, and to verify the global identity identifier and the first VC certificate in the first event information respectively. If the global identity identifier matches any global identity identifier registered in the identity chain, and the first VC certificate matches the standard VC certificate corresponding to the global identity identifier pre-stored in the source chain, then the digital asset associated with the source address is locked, and the second event information is generated and forwarded to the first gateway node set.

[0134] First gateway node set: Used to send second event information to relay node set.

[0135] Relay Node Set: The relay node set is used to transmit the second event information between the first gateway node set and the second gateway node set, and to send the second event information to the verification node set.

[0136] Second gateway node set: used to send the second event information to the second contract node.

[0137] The contract nodes of the target chain are used to verify the global identity identifier and the second VC certificate respectively. If the global identity identifier matches any global identity identifier registered in the identity chain, and the second VC certificate matches the VC certificate corresponding to the global identity identifier pre-stored in the target chain, then the target chain is invoked to perform the addition operation on the digital asset associated with the target address.

[0138] Observation node set: Used to monitor the first gateway node set and the second gateway node set, and send the monitored second event information to the verification node set.

[0139] The verification node set is used to verify the first identifier, first signature, global identity identifier, first VC credential, and second VC credential in the second event information, obtain the verification results, and feed back the verification results to the corresponding node set.

[0140] The audit node set is used to verify whether the interaction process between the verification node set, relay node set, observation node set, gateway node set, source chain contract nodes, and target chain contract nodes meets the preset interaction conditions.

[0141] In the above embodiments, by verifying the first identifier, first signature, global identity identifier, first VC certificate and second VC certificate respectively through the cross-chain bridge, it can be determined whether the second event information can be forwarded to the target chain through the cross-chain bridge, making the process of digital asset processing on the target chain more accurate and secure.

[0142] In other embodiments of this application, after invoking the target chain to perform a new operation on the digital asset associated with the target address, the method further includes: The target chain is invoked to generate third event information corresponding to the digital asset; the third event information includes at least a second identifier; the second identifier indicates whether the addition operation of the digital asset associated with the target address has been completed within the target chain. The third event information is forwarded to the source chain via a cross-chain bridge; the source chain is invoked to verify the second identifier in the third event information; if the second identifier indicates that the target chain has completed the addition operation of the digital asset associated with the target address, the source chain is invoked to destroy the digital asset locked in the source chain or keep it locked.

[0143] Specifically, after the target chain completes the new operation on the digital asset associated with the target address, it calls the target chain to generate the third event information corresponding to the digital asset. The third event information represents the processing result of the target chain on the digital asset and is sent to the cross-chain bridge. The cross-chain bridge forwards the third event information to the source chain. The locking contract in the source chain records the completion of this digital asset transfer and calls the source chain to destroy or keep the locked digital asset in the source chain in a locked state to prevent further control of the digital asset.

[0144] Furthermore, the third event information includes at least a second identifier; the second identifier indicates whether the addition operation of the digital asset associated with the target address has been completed within the target chain. The source chain needs to verify the second identifier in the third event information to determine whether the digital asset transfer has been completed. If the second identifier indicates that the addition operation of the digital asset associated with the target address has been completed within the target chain, then the digital asset transfer has been completed. The source chain can be called to destroy or keep the locked digital assets in the source chain in a locked state.

[0145] In some embodiments, the means of destroying digital assets locked in the source chain include: calling the source chain's built-in destruction interface to destroy the digital assets locked in the source chain; or, transferring the digital assets locked in the source chain to a standard zero address on the source chain, which has no permission to transfer any digital assets out; or, constructing a destruction script to mark the digital assets locked in the source chain as permanently destroyed, and permanently deleting the ownership record of the corresponding digital assets on the source chain. The specific means of destroying digital assets are not limited here.

[0146] In some embodiments, the means of keeping digital assets locked in the source chain in a locked state include: setting a lock duration for the digital assets locked in the source chain, and waiting for the lock duration to expire before processing operations can be performed on the digital assets; or setting an unlocking condition for the digital assets locked in the source chain, for example, the digital assets can only be unlocked after 2 / 3 of the blockchains in the metaverse space have authorized it. No specific means of keeping digital assets locked in a locked state are limited herein.

[0147] In some embodiments, the third event information also includes a first VC credential and a global identity identifier. While calling the source chain to verify the second identifier in the third event information, the source chain can also be called to verify the first VC credential and the global identity identifier contained in the third event information. That is, if the global identity identifier matches any global identity identifier registered in the identity chain, the first VC credential matches the standard VC credential corresponding to the global identity identifier pre-stored in the source chain, and the second identifier indicates that the target chain has completed the addition operation of the digital asset associated with the target address, then the source chain will destroy the digital asset locked in the source chain or keep it locked.

[0148] In some embodiments, the third event information further includes a second signature, which is a signature signed by the target chain for adding the corresponding digital asset. Specifically, the contract node of the target chain performs hash digest processing on the third event information and signs the hash digest of the third event information using the private key corresponding to the global identity identifier to obtain the second signature of the target chain. Then, the third event information and the second signature are forwarded to the source chain through a cross-chain bridge. The source chain is called to perform inverse operation verification on the second signature using the public key corresponding to the global identity identifier to obtain the restored hash digest information. The source chain is then called to perform hash digest processing on the third event information again to obtain new hash digest information. The two hash digest information are compared. If they match, it is determined that the third event information received by the source chain is complete and accurate.

[0149] In some embodiments, the third event information further includes a second signature, a second identifier, a first VC certificate, a second VC certificate, and a global identity identifier. During the process of forwarding the third event information to the source chain via a cross-chain bridge, the cross-chain bridge also verifies the second signature, second identifier, first VC certificate, second VC certificate, and global identity identifier in the third event information. That is, the third event information is forwarded to the source chain only when the second signature indicates that the transmitted third event information is authentic, the second identifier indicates that the target chain has completed the addition operation of the digital asset associated with the target address, the first VC certificate is the standard VC certificate corresponding to the global identity identifier on the source chain, the second VC certificate is the standard VC certificate corresponding to the global identity identifier on the target chain, and the global identity identifier is any global identity identifier registered in the identity chain.

[0150] In the above embodiments, after the target chain is invoked to perform a new operation on the digital asset associated with the target address, the processing result of the target chain can be fed back to the source chain through a cross-chain bridge, so that the source chain destroys or keeps the locked digital asset in the source chain in a locked state, avoiding the possibility of subsequently controlling the locked digital asset again, thereby improving the reliability of digital asset processing.

[0151] In other embodiments of this application, forwarding the second event information to the target chain via a cross-chain bridge includes: The second event information is converted into standard event information in a standard format through a cross-chain bridge, and then the standard event information is converted into a fourth event information that conforms to the data format of the target chain; the fourth event information is then forwarded to the target chain through the cross-chain bridge.

[0152] Specifically, the role of cross-chain bridges is primarily to facilitate the transfer of data, assets, and information between different blockchains in the metaverse. Since different blockchains have different protocols, data structures, and consensus mechanisms, the implementation of cross-chain bridges needs to address these heterogeneities and ensure security and data integrity during transmission.

[0153] In other words, before forwarding the second event information to the target chain, the cross-chain bridge first resolves the protocol differences between heterogeneous blockchains. Specifically, this protocol difference issue can be addressed through the following layers of protocol conversion: 1. Data parsing: Extracting the format of the second event information from the source chain (e.g., the format of a certain blockchain is CM-NFTv1). 2. Structure Mapping: Convert the format of the second event information in the source chain into the standardized JSON Schema format within the cross-chain bridge to obtain standard event information in a standard format; 3. Target Chain Adaptation: Convert standard event information in standard format into fourth event information that conforms to the executable data format of the target chain, such as the ACS contract input parameters of the target chain.

[0154] In some cases, during the process of forwarding second event information to the target chain via a cross-chain bridge, the signature mechanism of the source chain can be converted to the signature mechanism required by the target chain, such as ECDSA→SM2.

[0155] In some embodiments, to achieve dynamic adaptation to multiple blockchains, the cross-chain bridge can have a built-in feature registration library, that is, pre-store the protocol rules of each blockchain, for example: Blockchain A: {Protocol: TCPB, Event information format: CM-NFTv1}; The second event information also includes the source chain identifier and the target chain identifier. The adapter is automatically invoked according to the source chain identifier / target chain identifier in the second event information. That is, according to the second event information, the format of the event information corresponding to the source chain identifier and the format of the event information corresponding to the target identifier are determined from the feature registration library, and the second event information is converted from the format of the event information corresponding to the source chain identifier to the standard event information, and the standard event information is converted to the format of the event information corresponding to the target identifier to obtain the fourth event information.

[0156] This process requires overcoming two major technical challenges: Heterogeneity handling: A unified mapping is used for the metadata fields (e.g., tokenURI → metadataURL) and ownership proofs of digital assets. Specifically, upon receiving the second event information from the source chain, the metadata fields and ownership proof fields of the digital assets within the second event information are mapped to this standard format. Then, for different target chains, this standard format is converted into a parameter format acceptable to the target chain's smart contract.

[0157] State synchronization: Audit nodes generate cross-chain transfer operation proofs (such as Merkle root hashes) and synchronize them to the two chains.

[0158] In some embodiments, the recording and synchronization of the digital asset processing process is led by a cross-chain bridge: all operation logs (including digital asset identifiers and hashes of digital asset processing operations on both chains) are persistently stored, and their hash digests are written to the relevant blockchain through a lightweight notarization contract to ensure global verifiability and data consistency.

[0159] In the above embodiments, the second event information is converted into standard event information in a standard format by the cross-chain bridge, and then the standard event information is converted into a fourth event information that conforms to the data format of the target chain. This avoids the complexity of customizing the format conversion between each pair of blockchains and improves the working efficiency of the cross-chain bridge. Furthermore, this design balances scalability and security through the decoupled architecture of the cross-chain bridge and the on-chain. Users initiate digital asset processing operations through a unified global identity identifier, and the underlying heterogeneity can be automatically resolved by the protocol conversion layer, realizing seamless interoperability of multi-chain assets.

[0160] In other embodiments of this application, at least one blockchain identifier includes a target chain identifier of the target chain; the VC credential set includes third VC credentials pre-issued to the user by the target chain; By using a global identity identifier and VC credential set, and leveraging a cross-chain bridge, digital assets are processed within the corresponding blockchain to obtain the processing results, including: The cross-chain bridge is invoked to forward the first event information to the target chain; the target chain is invoked to verify the global identity identifier and the third VC credential respectively; if the verification is successful, the target chain is invoked to process the digital asset associated with the target address; the target address is the address of the digital asset storage unit of the global identity identifier on the target chain.

[0161] The target chain is the blockchain through which users process digital assets.

[0162] Specifically, this embodiment describes a digital asset processing operation performed by a user on a single blockchain. For example, adding a digital asset to a digital asset storage unit associated with a specific blockchain; or destroying a digital asset in a digital asset storage unit associated with a specific blockchain. Adding a digital asset to a digital asset storage unit associated with a specific blockchain could also be a digital asset obtained by the user through completing a task within the metaverse space, or a digital asset purchased by the user within the metaverse space. The specific type of digital asset processing operation is not limited here.

[0163] When a user's digital asset processing operation triggered by a blockchain within the metaverse space is captured, the metaverse space responds to the user's digital asset processing operation by obtaining the first event information corresponding to the digital asset processing operation. The first event information includes the user's global identity identifier, the target chain identifier of the target chain, and the user's permission verification VC credential set. This VC credential set contains the third VC credential pre-issued to the user by the target chain.

[0164] The cross-chain bridge is invoked to forward the first event information to the target chain. In this embodiment, the main function of the cross-chain bridge is to forward the first event information detected in the metaverse space to the target chain, and to ensure the secure, intact, and real-time transmission of data between the metaverse space and the target chain.

[0165] Based on the target chain identifier and the third VC certificate pre-issued to the user by the target chain, the target chain is invoked to process digital assets within the target chain and obtain the digital asset processing result.

[0166] Specifically, the process of calling the target chain to process digital assets within the target chain, based on the target chain identifier and the third VC certificate pre-issued to the user by the target chain, means that the target chain is first called to verify the global identity identifier and the third VC certificate respectively. If the verification is successful, the target chain is called to process the digital assets within the target chain to obtain the digital asset processing result.

[0167] In this context, "calling the target chain to process digital assets within the target chain" refers to calling the target chain to process the digital assets associated with the target address; the target address is the address of the digital asset storage unit on the target chain where the global identity is identified.

[0168] In some embodiments, the target chain is invoked to verify the global identity identifier and the third VC credential respectively. If the global identity identifier matches any registered global identity identifier stored in the identity chain, and the third VC credential matches any authorized VC credential associated with the target chain, the verification is considered successful. If the global identity identifier does not match any registered global identity identifier stored in the identity chain, or the third VC credential does not match any authorized VC credential associated with the target chain, the verification is considered unsuccessful.

[0169] In some embodiments, the first event information contains user information bound to the global identity identifier. The method of calling the target chain to verify the global identity identifier and the third VC credential may also include one or more of the following: the target chain verifies the user information bound to the global identity identifier in the first event information and verifies the data format in the global identity identifier and the third VC credential. This is similar to the method of calling the target chain to verify the global identity identifier and the first VC credential in the first event information in the cross-chain transfer operation described above, and will not be elaborated here.

[0170] In some embodiments, when the target chain is invoked to verify the third VC certificate, it can not only verify whether the permissions in the VC certificate conform to the permissions issued by the target chain to the user, but also verify the status of the third VC certificate, that is, verify whether the time of triggering the digital asset processing operation exceeds the validity period of the third VC certificate. If the time of triggering the digital asset processing operation exceeds the validity period of the VC certificate, the third VC certificate is in an invalid state, and the target chain fails to verify the third VC certificate.

[0171] In some embodiments, the target chain can be invoked not only to verify the global identity and the third-party VC credential, but also to verify the authenticity and integrity of the digital asset processing operation. Specifically, when the cross-chain bridge forwards the first event information to the target chain, multiple nodes of the cross-chain bridge will perform hash digest processing on the first event information and sign the hash digested first event information using the private key corresponding to the user's global identity, forming a cross-chain bridge signature set. The cross-chain bridge signature set and the first event information are then sent to the target chain. The target chain can use the public key corresponding to the user's global identity to perform the inverse operation on the cross-chain bridge signature set to obtain the restored hash digest. The first event information is then hash digested again to obtain a new hash digest. The two hash digests are compared. If they match, it is determined that the signature of each node represents that the user has actually uploaded the first event information. Furthermore, the ratio of the total number of node signatures representing that the user has actually uploaded the first event information to the number of nodes of the cross-chain bridge can be calculated. If this ratio is greater than a threshold, it is confirmed that all signatures signed by the private key corresponding to the user's global identity are for the same event information, have not been tampered with or replaced, and the entire first event information is complete.

[0172] In some embodiments, contract nodes on the target chain receive first event information forwarded by the cross-chain bridge. When a contract node on the target chain receives the first event information, it verifies both the global identity identifier and the third-party VC credential. Once both verifications pass, the contract node processes the digital assets within the target chain. In other words, all digital asset processing operations within the target chain can be implemented by contract nodes on the target chain.

[0173] For example, when the type of digital asset processing operation contained in the first event information is a digital asset creation operation, the contract node of the target chain executes the corresponding digital asset minting task. This task is to mint a new digital asset and associate the digital asset creation result with the user's global identity and the address of the digital asset storage unit on the target chain corresponding to the global identity.

[0174] For example, when the type of digital asset processing operation contained in the first event information is a digital asset destruction operation, the contract node of the target chain executes the corresponding digital asset destruction task, which can destroy the corresponding digital asset in the digital asset storage unit on the target chain corresponding to the global identity identifier.

[0175] In some embodiments, after the target chain processes the digital assets, it can also feed the processing results back to the metaverse space through a cross-chain bridge. The metaverse space can then perform further operations on the user based on the processing results, such as displaying the user's newly acquired digital assets, providing related content rights for the digital assets, and updating the declaration information of the target chain's VC certificate (e.g., obtaining some new rights when owning certain digital assets, such as automatically increasing the membership level when acquiring a certain digital asset).

[0176] In some embodiments, during the process of invoking the cross-chain bridge to forward the first event information to the target chain, the cross-chain bridge also verifies the first event information. Specifically, the cross-chain bridge verifies one or more of the global identity identifier in the first event information, as well as the authenticity and completeness of the first event information. The verification process can refer to the process described above for the target chain to verify the authenticity and completeness of digital asset processing operations, and will not be elaborated upon here. In other words, the off-chain verification by the cross-chain bridge can serve as a reference for the target chain's verification process. Then, the target chain independently verifies the information on-chain as the final security barrier. This two-layer verification improves the reliability of the target chain's digital asset processing.

[0177] In the above embodiments, when a user performs digital asset processing operations on a single blockchain, there is no need to query the corresponding user identifier from a large number of user identifiers. Instead, the user can perform digital asset processing operations on any blockchain based on a built-in global identity identifier, which improves the efficiency of digital asset processing in a single blockchain. Furthermore, by calling the target chain to verify the global identity identifier and the third VC certificate respectively, it can be determined whether the target chain can process the digital asset corresponding to the first event information, thereby improving the accuracy of digital asset processing in a single blockchain.

[0178] To more clearly illustrate the digital asset processing solution of this application, such as Figure 5 As shown below, the digital asset processing process will be explained in detail from two aspects: a user adding an NFT on blockchain A, and transferring a user's NFT on blockchain A to blockchain B. 1. Registration: 1.1 In the metaverse space, a user creates a decentralized identity, namely a global DID, by calling the DID identity chain. This global DID serves as the user's unique identifier within the metaverse space. The user applies for an account on the corresponding blockchains, A and B, and this account will be associated with the user's global DID.

[0179] 1.2 Blockchain A and Blockchain B register decentralized DID identities on the DID identity chain. After registration, they enter the Metaverse VC Certificate Issuance Hall. This operation makes both Blockchain A and Blockchain B issuers of VC certificates in the Metaverse space.

[0180] 2. VC Certificate Application: A user submits a request for a VC credential on Blockchain A. This request includes the account address of Blockchain A, the scope of permissions for the VC credential, the validity period of the VC credential, the user's global DID, and signature authentication information generated from the private key corresponding to the user's global DID. Upon receiving the user's request, Blockchain A automatically calls the VC authentication contract node interface on Blockchain A to verify the correctness of Blockchain A's account address and signature authentication information. If the verification passes, Blockchain A records the user's VC credential on Blockchain A and authorizes the user with the VC credential. The application process for a VC credential on Blockchain B is similar and will not be elaborated upon here.

[0181] 3. A user adds an NFT on blockchain A: 3.1 When a user completes a task in the metaverse space to obtain an NFT of blockchain A or purchases an NFT of blockchain A, such behavior is captured, and behavioral information related to the NFT creation operation is obtained.

[0182] 3.2 Based on the captured behavioral information related to NFT creation operations, an NFT creation event information is generated within the metaverse space. This NFT creation event information may include detailed behavioral information, such as the user's global DID, the VC certificate of blockchain A, the operation type (digital asset creation operation), NFT item information, operation timestamp, etc.

[0183] 3.3 Metaverse Space submits new event information for NFTs to the cross-chain bridge.

[0184] 3.4 The cross-chain bridge forwards the NFT new event information to blockchain A. Contract nodes on blockchain A receive the NFT new event information from the cross-chain bridge and verify the global identity identifier, blockchain A's VC certificate, and the authenticity and completeness of the transaction event in the NFT new event information. After all verifications pass, the contract nodes on blockchain A execute the corresponding minting task. This task is to mint a new NFT and associate it with the user's global DID.

[0185] Blockchain A feeds back the results of the minting task to the metaverse space via a cross-chain bridge. The metaverse space can then perform further operations on users based on the results of the minting task, such as displaying newly acquired NFTs, providing related content rights, and updating the declaration information of VC credentials on Blockchain A (e.g., acquiring certain NFTs can grant new rights, such as membership levels, and can automatically update permissions in VC credentials).

[0186] 4. Transfer the user's NFT from blockchain A to blockchain B: 4.1 When a user initiates a cross-chain transfer request for an NFT, the cross-chain transfer request includes the VC certificate of blockchain A, the VC certificate of blockchain B, and the TokenId of the NFT.

[0187] 4.2 Based on the above cross-chain transfer request, the metaverse space generates a first event information, which includes the VC certificate of blockchain A, the VC certificate of blockchain B, and the TokenId of the NFT.

[0188] 4.3 The metaverse space sends the first event information to the cross-chain bridge. The cross-chain bridge first verifies the authenticity of the first event information. After the verification is successful, the first event information is first passed to blockchain A.

[0189] 4.4 The contract node on blockchain A receives the first event information from the cross-chain bridge, locks the NFT corresponding to the TokenId of the NFT in the first event information, that is, transfers the NFT to a designated "locked contract" address and marks it as pending transfer. After the locking operation is successful, the contract node on blockchain A will generate a second cross-chain event information.

[0190] 4.5 The second event information contains relevant information about the NFT (such as the TokenId of the locked NFT, the metadata of the locked NFT, the asset amount of the locked NFT, the user's global DID, etc.), and submits it to the cross-chain bridge.

[0191] 4.6 After receiving the second event information, the cross-chain bridge converts the second event information into standard event information in a standard format, converts the standard event information into fourth event information in a data format that conforms to blockchain B, and sends the fourth event information to blockchain B.

[0192] 4.7 After receiving the fourth event information, the contract nodes on blockchain B will first verify the legality of the NFT, the legality of the transfer operation, and the authenticity of the DID. Upon successful verification, a new NFT with the same TokenId, metadata, and asset amount as the NFT locked on blockchain A will be generated and allocated to the account bound to the user's global DID. After blockchain B completes the minting process, the third event information will be generated and sent to the cross-chain bridge.

[0193] 4.8 The third event information is transmitted to blockchain A via a cross-chain bridge. Contract nodes on blockchain A record the completion of this transfer and permanently lock or destroy the locked NFTs to prevent dual ownership.

[0194] 4.9 The results and related information of the entire cross-chain transfer operation are fed back to the user through the cross-chain bridge.

[0195] It should be understood that the sequence number of each step in the above embodiments does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0196] It should be understood that, when used in this specification and the appended claims, the terms "comprising" and "including" indicate the presence of the described features, integrals, steps, operations, elements and / or components, but do not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or collections thereof.

[0197] It should be noted that the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0198] In addition, in the embodiments of this application, "first," "second," etc. are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0199] The digital asset processing method of this application embodiment can be implemented by a processor in an electronic device, such as a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU), or a field-programmable gate array (FPGA).

[0200] To implement the method of the embodiments of this application, the embodiments of this application also provide an electronic device. Figure 6 This is a schematic diagram of the hardware composition structure of an electronic device provided in an embodiment of this application, such as... Figure 6 As shown, the electronic device includes: The communication interface 601 enables information exchange with other devices, such as electronic devices. The processor 602 is connected to the communication interface 601 to enable information exchange with other devices and to execute the methods provided by one or more of the above-mentioned technical solutions when running a computer program. The computer program is stored in the memory 603.

[0201] Of course, in practical applications, the various components in an electronic device are coupled together through a bus system 604. It can be understood that the bus system 604 is used to implement communication between these components. In addition to a data bus, the bus system also includes a power bus, a control bus, and a status signal bus. However, for clarity, in... Figure 6 The general designated all buses as Bus System 604.

[0202] The memory 603 in this embodiment is used to store various types of data to support the operation of the computer device. Examples of such data include any computer program used to operate on the electronic device.

[0203] It is understood that memory can be volatile or non-volatile, or both. Non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), ferromagnetic random access memory (FRAM), flash memory, magnetic surface memory, optical disc, or compact disc read-only memory (CD-ROM); magnetic surface memory can be disk storage or magnetic tape storage. Volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of RAM are available, such as Static Random Access Memory (SRAM), Synchronous Static Random Access Memory (SSRAM), Dynamic Random Access Memory (DRAM), Synchronous Dynamic Random Access Memory (SDRAM), Double Data Rate Synchronous Dynamic Random Access Memory (DDRSDRAM), Enhanced Synchronous Dynamic Random Access Memory (ESDRAM), SyncLink Dynamic Random Access Memory (SLDRAM), and Direct Rambus Random Access Memory (DRRAM).The memories described in the embodiments of this application are intended to include, but are not limited to, these and any other suitable types of memories.

[0204] The methods disclosed in the embodiments of this application can be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip with signal processing capabilities. During implementation, each step of the above method can be completed by integrated logic circuits in the processor's hardware or by instructions in software form. The processor may be a general-purpose processor, a DSP, or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The processor can implement or execute the methods, steps, and logic block diagrams disclosed in the embodiments of this application. A general-purpose processor may be a microprocessor or any conventional processor, etc. The steps of the methods disclosed in the embodiments of this application can be directly manifested as execution by a hardware decoding processor, or execution by a combination of hardware and software modules in the decoding processor. The software modules may be located in a storage medium, which is located in memory. The processor reads the program from the memory and, in conjunction with its hardware, completes the steps of the aforementioned method.

[0205] Optionally, when the processor executes the program, it implements the corresponding processes implemented by the electronic device in the various methods of the embodiments of this application. For the sake of brevity, these will not be described in detail here.

[0206] In an exemplary embodiment, this application also provides a storage medium, namely a computer storage medium, specifically a computer-readable storage medium, such as a first memory storing a computer program, which can be executed by a processor of a computer device to complete the aforementioned method steps. The computer-readable storage medium may be a memory such as FRAM, ROM, PROM, EPROM, EEPROM, Flash Memory, magnetic surface memory, optical disc, or CD-ROM.

[0207] In the several embodiments provided in this application, it should be understood that the disclosed apparatus, computer devices, and methods can be implemented in other ways. The device embodiments described above are merely illustrative. For example, the division of units is only a logical functional division, and in actual implementation, there may be other division methods, such as: multiple units or components may be combined, or integrated into another system, or some features may be ignored or not executed. In addition, the coupling, direct coupling, or communication between the various components shown or discussed may be through some interfaces, and the indirect coupling or communication between devices or units may be electrical, mechanical, or other forms.

[0208] The units described above as separate components may or may not be physically separate. The components shown as units may or may not be physical units, that is, they may be located in one place or distributed across multiple network units. Some or all of the units may be selected to achieve the purpose of this embodiment according to actual needs.

[0209] In addition, each functional unit in the various embodiments of this application can be integrated into one processing unit, or each unit can be a separate unit, or two or more units can be integrated into one unit; the integrated unit can be implemented in hardware or in the form of hardware plus software functional units.

[0210] Those skilled in the art will understand that all or part of the steps of the above method embodiments can be implemented by hardware related to program instructions. The aforementioned program can be stored in a computer-readable storage medium. When the program is executed, it performs the steps of the above method embodiments. The aforementioned storage medium includes various media that can store program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0211] Alternatively, if the integrated units described above are implemented as software functional modules and sold or used as independent products, they can also be stored in a computer-readable storage medium. Based on this understanding, the technical solutions of the embodiments of this application, or the parts that contribute to related technologies, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, electronic device, etc.) to execute all or part of the methods of the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as mobile storage devices, ROM, RAM, magnetic disks, or optical disks.

[0212] In an exemplary embodiment, this application also provides a computer program product, including a computer program that can be executed by a processor 602 of an electronic device to perform the steps of the digital asset processing method in this application embodiment.

[0213] It should be noted that terms such as "first" and "second" are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence.

[0214] Furthermore, the technical solutions described in the embodiments of this application can be combined arbitrarily without conflict.

[0215] The above are merely specific embodiments of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A method for processing digital assets, characterized in that, The method includes: In response to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, the system acquires first event information corresponding to the digital asset processing operation. The metaverse space includes multiple blockchains that interact with each other via cross-chain bridges. The first event information includes the user's global identity identifier, at least one blockchain identifier, and the user's permission verification VC credential set. The global identity identifier is a unified identifier used by the multiple blockchains to identify the user. The VC credential set includes VC credentials pre-issued to the user by the blockchain corresponding to at least one blockchain identifier, and the VC credentials serve as proof of the user's permissions within the corresponding blockchain. Using the global identity identifier and the VC certificate set, the cross-chain bridge is used to process digital assets within the corresponding blockchain to obtain the digital asset processing result.

2. The method according to claim 1, characterized in that, The metaverse space also includes an identity chain; the identity chain is used to issue global identity identifiers to users. Prior to responding to a user's digital asset processing operation triggered by at least one blockchain within the metaverse space, the method further includes: In response to a user's identity registration operation in the metaverse space, the identity chain is invoked to issue a global identity identifier to the user. In response to the user's registration operation for a digital asset storage unit of any blockchain in the metaverse space, the corresponding blockchain is invoked to allocate a digital asset storage unit for the user, and the digital asset storage unit is associated with the global identity identifier; In response to the user's VC application operation for any blockchain within the metaverse space, based on the global identity identifier and the address of the digital asset storage unit associated with the global identity identifier on the corresponding blockchain, the corresponding blockchain is invoked to issue a VC certificate for the user.

3. The method according to claim 1, characterized in that, The at least one blockchain identifier includes the source chain identifier of the source chain and the target chain identifier of the target chain; the VC credential set includes a first VC credential pre-issued to the user by the source chain and a second VC credential pre-issued to the user by the target chain. The process of processing digital assets within the corresponding blockchain using the global identity identifier and the VC certificate set via the cross-chain bridge includes: The first event information is forwarded to the source chain via the cross-chain bridge; The source chain is invoked to verify the global identity identifier and the first VC credential in the first event information, respectively; If the verification is successful, the source chain is invoked to lock the digital asset associated with the source address, and the source chain is invoked to generate second event information; the second event information includes at least the global identity identifier and the second VC certificate; the source address is the address of the digital asset storage unit of the global identity identifier on the source chain; The second event information is forwarded to the target chain via the cross-chain bridge; The target chain is invoked to verify the global identity identifier and the second VC credential, respectively. If the verification is successful, the target chain is invoked to perform a new asset operation on the digital asset associated with the target address; the amount of new digital assets in the target chain is equal to the amount of digital assets locked in the source chain; the target address is the address of the digital asset storage unit of the global identity identifier on the target chain.

4. The method according to claim 3, characterized in that, The second event information also includes a first VC certificate, a first signature, and a first identifier; the first signature is the signature signed by the source chain to lock the corresponding digital asset; the first identifier indicates whether the digital asset associated with the preset address in the source chain is in a locked state; The step of forwarding the second event information to the target chain via the cross-chain bridge includes: The first identifier, first signature, global identity identifier, first VC credential, and second VC credential are verified through the cross-chain bridge. If the verification passes, the second event information is forwarded to the target chain via the cross-chain bridge.

5. The method according to claim 3, characterized in that, After the method calls the target chain to perform a new operation on the digital asset associated with the target address, the method further includes: The target chain is invoked to generate third event information corresponding to the digital asset; the third event information includes at least a second identifier; the second identifier indicates whether the addition operation of the digital asset associated with the target address has been completed within the target chain. The third event information is forwarded to the source chain via the cross-chain bridge. The source chain is invoked to verify the second identifier in the third event information; If the second identifier indicates that the target chain has completed the addition operation of the digital asset associated with the target address, then the source chain is invoked to destroy or keep the locked digital asset in the source chain in a locked state.

6. The method according to claim 3, characterized in that, The step of forwarding the second event information to the target chain via the cross-chain bridge includes: The second event information is converted into standard event information in a standard format through the cross-chain bridge, and the standard event information is converted into fourth event information that conforms to the data format of the target chain. The fourth event information is forwarded to the target chain via the cross-chain bridge.

7. The method according to claim 1, characterized in that, The at least one blockchain identifier includes the target chain identifier of the target chain; the VC credential set includes third VC credentials pre-issued to the user by the target chain; The process of using the global identity identifier and the VC certificate set, and utilizing the cross-chain bridge to process digital assets within the corresponding blockchain to obtain digital asset processing results includes: Invoke the cross-chain bridge to forward the first event information to the target chain; The target chain is invoked to verify the global identity identifier and the third VC credential, respectively. If the verification is successful, the target chain is invoked to process the digital assets associated with the target address; the target address is the address of the digital asset storage unit of the global identity identifier on the target chain.

8. An electronic device, characterized in that, The electronic device includes: Memory is used to store executable instructions or computer programs. A processor, when executing computer-executable instructions or computer programs stored in the memory, implements the method according to any one of claims 1 to 7.

9. A computer storage medium storing a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method according to any one of claims 1 to 7.

10. A computer program product, comprising a computer program, characterized in that, When the computer program is executed by a processor, it implements the steps of the method as described in any one of claims 1 to 7.

Images