Asset digitalization processing method, electronic device, and medium

Abstract

The application is suitable for the technical field of asset digitization, and provides a processing method for asset digitization, an electronic device and a medium.The method comprises the following steps: acquiring asset configuration information of a target asset; determining a first smart contract corresponding to the target asset according to a target non-fungible token protocol and a preset smart contract set, and determining a second smart contract corresponding to the target asset according to a target fungible token protocol and the smart contract set; and sending the first smart contract, the second smart contract, first sub-information and second sub-information to a blockchain system, so that the blockchain system creates at least one non-fungible token corresponding to the target asset according to the first smart contract and the first sub-information, and creates a fungible token for each non-fungible token according to the second smart contract and the second sub-information. The liquidity of the rwa asset in the blockchain system is improved, and the difficulty of rwa asset digitization is reduced.

Description

Technical Field

[0001] This application belongs to the field of asset digitization technology, and in particular relates to asset digitization processing methods, electronic devices and media. Background Technology

[0002] In blockchain systems, the digitization of real-world assets (RWA) can break the limitations of traditional asset trading in terms of geography, time, and transaction processes, thus greatly expanding the scope of asset circulation.

[0003] Current RWA asset digitization typically relies on the asset type, issuing either fungible tokens (FTs) or non-fungible tokens (NFTs). However, FTs are difficult to precisely anchor to off-chain RWA assets, resulting in inaccurate asset value mapping, limited investor trust, and consequently, impacting the liquidity of RWA assets within the blockchain system. While NFTs can reflect asset uniqueness, their unit asset shares are often too large to be easily divided, significantly restricting the liquidity of RWA assets within the blockchain system. Furthermore, RWA asset digitization often requires customized smart contracts for specific RWA assets, lacking universality.

[0004] Therefore, improving the liquidity of RWA assets in blockchain systems and reducing the difficulty of digitizing RWA assets have become urgent technical problems that need to be solved. Summary of the Invention

[0005] This application provides a method, electronic device, and medium for asset digitization, which can solve the problems of how to improve the liquidity of RWA assets in the blockchain system and reduce the difficulty of RWA asset digitization.

[0006] In a first aspect, embodiments of this application provide a method for asset digitization, applied to electronic devices, the method comprising:

[0007] Obtain the asset allocation information of the target asset. The asset allocation information includes the target non-fungible token protocol, the target fungible token protocol, the first sub-information, and the second sub-information corresponding to the target asset. The first sub-information is used to instruct the blockchain system to create the non-fungible token corresponding to the target asset, and the second sub-information is used to instruct the blockchain system to create the fungible token corresponding to the non-fungible token.

[0008] Based on the target non-fungible token protocol and the pre-defined set of smart contracts, a first smart contract corresponding to the target asset is determined, and based on the target fungible token protocol and the set of smart contracts, a second smart contract corresponding to the target asset is determined. The set of smart contracts includes smart contracts corresponding to multiple non-fungible token protocols and smart contracts corresponding to multiple fungible token protocols.

[0009] The first smart contract, the second smart contract, the first sub-information, and the second sub-information are sent to the blockchain system so that the blockchain system can create at least one non-fungible token corresponding to the target asset based on the first smart contract and the first sub-information, and create a fungible token for each non-fungible token based on the second smart contract and the second sub-information. Nodes in the blockchain system can then trade the target asset based on the fungible tokens.

[0010] In some embodiments, obtaining the asset configuration information of the target asset includes:

[0011] Obtain the asset metadata of the target asset, which includes asset configuration information;

[0012] If the asset metadata meets the first condition, the asset configuration information is extracted from the asset metadata. The first condition includes that the data format of the asset metadata is a preset format and that the asset specification file of the target asset in the asset metadata meets the preset rules.

[0013] In some embodiments, before sending the first smart contract, the second smart contract, the first sub-information, and the second sub-information to the blockchain system, the method further includes:

[0014] Based on the first sub-information, parse the first initialization parameters corresponding to the first smart contract;

[0015] Based on the second sub-information and the first initialization parameters, parse the second initialization parameters corresponding to the second smart contract;

[0016] Sending the first smart contract, the second smart contract, the first sub-information, and the second sub-information to the blockchain system includes:

[0017] The first smart contract, the second smart contract, the second initialization parameters, and the first initialization parameters are sent to the blockchain system so that the blockchain system can deploy the first smart contract based on the first initialization parameters and deploy the second smart contract based on the second initialization parameters, so as to subsequently obtain non-fungible tokens and fungible tokens.

[0018] In some embodiments, the method further includes:

[0019] If the asset metadata meets the first condition, the asset metadata will be stored in a distributed storage system.

[0020] Obtain the storage link corresponding to the asset metadata returned by the distributed storage system;

[0021] The storage link is stored in the first sub-information so that the subsequent blockchain system can create at least one non-fungible token based on the first sub-information and the first smart contract.

[0022] Secondly, embodiments of this application provide a method for processing asset digitization, applied to a blockchain system as described in any embodiment of the first aspect, the method comprising:

[0023] Obtain the first smart contract, the second smart contract, the first sub-information, and the second sub-information corresponding to the target asset. The first sub-information is used to instruct the blockchain system to create a non-fungible token corresponding to the target asset. The second sub-information is used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token. The first smart contract is a smart contract determined by the electronic device based on the target non-fungible token protocol corresponding to the target asset. The second smart contract is a smart contract determined by the electronic device based on the target fungible token protocol corresponding to the target asset.

[0024] Based on the first sub-information, create at least one non-fungible token corresponding to the target asset through the first smart contract;

[0025] Based on the second sub-information, a fungible token is created for each non-fungible token through a second smart contract, enabling nodes in the blockchain system to trade the target asset based on the fungible token.

