Resource transfer method and device in meta universe, electronic equipment and storage medium

By directly transferring resources using smart contracts in the metaverse, the problem of low resource transfer efficiency in the existing technology is solved, and more efficient and simple resource flow is achieved.

CN119398773APending Publication Date: 2025-02-07SAMSUNG ELECTRONICS CHINA R&D CENT +1
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202411455086.7
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2024-10-17
Publication Date
2025-02-07

AI Technical Summary

Technical Problem

In the prior art, resource transfer between the metaverses is inefficient and cumbersome, and requires complicated steps such as transactions and token purchases.

Method used

By creating smart contracts in the metaverse, directly transfer resources from the resource pool of one metaverse to the resource pool of another metaverse, realizing direct transfer and use of resources.

Benefits of technology

It improves the efficiency and simplicity of resource transfer, avoids the steps of third-party platforms and resource transactions, and enhances the liquidity of resources between the multiverse.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN119398773A_ABST
    Figure CN119398773A_ABST
Patent Text Reader

Abstract

The invention provides a resource transfer method and device in meta universe, electronic equipment and a storage medium. The method comprises the following steps: transferring a resource specified by a user to a first smart contract; initiating a resource locking request through the first smart contract; evaluating a Token value which can be borrowed by the resource to obtain a Token value M; transferring the universal Token of the value M from a resource pool of the first meta-universe to the first smart contract, and locking resources; transferring the Token of the value M to a second smart contract through the first smart contract; and enabling the second smart contract to lock the Token of the value M, and transferring the Token of the value M from the resource pool of the second meta-universe to the second account. According to the method, resource transfer can be directly carried out in the meta universe, and the efficiency and convenience of resource transfer are improved.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The embodiments of the present disclosure relate to the field of metaverse, and specifically to a method, device, electronic device, and storage medium for transferring resources in the metaverse. Background Art

[0002] In the future, more and more real-life scenarios will be realized in the metaverse. For example, games, shopping, travel, etc. all involve identity authentication and economic consumption.

[0003] A user’s resources in one metaverse cannot be used directly in another metaverse. If a user wants to use them in another metaverse, he or she needs to transfer resources between different metaverses.

[0004] In the current related technologies, when users have resource transfer needs in the metaverse, they generally need to trade in the current metaverse first, and then purchase tokens circulating in the target metaverse in the target metaverse. This resource transfer method has the problems of low resource transfer efficiency and cumbersomeness. Summary of the invention

[0005] In view of this, the present application provides a metaverse resource transfer method, device, electronic device and storage medium, which can directly transfer resources in the metaverse, thereby improving the efficiency and simplicity of resource transfer.

[0006] To solve the above technical problems, the technical solution of this application is implemented as follows: In one embodiment, a method for transferring resources in a metaverse is provided, the method comprising: Transferring resources specified by the user to a first smart contract; the first smart contract is created by the user in the first metaverse when the first account of the first metaverse is linked to the second account of the second metaverse; Initiating a lock request for the resource through the first smart contract; Evaluate the loanable Token value of the resource to obtain a Token value M; Transfer M universal tokens from the resource pool of the first metaverse to the first smart contract and lock the resources; the resource pool of the first metaverse is created when the first metaverse is established; Transferring Tokens worth M to the second smart contract through the first smart contract; enabling the second smart contract to lock Tokens worth M and transfer Tokens worth M from the resource pool of the second metaverse to the second account; the second smart contract is created in the second metaverse when the first account of the user in the first metaverse is linked to the second account in the second metaverse; the resource pool of the second metaverse is created when the second metaverse is established.

[0007] The step of evaluating the loanable Token value of the resource to obtain the Token value M includes: Get the resource type of the resource; Determining whether the resource is a homogeneous resource according to the resource type; If yes, the latest price of the resource in the free market is used as the valuation benchmark; the loanable Token value is obtained based on the valuation benchmark and the preset safety factor; If not, initiate a bidding request in the free market for the resource to create a third smart contract; conduct a limited-time public bidding in the free market through the third smart contract; and lock the tokens transferred by the users participating in the bidding; at the end of the bidding, use the highest bid as the valuation benchmark; obtain the loanable token value based on the valuation benchmark and the preset safety factor, and destroy the third smart contract.

[0008] in, The resources in the resource pool are composed of a basic pool and a flow pool; Among them, the resources in the basic pool are provided by the Metaverse; the resources in the liquidity pool are provided by users.

[0009] Wherein, the method further comprises: In response to a request initiated by a user who logs into a first account of the first metaverse to link to a second account of the second metaverse, creating a first smart contract; Sending the request to the second metaverse through the first smart contract, the request carrying the account information of the first account and the identity authentication information of the user, so that the second metaverse uses the biometric authentication information in the request for authentication; when the authentication is successful, creating a second smart contract and recording the account information of the first account; In response to a link success message sent by the second metaverse when the link is successful, the account information of the second account and the link status as link success are recorded through the first smart contract; In response to a link rejection message sent by the second metaverse due to authentication failure, feedback is given to the user through the first smart contract, and the first smart contract is destroyed.

[0010] Wherein, the method further comprises: When the monitoring period is up, the valuation benchmark of the resource is updated according to whether the resource is a homogeneous resource, and the current Token value N of the resource is determined according to the valuation benchmark, and the current safety factor is calculated according to the Token value N; If it is determined that the current Token value N of the resource and the current security factor do not meet the preset resource lending conditions, notify the user to supplement the resource and the Token value corresponding to the supplemented resource; In response to the resource corresponding to the Token value supplemented by the user, waiting for the next cycle to continue monitoring; In response to not receiving the supplementary resources from the user within the preset time or the value of the supplemented resources is less than the notified Token value, the resources are traded according to whether the resources are homogeneous resources; and the Tokens with a value of M obtained from the transaction are transferred to the resource pool of the first metaverse, and the Tokens exceeding the value of M are transferred to the first account.

