A digital asset management system, method, electronic device and storage medium

Abstract

The embodiments of the present application relate to the field of information security technology, and disclose a digital asset management system, method, electronic device and storage medium, wherein the digital asset management system comprises: a multi-chain layer, a control layer and a service layer, wherein the control layer is connected to the multi-chain layer and the service layer respectively; the multi-chain layer comprises a plurality of blockchains corresponding to different types of digital assets; the control layer comprises a first customized interface, wherein the first customized interface is used to design a corresponding data model for each of the blockchains, and each of the data models is used to indicate a transaction mode of a corresponding digital asset; the service layer is used to receive a user's asset service request, and call the first customized interface according to the asset service request, so as to design a corresponding data model for each of the blockchains. The digital asset management system provided by the embodiments of the present application can realize customized services for digital assets and improve the security of digital asset management.

Description

Technical Field

[0001] The embodiments of the present application relate to the field of information security technology, and in particular to a digital asset management system, method, electronic device and storage medium. Background Art

[0002] The current blockchain system architecture can be divided into two types: ① "end-chain" separation architecture based on a third party; ② "end-chain" merged architecture that eliminates the third party, where "end" refers to the application end and "chain" refers to the blockchain system.

[0003] The third-party-based "end-chain" separation architecture uses blockchain as a data service platform, similar to a database. The platform is provided by a third party rather than deployed locally. When designing applications based on this architecture, the upper-layer applications and the underlying data service platform are separated. However, this architecture describes digital assets and their transaction patterns through smart contracts, resulting in a high degree of dependence of digital assets on the availability of smart contracts, low security, and difficulty in implementing customized services for different types of digital assets.

[0004] Compared with the "end-chain" separation architecture based on a third party, the "end-chain" merger architecture that exempts third parties emphasizes the native support of blockchain. Under this architecture, the server that provides the application is also a node of the blockchain network, and the blockchain network is maintained by nodes belonging to application users. Therefore, this architecture is no longer provided by a third party. Data services. However, this architecture cannot adapt to different types of digital assets, that is, the blockchain BDAMS based on this architecture cannot provide customized services for multiple types of digital assets. Summary of the invention

[0005] The purpose of the embodiments of the present application is to provide a digital asset management system, method, electronic device and storage medium, which can realize customized services for digital assets and improve the security of digital asset management.

[0006] To solve the above technical problems, an embodiment of the present application provides a digital asset management system, comprising: a multi-chain layer, a control layer and a service layer, the control layer being connected to the multi-chain layer and the service layer respectively; the multi-chain layer comprising multiple blockchains corresponding to different types of digital assets; the control layer comprising a first customized interface, the first customized interface being used to design a corresponding data model for each of the blockchains, each of the data models being used to indicate a transaction mode of a corresponding digital asset; the service layer being used to receive an asset service request from a user, and calling the first customized interface according to the asset service request to design a corresponding data model for each of the blockchains.

[0007] An embodiment of the present application also provides a digital asset management method, which is applied to the above-mentioned digital asset management system, and includes the following steps: receiving an asset service request from a user; calling a first customized interface according to the asset service request, so as to design corresponding data models for multiple blockchains corresponding to different types of digital assets through the first customized interface; wherein each of the data models is used to indicate the transaction mode of the corresponding digital asset.

[0008] An embodiment of the present application also provides an electronic device, comprising: at least one processor; and a memory communicatively connected to the at least one processor; wherein the memory stores instructions executable by the at least one processor, and the instructions are executed by the at least one processor so that the at least one processor can execute the above-mentioned digital asset management method.

[0009] An embodiment of the present application further provides a computer-readable storage medium storing a computer program, wherein the computer program implements the above-mentioned digital asset management method when executed by a processor.