[0026] In some embodiments, the method further includes:

[0027] When a user's first operation request for a target fungible token is detected, the user's first operation permission is verified. The first operation permission is used to indicate whether the user can perform the first operation for the target fungible token. The first operation includes creating a target fungible token, transferring a target fungible token, destroying a target fungible token, freezing the account corresponding to the target fungible token, redeeming a target fungible token, or subscribing to a target fungible token. The target fungible token is any fungible token corresponding to the target asset.

[0028] If the first operation permission is granted, execute the first operation corresponding to the first operation request on the target fungible token.

[0029] In some embodiments, performing a first operation corresponding to a first operation request on a target fungible token includes:

[0030] If the first operation is to redeem the target fungible token, obtain the asset value and trading rules corresponding to the target fungible token;

[0031] If the transaction rules include information restricting the first operation, it is determined that the first operation on the target fungible token failed.

[0032] If the transaction rules include information allowing the first operation, stablecoins corresponding to the asset value are extracted from the stablecoin vault of the blockchain system, and the extracted stablecoins are stored in the user's corresponding account node in the blockchain system.

[0033] Thirdly, embodiments of this application provide an electronic device including a processor, a memory, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it causes the electronic device to perform the method described in any embodiment of the first aspect.

[0034] Fourthly, embodiments of this application provide a blockchain system, which includes:

[0035] The data acquisition component is used to acquire the first smart contract, the second smart contract, the first sub-information, and the second sub-information corresponding to the target asset. The first sub-information is used to instruct the blockchain system to create a non-fungible token corresponding to the target asset. The second sub-information is used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token. The first smart contract is a smart contract determined by the electronic device based on the target non-fungible token protocol corresponding to the target asset. The second smart contract is a smart contract determined by the electronic device based on the target fungible token protocol corresponding to the target asset.

[0036] A non-fungible token component is used to create at least one non-fungible token corresponding to the target asset through a first smart contract based on the first sub-information.

[0037] The fungible token component is used to create fungible tokens for each non-fungible token through a second smart contract based on second sub-information, so that nodes in the blockchain system can trade target assets based on fungible tokens.

[0038] Fifthly, embodiments of this application provide a computer-readable storage medium storing a computer program that, when executed, causes the asset digitization processing method as described in any embodiment of the first aspect or any embodiment of the second aspect to be performed.

[0039] In a sixth aspect, embodiments of this application provide a computer program product that, when executed, causes the asset digitization processing method as described in any embodiment of the first aspect or any embodiment of the second aspect to be performed.

[0040] The beneficial effects of the embodiments in this application compared with the prior art are:

[0041] Based on pre-configured token protocols in the asset allocation information, the first and second smart contracts corresponding to the target asset are automatically determined from a pre-set set of smart contracts. This eliminates the need to develop and customize smart contracts for different assets, reducing the difficulty of asset digitization. Furthermore, the first and second sub-information are pre-configured in the asset allocation information, enabling the blockchain system to create at least one non-fungible token corresponding to the target asset based on the first smart contract and the first sub-information, thus achieving the anchoring of digital tokens to real-world assets. The blockchain system then creates fungible tokens for each non-fungible token based on the second smart contract and the second sub-information. This allows for the division of non-fungible tokens with excessively large unit shares into smaller fungible tokens, facilitating the circulation of the target asset in the cross-chain system through smaller fungible tokens. Simultaneously, it enables fungible tokens to be anchored to the target asset through non-fungible tokens, thereby improving the liquidity of RWA assets within the blockchain system. Attached Figure Description

[0042] To more clearly illustrate the technical solutions in the embodiments of this application, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0043] Figure 1 This is a schematic diagram of the structure of an asset digitization system provided in an embodiment of this application;

[0044] Figure 2 This is a flowchart illustrating a method for asset digitization provided in an embodiment of this application;

[0045] Figure 3 This is provided by the embodiments of this application. Figure 1 as well as Figure 2 A schematic diagram of the blockchain system in any embodiment;

[0046] Figure 4 This is a flowchart illustrating another asset digitization processing method provided in the embodiments of this application;

[0047] Figure 5 This is a schematic diagram illustrating a method for digitizing assets using a blockchain system in an application scenario.

[0048] Figure 6 This is a schematic diagram of the structure of an electronic device provided in an embodiment of this application. Detailed Implementation

[0049] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0050] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0051] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0052] As used in this application specification and the appended claims, the term "if" may be interpreted, depending on the context, as "when," "once," "in response to determination," or "in response to detection." Similarly, the phrases "if determined" or "if detected [the described condition or event]" may be interpreted, depending on the context, as meaning "once determined," "in response to determination," "once detected [the described condition or event]," or "in response to detection [the described condition or event]."

[0053] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0054] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0055] Current digitization solutions for RWA assets often involve creating NFT tokens for unique or unquantifiable RWA assets such as real estate or art, and FT tokens for quantifiable RWA assets such as stocks or securities. However, FT tokens are difficult to accurately anchor to off-chain real-world assets, resulting in inaccurate asset value mapping, limited investor trust, and consequently affecting trading activity and liquidity. While NFT tokens can reflect asset uniqueness, the unit asset share is often too large to be easily divided, deterring small and medium-sized investors and hindering widespread participation, significantly restricting the speed and frequency of asset circulation in the market. This severely limits the liquidity of RWA assets within the blockchain system.

[0056] Moreover, the current digitization of RWA assets often requires customized smart contracts for specific RWA assets. This development model, which lacks universality, consumes a lot of time and manpower, increases the difficulty of digitizing RWA assets, and makes it difficult for different RWA assets to form an efficient collaborative and interactive ecosystem, ultimately affecting the liquidity of the entire RWA asset in the blockchain system.