[0011] Wherein, the method further comprises: In response to a request to unlink an account initiated by the user, performing biometric authentication; If the authentication is successful, the Metaverse in which the resource is to be retained is determined; If it is determined to retain the resources in the first and second metaverses, the tokens worth M are locked in the first smart contract, and a message for unlinking the account is sent to the second metaverse through the first smart contract, so that after the biometric authentication is successful, the second metaverse transfers the locked tokens to the resource pool of the second metaverse through the second smart contract, sends a message of successful unlinking of the account to the first smart contract, and destroys the second smart contract; In response to the message of successful account link release sent by the second smart contract, the locked Tokens worth M are transferred to the resource pool through the first smart contract, the resources are unlocked, and the first smart contract is destroyed.

[0012] Wherein, the method further comprises: If it is determined to retain the resources in the first metaverse, a message for unlinking the account is sent to the second metaverse through the first smart contract, so that when the biometric authentication is successful, the second metaverse converts the resources in the second account into universal tokens and transfers them to the second smart contract. A message for successfully unlinking the account is sent to the first smart contract through the second smart contract, and the converted tokens with a value of Q are transferred to the first smart contract, and the second smart contract is destroyed; In response to the account link release success message sent by the second smart contract, determine whether Q is less than M. If so, notify the user to make up the resources with a value of MQ, return the tokens with a value of M to the resource pool through the first smart contract, unlock the resources and destroy the first smart contract; otherwise, return the tokens with a value of M to the resource pool through the first smart contract, unlock the resources, transfer the remaining tokens with a value of QM and the locked resources to the first account, and destroy the first smart contract.

[0013] Wherein, the method further comprises: If it is determined to retain the resources in the second Metaverse, a message for unlinking the account is sent to the second Metaverse through the first smart contract, so that when the biometric authentication is successful, the second Metaverse sends a message of successful unlinking of the account to the first smart contract through the second smart contract and destroys the second smart contract; In response to the account link release success message sent by the second smart contract, the locked resources are converted into universal tokens through the first smart contract, tokens worth M are transferred to the resource pool of the first metaverse, the remaining tokens are returned to the first account, and the first smart contract is destroyed.

[0014] In another embodiment, a device for transferring resources in a metaverse is provided, the device comprising: A first transfer unit, configured to transfer resources specified by a user to a first smart contract; the first smart contract is created by the user in the first metaverse when a first account in the first metaverse is linked to a second account in the second metaverse; An evaluation unit, configured to evaluate the loanable Token value of the resource to obtain a Token value M; A second transfer unit is used to transfer a universal token with a value of M from the resource pool of the first metaverse to the first smart contract; the resource pool of the first metaverse is created when the first metaverse is established; The first smart contract is used to initiate a lock request for the resource; and lock the resource; transfer the token worth M to the second smart contract; so that the second smart contract locks the token worth M and transfers the token worth M from the resource pool of the second metaverse to the second account; the second smart contract is created in the second metaverse when the first account of the user in the first metaverse is linked to the second account in the second metaverse; the resource pool of the second metaverse is created when the second metaverse is established.

[0015] In another embodiment, an electronic device is provided, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor implements a resource transfer method in a metaverse when executing the program.

[0016] In another embodiment, a computer-readable storage medium is provided, on which a computer program is stored, and when the program is executed by a processor, a resource transfer method in a metaverse is implemented.

[0017] It can be seen from the above technical solution that in the above embodiment, the resources in the first metaverse are locked in the first smart contract, and the tokens of the corresponding value of the locked resources are transferred to the user through the first smart contract to be locked in the second smart contract of the second metaverse, and the resource pool of the second metaverse transfers the tokens of the corresponding value to the second account in the second metaverse for use in the second metaverse; therefore, this solution does not require a third-party platform or resource transactions, that is, resources can be directly transferred between different metaverses, which improves the efficiency and simplicity of resource transfer. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings required for use in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other drawings can be obtained based on these drawings without paying any creative work.

[0019] Figure 1 This is a schematic diagram of the linking process of different accounts of the same user in different metaverses in an embodiment of the present application; Figure 2 This is a schematic diagram of the resource transfer process in the Metaverse in the embodiment of this application; Figure 3 This is a schematic diagram of the process of evaluating the loanable Token value of resources in an embodiment of the present application; Figure 4 This is a schematic diagram of the resource monitoring process in the embodiment of the present application; Figure 5 This is a schematic diagram of the account link removal process in an embodiment of the present application; Figure 6 This is a schematic diagram of the system architecture consisting of two metaverses in an embodiment of the present application; Figure 7 This is a schematic diagram of the structure of a resource transfer device in the metaverse in an embodiment of the present application; Figure 8 A schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention. DETAILED DESCRIPTION

[0020] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are only part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of this application.

[0021] The terms "first", "second", "third", "fourth", etc. (if any) in the specification and claims of the present invention and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe the order or precedence of the objects. It should be understood that the data used in this way can be interchanged where appropriate, so that the implementation of the present invention described herein can be implemented in an order other than those illustrated or described herein, for example. In addition, the terms "including" and "having" and any variations thereof are intended to cover non-exclusive inclusions. For example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

[0022] The technical solution of the present invention is described in detail with specific embodiments below. The following specific embodiments can be combined with each other, and the same or similar concepts or processes may not be described in detail in some embodiments.

[0023] The emergence of more and more metaverse scenarios in life has led users to log in to multiple metaverses. However, direct resource consumption in each metaverse will bring great inconvenience. It is necessary to directly pledge or operate resources in each metaverse. This will bring great inconvenience. If resources are limited, it is necessary to first trade resources in one metaverse, then purchase the tokens circulating in the current metaverse to be consumed, and finally transfer them to the current metaverse to be consumed. This resource transfer method has the problems of low resource transfer efficiency and cumbersomeness.

[0024] Based on the above problems, a method for transferring resources in a metaverse is provided in an embodiment of the present application, which locks the resources in a first metaverse in a first smart contract, and transfers the tokens of the corresponding value of the locked resources to the user through the first smart contract to be locked in a second smart contract in a second metaverse, and the resource pool of the second metaverse transfers the tokens of the corresponding value to the second account in the second metaverse for use in the second metaverse; therefore, this solution does not require a third-party platform or resource transactions, that is, resources can be directly transferred between different metaverses, thereby improving the efficiency and simplicity of resource transfer.