[0010] The digital asset management system provided by the embodiment of the present application includes a multi-chain layer, a control layer and a service layer. The multi-chain layer includes multiple blockchains corresponding to different types of digital assets, and the control layer is connected to the multi-chain layer, which includes a first customized interface that can design a corresponding data model for each blockchain in the multi-chain layer, that is, it can design corresponding data models for different types of digital assets. In addition, the service layer is connected to the control layer. After the service layer receives the asset service request of the user, it can directly call the first customized interface to design corresponding data models for different types of digital assets. The data model is used to indicate the transaction mode of the corresponding digital asset. Since digital assets need their corresponding data models to support, and the present application can directly call the corresponding customized interface according to the user's request, and design different types of digital assets through the customized interface. The corresponding data model is designed so that different types of digital assets are supported by corresponding data models, so the present application supports the coexistence of multiple types of digital assets, and provides users with the required data models of digital assets, thereby realizing customized services for digital assets. In addition, the data model of the present application is not defined in the smart contract, so there is no need to rely on the smart contract, and the system security will not be threatened due to security vulnerabilities in the smart contract, so the security of the present system is relatively high.

[0011] In some optional embodiments, the digital asset management system further includes a contract layer, which is connected to the multi-chain layer and the control layer respectively; the contract layer is used to store multiple contract templates corresponding to different types of digital assets. The contract of the digital asset of this application adopts a contract template, which does not involve business logic, further improving security.

[0012] In some optional embodiments, the control layer further includes a second customized interface, which is used to execute each of the contract templates or configure each of the contract templates; the service layer is further used to call the second customized interface according to the asset service request to execute each of the contract templates or configure each of the contract templates. This application can further realize customized services for contracts.

[0013] In some optional embodiments, the control layer further includes a third customized interface, and the third customized interface is used to write a corresponding consensus protocol for each blockchain; the service layer is also used to call the third customized interface according to the asset service request to write a corresponding consensus protocol for each blockchain. This application can further realize customized services for consensus protocols.

[0014] In some optional embodiments, the digital asset management system also includes a network layer, which is connected to the multi-chain layer and the control layer respectively; the network layer is used to store a corresponding consensus protocol written for each of the blockchains.

[0015] In some optional embodiments, the service layer is further used to configure any one or any combination of the first customized interface, the second customized interface, and the third customized interface according to the asset service request. The present application can further realize customized services of the control layer interface.

[0016] In some optional embodiments, the digital asset management system also includes a data service layer, which is connected to the multi-chain layer, the contract layer and the control layer respectively; the data service layer is used to store the business data generated by the service layer in the process of executing the asset service request. BRIEF DESCRIPTION OF THE DRAWINGS

[0017] One or more embodiments are exemplarily described by the pictures in the corresponding drawings, and these exemplary descriptions do not constitute limitations on the embodiments.

[0018] Figure 1 is a schematic diagram of a digital asset management system provided according to an embodiment of the present application;

[0019] Figure 2 is a schematic diagram of a digital asset transaction model provided according to an embodiment of the present application;

[0020] Figure 3 is a schematic diagram of a digital asset life cycle provided according to an embodiment of the present application;

[0021] Figure 4is an example diagram of a contract template provided according to an embodiment of the present application;

[0022] Figure 5 is a schematic diagram of internal components of a digital asset management system provided according to an embodiment of the present application;

[0023] Figure 6 This is a state migration diagram of a digital asset management system provided according to an embodiment of the present application;

[0024] Figure 7 Another embodiment of the present application provides a flowchart of a digital asset management method;

[0025] Figure 8 It is a structural schematic diagram of an electronic device provided by another embodiment of the present application. DETAILED DESCRIPTION

[0026] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the embodiments of the present application will be described in detail below in conjunction with the accompanying drawings. However, it will be appreciated by those skilled in the art that in the present application, many technical details are proposed in order to enable the reader to better understand the present application. However, even without these technical details and various changes and modifications based on the following embodiments, the technical scheme claimed in the present application can also be implemented. The division of the following embodiments is for the convenience of description, and the specific implementation of the present application should not be construed as any limitation, and the various embodiments can be combined and referenced with each other under the premise of no contradiction.

[0027] First, the current blockchain system architecture is introduced as follows:

[0028] Ethereum is a typical representative of the "end-chain" separation architecture based on a third party. Med-Share, MedChain and BiiMED are all medical data management systems based on Ethereum. Ethereum, as a third-party platform, provides data services for these systems. Usually, applications using this architecture use smart contracts to implement business logic. For example, BC-Rec implements smart recommendations based on Ethereum and uses smart contracts to alleviate cold start, sparsity and shilling attack problems; AuthROS encodes smart contracts to ensure the immutability and security of private data flows between nodes for data sharing; TickEth aims to use Ethereum smart contracts to implement online ticket authentication, etc. However, the "end-chain" separation architecture based on a third party has the problem of difficulty in implementing customized services for different types of digital assets and low security.

[0029] The idea of ​​the "end-chain" merged architecture that eliminates the need for third parties is to allow each peer node to execute business logic independently, and some special nodes maintain the consistency of chain data through consensus. Hyperledger Fabric is one of the representative construction technologies of this architecture. For example, the electronic personnel information management system built on Hyperledger Fabric is used to improve the storage and synchronization efficiency of data in the management process; the UniCon architecture based on Hyperledger Fabric is used to build a management system for managing large-scale digital assets. Its core idea is to allow tracking of asset ownership, but it is still difficult to adapt to the coexistence of multiple digital asset types. Therefore, the "end-chain" merged architecture that eliminates the need for third parties also has the problem of difficulty in implementing customized services for different types of digital assets.

[0030] The digital asset management system of the embodiment of the present application can solve the problem that the above-mentioned data asset management architecture cannot provide customized services for different types of digital assets and has low security.

[0031] An embodiment of the present application relates to a digital asset management system. The implementation details of the digital asset management system of this embodiment are described in detail below. The following content is only for the convenience of understanding the implementation details and is not necessary for the implementation of this solution. Figure 1 As shown, it includes: a multi-chain layer 11, a control layer 12 and a service layer 13, and the control layer 12 is connected to the multi-chain layer 11 and the service layer 13 respectively.

[0032] Specifically, the multi-chain layer 11 allows the existence of multiple chains. If the present embodiment needs to manage multiple different types of digital assets, the multi-chain layer 11 specifically includes multiple blockchains corresponding to different types of digital assets, and each blockchain is used to help and manage the life cycle of the corresponding type of digital assets. These multiple blockchains can be obtained by developers designing different blockchain underlying data structures and data manipulations based on different types of digital assets. Each blockchain can be used as a base class, and all data models serving the corresponding digital assets should inherit from the base class.

[0033] The control layer 12 is used to provide a customizable interface, which specifically includes a first customized interface. The first customized interface is used to design a corresponding data model for each blockchain in the multi-chain layer 11. The data model can be derived from the blockchain (i.e., the base class) through the first customized interface parameter configuration. Each data model includes two major elements: data structure and data manipulation, which are used to indicate the transaction mode of the corresponding digital asset.

[0034] The trading modes of digital assets can be divided into: Figure 2The three transaction modes shown in the figure correspond to the three types of digital assets: ownership transfer type, use right distribution type, and value-added type. Among them, the representative digital asset of ownership transfer type is digital currency, and its transaction mode is represented by A transferring the relevant rights of digital asset d to B, and B then transfers it to C, and finally C has the ownership and use right of d. The representative digital assets of use right distribution type include data, software, etc., and its transaction mode is represented by A distributing the use right of digital asset d to B and C, and B and C only have the use right of d. The representative digital assets of value-added type include adaptable digital works, creative solutions, NFT, etc., and its transaction mode is represented by A transforming digital asset d into d' for value-added, and A has the ownership and use right of d', and similarly B also has the ownership and use right of d'. Figure 2 sig x Represents the digital signature of the transaction party x, txn i represents the i-th transaction, ftr x The new feature added by the transaction party x, d represents the digital asset being traded, o represents ownership, and u represents the right to use. In addition, the on-chain life cycle of the digital assets corresponding to these three transaction modes is as follows: Figure 3 shown.