[0057] To address the aforementioned issues, this application provides a method, electronic device, and medium for asset digitization. It can automatically determine corresponding smart contracts based on asset allocation information, issue NFT tokens corresponding to RWA assets, and further issue FT tokens based on the NFT tokens. This eliminates the need for custom smart contract development. Furthermore, it allows for the allocation of NFT tokens through FT tokens and the anchoring of FT tokens to real assets via NFT tokens. This improves the liquidity of RWA assets within the blockchain system while reducing the difficulty of RWA asset digitization.

[0058] To illustrate the technical solution of this application, specific embodiments are described below.

[0059] Figure 1 This is a schematic diagram of the structure of an asset digitization system provided in an embodiment of this application. This asset digitization system is applicable to the asset digitization processing method of this application, such as... Figure 1 As shown, the asset digitization system consists of a blockchain system and off-chain electronic devices, including data acquisition components, smart contract adaptation components, and automatic execution components.

[0060] The data processing component is used to obtain the asset configuration information of the target asset. The asset configuration information includes the target non-fungible token protocol, the target fungible token protocol, the first sub-information, and the second sub-information corresponding to the target asset. The first sub-information is used to instruct the blockchain system to create the non-fungible token corresponding to the target asset, and the second sub-information is used to instruct the blockchain system to create the fungible token corresponding to the non-fungible token.

[0061] The smart contract adaptation component is used to determine the first smart contract corresponding to the target asset based on the target non-fungible token protocol and a preset smart contract set. The smart contract set includes smart contracts corresponding to different non-fungible token protocols and fungible token protocols respectively. Based on the target fungible token protocol and the smart contract set, the component determines the second smart contract corresponding to the target asset.

[0062] An automated execution component is used to create at least one non-fungible token corresponding to a target asset in a blockchain system based on a first smart contract and first sub-information; and to create a fungible token for each non-fungible token in a blockchain system based on a second smart contract and second sub-information, with nodes in the blockchain system trading the target asset based on the fungible tokens.

[0063] Electronic devices can be servers, desktop computers, laptops, etc., and the embodiments of this application do not limit the specific types of electronic devices.

[0064] In some embodiments, the asset digitization system further includes a distributed storage system, and the data processing components include a data gateway and an asset metadata sub-component. The data gateway receives asset data of the target asset input by the user, parses the asset data into asset metadata, and sends the asset metadata to the asset metadata sub-component. The asset data is the original and detailed record information of the target asset, which can cover specific details of various aspects such as the physical and economic attributes of the target asset. The asset metadata is a set of key information extracted from the asset data and used for managing, identifying, and understanding the asset. For example, taking real estate as an example, asset data may include the precise geographical location of the property, the type and specifications of building materials, the number of floors, the floor plan, the area of ​​the property, and the facilities and equipment of the property. The asset metadata may include information such as the type of property (residential, commercial, or industrial), the real estate market grade of the area, and the construction year range of the property.

[0065] The asset metadata subcomponent is used to verify whether the asset metadata conforms to the standards (e.g., whether the asset metadata format is correct, whether the asset specification documents such as the ownership documents and / or contract documents of the target asset carry a signature, etc.). After confirming that the asset metadata is qualified, it stores the asset metadata in the distributed storage system and receives the storage link corresponding to the asset metadata returned by the distributed storage system; and it extracts the asset configuration information of the target asset based on the asset metadata and sends the asset configuration information to the smart contract adaptation component so that the smart contract adaptation component can determine the smart contract corresponding to the target asset.

[0066] In the above technical solution, the data gateway automatically parses the asset data into asset metadata, and the asset metadata sub-component automatically verifies whether the asset data conforms to the standard, providing a solid and reliable data foundation for the digitization of target assets, such as RWA assets.

[0067] In some embodiments, the smart contract adaptation component is specifically used to generate initialization parameters for contract deployment based on asset configuration, and forward the smart contract to be deployed and the initialization parameters to the automatic execution component. The smart contract to be deployed includes a first smart contract and a second smart contract, and the initialization parameters include a first initialization parameter corresponding to the first smart contract and a second initialization parameter corresponding to the second smart contract.

[0068] The automated execution component packages the smart contracts to be deployed and initialization parameters into a transaction and sends the transaction to the corresponding blockchain system so that the blockchain system can deploy the smart contract corresponding to the target asset on the chain.

[0069] In the above technical solution, the smart contract adaptation component can automatically determine the initialization parameters required for contract deployment based on asset configuration, and the automatic execution component can package the smart contract to be deployed and the initialization parameters into a transaction and send it to the blockchain system, thereby realizing the fully automated deployment of smart contracts for the target asset and improving the deployment efficiency of smart contracts corresponding to RWA assets.

[0070] In some embodiments, the automatic execution component is also used to receive transaction information returned by the blockchain system, parse contract information from the transaction information, and send the contract information to the data gateway. The transaction information may include contract information, the identity information of the users participating in the transaction target asset, the type and description of the target asset, and the total amount of the target asset, etc. The contract information may include the pricing mechanism, trading method, and rights and interests of the issuer of the target asset, etc.

[0071] The data gateway is also used to generate the issuance results of the target asset based on contract information and send the issuance results to the preset user terminal. The issuance results may include the total issuance of non-fungible tokens and fungible tokens, the initial issuance price of fungible tokens, non-fungible tokens and fungible tokens corresponding to each non-fungible token, and an explanation of the price formation mechanism of non-fungible tokens and fungible tokens.

[0072] In the above technical solution, the contract information is parsed from the transaction information through the automatic execution component, and the specific issuance results of the target asset are provided to the user through the data gateway, so that the user can view the relevant data in a timely manner and improve the user's trading experience of RWA assets in the blockchain system.