[0025] The following is a detailed description of the resource transfer process in the Metaverse implemented in accordance with an embodiment of the present application in conjunction with the accompanying drawings.

[0026] When the first metaverse is established, a resource pool for the first metaverse is created; when the second metaverse is established, a resource pool for the second metaverse is created; Among them, the resources in the resource pool of each metaverse have two sources. Therefore, the resource pool is composed of two parts, namely the basic pool and the liquidity pool; the resources in the basic pool are provided by the metaverse; the resources in the liquidity pool are provided by users. If users spontaneously pledge or invest in tokens, they can obtain interest by lending tokens.

[0027] Take the example of a user transferring resources from the first metaverse to the second metaverse: In the first metaverse, the user's login account is the first account, and in the second metaverse, the user's login account is the second account.

[0028] Before transferring resources between two metaverses, users need to link their accounts in the two metaverses. Figure 1 , Figure 1 This is a schematic diagram of the linking process of different accounts of the same user in different metaverses in the embodiment of this application. The specific steps are: Step 101, in response to a request initiated by a user who logs into a first account of a first metaverse to link to a second account of a second metaverse, a first smart contract is created.

[0029] When a user logs in to a first account in the first metaverse and needs to link with a second account in the second metaverse, a link request is initiated; in order to link the accounts, a first smart contract is created in the first metaverse to achieve this.

[0030] Step 102, the request is sent to the second metaverse through the first smart contract. The request carries the account information of the first account and the identity authentication information of the user, so that the second metaverse uses the biometric authentication information in the request for authentication; when the authentication is successful, a second smart contract is created and the account information of the first account is recorded.

[0031] The account information of the first account is used to identify the first account, such as the account name, the metaverse it is in, etc.; the user's biometric authentication information includes the user's fingerprint, iris, etc.

[0032] When the second metaverse receives the request sent by the first smart contract, it performs authentication based on the biometric authentication information carried in the request, specifically: obtaining the biometric authentication information carried in the request and the biometric authentication information obtained in the second metaverse, matching the two biometric authentication information, and determining that the authentication is successful when the matching degree meets the preset conditions; otherwise, determining that the authentication is unsuccessful.

[0033] When the authentication is successful, a second smart contract is created to record the account information of the first account carried in the request, indicating that the second account is linked to the first account; When authentication fails, a link rejection message is sent directly to the first smart contract.

[0034] In the embodiments of the present application, when information is exchanged between different metaverses, for the sake of information security, the exchanged information is usually encrypted. For example, when the request is sent in this step, it needs to be encrypted before being sent. The specific encryption algorithm is not limited in the embodiments of the present application and can be selected according to the actual application environment in actual applications.

[0035] Step 103, in response to the link success message sent by the second metaverse when the link is successful, the account information of the second account and the link status as link success are recorded through the first smart contract. This process ends.

[0036] Step 104, in response to the link rejection message sent by the second metaverse due to authentication failure, feedback is given to the user through the first smart contract, and the first smart contract is destroyed.

[0037] At this point, the link between accounts has been completed. The link result may be successful or failed. If it fails, you can also update the biometric authentication information and initiate the link again.

[0038] See also Figure 2 , Figure 2 This is a schematic diagram of the resource transfer process in the Metaverse in the embodiment of this application. The specific steps are: Step 201, transfer the resources specified by the user to the first smart contract; the first smart contract is created in the first metaverse when the first account of the user in the first metaverse is linked to the second account of the second metaverse.

[0039] The resources here refer to any tradable digital assets owned by users in the Metaverse, such as virtual land, virtual currency, virtual artwork, etc., but are not limited to these.

[0040] Step 202: Initiate a resource locking request through the first smart contract.

[0041] If the resource in the first metaverse is transferred to the second metaverse, the resource needs to be locked in the first metaverse. Usually, the token value of the resource needs to be evaluated to determine the loanable token value. When determining the loanable token value, a preset safety factor is used to reduce the risk of resource value fluctuations during the cross-chain resource locking period.

[0042] Step 203: Evaluate the loanable Token value of the resource to obtain a Token value M.

[0043] Step 204: transfer a universal token worth M from the resource pool of the first metaverse to the first smart contract and lock the resource.

[0044] Step 205, transfer the token worth M to the second smart contract through the first smart contract; so that the second smart contract locks the token worth M and transfers the token worth M from the resource pool of the second metaverse to the second account; the second smart contract is created in the second metaverse when the user's first account in the first metaverse is linked to the second account in the second metaverse.

[0045] The first smart contract of the first metaverse tries to use the tokens directly available in the second metaverse for transfer operations, so that the second smart contract can directly transfer the corresponding tokens from the resource pool to the second account; if it is not a token directly available in the second metaverse, it needs to be locked by the second smart contract and converted into a directly available token before being transferred from the resource pool of the second metaverse to the second account.

[0046] When interacting with the first and second metaverses, biometric authentication is required; resource transfer is also a type of interaction, and usually biometric authentication is performed first, followed by token transfer. If the authentication is successful, the token worth M is transferred to the second smart contract through the first smart contract; If the authentication fails, the second smart contract will feedback to the first smart contract that the resource transfer cannot be performed; the first smart contract will then feedback to the user.

[0047] At this point, a resource transfer process is completed.

[0048] In the embodiment of the present application, through the established account link relationship and the created smart contract, the resources in the first metaverse are locked in the first smart contract, and the tokens of the corresponding value of the locked resources are transferred to the user through the first smart contract to be locked in the second smart contract of the second metaverse, and the resource pool of the second metaverse transfers the tokens of the corresponding value to the second account in the second metaverse for use in the second metaverse; therefore, this solution does not require a third-party platform or resource transactions, that is, resources can be directly transferred between different metaverses, thereby improving the efficiency and simplicity of resource transfer.

[0049] And through the management of resource pools, users can transfer resources to an associated account in another metaverse and manage resources through smart contracts, which reduces the process of users repeatedly trading resources, improves the convenience of resource transfer between metaverses, and reduces transaction costs.

[0050] In the specific implementation, on-demand lending can be achieved within the scope allowed by the mortgaged resources.