[0035] The service layer 13 is used to receive the user's asset service request, and call the first customized interface of the control layer 12 according to the asset service request to design a corresponding data model for each blockchain, that is, to design corresponding data models for different types of digital assets. It can be seen that the service layer 13 is used to call the interface of the control layer (the first customized interface) to implement the corresponding digital asset service (digital asset customized service).

[0036] In this embodiment, the digital asset management system includes a multi-chain layer, a control layer, and a service layer. The multi-chain layer includes multiple blockchains corresponding to different types of digital assets, and the control layer is connected to the multi-chain layer, which includes a first customized interface that can design a corresponding data model for each blockchain in the multi-chain layer, that is, it can design corresponding data models for different types of digital assets. In addition, the service layer is connected to the control layer. After the service layer receives the user's asset service request, it can directly call the first customized interface to design corresponding data models for different types of digital assets. The data model is used to indicate the transaction mode of the corresponding digital asset. Since digital assets need their corresponding data models to support, and this application can directly call the corresponding customized interface according to the user's request, and design different types of digital assets through the customized interface. The corresponding data model is designed so that different types of digital assets have corresponding data models to support, so this application supports the coexistence of multiple types of digital assets, and provides users with the required digital asset data model, thereby realizing customized services for digital assets. In addition, the data model of this application is not defined in the smart contract, so there is no need to rely on the smart contract, and the system security will not be threatened due to security vulnerabilities in the smart contract, so the security of this system is relatively high.

[0037] In some embodiments, the digital asset management system further includes: Figure 1 The contract layer 14 shown is connected to the multi-chain layer 11 and the control layer 12 respectively. The contract layer 14 is used to store contracts of different types of digital assets, and the contracts exist in the form of contract templates, that is, the contract layer 14 is used to store multiple contract templates corresponding to different types of digital assets. It should be noted that in addition to the above-mentioned multiple blockchains (regarded as state chains), the multi-chain layer 11 also includes a mandatory chain, also called a contract chain, which is connected to multiple contract templates of this embodiment.

[0038] Among them, the contract template is not the source code written in a high-level language, but a contract template that is closer to natural language. It is mainly used to execute the agreement in the transaction and constrain the behavior of both parties to the transaction. The example of the contract template is as follows Figure 4 It should be noted that the contract layer 14 of this embodiment can be regarded as a database, and a key-value pair database that is easy to transplant, such as CouchDB, LevelDB, etc., can be used as the contract layer 14.

[0039] In one example, the control layer 12 also includes a second customized interface, which is used to execute each contract template or configure each contract template. At this time, the service layer 13 is also used to call the second customized interface according to the asset service request to execute each contract template or configure each contract template.

[0040] The contract template in this embodiment can be regarded as a header file in the C programming language. The terms contained in it are descriptions and declarations of business logic. These declarations are only identifiers rather than references. This contract template is different from a smart contract and cannot be executed independently. It requires the service layer 13 to call the corresponding interface (second customized interface) in the control layer 12 according to the user's asset service request before it can be executed. Therefore, the business logic is separated from the contract at the programming layer. Compared with the inevitable loopholes and defects that may occur in smart contracts and affect the execution of digital asset services, the availability of the contract in this embodiment will not affect the execution of the business logic, thereby ensuring the security of the digital asset management system. In addition, the use of contract templates can also reduce repeated development and reduce the serious economic losses caused by smart contract vulnerabilities.

[0041] Furthermore, in this embodiment, the service layer 13 can call the corresponding interface (second customized interface) in the control layer 12 according to the user's asset service request, and the contract template can also be configured, such as creation, deletion, modification and other operations, thereby realizing customized services for digital asset contracts.

[0042] In some embodiments, the control layer 12 also includes a third customized interface, which is used to write a corresponding consensus protocol for each blockchain. The service layer 13 is also used to call the third customized interface according to the asset service request to write a corresponding consensus protocol for each blockchain, that is, to write a consensus protocol that meets the transaction requirements of each type of digital asset, thereby realizing customized services for digital asset consensus protocols.