[0073] Figure 2This is a flowchart illustrating an asset digitization processing method provided in an embodiment of this application. The method is applied to... Figure 1 The electronic device in any of the embodiments shown, such as Figure 2 The method shown includes the following steps:

[0074] Step S101: Obtain the asset allocation information of the target asset.

[0075] In this embodiment, the asset allocation information includes the target non-fungible token protocol corresponding to the target asset, the target fungible token protocol, a first sub-information, and a second sub-information. The first sub-information is used to instruct the blockchain system to create a non-fungible token corresponding to the target asset, and the second sub-information is used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token. The target asset can be an RWA asset such as stocks, securities, real estate, or artwork; this embodiment does not impose specific limitations. Taking real estate as an example, the first sub-information may include the storage link corresponding to the target asset, the name, description, quantity, initial price, rights holder, and pricing mechanism of the non-fungible token, etc. The second sub-information may include the name, symbol, precision, valuation frequency, and minimum trading unit of the fungible token corresponding to each non-fungible token, etc. These details can be set for different target asset types; this embodiment does not impose specific limitations.

[0076] Electronic devices can provide users with an interface for issuing assets. When a user needs to issue a target asset, they can enter the asset configuration information of the target asset into the interface, and the electronic device will then obtain the asset configuration information. It is understood that the interface will prompt the user to enter at least the target non-fungible token protocol, the target fungible token protocol, the first sub-information, and the second sub-information of the target asset.

[0077] In one implementation, obtaining the asset allocation information of the target asset includes:

[0078] Obtain the asset metadata of the target asset, which includes asset configuration information;

[0079] If the asset metadata meets the first condition, the asset configuration information is extracted from the asset metadata. The first condition includes that the data format of the asset metadata is a preset format and that the asset specification file of the target asset in the asset metadata meets the preset rules.

[0080] Asset specification documents refer to a series of documents used to prove that the target asset meets the requirements at multiple levels, such as industry standards, relevant regulations, and contractual agreements. These documents may include at least one of the following: the target asset's ownership certificate, licenses and permits, transaction contracts, tax payment certificates, or quality certification certificates.

[0081] Electronic devices can receive asset data of a target asset provided by a user through their own data gateway. The asset data includes at least the asset specification document and asset configuration information of the target asset. The specific method by which the data gateway parses the asset data into asset metadata is not specifically limited in this embodiment and can be chosen based on requirements. For example, the asset metadata sub-component can select attributes representing the core characteristics of the asset from the asset data as asset metadata; or, based on specific classification standards, information conforming to the standards can be filtered from the asset data as asset metadata; or, multiple related pieces of information in the asset data can be aggregated and transformed to generate asset metadata, which is then verified. If the asset metadata meets a first condition, asset configuration information can be extracted from the asset metadata. If the asset metadata does not meet the first condition, an alarm message is sent to a preset user terminal, indicating that the target asset data is incorrect and the asset digitization process for the target asset has failed.

[0082] In the above technical solution, after verifying the data format of the asset metadata and the asset specification document of the target asset, the asset configuration information is extracted from the asset metadata only after the verification is passed, which improves the security of the subsequent on-chain blockchain system of the target asset and thus ensures the security of the transaction target asset.

[0083] In one implementation, the method further includes: storing the asset metadata in a distributed storage system if the asset metadata meets the first condition;

[0084] Obtain the storage link corresponding to the asset metadata returned by the distributed storage system;

[0085] The storage link is stored in the first sub-information so that the subsequent blockchain system can create at least one of the non-fungible tokens based on the first sub-information and the first smart contract.

[0086] The storage link includes the storage address of asset metadata in the distributed system. Electronic devices can send asset metadata to the distributed storage system via the asset metadata sub-component. The distributed storage system stores the received asset metadata, generates a storage link corresponding to the asset metadata, and returns the storage link to the asset metadata sub-component. The asset metadata sub-component then sends the storage link to the smart contract adaptation component, which in turn sends it to the blockchain system via an automatic execution component. The blockchain system subsequently executes a first smart contract, which generates at least one non-fungible token for the storage link based on the first sub-information.

[0087] In the above technical solution, a distributed storage system is used to store the asset metadata of the target asset, which can save the storage resources of electronic devices. The storage link corresponding to the asset metadata is sent to the blockchain system so that the non-fungible token of the target asset includes the storage link, thereby further strengthening the association between the non-fungible token and the target asset.

[0088] Step S102: Based on the target non-fungible token protocol and the preset smart contract set, determine the first smart contract corresponding to the target asset, and based on the target fungible token protocol and the smart contract set, determine the second smart contract corresponding to the target asset.

[0089] In this embodiment, the smart contract set includes smart contracts corresponding to multiple non-fungible token protocols and smart contracts corresponding to multiple fungible token protocols. The multiple non-fungible token protocols may include Ethereum Request for Comment 721 (ERC721), ERC1155, and TRON Request for Comment 721 (TRC721). The multiple fungible token protocols may include ERC20 or TRC20; the specific choice is optional and this embodiment does not impose any specific limitations.

[0090] Electronic devices can use their own smart contract adaptation components to match a first smart contract corresponding to the target non-fungible token protocol from the smart contract set, and then match a second smart contract corresponding to the target fungible token protocol from the smart contract set.

[0091] In one implementation, before sending the first smart contract, the second smart contract, the first sub-information, and the second sub-information to the blockchain system, the following steps are also included:

[0092] Based on the first sub-information, parse the first initialization parameters corresponding to the first smart contract;

[0093] Based on the second sub-information, parse the second initialization parameters corresponding to the second smart contract;

[0094] Sending the first smart contract, the second smart contract, the first sub-information, and the second sub-information to the blockchain system includes:

[0095] The first smart contract, the second smart contract, the second initialization parameters, and the first initialization parameters are sent to the blockchain system so that the blockchain system can deploy the first smart contract based on the first initialization parameters and deploy the second smart contract based on the second initialization parameters, so as to subsequently obtain non-fungible tokens and fungible tokens.

[0096] The first initialization parameters include at least one of the following: the initial price of the target asset, owner information, the number of equity shares, transfer and trading rights, trading restrictions, or transaction fees. The second initialization parameters include at least one of the following: the share ratio of the fungible tokens corresponding to each non-fungible token, the minimum trading unit, transaction fees, distribution conditions for value-added revenue, or trading time restrictions.

[0097] For example, when determining non-fungible tokens (NFTs) for a company's stock and creating fungible tokens for those NFTs, the first sub-information includes historical stock issuance prices and company background information (years of establishment, company address, and historical performance, etc.), while the second sub-information includes the total amount of fungible tokens the company expects.

[0098] The electronic device analyzes the first piece of information through a smart contract adapter component, determines the name and code of the company's stock, sets the initial par value of the stock at 10 yuan, and sets the generation of 5 non-fungible tokens. Simultaneously, it determines the company as the initial owner of the stock and sets the transaction fee at 1% of the transaction amount, with each party bearing 0.5%. The stock name and code, initial par value, total number of non-fungible tokens (5), initial owner, and transaction fee are defined as the first initialization parameters.

[0099] Simultaneously, the electronic device can analyze the second sub-information and the first initialization parameters through the smart contract adaptation component to clarify that the fungible token is a subdivision of the non-fungible token corresponding to the company's stock. The association between the non-fungible token and the fungible token is determined. For example, if each non-fungible token represents 5 shares, each non-fungible token is further subdivided into 10 fungible tokens, each representing 0.5 shares. This association clearly defines the value basis of the fungible token, allowing investors to indirectly hold the company's stock through the fungible token. The initial value of each fungible token can be determined to be 5 yuan based on this association and the initial face value. The transaction fee for the fungible token is set at 0.5% of the transaction amount, with each party bearing 0.25%. Thus, the electronic device obtains a total of 25 fungible tokens. The total number of fungible tokens, each of the aforementioned associations, the initial value of each fungible token, and the transaction fee are used as the second initialization parameters.

[0100] The electronic device sends the first initialization parameters, the second initialization parameters, the first smart contract, and the second smart contract to the automatic execution component through the smart contract adaptation component. The automatic execution component packages this information into a transaction and sends it to the blockchain system to instruct the blockchain system to deploy the first smart contract and the second smart contract, and to generate non-fungible tokens and fungible tokens.

[0101] In the above technical solution, the electronic device can determine the initialization parameters corresponding to the smart contract based on relevant information, and send the smart contract and initialization parameters to the blockchain system. This allows the blockchain system to automatically deploy the relevant smart contract, achieving fully automated deployment of the smart contract for RWA assets and accelerating the digitization of RWA assets. Furthermore, it eliminates the need for manual customization of smart contracts and related parameters, reducing the difficulty of digitizing RWA assets.

[0102] Step S103: The first smart contract, the second smart contract, the first sub-information, and the second sub-information are sent to the blockchain system so that the blockchain system can create at least one non-fungible token corresponding to the target asset based on the first smart contract and the first sub-information, and create a fungible token for each non-fungible token based on the second smart contract and the second sub-information. Nodes in the blockchain system can then trade the target asset based on the fungible tokens.

[0103] Electronic devices can use their own automatic execution components to package a first smart contract, a second smart contract, a first sub-information, and a second sub-information into a transaction and send it to the blockchain system. The blockchain system can then deploy the first and second smart contracts on its on-chain network based on the received transaction. The first smart contract issues at least one non-fungible token for the target asset, and the second smart contract issues corresponding fungible tokens for each non-fungible token. In this way, users within the blockchain system can trade the target asset based on fungible tokens through nodes within the system.

[0104] In this embodiment, based on the pre-configured token protocols in the asset configuration information, the first and second smart contracts corresponding to the target asset are automatically determined from a pre-set set of smart contracts. This eliminates the need to develop and customize smart contracts for different assets, reducing the difficulty of asset digitization. Furthermore, the first and second sub-information are pre-configured in the asset configuration information, enabling the blockchain system to create at least one non-fungible token corresponding to the target asset based on the first smart contract and the first sub-information, thus achieving the anchoring of digital tokens to real-world assets. The blockchain system then creates fungible tokens for each non-fungible token based on the second smart contract and the second sub-information. This achieves the purpose of dividing non-fungible tokens with excessively large unit shares into smaller shares, facilitating the circulation of the target asset in the cross-chain system through small-share fungible tokens, while also enabling fungible tokens to be anchored to the target asset through non-fungible tokens, thereby improving the liquidity of RWA assets in the blockchain system.

[0105] Figure 3 yes Figure 1 as well as Figure 2 A schematic diagram of the blockchain system in any embodiment, such as Figure 3As shown, the blockchain system includes a receiving component, a non-fungible token component, and a fungible token component.

[0106] The data acquisition component is used to receive a first smart contract, a second smart contract, a first sub-information, and a second sub-information sent by an electronic device. The first sub-information is used to instruct the blockchain system to create a non-fungible token corresponding to the target asset. The second sub-information is used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token. The first smart contract is a smart contract determined by the electronic device based on the target non-fungible token protocol corresponding to the target asset. The second smart contract is a smart contract determined by the electronic device based on the target fungible token protocol corresponding to the target asset.

[0107] A non-fungible token component is used to create at least one non-fungible token corresponding to the target asset based on the first sub-information and the first smart contract.

[0108] The fungible token component is used to create fungible tokens for each non-fungible token through a second smart contract based on second sub-information, so that nodes in the blockchain system can trade target assets based on fungible tokens.