[0051] In step 203, the loanable Token value of the resource is evaluated, and the specific implementation of obtaining the Token value M is shown in Figure 3 , Figure 3 This is a schematic diagram of the process of evaluating the loanable Token value of resources in the embodiment of this application. The specific steps are: Step 301, obtaining the resource type of the resource.

[0052] Step 302: If the resource type of the resource is a homogeneous resource, the latest price of the resource in the free market is used as the valuation benchmark; the loanable Token value is obtained based on the valuation benchmark and the preset safety factor. This process ends.

[0053] Step 303: If the resource type of the resource is a non-homogeneous resource, a bidding request is initiated in the free market for the resource to create a third smart contract; a limited-time public bidding is conducted in the free market through the third smart contract; and the tokens transferred by the users participating in the bidding are locked; at the end of the bidding, the highest bid is used as the valuation benchmark; the loanable token value is obtained based on the valuation benchmark and the preset safety factor, and the third smart contract is destroyed.

[0054] During the bidding process, multiple users may participate in the bidding. The tokens transferred by multiple users are locked in the third smart contract. At the end of the bidding, the transaction is completed with the user who transferred the most tokens, and the tokens transferred by other users are unlocked and returned to the corresponding users.

[0055] Here, the preset safety factor can be set to 0.6. For example, if the valuation basis for a resource is 100 Tokens, then the Token value of the loanable Tokens of the resource is 60. In the embodiment of the present application, there is no restriction on the setting of the preset safety factor, which is set according to the Metaverse system.

[0056] After the resources are transferred, since the value of the resources locked in the first smart contract in the market may change at any time, it is also necessary to monitor whether the Token value of the resources changes and whether it can still meet the locked value.

[0057] See also Figure 4 , Figure 4 This is a schematic diagram of the resource monitoring process in the embodiment of this application. The specific steps are: Step 401, when the monitoring period is up, the resource valuation benchmark is updated according to whether the resource is a homogeneous resource, and the current Token value N of the resource and the current safety factor are determined according to the valuation benchmark.

[0058] Among them, the valuation basis of resources is updated according to whether the resources are homogeneous resources, specifically: Get the resource type of the resource; if the resource type of the resource is a homogeneous resource, the latest purchase and sale price of the resource in the free market is used as the valuation benchmark; if the resource type of the resource is a non-homogeneous resource, initiate a bidding request for the resource in the free market to create a third smart contract; conduct a limited-time public bidding in the free market through the third smart contract; and lock the Token value of the corresponding value in the third smart contract; at the end of the bidding, the highest bid is used as the valuation benchmark.

[0059] For example, when the resource is locked, the Token value M = K × P1; K is the preset safety factor, and P1 is the valuation benchmark corresponding to the resource when the resource is locked; The current Token value of the resource is N=K×P2; K is the preset safety factor, and P2 is the valuation benchmark for the current valuation of the resource; The current safety factor K1 is calculated based on the Token value N as M / P2.

[0060] If K is 0.6, P1 is 100, M is 60, if P2 is 150, N is 90, and K1 is 0.4; if P2 is 80, N is 64, and K1 is 0.75.

[0061] Step 402: If it is determined that the current Token value N and the current security factor of the resource do not meet the preset resource lending conditions, the user is notified to supplement the resource and the Token value corresponding to the supplemented resource.

[0062] The preset resource release condition here can be determined based on the Token value of the resource when the resource was locked, and the preset safety factor; for example, it needs to be not less than the Token value of the resource when the resource was locked, and the calculated current safety factor is not greater than the preset safety factor; If the current Token value of the resource is not less than M, and the calculated safety factor is not greater than K; if P2 is 150, the preset resource lending conditions are met; if P2 is 80, the resource lending conditions are not met.

[0063] Step 403, in response to the resources corresponding to the token value added by the user, wait for the next cycle to continue monitoring. End this process; Step 404, in response to not receiving the user's supplementary resources within the preset time or the value of the supplemented resources is less than the notified Token value, based on whether the resources are homogeneous resource trading resources; and transfer the Tokens of value M obtained from the transaction to the resource pool of the first metaverse, and transfer the Tokens exceeding the value M to the first account.

[0064] Dynamically monitor the actual value of locked resources, and respond in a timely manner when the value of locked resources is insufficient to avoid loss of resources.

[0065] The locking of resources and real-time value monitoring in the embodiment of the present application ensure the resource security of the resource pool, and will not cause resource pool losses due to a substantial depreciation of resources during the locking process, nor will it cause user losses due to a substantial appreciation of resources.

[0066] The changes in resource valuation and transactions are entirely dependent on the spontaneous behavior of users in the free market. When the free market is large enough, the stability of resource valuation can be guaranteed. The system can regularly synchronize resource changes, monitor resource security, and process resources accordingly when conditions such as resource security thresholds and time locks are triggered, reducing the risk of resource pool losses.

[0067] Account linking and resource transfer can be performed in the first and second metaverses. When account linking is no longer needed, the account linking can also be released. The process of releasing the account linking is given in detail below with reference to the accompanying drawings.

[0068] See also Figure 5 , Figure 5 This is a schematic diagram of the account link removal process in the embodiment of this application. The specific steps are: Step 501, in response to a request to unlink an account initiated by a user, biometric authentication is performed.

[0069] Step 502: If the authentication is successful, determine the metaverse in which the resources are to be retained.

[0070] If the authentication fails, a message indicating that the account unlinking failed is returned to the user.

[0071] Step 503: If it is determined that the resources in the first and second metaverses are to be retained, a token worth M is locked in the first smart contract, and a message for unlinking the account is sent to the second metaverse through the first smart contract. After the biometric authentication is successful, the second metaverse transfers the locked token to the resource pool of the second metaverse through the second smart contract, sends a message of successful unlinking of the account to the first smart contract, and destroys the second smart contract.

[0072] When the second Metaverse receives the account unlinking message, it performs biometric authentication. If the authentication fails, it sends a rejection unlinking message to the first smart contract through the second smart contract, and the first smart contract feeds back to the user; If the authentication is successful, the locked Token will be transferred to the resource pool of the second metaverse through the second smart contract, a message of successful account link release will be sent to the first smart contract, and the second smart contract will be destroyed.