[0043] In one example, the digital asset management system also includes Figure 1 The network layer 15 shown is connected to the multi-chain layer 11, the control layer 12 and the service layer 13 respectively, and the network layer 15 is used to store the consensus protocol written for each blockchain. It can be understood that there are multiple user nodes of the digital asset management system in the network layer 15, and each user node also needs to communicate with each other, so the network layer 15 can also provide communication services for each user node. Specifically, the communication method between user nodes is TCP real-time connection, and the dynamic address table is used to implement the maintenance of TCP long connection. The network layer 15 can use remote object call frameworks such as Dubbo to realize communication between user nodes, and can also cooperate with ZooKeeper to establish a more reliable distributed bottom layer to realize communication between user nodes.

[0044] In some embodiments, the service layer 13 is also used to configure any one or any combination of the first customized interface, the second customized interface, and the third customized interface according to the asset service request, for example, deleting or adding a certain interface, thereby realizing the customization of the control layer 12 interface and providing more service types for digital assets.

[0045] In some embodiments, the digital asset management system further includes: Figure 1 The data service layer 16 shown is connected to the multi-chain layer 11, the contract layer 14 and the control layer 12 respectively. The data service layer 16 is used to store the business data generated in the process of the service layer 13 executing the asset service request. Business data includes permanent data and temporary data, which may be structured or unstructured, depending on the needs of business logic. This layer is equivalent to the database layer in the three-tier architecture of the Web. It can be implemented using a relational or non-relational database, but considering the consistency of multi-node data, a key-value database is usually selected, and the database table structure design is not too complicated as much as possible.

[0046] In some embodiments, since the service layer 13 described in any of the above embodiments receives an asset service request from a user, the digital asset management system described in the embodiment of the present application further includes: Figure 1 The application layer 17 shown is the top layer of the system, which is used to enable users to initiate requests to the service layer 13 to execute corresponding digital asset services. Specifically, the service layer may also include multiple interfaces for corresponding multiple digital asset services (digital asset customized services, contract customized services, consensus protocol customized services, and customized services of the control layer 12 interface). Users call the corresponding interface of the service layer 13 through the application layer 17 to initiate the corresponding digital asset service request, and then the service layer 13 calls the corresponding interface of the control layer 1 according to the request.

[0047] In one embodiment, the digital asset management system of the present application is a set of node programs that can be run on any server. Users (usually digital asset managers) and developers (including service developers and application developers) use the node program through the following steps.

[0048] Step 1: The user becomes a node in the blockchain network by installing and running the node program on the client.

[0049] Step 2: Service developers write business services of the service layer in the node program (i.e. customized services for digital assets, customized services for contracts, customized services for consensus protocols, and customized services for control layer interfaces) to support different types of digital assets.

[0050] Step 3: Application developers write the application layer and implement digital asset management for human-computer interaction by calling various services provided by the service layer.

[0051] Step 4: After entering the underlying network, users can enjoy and customize various customizable services provided by the application layer. For example, when a user initiates an asset service request, the first customized interface is called according to the user's asset service request to design a corresponding data model for each blockchain and implement customizable services for digital assets; the second customized interface is called according to the user's asset service request to execute each contract template, or configure each contract template to implement customizable services for contracts; the third customized interface is called according to the user's asset service request to write a corresponding consensus protocol for each blockchain and implement customizable services for consensus protocols, etc.

[0052] After receiving the user's asset service request, the internal elements of the system begin to collaborate to process the user's request. The three important elements in the system architecture are components, connections, and configurations. In this architecture, each layer has different components, connections, and configurations, such as Figure 5 As shown, the diagram describes the components of the architecture and their connection relationships.