[0109] In some embodiments, see continue to see Figure 3 The blockchain system also includes a permission management component for managing operational permissions for fungible tokens. These permissions include at least one of the following: freezing the account associated with the fungible token, minting (also known as creating), burning, or transferring the fungible token. Specifically, when the permission management component detects a user's operational request for a target fungible token, it verifies the user's operational permissions for the corresponding operation. If the user's operational permissions are verified, the corresponding operation in the operational request is executed on the target fungible token.

[0110] In some embodiments, the blockchain system also includes a fungible token management component. The fungible token manager is used to manage subscription and redemption operations for fungible tokens. After the target asset issues fungible tokens on the chain, the blockchain system can provide on-chain investors with an entry point for subscription (i.e., investment) and redemption through the fungible token management component.

[0111] In some embodiments, the blockchain system further includes an investment management component for managing investment permissions and value control logic for fungible tokens. For example, it determines whether the fungible tokens corresponding to the target asset are allowed to be subscribed and redeemed, and calculates the value represented by each fungible token. It can be understood that when determining the value represented by each fungible token, the investment management component can be coupled with an oracle contract (e.g., an oracle contract) to provide the off-chain value of the target asset.

[0112] In some embodiments, the blockchain system also includes a stablecoin vault, which provides storage for stablecoins. For example, when a user issues a target asset, the blockchain system can extract the corresponding stablecoins from the stablecoin vault and deposit them into the user's account within the blockchain system. Alternatively, when a user detects a redemption operation on a target fungible token, the system can extract the corresponding stablecoins from the stablecoin vault and deposit them into the user's account within the blockchain system based on the redemption amount calculated by the fungibility management component and the investment management component.

[0113] Figure 4 This is a flowchart illustrating another asset digitization processing method provided in this application embodiment, which is applied to... Figures 1 to 3 In any of the blockchain systems shown in the embodiments, such as Figure 4 The method shown also includes the following steps:

[0114] Step S201: Obtain the first smart contract, the second smart contract, the first sub-information, and the second sub-information corresponding to the target asset.

[0115] The first sub-information is used to instruct the blockchain system to create a non-fungible token corresponding to the target asset, and the second sub-information is used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token. The first smart contract is a smart contract determined by the electronic device based on the target non-fungible token protocol corresponding to the target asset, and the second smart contract is a smart contract determined by the electronic device based on the target fungible token protocol corresponding to the target asset.

[0116] The electronic device packages the first smart contract, the second smart contract, the first sub-information, and the second sub-information into a transaction and sends it to the blockchain system. The blockchain system can then parse the first smart contract, the second smart contract, the first sub-information, and the second sub-information corresponding to the target asset from the received transaction.

[0117] Step S202: Based on the first sub-information, create at least one non-fungible token corresponding to the target asset through the first smart contract.

[0118] The first piece of information includes a storage link for the target asset. The blockchain system can execute a first smart contract, which, based on the first piece of information, creates at least one non-fungible token for the storage link.

[0119] Step S203: Based on the second sub-information, create a fungible token for each non-fungible token through the second smart contract, so that nodes in the blockchain system can trade the target asset based on the fungible token.

[0120] The blockchain system can also execute a second smart contract, which, based on the second sub-information, creates a corresponding fungible token for each non-fungible token created.

[0121] In one implementation, before creating at least one non-fungible token corresponding to the target asset via a first smart contract based on the first sub-information, the method further includes:

[0122] Upon receiving the first initialization parameters and the second initialization parameters sent by the electronic device, a first smart contract is deployed based on the first initialization parameters, and a second smart contract is deployed based on the second initialization parameters.

[0123] Based on the first sub-information, at least one non-fungible token corresponding to the target asset is created through the first smart contract, including:

[0124] Execute the deployed first smart contract to generate at least one non-fungible token corresponding to the target asset;

[0125] Based on the second sub-information, a fungible token is created for each non-fungible token via the second smart contract, including:

[0126] Execute the deployed second smart contract to create a fungible token for each non-fungible token.

[0127] In the above technical solution, after generating the non-fungible token corresponding to the target asset, a fungible token is also created for each non-fungible token. This allows the fungible token to be associated with real-world assets through the non-fungible token, enabling any token to be anchored to a real-world asset. Furthermore, the non-fungible token is subdivided through the fungible token. By combining the advantages of non-fungible and fungible tokens, the on-chain tokens of RWA assets can be flexibly configured, improving the liquidity of RWA assets in the blockchain system.

[0128] In one implementation, the method further includes: upon detecting a user's first operation request for the target fungible token, verifying the user's first operation permission, the first operation permission being used to indicate whether the user can perform the first operation for the target fungible token, the first operation including creating the target fungible token, transferring the target fungible token, destroying the target fungible token, freezing the account corresponding to the target fungible token, redeeming the target fungible token, or subscribing to the target fungible token, the target fungible token being any fungible token corresponding to the target asset;

[0129] If the first operation permission is granted, execute the first operation corresponding to the first operation request on the target fungible token.

[0130] The target homogenized token is any homogenized asset of any non-homogeneous asset corresponding to the target asset.

[0131] Combination Figure 1 as well as Figure 5The above technical solution describes a blockchain system that, upon receiving relevant information (such as a first smart contract) from an electronic device, deploys the first smart contract and issues asset certificates (an example of a non-fungible token corresponding to the target asset) through it. The blockchain system locks the asset certificates through an asset pool (an example of a fungible token component), and issues share certificates (an example of a fungible token corresponding to a non-fungible token) for these asset certificates according to the deployed second smart contract. It also manages the further deployment and investment permissions of these share asset certificates. In this example, the share certificate represents a share issued by the asset pool for the locked asset certificates. The share certificate is a pure fungible token, without complex operational logic; other subscription and investment logic and transfer / freezing permissions are handled by other contracts.