[0073] Step 504: In response to the message of successful account unlinking sent by the second smart contract, the locked Tokens with a value of M are transferred to the resource pool through the first smart contract, the resources are unlocked, and the first smart contract is destroyed. This process ends.

[0074] Step 505: If it is determined that the resources in the first metaverse are to be retained, a message for unlinking the account is sent to the second metaverse through the first smart contract, so that when the biometric authentication is successful, the second metaverse converts the resources in the second account into universal tokens and transfers them to the second smart contract. A message of successful unlinking of the account is sent to the first smart contract through the second smart contract, and the converted tokens of value Q are transferred to the first smart contract, and the second smart contract is destroyed.

[0075] When the second Metaverse receives the account unlinking message sent by the first smart contract, it performs biometric authentication. If the biometric authentication is successful, the resources in the second account are converted into universal tokens and transferred to the second smart contract. The second smart contract sends a message of successful account unlinking to the first smart contract, transfers the converted tokens of value Q to the first smart contract, and destroys the second smart contract.

[0076] If the authentication fails, the second smart contract sends a rejection message to the first smart contract, and the first smart contract feeds back to the user; Step 506: In response to the successful account link release message sent by the second smart contract, determine whether Q is less than M. If so, notify the user to make up the resources worth MQ, return the tokens worth M to the resource pool through the first smart contract, unlock the resources and destroy the first smart contract; otherwise, return the tokens worth M to the resource pool through the first smart contract, unlock the resources, transfer the remaining tokens worth QM and the locked resources to the first account, and destroy the first smart contract. End this process.

[0077] Step 507: If it is determined that the resources in the second Metaverse are to be retained, a message for unlinking the account is sent to the second Metaverse through the first smart contract, so that when the biometric authentication is successful, the second Metaverse sends a message for successfully unlinking the account to the first smart contract through the second smart contract, and destroys the second smart contract.

[0078] When the second Metaverse receives the account unlinking message sent by the first smart contract, it performs biometric authentication. If the biometric authentication is successful, it sends a successful account unlinking message to the first smart contract through the second smart contract and destroys the second smart contract. If the authentication fails, the second smart contract sends a rejection message to the first smart contract, and the first smart contract feeds back to the user; Step 508, in response to the account link release success message sent by the second smart contract, the locked resources are converted into universal tokens through the first smart contract, tokens worth M are transferred to the resource pool of the first metaverse, the remaining tokens are returned to the first account, and the first smart contract is destroyed.

[0079] At this point, the account unlinking is complete.

[0080] After the experience, the user can easily make a final decision, such as unlinking the account and specifying the metaverse for resource retention. The embodiment of the present application provides a method for the user to choose to retain a single metaverse and resources in all metaverses. The user does not need to repeatedly perform resource and universal token conversion to achieve the final selection. Only one operation is required to determine the direction of resource transfer, saving the cost of experience and resource transfer.

[0081] The following is a detailed description of the implementation process of this application, using the account linking, resource transfer and account link unlinking between Metaverse A and Metaverse B as an example.

[0082] See also Figure 6 , Figure 6 Schematic diagram of the system architecture consisting of two metaverses in an embodiment of the present application. Figure 6 Metaverse A and Metaverse B are two independent metaverses. User 1's account in Metaverse A is Account A, and the account in Metaverse B is Account B. The interaction between Metaverse A and Metaverse B is carried out through Service A and Server B. The resource pool corresponding to Metaverse A is Resource Pool A, and the resource pool corresponding to Metaverse B is Resource Pool B. The resources in Resource Pool A are provided by Metaverse A as basic resources, and some liquid resources can also be provided by users of Metaverse A through mortgaging resources, directly investing resources, etc.; the value of these liquid resources changes according to market conditions, and Resource Pool B is implemented in the same way as Resource Pool A.

[0083] When user 1 logs in to Metaverse A and Metaverse B, account A and account B can be linked as follows: User 1 initiates a request in Metaverse A to link account B in Metaverse B, and server A creates smart contract A.

[0084] Server A encrypts the request through smart contract A and sends it to original universe B; the request carries the account information of account A and the biometric authentication information of user 1.

[0085] After Metaverse B decrypts the request, it uses the biometric authentication information carried in the request for authentication; when the authentication is successful, it creates Smart Contract B and records the account information of Account A; and sends a link success message to Smart Contract A through Smart Contract B.

[0086] Smart Contract A in Metaverse A responds to the link success message sent by the second Metaverse when the link is successful, and records the account information of Account B through Smart Contract A, and the link status is link success.

[0087] At this point, the link between account A and account B is completed.

[0088] After Account A and Account B are linked, resources can be transferred. Take the example of transferring resources from Metaverse A to Metaverse B: Server A transfers the resources specified by user 1 to smart contract A; the resources here are the digital assets owned by the user in the metaverse, which are assets in the virtual world, such as virtual land, virtual currency, virtual artwork, etc., but not limited to these.

[0089] Server A initiates a resource lock request through smart contract A, evaluates the loanable token value of the resource, and obtains the token value M.

[0090] During the evaluation, the valuation benchmark is determined based on whether the resources are homogeneous. For example, if the locked resources are valued at 1 million and the preset safety factor is 0.6, the token value of the resource is 600,000.

[0091] Transfer a universal token worth M from resource pool A in Metaverse A to smart contract A and lock the resource.

[0092] Server A notifies Metaverse B through Smart Contract A that it has locked tokens worth M, that is, it notifies Metaverse B that it will transfer resources and the specific resources to be transferred.

[0093] Metaverse B first performs biometric authentication, and when the biometric authentication is successful, it notifies smart contract A in Metaverse A.

[0094] Smart contract A transfers tokens worth M to smart contract B; Smart contract B locks the token with a value of M and transfers the token with a value of M from resource pool B of Metaverse B to account B of user 1.

[0095] At this point, a resource transfer is completed.