[0053] Specifically, the application layer contains the user component (User), which represents the client where the user is located. The service layer includes the meta-service component (MetaService), as well as the asset service component (AssetService), the transaction service component (TransService), the contract service component (ContrService) and the user service component (UserService). Among them, MetaService provides basic services for other components in its service layer. User can request services from other components, and these components call interfaces from the control layer to provide services to users. The control layer contains the asset control component (AssetControl), the transaction control component (TransControl), the contract control component (ContrControl) and the user control component (UserControl). The data of TransControl and AssetControl comes from the multi-chain layer, and the data of Controlcontrol and UserControl comes from the service data layer. The multi-chain layer contains the asset component (Asset), the transaction component (Transaction), the blockchain component (BlockChain) and the block component (Block), which are used to store information such as assets and transactions. The database service layer contains the database component (Database), which is used to store contract information and data during user execution. In addition, the configuration information of the components of this architecture is set through parameters, which allows developers to easily customize digital asset management systems that meet various needs.

[0054] The whole system collaboratively handles user asset service requests as follows: 1) User request data is first stored in components such as Asset, Transaction, and Database, and then passed to the system through the interface as needed. 2) The component responsible for a certain user request service calls the interface from the control layer to provide services to users. The assets and transaction information required in the process are provided by the Asset, Transaction, and Database components, which are also the cornerstones of the blockchain. 3) Some reusable basic services are integrated in the MetaService component, which provides services to other service components. 4) When the service request consensus is over, the node component (Node), which serves as the carrier of other components, will package the relevant information on the chain.

[0055] In the specific implementation, after the system completes the user request, the system state will change. The system can be defined as a five-tuple M = {Q, R, E, q0, F}, and the state transition process of M is as follows: Figure 6 As shown. Where Q is a non-empty finite state set, Q = {q0, q1, ..., q n}(n≥0), q0 is the initial state of M; R is the user’s request, R={r0,r1,…,r m}(m≥0); E is the state transition function, E=Q×R→Q, which means that M is in state q, and after a certain user request, the state becomes p; F is the acceptance state of the system, For each service request, the specific processing process of M state change is as follows: 1) The initial state of the system is q0, and the user will make a user request to the system. 2) The system broadcasts the user request to the blockchain network, and the system state becomes q1. 3) The communication between nodes in the blockchain network enters the consensus stage, and the system state becomes q2. 4) If the consensus result of the nodes in the blockchain network is agreement, then the system will enter q3, otherwise, the system will return to the initial state q0.

[0056] The effectiveness of the digital asset management system of the embodiment of the present application can be verified from the following aspects:

[0057] 1. Meet the basic design requirements of digital asset management system

[0058] 1) User behavior determines the state of the system

[0059] The user operation that completely changes the system state is called OprT, and the one that does not completely change the system state is called OprNT. The process of changing the system state is defined as follows:

[0060]

[0061] Therefore, the occurrence of at least one OprT triggering a change in the system state is a necessary and sufficient condition for the system state change to occur.

[0062] Assume that the current state of the system is q m , the user's operation set O n = {Opr0,Opr1,...Opr n},n≥0, there exists Opr i It is OprT. According to the above definition, it can be seen that the occurrence of an OprT will trigger a change in the system state and cause the system state to change. Assuming that no OprT occurs, according to the above, it can be seen that the system state will not change, then the system state change must be caused by an OprT.

[0063] Therefore, the digital asset management system of the embodiment of the present application meets the requirement that the user's behavior determines the state of the system.

[0064] 2) Satisfy the digital asset management process

[0065] The tasks of the basic digital asset management system include registration, cancellation, transfer, distribution, minting, feeding and conversion. In the on-chain life cycle of digital assets, the conversion of digital asset status still follows Figure 2 The digital asset states in the figure all belong to OprT in the above definition. Therefore, the digital asset management system of the embodiment of the present application meets the digital asset management process.

[0066] 2. Customizable services

[0067] Please refer to the above embodiments for details, which will not be described again here.

[0068] 3. Security

[0069] The digital asset management system of the embodiment of the present application can resist common attacks: Sybil attacks, relay attacks, DoS attacks and smart contract risks.

[0070] (1) A Sybil attack is a network attack that disrupts the balance of the system by creating multiple virtual identities, accounts, or nodes. If the attacker creates a sufficient number of fake identities, he or she can control the entire system by outvoting other honest nodes. However, the embodiment of the present application stipulates that a user can only contribute one node to the network at most, and authenticate online and offline. Therefore, the success rate of a Sybil attack is very low.