[0132] When the permission management component receives an operation request from a user to perform operations such as mint, burn, or transfer on share certificates (an example of the first operation request), it verifies the user's operation permissions. If the verification is successful, the user's operation is permitted, and the asset pool is requested to execute the operation corresponding to the operation request for the share certificates. If the verification fails, the user's operation is rejected.

[0133] When the investment management component receives an operation request from a user (investor) to subscribe for or redeem unit tokens (another example of the first operation request), it determines whether the unit tokens can be subscribed for or redeemed. If so, it calculates the total amount of stablecoins that need to be withdrawn from or deposited into the stablecoin treasury, and redeems or subscribes for unit tokens through the unit token management component (an example of the fungible token management component).

[0134] In the above technical solution, when a user's first operation request for the target fungible token is detected, the user's first operation permission is verified first, and the first operation is only performed on the target fungible token when the verification is successful, which can ensure the security of the fungible token corresponding to the RWA asset in the blockchain system.

[0135] In one implementation, performing a first operation corresponding to a first operation request on the target fungible token includes:

[0136] If the first operation is to redeem the target fungible token, obtain the asset value and trading rules corresponding to the target fungible token;

[0137] If the transaction rules include information restricting the first operation, it is determined that the first operation on the target fungible token failed.

[0138] If the transaction rules include information allowing the first operation, stablecoins corresponding to the asset value are extracted from the stablecoin vault of the blockchain system, and the extracted stablecoins are stored in the user's corresponding account node in the blockchain system.

[0139] Transaction rules instruct nodes in the blockchain system to subscribe to or redeem target fungible tokens. The blockchain system can monitor the value changes of the non-fungible tokens (NFTs) corresponding to the target asset in real time through a first smart contract, record the changed value through the first smart contract, and then update the price of the corresponding fungible tokens through a second smart contract. In this way, the blockchain system can obtain the current value of the target fungible token, i.e., the asset value (for example, if one fungible token corresponds to 0.5 shares of stock, with an initial face value of 5 yuan, 10 yuan, and a current face value of 5 yuan, then the current value of the fungible token is 2.5 yuan). When a stablecoin is equivalent to 2 yuan, the blockchain system can extract 1.25 stablecoins from the stablecoin repository and store them in the user's corresponding account node within the blockchain system.

[0140] In this embodiment, after generating the non-fungible token corresponding to the target asset, a fungible token is created for each non-fungible token. This allows the fungible token to be associated with real-world assets through the non-fungible token, achieving the anchoring of any token to a real-world asset. Furthermore, the non-fungible token is subdivided through the fungible token, enabling flexible configuration of the on-chain tokens of RWA assets and improving the liquidity of RWA assets within the blockchain system. The blockchain system also allows for the creation, transfer, freezing, subscription, or redemption of fungible tokens of RWA assets, achieving lifecycle management of these tokens, improving the user's trading experience within the blockchain system, and thus increasing trading activity.

[0141] Figure 6 This is a schematic diagram of the structure of a single device provided in an embodiment of this application. For example... Figure 6 As shown, the single-device 6 of this embodiment includes: at least one processor 60 ( Figure 6 (Only one is shown) a processor, a memory 61, and a computer program 62 stored in the memory 61 and executable on the at least one processor 60, which, when executing the computer program 62, implements the steps in any of the above-described method embodiments.

[0142] The single device 6 can be a computing device such as a desktop computer, laptop, handheld computer, or cloud server. This single device may include, but is not limited to, a processor 60 and a memory 61. Those skilled in the art will understand that... Figure 6 This is merely an example of a single device 6 and does not constitute a limitation on the single device 6. It may include more or fewer components than shown, or combine certain components, or different components, such as input / output devices, network access devices, etc.

[0143] The processor 60 may be a Central Processing Unit (CPU), or it may be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. A general-purpose processor may be a microprocessor or any conventional processor.

[0144] In some embodiments, the memory 61 may be an internal storage unit of the single device 6, such as a hard disk or memory of the single device 6. In other embodiments, the memory 61 may be an external storage device of the single device 6, such as a plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, etc., equipped on the single device 6. Further, the memory 61 may include both internal storage units and external storage devices of the single device 6. The memory 61 is used to store the operating system, applications, bootloader, data, and other programs, such as the program code of the computer program. The memory 61 can also be used to temporarily store data that has been output or will be output.

[0145] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the steps described in the various method embodiments above.

[0146] This application provides a computer program product that, when run on a mobile terminal, enables the mobile terminal to implement the steps described in the above-described method embodiments.

[0147] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments of this application can be implemented by a computer program instructing related hardware. The computer program can be stored in a computer-readable storage medium, and when executed by a processor, it can implement the steps of the various method embodiments described above. The computer program includes computer program code, which can be in the form of source code, object code, executable files, or certain intermediate forms. The computer-readable medium can include at least: any entity or device capable of carrying computer program code to a photographing device / terminal device, a recording medium, a computer memory, a read-only memory (ROM), a random access memory (RAM), an electrical carrier signal, a telecommunication signal, and a software distribution medium. Examples include USB flash drives, portable hard drives, magnetic disks, or optical disks. In some jurisdictions, according to legislation and patent practice, computer-readable media cannot be electrical carrier signals or telecommunication signals.

[0148] In the above embodiments, the descriptions of each embodiment have different focuses. For parts that are not described in detail or recorded in a certain embodiment, please refer to the relevant descriptions of other embodiments.

[0149] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0150] In the embodiments provided in this application, it should be understood that the disclosed systems / electronic devices and methods can be implemented in other ways. For example, the device / network device embodiments described above are merely illustrative. For instance, the division of modules or units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the mutual coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between devices or units may be electrical, mechanical, or other forms.