[0096] If account linking is no longer required, User 1 can initiate an account link unlinking request in Metaverse A. The specific implementation process is as follows: User 1 initiates a request to unlink the account in Metaverse A, and based on the request, biometric authentication is performed on User 1 who initiated the request; If the authentication is successful and it is determined that the resources in Metaverse B are to be retained, a message to unlink the account is sent to Metaverse B through Smart Contract A; When Metaverse B receives the account unlink message sent by the smart contract, it performs biometric authentication based on the biometric authentication information carried in the message. When the authentication is successful, it sends the account unlink success message to Smart Contract A through Smart Contract B and destroys Smart Contract B.

[0097] When smart contract A receives the successful account link release message sent by smart contract B, it converts the locked resources into universal tokens through smart contract A, transfers tokens worth M to resource pool A of metaverse A, returns the remaining tokens to account A, and destroys smart contract A.

[0098] At this point, the account link between account A and account B is completed.

[0099] All the above optional technical solutions can be arbitrarily combined to form optional embodiments of the present disclosure, and will not be described in detail here.

[0100] For scenarios where the same user synchronizes identities and identifies resources in the multiverse, biometric authentication can be performed separately in the multiverse to ensure that the accounts belong to the same user, facilitate account linking, and ensure the security of account linking, cross-chain contract message synchronization, and resource transfer.

[0101] In most related applications, tokens are not universal in different metaverses. If users have resources in Metaverse A and want to experience and consider transferring resources to Metaverse B, they do not need to convert resources into tokens in the target Metaverse. By locking resources in smart contracts and borrowing tokens from the resource pool, they can transfer tokens to Metaverse B, and quickly have a certain identity and resources in Metaverse B to facilitate the experience of most functions.

[0102] In the embodiment of the present application, the interaction between two metaverses is taken as an example. In specific applications, it is not limited to two metaverses, but can be expanded to the multiverse, which provides convenience for users to experience different metaverses, promotes the development of the metaverse, and expands to the multiverse. For example, by operating two by two, it is possible to realize account association, resource transfer, and release of account association between the three metaverses.

[0103] Based on the same inventive concept, the embodiment of the present application also provides a resource transfer device in the metaverse. Figure 7 , Figure 7 This is a schematic diagram of the structure of a resource transfer device in the metaverse in the embodiment of this application. The device includes: The first transfer unit 701 is used to transfer the resources specified by the user to the first smart contract; the first smart contract is created by the user in the first metaverse when the first account of the first metaverse is linked to the second account of the second metaverse; An evaluation unit 702 is used to evaluate the loanable Token value of the resource to obtain a Token value M; The second transfer unit 703 is used to transfer the universal token with a value of M from the resource pool of the first metaverse to the first smart contract; the resource pool of the first metaverse is created when the first metaverse is established; The first smart contract 704 is used to initiate a resource lock request; and lock the resource; transfer the token worth M to the second smart contract; so that the second smart contract locks the token worth M and transfers the token worth M from the resource pool of the second metaverse to the second account; the second smart contract is created in the second metaverse when the user's first account in the first metaverse is linked to the second account in the second metaverse; the resource pool of the second metaverse is created when the second metaverse is established.

[0104] In another embodiment, The first smart contract 704 evaluates the loanable Token value of the resource, and when the Token value M is obtained, the resource type of the resource is obtained; according to the resource type, it is determined whether the resource is a homogeneous resource; if so, the latest purchase and sale price of the resource in the free market is used as the valuation benchmark; according to the valuation benchmark and the preset safety factor, the loanable Token value is obtained; if not, a bidding request is initiated for the resource in the free market to create a third smart contract; a limited-time public bidding is conducted in the free market through the third smart contract; and the Tokens transferred by the users participating in the bidding are locked; at the end of the bidding, the highest bid is used as the valuation benchmark; according to the valuation benchmark and the preset safety factor, the loanable Token value is obtained, and the third smart contract is destroyed.

[0105] In another embodiment, The resources in the resource pool are composed of the basic pool and the liquidity pool; Among them, the resources in the basic pool are provided by the Metaverse; the resources in the liquidity pool are provided by users.

[0106] In another embodiment, the apparatus further comprises: A creation unit 705, configured to create a first smart contract in response to a request initiated by a user who logs into a first account of a first metaverse to link to a second account of a second metaverse; The first smart contract 704 is used to send the request to the second metaverse through the first smart contract. The request carries the account information of the first account and the identity authentication information of the user, so that the second metaverse uses the biometric authentication information in the request for authentication; when the authentication is successful, create a second smart contract and record the account information of the first account; in response to the link success message sent by the second metaverse when the link is successful, record the account information of the second account and the link status as link success; in response to the link rejection message sent by the second metaverse due to authentication failure, feedback is given to the user and the first smart contract is destroyed.

[0107] In another embodiment, The first smart contract 704, when the monitoring period expires, updates the valuation benchmark of the resource according to whether the resource is a homogeneous resource, and determines the current Token value N of the resource and the current safety factor according to the valuation benchmark; if it is determined that the current Token value N of the resource and the current safety factor do not meet the preset resource lending conditions, notifies the user to supplement the resource and the Token value corresponding to the supplemented resource; in response to the resource corresponding to the Token value supplemented by the user, waits for the next period to continue monitoring; in response to not receiving the user's supplementary resources within the preset time or the value of the supplemented resources is less than the notified Token value, trades the resource according to whether the resource is a homogeneous resource; and transfers the Tokens of value M obtained from the transaction to the resource pool of the first metaverse, and transfers the Tokens exceeding the value M to the first account.