[0071] (2) A relay attack is a type of network attack in which an attacker intercepts and forwards communications between two legitimate parties. The attacker uses specialized equipment to capture and transmit signals, allowing them to bypass security measures and gain unauthorized access. The embodiments of the present application allow designers to use session tokens to prevent this attack from occurring. Once a transaction begins, the sender sends a one-time token to the receiver, which uses the token to convert a secret. Assuming an attacker steals this secret and attempts to initiate a new session, the token for the new session will be changed, making the attacker's work meaningless. This design can be implemented by customizing the consensus protocol of the network layer. Therefore, the embodiments of the present application can effectively resist relay attacks.

[0072] (3) DoS attack means that a malicious client can send a service request effortlessly, but the system must use a large amount of resources to process the request and respond to the client. This is a common vulnerability that DoS attackers usually exploit. However, in the embodiment of the present application, users entering the system must undergo online and offline authentication. At the same time, the embodiment of the present application can limit the variables of user requests by setting the MetaService component, prohibiting users from directly interacting with the business data layer, and preventing invalid requests from consuming storage resources.

[0073] (4) Risks of smart contracts: Please refer to the above embodiments for details, which will not be elaborated here.

[0074] It should be noted that the above examples in this embodiment are all illustrative descriptions for easy understanding and do not constitute a limitation on the technical solutions of the present invention.

[0075] Another embodiment of the present application relates to a digital asset management method, which is applied to the digital asset management system described in any of the above embodiments. The implementation details of the digital asset management method of this embodiment are described in detail below. The following content is only for the convenience of understanding the implementation details provided, and is not necessary for implementing this solution.

[0076] The specific process of the digital asset management method of this embodiment can be as follows: Figure 7 As shown, including:

[0077] Step 701, receiving a user's asset service request;

[0078] Step 702: Call the first customized interface according to the asset service request of the user, so as to design corresponding data models for multiple blockchains corresponding to different types of digital assets through the first customized interface; wherein each data model is used to indicate the transaction mode of the corresponding digital asset.

[0079] In this embodiment, after receiving the user's asset service request, the first customized interface can be directly called to design corresponding data models for different types of digital assets, and the data model is used to indicate the transaction mode of the corresponding digital asset. Therefore, this application can realize customized services for digital assets, and the data model is not defined in the smart contract, so there is no need to rely on the smart contract, and the security is higher.

[0080] It is not difficult to find that this embodiment is a method embodiment corresponding to the above-mentioned system embodiment, and this embodiment can be implemented in conjunction with the above-mentioned system embodiment. The relevant technical details and technical effects mentioned in the above-mentioned embodiment are still valid in this embodiment, and in order to reduce repetition, they are not repeated here. Accordingly, the relevant technical details mentioned in this embodiment can also be applied in the above-mentioned embodiment.

[0081] The step division of the above methods is only for the purpose of clear description. When implemented, they can be combined into one step or some steps can be split and decomposed into multiple steps. As long as they include the same logical relationship, they are all within the scope of protection of this patent; adding insignificant modifications to the algorithm or process or introducing insignificant designs without changing the core design of the algorithm and process are all within the scope of protection of this patent.

[0082] ,Another embodiment of the present application relates to an electronic device, such as Figure 8 As shown, it includes: at least one processor 801; and a memory 802 that is communicatively connected to the at least one processor 801; wherein the memory 602 stores instructions that can be executed by the at least one processor 801, and the instructions are executed by the at least one processor 801 so that the at least one processor 801 can execute the digital asset management method in the above-mentioned embodiments.

[0083] Among them, the memory and the processor are connected in a bus manner, and the bus may include any number of interconnected buses and bridges, and the bus connects various circuits of one or more processors and memories together. The bus can also connect various other circuits such as peripherals, voltage regulators, and power management circuits, which are well known in the art and are therefore not further described herein. The bus interface provides an interface between the bus and the transceiver. The transceiver can be one element or multiple elements, such as multiple receivers and transmitters, providing a unit for communicating with various other devices on a transmission medium. The data processed by the processor is transmitted on a wireless medium via an antenna, and further, the antenna also receives data and transmits the data to the processor.