[0151] The units described 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 can be selected to achieve the purpose of this embodiment according to actual needs.

[0152] The above-described embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A processing method for asset digitization, characterized by, The method is applied to an electronic device, and the method comprises: obtaining asset configuration information of a target asset, the asset configuration information comprising a target non-fungible token protocol corresponding to the target asset, a target fungible token protocol, first sub-information and second sub-information, the first sub-information being used to instruct a blockchain system to create a non-fungible token corresponding to the target asset, and the second sub-information being used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token; determining a first smart contract corresponding to the target asset according to the target non-fungible token protocol and a preset smart contract set, and determining a second smart contract corresponding to the target asset according to the target fungible token protocol and the smart contract set, the smart contract set comprising smart contracts corresponding to a plurality of non-fungible token protocols and smart contracts corresponding to a plurality of fungible token protocols; sending the first smart contract, the second smart contract, the first sub-information and the second sub-information to the blockchain system, so that the blockchain system creates at least one non-fungible token corresponding to the target asset according to the first smart contract and the first sub-information, and creates the fungible token for each non-fungible token according to the second smart contract and the second sub-information, and a node in the blockchain system trades the target asset based on the fungible token.

2. The method of claim 1, wherein, The obtaining of the asset configuration information of the target asset comprises: obtaining asset metadata of the target asset, the asset metadata comprising the asset configuration information; in a case where the asset metadata satisfies a first condition, extracting the asset configuration information from the asset metadata, the first condition comprising that a data format of the asset metadata is a preset format, and an asset specification file of the target asset in the asset metadata satisfies a preset rule.

3. The method of claim 1 or 2, wherein, Before the sending of the first smart contract, the second smart contract, the first sub-information and the second sub-information to the blockchain system, the method further comprises: parsing a first initialization parameter corresponding to the first smart contract according to the first sub-information; parsing a second initialization parameter corresponding to the second smart contract according to the second sub-information and the first initialization parameter; the sending of the first smart contract, the second smart contract, the first sub-information and the second sub-information to the blockchain system comprises: sending the first smart contract, the second smart contract, the second initialization parameter and the first initialization parameter to the blockchain system, so that the blockchain system deploys the first smart contract based on the first initialization parameter, and deploys the second smart contract based on the second initialization parameter, so as to subsequently obtain the non-fungible token and the fungible token.

4. The method of claim 2, wherein, The method further comprises: in a case where the asset metadata satisfies the first condition, storing the asset metadata to a distributed storage system; obtaining a storage link corresponding to the asset metadata returned by the distributed storage system; store the storage link into the first sub-information, so that a subsequent blockchain system creates at least one non-fungible token based on the first sub-information and the first smart contract.

5. A processing method of asset digitization, characterized by, The method is applied to a blockchain system, and the method comprises: obtaining a first smart contract, a second smart contract, first sub-information and second sub-information corresponding to a target asset, the first sub-information being used to instruct the blockchain system to create a non-fungible token corresponding to the target asset, the second sub-information being used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token, the first smart contract being a smart contract determined by an electronic device based on a target non-fungible token protocol corresponding to the target asset, and the second smart contract being a smart contract determined by the electronic device based on a target fungible token protocol corresponding to the target asset; creating at least one non-fungible token corresponding to the target asset through the first smart contract according to the first sub-information; creating the fungible token for each non-fungible token through the second smart contract according to the second sub-information, so that a node in the blockchain system trades the target asset based on the fungible token.

6. The method of claim 5, wherein, The method further comprises: when detecting a first operation request of a user for a target fungible token, verifying a first operation authority of the user, the first operation authority being used to indicate whether the user can implement a first operation for the target fungible token, the first operation comprising at least one of creating the target fungible token, transferring the target fungible token, destroying the target fungible token, freezing an account corresponding to the target fungible token, redeeming the target fungible token, or subscribing to the target fungible token, the target fungible token being any fungible token corresponding to the target asset; when the first operation authority is passed, performing a first operation corresponding to the first operation request on the target fungible token.

7. The method of claim 6, wherein, The performing of the first operation corresponding to the first operation request on the target fungible token comprises: when the first operation is the redeeming of the target fungible token, obtaining an asset value corresponding to the target fungible token and a transaction rule; when the transaction rule comprises information limiting the first operation, determining that the first operation on the target fungible token fails; when the transaction rule comprises information allowing the first operation, extracting a stable currency corresponding to the asset value from a stable currency library of the blockchain system, and storing the extracted stable currency into a corresponding account node of the user in the blockchain system.

8. An electronic device, comprising: The system comprises: 9.A blockchain system, characterized in that, The system comprises: The data acquisition component is configured to acquire a first smart contract, a second smart contract, first sub-information and second sub-information corresponding to a target asset, the first sub-information is used to instruct the blockchain system to create a non-fungible token corresponding to the target asset, the second sub-information is used to instruct the blockchain system to create a fungible token corresponding to the non-fungible token, the first smart contract is a smart contract determined by the electronic device based on a target non-fungible token protocol corresponding to the target asset, and the second smart contract is a smart contract determined by the electronic device based on a target fungible token protocol corresponding to the target asset. The non-fungible token component is configured to create at least one non-fungible token corresponding to the target asset through the first smart contract according to the first sub-information. The fungible token component is configured to create a corresponding fungible token for each non-fungible token through the second smart contract according to the second sub-information, so that a node in the blockchain system trades the target asset based on the fungible token.

10. A computer-readable storage medium storing a computer program, the computer program comprising instructions that, when executed by a computer, cause the computer to perform the method of any one of claims 1 to 9. The computer program is executed when running, so that the asset digitization processing method in any one of claims 1-7 is executed.

Images