[0108] In another embodiment, the apparatus further comprises: The authentication unit 706 performs biometric authentication in response to a request to unlink an account initiated by a user; if the authentication is successful, determines the metaverse in which the resource is to be retained; The first smart contract 704 is used to lock the tokens worth M in the first smart contract if it is determined to retain the resources in the first and second metaverses, and send an account unlinking message to the second metaverse, so that after the biometric authentication is successful, the second metaverse transfers the locked tokens to the resource pool of the second metaverse through the second smart contract, sends a message of successful account unlinking to the first smart contract, and destroys the second smart contract; in response to the message of successful account unlinking sent by the second smart contract, transfers the locked tokens worth M to the resource pool, unlocks the resources, and destroys the first smart contract; If it is determined to retain the resources in the first Metaverse, a message for unlinking the account is sent to the second Metaverse, so that when the biometric authentication is successful, the second Metaverse converts the resources in the second account into universal tokens and transfers them to the second smart contract, sends a message of successful account unlinking to the first smart contract through the second smart contract, transfers the converted tokens with a value of Q to the first smart contract, and destroys the second smart contract; in response to the message of successful account unlinking sent by the second smart contract, determines whether Q is less than M. If so, notifies the user to make up the resources with a value of MQ, returns the tokens with a value of M to the resource pool, unlocks the resources and destroys the first smart contract; otherwise, returns the tokens with a value of M to the resource pool, unlocks the resources, transfers the remaining tokens with a value of QM and the locked resources to the first account, and destroys the first smart contract; If it is determined to retain the resources in the second Metaverse, an account unlinking message is sent to the second Metaverse, so that when the biometric authentication is successful, the second Metaverse sends the account unlinking success message to the first smart contract through the second smart contract, and destroys the second smart contract; in response to the account unlinking success message sent by the second smart contract, the locked resources are converted into general Tokens, Tokens worth M are transferred to the resource pool of the first Metaverse, the remaining Tokens are returned to the first account, and the first smart contract is destroyed.

[0109] In another embodiment, an electronic device is also provided, including a memory, a processor, and a computer program stored in the memory and executable on the processor, and when the processor executes the program, a resource transfer method in the metaverse is implemented.

[0110] In another embodiment, a computer-readable storage medium is provided, on which computer instructions are stored, and when the instructions are executed by a processor, a resource transfer method in a metaverse is implemented.

[0111] Figure 8 Schematic diagram of the physical structure of an electronic device provided by an embodiment of the present invention. Figure 8 As shown, the electronic device may include: a processor (Processor) 810, a communication interface (Communications Interface) 820, a memory (Memory) 830 and a communication bus 840, wherein the processor 810, the communication interface 820, and the memory 830 communicate with each other through the communication bus 840. The processor 810 may call the logic instructions in the memory 830 to execute the following method: Transferring resources specified by the user to a first smart contract; the first smart contract is created by the user in the first metaverse when the first account of the first metaverse is linked to the second account of the second metaverse; Initiate a resource locking request through the first smart contract; Evaluate the loanable Token value of the resource and obtain the Token value M; Transfer M universal tokens from the resource pool of the first metaverse to the first smart contract and lock the resources; Transfer Tokens worth M to the second smart contract through the first smart contract; enable the second smart contract to lock Tokens worth M and transfer Tokens worth M from the resource pool of the second metaverse to the second account; the second smart contract is created in the second metaverse when the user's first account in the first metaverse is linked to the second account in the second metaverse.

[0112] In addition, the logic instructions in the above-mentioned memory 830 can be implemented in the form of a software functional unit and can be stored in a computer-readable storage medium when it is sold or used as an independent product. Based on this understanding, the technical solution of the present invention can be essentially or partly embodied in the form of a software product that contributes to the prior art. The computer software product is stored in a storage medium, including several instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the methods of various embodiments of the present invention. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM, Read-Only Memory), random access memory (RAM, Random Access Memory), disk or optical disk, etc. Various media that can store program codes.

[0113] The device embodiments described above are merely illustrative, wherein the units described as separate components may or may not be physically separated, and the components displayed as units may or may not be physical units, that is, they may be located in one place, or they may be distributed on multiple network units. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this embodiment. Ordinary technicians in this field can understand and implement it without paying creative labor.

[0114] Through the description of the above implementation methods, those skilled in the art can clearly understand that each implementation method can be implemented by means of software plus a necessary general hardware platform, and of course, can also be implemented by hardware. Based on this understanding, the above technical solution is essentially or the part that contributes to the prior art can be embodied in the form of a software product, and the computer software product can be stored in a computer-readable storage medium, such as ROM / RAM, a disk, an optical disk, etc., including a number of instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to execute the methods described in each embodiment or some parts of the embodiments.

[0115] The flow chart and block diagram in the accompanying drawings of the present application show the possible architecture, function and operation of the system, method and computer program product according to the various embodiments disclosed in the present application. In this regard, each box in the flow chart or block diagram can represent a module, a program segment or a part of a code, and the above-mentioned module, program segment or a part of a code contains one or more executable instructions for realizing the specified logical function. It should also be noted that in some implementations as replacements, the functions marked in the box can also occur in the order of the standards in different figures. For example, the boxes represented by two connections can actually be executed substantially in parallel, and they can sometimes be executed in the opposite order, depending on the functions involved. It should also be noted that each box in the block diagram or flow chart, and the combination of the boxes in the block diagram or flow chart can be implemented with a dedicated hardware-based system that performs the specified function or operation, or can be implemented with a combination of dedicated hardware and computer instructions.

[0116] Those skilled in the art will appreciate that the features described in the various embodiments and / or claims disclosed in this application may be combined and / or combined in a variety of ways, even if such combinations and / or combinations are not explicitly described in this application. In particular, without departing from the spirit and teachings of this application, the features described in the various embodiments and / or claims of this application may be combined and / or combined in a variety of ways, and all of these combinations and / or combinations fall within the scope disclosed in this application.

[0117] Specific embodiments are used herein to illustrate the principles and implementation methods of the present invention. The description of the above embodiments is only used to help understand the method of the present invention and its core ideas, and is not used to limit the present application. For those skilled in the art, changes can be made in the specific implementation methods and application scopes according to the ideas, spirits and principles of the present invention, and any modifications, equivalent substitutions, improvements, etc. made therein should be included in the scope of protection of this application.

Claims