[0084] The processor is responsible for managing the bus and general processing, and can also provide various functions, including timing, peripheral interfaces, voltage regulation, power management, and other control functions. Memory can be used to store data used by the processor when performing operations.

[0085] Another embodiment of the present application relates to a computer-readable storage medium storing a computer program, which implements the above method embodiment when executed by a processor.

[0086] That is, those skilled in the art can understand that all or part of the steps in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a program, and the program is stored in a storage medium, including a number of instructions to enable a device (which can be a single-chip microcomputer, chip, etc.) or a processor to execute all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as: ROM), random access memory (Random Access Memory, referred to as: RAM), disk or optical disk and other media that can store program codes.

[0087] Those skilled in the art will appreciate that the above embodiments are specific embodiments for implementing the present application, and in actual applications, various changes may be made thereto in form and detail without departing from the spirit and scope of the present application.

Claims

1. A digital asset management system, characterized in that: include: A multi-chain layer, a control layer and a service layer, wherein the control layer is connected to the multi-chain layer and the service layer respectively; The multi-chain layer includes multiple blockchains corresponding to different types of digital assets; The control layer includes a first customized interface, wherein the first customized interface is used to design a corresponding data model for each of the blockchains, and each of the data models is used to indicate a transaction mode of a corresponding digital asset; The service layer is used to receive the asset service request of the user, and call the first customized interface according to the asset service request to design a corresponding data model for each blockchain; The digital asset management system further includes a contract layer, which is connected to the multi-chain layer and the control layer respectively; The contract layer is used to store multiple contract templates corresponding to different types of digital assets, and each contract template does not involve business logic; The multi-chain layer also includes a mandatory chain, which serves as a contract chain and is connected to multiple contract templates at the same time; The control layer further includes a second customized interface, and the second customized interface is used to execute each of the contract templates, or configure each of the contract templates; The service layer is also used to call the second customized interface according to the asset service request to execute each of the contract templates, or configure each of the contract templates.

2. The digital asset management system according to claim 1, characterized in that: The control layer also includes a third customized interface, and the third customized interface is used to write a corresponding consensus protocol for each of the blockchains; The service layer is further used to call the third customized interface according to the asset service request to write a corresponding consensus protocol for each of the blockchains.

3. The digital asset management system according to claim 2, characterized in that: The digital asset management system further comprises a network layer, wherein the network layer is connected to the multi-chain layer and the control layer respectively; The network layer is used to store the consensus protocol written corresponding to each of the blockchains.

4. The digital asset management system according to claim 3, characterized in that: The service layer is also used to configure any one or any combination of the first customized interface, the second customized interface, and the third customized interface according to the asset service request.

5. The digital asset management system according to any one of claims 1 to 4, characterized in that: The digital asset management system further includes a data service layer, which is connected to the multi-chain layer, the contract layer and the control layer respectively; The data service layer is used to store the business data generated during the process of the service layer executing the asset service request.

6. A digital asset management method, characterized in that: Applied to the digital asset management system according to any one of claims 1 to 5, the method comprises: Receive asset service requests from users; Calling a first customized interface according to the asset service request, so as to design corresponding data models for multiple blockchains corresponding to different types of digital assets through the first customized interface; wherein each of the data models is used to indicate a transaction mode of a corresponding digital asset; The second customized interface is called according to the asset service request to execute each contract template corresponding to each type of digital asset through the second customized interface, or to configure each contract template.

7. An electronic device, characterized in that: include: at least one processor; as well as, a memory communicatively connected to the at least one processor; wherein, The memory stores instructions that can be executed by the at least one processor, and the instructions are executed by the at least one processor to enable the at least one processor to execute the digital asset management method as described in claim 6.

8. A computer-readable storage medium storing a computer program, characterized in that: When the computer program is executed by a processor, the digital asset management method as claimed in claim 6 is implemented.

Images