1. A method for transferring resources in a metaverse, characterized in that: The method comprises: Transferring resources specified by the user to a first smart contract; the first smart contract is created by the user in the first metaverse when the first account of the first metaverse is linked to the second account of the second metaverse; Initiating a lock request for the resource through the first smart contract; Evaluate the loanable Token value of the resource to obtain a Token value M; Transfer M universal tokens from the resource pool of the first metaverse to the first smart contract and lock the resources; the resource pool of the first metaverse is created when the first metaverse is established; Transferring Tokens worth M to the second smart contract through the first smart contract; enabling the second smart contract to lock Tokens worth M and transfer Tokens worth M from the resource pool of the second metaverse to the second account; the second smart contract is created in the second metaverse when the first account of the user in the first metaverse is linked to the second account in the second metaverse; the resource pool of the second metaverse is created when the second metaverse is established.

2. The method according to claim 1, characterized in that The step of evaluating the loanable Token value of the resource to obtain the Token value M includes: Get the resource type of the resource; Determining whether the resource is a homogeneous resource according to the resource type; If yes, the latest price of the resource in the free market is used as the valuation benchmark; the loanable Token value is obtained based on the valuation benchmark and the preset safety factor; If not, initiate a bidding request in the free market for the resource to create a third smart contract; conduct a limited-time public bidding in the free market through the third smart contract; and lock the tokens transferred by the users participating in the bidding; at the end of the bidding, use the highest bid as the valuation benchmark; obtain the loanable token value based on the valuation benchmark and the preset safety factor, and destroy the third smart contract.

3. The method according to claim 1, characterized in that The resources in the resource pool are composed of a basic pool and a flow pool; Among them, the resources in the basic pool are provided by the Metaverse; the resources in the liquidity pool are provided by users.

4. The method according to claim 1, characterized in that: The method further comprises: In response to a request initiated by a user who logs into a first account of the first metaverse to link to a second account of the second metaverse, creating a first smart contract; Sending the request to the second metaverse through the first smart contract, the request carrying the account information of the first account and the identity authentication information of the user, so that the second metaverse uses the biometric authentication information in the request for authentication; when the authentication is successful, creating a second smart contract and recording the account information of the first account; In response to a link success message sent by the second metaverse when the link is successful, the account information of the second account and the link status as link success are recorded through the first smart contract; In response to a link rejection message sent by the second metaverse due to authentication failure, feedback is given to the user through the first smart contract, and the first smart contract is destroyed.

5. The method according to claim 1, characterized in that The method further comprises: When the monitoring period is up, the valuation benchmark of the resource is updated according to whether the resource is a homogeneous resource, and the current Token value N and the current safety factor of the resource are determined according to the valuation benchmark; If it is determined that the current Token value N of the resource and the current security factor do not meet the preset resource lending conditions, notify the user to supplement the resource and the Token value corresponding to the supplemented resource; In response to the resource corresponding to the Token value supplemented by the user, waiting for the next cycle to continue monitoring; In response to not receiving the supplementary resources from the user within the preset time or the value of the supplemented resources is less than the notified Token value, the resources are traded according to whether the resources are homogeneous resources; and the Tokens with a value of M obtained from the transaction are transferred to the resource pool of the first metaverse, and the Tokens exceeding the value of M are transferred to the first account.

6. The method according to claim 1, characterized in that The method further comprises: In response to a request to unlink an account initiated by the user, performing biometric authentication; If the authentication is successful, the Metaverse in which the resource is to be retained is determined; If it is determined to retain the resources in the first and second metaverses, the tokens worth M are locked in the first smart contract, and a message for unlinking the account is sent to the second metaverse through the first smart contract, so that after the biometric authentication is successful, the second metaverse transfers the locked tokens to the resource pool of the second metaverse through the second smart contract, sends a message of successful unlinking of the account to the first smart contract, and destroys the second smart contract; In response to the message of successful account link release sent by the second smart contract, the locked Tokens worth M are transferred to the resource pool through the first smart contract, the resources are unlocked, and the first smart contract is destroyed.

7. The method according to claim 6, characterized in that The method further comprises: If it is determined to retain the resources in the first metaverse, a message for unlinking the account is sent to the second metaverse through the first smart contract, so that when the biometric authentication is successful, the second metaverse converts the resources in the second account into universal tokens and transfers them to the second smart contract. A message for successfully unlinking the account is sent to the first smart contract through the second smart contract, and the converted tokens with a value of Q are transferred to the first smart contract, and the second smart contract is destroyed; In response to the account link release success message sent by the second smart contract, determine whether Q is less than M. If so, notify the user to make up the resources with a value of MQ, return the tokens with a value of M to the resource pool through the first smart contract, unlock the resources and destroy the first smart contract; otherwise, return the tokens with a value of M to the resource pool through the first smart contract, unlock the resources, transfer the remaining tokens with a value of QM and the locked resources to the first account, and destroy the first smart contract.

8. The method according to claim 6, characterized in that The method further comprises: If it is determined to retain the resources in the second Metaverse, a message for unlinking the account is sent to the second Metaverse through the first smart contract, so that when the biometric authentication is successful, the second Metaverse sends a message of successful unlinking of the account to the first smart contract through the second smart contract and destroys the second smart contract; In response to the account link release success message sent by the second smart contract, the locked resources are converted into universal tokens through the first smart contract, tokens worth M are transferred to the resource pool of the first metaverse, the remaining tokens are returned to the first account, and the first smart contract is destroyed.

9. A resource transfer device in a metaverse, characterized in that: The device comprises: A first transfer unit, configured to transfer resources specified by a user to a first smart contract; the first smart contract is created by the user in the first metaverse when a first account in the first metaverse is linked to a second account in the second metaverse; An evaluation unit, configured to evaluate the loanable Token value of the resource to obtain a Token value M; A second transfer unit is used to transfer a universal token with a value of M from the resource pool of the first metaverse to the first smart contract; the resource pool of the first metaverse is created when the first metaverse is established; The first smart contract is used to initiate a lock request for the resource; and lock the resource; transfer the token worth M to the second smart contract; so that the second smart contract locks the token worth M and transfers the token worth M from the resource pool of the second metaverse to the second account; the second smart contract is created in the second metaverse when the first account of the user in the first metaverse is linked to the second account in the second metaverse; the resource pool of the second metaverse is created when the second metaverse is established.

10. An electronic device comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the program, the method according to any one of claims 1 to 8 is implemented.

11. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the program is executed by a processor, the method described in any one of claims 1 to 8 is implemented.