WO2022206209A1 - Gestion d'actifs basée sur une chaîne de blocs - Google Patents

Gestion d'actifs basée sur une chaîne de blocs Download PDF

Info

Publication number
WO2022206209A1
WO2022206209A1 PCT/CN2022/076779 CN2022076779W WO2022206209A1 WO 2022206209 A1 WO2022206209 A1 WO 2022206209A1 CN 2022076779 W CN2022076779 W CN 2022076779W WO 2022206209 A1 WO2022206209 A1 WO 2022206209A1
Authority
WO
WIPO (PCT)
Prior art keywords
asset
blockchain
type
transaction
target
Prior art date
Application number
PCT/CN2022/076779
Other languages
English (en)
Chinese (zh)
Inventor
李艳鹏
陆旭明
周知远
郭学鹏
赵文强
Original Assignee
支付宝(杭州)信息技术有限公司
蚂蚁区块链科技(上海)有限公司
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 支付宝(杭州)信息技术有限公司, 蚂蚁区块链科技(上海)有限公司 filed Critical 支付宝(杭州)信息技术有限公司
Publication of WO2022206209A1 publication Critical patent/WO2022206209A1/fr

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3827—Use of message hashing
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
    • G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
    • G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor

Definitions

  • the embodiments of this specification relate to the field of blockchain technology, and in particular, to a blockchain-based asset management.
  • This specification proposes a blockchain-based asset management method, which is applied to node devices in the blockchain; wherein the transaction types supported by the blockchain include a first asset definition transaction for defining an asset model ;
  • the operator of the blockchain defines an asset type and an asset format corresponding to the asset type in the blockchain; the method includes: receiving the information issued by the asset management party accessing the blockchain The first asset definition transaction; wherein the first asset definition transaction includes an asset model defined by the asset manager and corresponding to a target asset type; the asset model includes asset creation information corresponding to the target asset type ; in response to the first asset definition transaction, save the asset model on the blockchain, so that the asset creator docked with the asset manager creates information based on the asset in the asset model, and communicates with The asset format corresponding to the target asset type creates a standardized blockchain asset in the blockchain.
  • the transaction type supported by the blockchain further includes a second asset definition transaction for defining an asset type; the method further includes: receiving the second asset definition transaction issued by the operator; wherein, The second asset definition transaction includes the target asset type defined by the operator and an asset format corresponding to the target asset type; in response to the second asset definition transaction, saving all the assets on the blockchain.
  • the target asset type and the asset format corresponding to the target asset type are included in the transaction type supported by the blockchain.
  • the storing the asset model on the blockchain includes: saving the asset model in the Merkle state tree of the blockchain in the form of a key-value pair;
  • the storing of the target asset type and the asset format corresponding to the target asset type on the blockchain includes: converting the target asset type and the asset format corresponding to the target asset type with key-
  • the form of value key-value pair is stored in the Merkle state tree of the blockchain.
  • the transaction type supported by the blockchain further includes an asset creation transaction for creating an asset corresponding to the target asset type; the method further includes: receiving a message from an asset creator connected by the asset management party The asset creation transaction; wherein, the asset creation transaction includes the type identifier of the target asset type; in response to the asset creation transaction, obtain the target asset type stored in the blockchain and indicated by the type identifier The corresponding asset format and the asset model corresponding to the target asset type, and based on the asset creation information in the asset model and the asset format corresponding to the target asset type, create a standardized area in the blockchain. blockchain assets.
  • the asset management party deploys an asset-related smart contract on the blockchain; the method further includes: receiving a contract invocation transaction sent by an asset creator connected to the asset management party; wherein, The contract invocation transaction includes the type identifier of the target asset type; in response to the contract invocation transaction, the query logic in the smart contract is invoked to query the data stored in the blockchain and indicated by the type identifier.
  • the asset format corresponding to the target asset type, and the asset model corresponding to the target asset type and after querying the asset format corresponding to the target asset type and the asset model corresponding to the target asset type, further call the According to the creation logic in the smart contract, based on the asset creation information in the asset model and the asset format corresponding to the target asset type, a standardized blockchain asset is created in the blockchain.
  • the asset format includes several asset attribute fields; the asset creation transaction or the contract invocation transaction includes attribute values submitted by the asset creator and corresponding to the several asset attribute fields; the asset creation information Including verification rules for attribute values corresponding to the several asset attribute fields; the asset creation information based on the asset model and the asset format corresponding to the target asset type, in the blockchain Creating standardized blockchain assets includes: verifying, based on the verification rules in the asset model, the attribute values submitted by the asset creator and corresponding to the several asset attribute fields; if the verification is passed, further Based on the attribute values, and an asset format corresponding to the target asset type, a standardized blockchain asset is created in the blockchain.
  • the asset creation information includes a state machine corresponding to the blockchain asset; the method further includes: after creating a standardized blockchain asset in the blockchain, based on the asset model The state machine of , updates the asset state corresponding to the blockchain asset.
  • the transaction type supported by the blockchain further includes an asset transfer transaction for transferring assets; the method further includes: receiving an asset transfer transaction sent by an asset transfer party docked by the asset management party; wherein, the The asset transfer transaction includes the asset identifier of the block chain asset to be transferred; in response to the asset transfer transaction, obtain the block chain asset stored in the block chain and corresponding to the asset identifier, and perform an analysis on the asset corresponding to the asset. Identify the corresponding blockchain assets for asset transfer.
  • the asset management party deploys an asset-related smart contract on the blockchain; the method further includes: receiving a contract invocation transaction sent by an asset transfer party docked by the asset management party; wherein, The contract invocation transaction includes the asset identifier of the blockchain asset; in response to the contract invocation transaction, the query logic in the smart contract is invoked to query the area stored in the blockchain that corresponds to the asset identifier.
  • block chain assets and after querying the block chain assets corresponding to the asset identifiers, further call the transfer logic in the smart contract to transfer the assets of the block chain assets corresponding to the asset identifiers.
  • the asset type and the asset format corresponding to the asset type are defined in the blockchain by the operator based on a general programming language; the asset model is defined by the asset manager based on the general programming language. language definition.
  • the general-purpose programming language includes a general-purpose declarative programming language.
  • the general-purpose declarative programming language includes a domain-specific language.
  • the operator includes a blockchain service platform;
  • the asset management party includes a financial institution accessing the blockchain service platform;
  • the asset creator includes a user who is provided with asset services by the financial institution client.
  • This specification also proposes a blockchain-based asset management device, which is applied to a node device in a blockchain; wherein the transaction type supported by the blockchain includes a first asset definition for defining an asset model transaction; the operator of the blockchain defines an asset type and an asset format corresponding to the asset type in the blockchain; the device includes: a first receiving module, which receives and accesses the blockchain The first asset definition transaction issued by the asset management party; wherein, the first asset definition transaction includes an asset model defined by the asset management party and corresponding to the target asset type; Asset creation information corresponding to the type; the first definition module, in response to the first asset definition transaction, saves the asset model on the blockchain, so that the asset creator docked with the asset manager is based on the The asset creation information in the asset model and the asset format corresponding to the target asset type are used to create standardized blockchain assets in the blockchain.
  • the transaction type supported by the blockchain further includes a second asset definition transaction used to define an asset type; the apparatus further includes: a second receiving module for receiving the second asset issued by the operator A definition transaction; wherein the second asset definition transaction includes the target asset type defined by the operator and an asset format corresponding to the target asset type; a second definition module, in response to the second asset definition transaction , and save the target asset type and the asset format corresponding to the target asset type on the blockchain.
  • the first definition module saves the asset model in the Merkle state tree of the blockchain in the form of key-value pairs; the second definition module: saves the asset model
  • the target asset type and the asset format corresponding to the target asset type are stored in the Merkle state tree of the blockchain in the form of key-value pairs.
  • the transaction type supported by the blockchain further includes an asset creation transaction for creating an asset corresponding to the target asset type;
  • the device further includes: a third receiving module for receiving the docking of the asset management party An asset creation transaction sent by the asset creator of The asset format corresponding to the target asset type indicated by the type identifier, and the asset model corresponding to the target asset type, and based on the asset creation information in the asset model, and the asset format corresponding to the target asset type , creating standardized blockchain assets in the blockchain.
  • the asset management party has deployed an asset-related smart contract on the blockchain;
  • the device further includes: a fourth receiving module that receives a contract sent by an asset creator connected to the asset management party Invoke transaction; wherein, the contract invocation transaction includes the type identifier of the target asset type; the second creation module, in response to the contract invocation transaction, invokes the query logic in the smart contract to query the blockchain storage
  • the asset format corresponding to the target asset type indicated by the type identifier, and the asset model corresponding to the target asset type, and the asset format corresponding to the target asset type and the target asset After the asset model corresponding to the type, the creation logic in the smart contract is further invoked, and based on the asset creation information in the asset model and the asset format corresponding to the target asset type, a standardized creation is created in the blockchain. blockchain assets.
  • the asset format includes several asset attribute fields;
  • the asset creation transaction or the contract invocation transaction includes attribute values submitted by the asset creator and corresponding to the several asset attribute fields;
  • the asset creation information Including verification rules for the attribute values corresponding to the several asset attribute fields;
  • the creation module based on the verification rules in the asset model The attribute value is verified; if the verification is passed, a standardized blockchain asset is created in the blockchain based on the attribute value and the asset format corresponding to the target asset type.
  • the asset creation information includes a state machine corresponding to the blockchain asset; the creation module: after creating a standardized blockchain asset in the blockchain, based on the A state machine that updates the asset state corresponding to the blockchain asset.
  • the transaction type supported by the blockchain further includes an asset transfer transaction for transferring the blockchain asset;
  • the device further includes: a fifth receiving module for receiving the asset transfer docked by the asset management party The asset transfer transaction sent by the party; wherein, the asset transfer transaction includes the asset identifier of the blockchain asset to be transferred; the first transfer module, in response to the asset transfer transaction, obtains the data stored in the blockchain and the The blockchain asset corresponding to the asset identifier, and the asset transfer is performed on the blockchain asset corresponding to the asset identifier.
  • the asset management party has deployed an asset-related smart contract on the blockchain;
  • the device further includes: a sixth receiving module for receiving a contract sent by an asset transfer party connected to the asset management party Invoke transaction; wherein, the contract invocation transaction includes the asset identifier of the blockchain asset; the second transfer module, in response to the contract invocation transaction, invokes the query logic in the smart contract to query the blockchain
  • the stored blockchain asset corresponding to the asset identifier and after querying the blockchain asset corresponding to the asset identifier, the transfer logic in the smart contract is further invoked, and the transfer logic corresponding to the asset identifier is further called.
  • the corresponding blockchain assets are transferred.
  • the asset type and the asset format corresponding to the asset type are defined in the blockchain by the operator based on a general programming language; the asset model is defined by the asset manager based on the general programming language. definition.
  • the general-purpose programming language includes a general-purpose declarative programming language.
  • the general-purpose declarative programming language includes a domain-specific language.
  • the operator includes a blockchain service platform;
  • the asset management party includes a financial institution accessing the blockchain service platform;
  • the asset creator includes a user who is provided with asset services by the financial institution client.
  • This specification also proposes an electronic device, comprising: a processor; a memory for storing instructions executable by the processor; wherein the processor implements the steps of the above method by running the executable instructions.
  • This specification also proposes a computer-readable storage medium on which computer instructions are stored, and when the instructions are executed by a processor, implement the steps of the above method.
  • the operator of the blockchain can define the target asset type and the asset format corresponding to the target asset type in the blockchain; the node device in the blockchain can receive the asset management party
  • the asset model corresponding to the target asset type defined by the asset manager in the first asset definition transaction is saved on the blockchain,
  • the asset creator connected with the asset manager can create a standardized asset in the blockchain based on the asset creation information stored in the asset model and the asset format corresponding to the target asset type. Since the operator of the above-mentioned blockchain defines the asset type and the asset format corresponding to the asset type in the above-mentioned blockchain, all asset managers accessing the blockchain are located in this area.
  • the asset model corresponding to the asset type defined in the blockchain all instructs the creation of blockchain assets according to the asset format corresponding to the asset type. Therefore, for the asset creator connected with any of the asset managers, these
  • the asset format of the blockchain assets corresponding to the asset type created by the asset creator on the blockchain is the same, and they are defined in the blockchain by the blockchain operator and correspond to the asset type. Asset format; thus realizes the creation of standardized blockchain assets in the blockchain, thereby facilitating the circulation of the created blockchain assets on the blockchain.
  • FIG. 1 is a schematic diagram of a network environment related to the blockchain shown in this specification
  • FIG. 2 is a flowchart of a blockchain-based asset management method shown in an exemplary embodiment of this specification
  • FIG. 3 is a schematic diagram of a state machine shown in an exemplary embodiment of the present specification
  • FIG. 4 is a hardware structure diagram of an electronic device where a blockchain-based asset management device is located according to an exemplary embodiment of this specification;
  • FIG. 5 is a block diagram of a blockchain-based asset management device shown in an exemplary embodiment of the present specification.
  • the steps of the corresponding methods are not necessarily performed in the order shown and described in this specification.
  • the method may include more or fewer steps than described in this specification.
  • a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. describe.
  • FIG. 1 is a schematic diagram of a network environment related to the blockchain shown in this specification.
  • a client-side computing device 101 a server-side 102, and at least one blockchain system may be included; for example, a blockchain system 103, a blockchain system 104, and a blockchain system 105.
  • the client-side computing device 101 may include various types of client-side computing devices; for example, the client-side terminal device may include, for example, a PC terminal device, a mobile terminal device, an Other forms of smart devices with certain computing capabilities, and so on.
  • the client-side terminal device may include, for example, a PC terminal device, a mobile terminal device, an Other forms of smart devices with certain computing capabilities, and so on.
  • client-side computing device 101 does not mean that all the client-side computing devices therein are in the same communication network, but is merely a general term for these client-side computing devices.
  • At least part of the computing devices in the client-side terminal device 101 may be coupled to the server side 102 through various communication networks; for example, the device 1 and device 2 shown in FIG. 1 and the server side 102 coupled.
  • terminal devices in the client-side terminal device 101 may not be coupled with the server-side 102, but directly coupled to the blockchain system as blockchain nodes through various communication networks; for example, The device 4 shown in Figure 1 can be coupled to the blockchain system as a blockchain node.
  • the above-mentioned communication network may include wired and/or wireless communication networks; for example, it may be a Local Area Network (LAN), Wide Area Network (WAN), the Internet, or a combination thereof.
  • LAN Local Area Network
  • WAN Wide Area Network
  • the Internet or a combination thereof.
  • the client-side computing device 101 may further include one or more user-side servers; for example, the device 5 shown in FIG. 1 . At least part of the computing devices in the client-side terminal device 101 may be coupled to the user-side server, and the user-side server may be further coupled to the above-mentioned server 102; for example, the device 1 and the device shown in FIG. 1 2 is coupled to the device 5, and the device 5 is further coupled to the server side 102.
  • the above-mentioned user-side server may be implemented by a service entity that has built a user account system; the above-mentioned service entity may include an operating entity that provides various online and/or offline services to users for service carriers; wherein , the above-mentioned service carrier may include a service carrier in the form of software, and may also include a service carrier in the form of hardware.
  • the above-mentioned service carrier may include various client software for providing online Internet services; for example, a website, a webpage, an APP, and the like.
  • the above service carrier may also include various smart devices deployed offline and capable of providing offline services; for example, smart express cabinets deployed in residential areas, office areas, and public places.
  • the above-mentioned operating entities may include operators corresponding to the above-mentioned service carriers; for example, the above-mentioned operating entities may include individuals, organizations, companies, and enterprises that operate and manage the above-mentioned service carriers, and so on.
  • the server side 102 may also be coupled to one or more blockchain systems through various communication networks; for example, the server side 102 shown in FIG. 1 may be respectively coupled to the blockchain system 103 , Blockchain System 104 and Blockchain System 105, etc.
  • each blockchain system may maintain one or more blockchains (eg, public blockchains, private blockchains, consortium blockchains, etc.) or multiple blockchain nodes of multiple blockchains; for example, blockchain node 1, blockchain node 2, blockchain node 3, blockchain node 4, blockchain node 4 as shown in Figure 1 Node i, etc. can jointly host one or more blockchains.
  • Cross-chain data access can also be performed between the blockchains included in each blockchain system and between the various blockchain systems.
  • blockchain nodes may include full nodes and light nodes.
  • the full node can download the blockchain transactions contained in each block in the blockchain in full, and can perform consensus verification on the blockchain transactions contained in each blockchain according to the blockchain consensus algorithm on board. .
  • the light node can not download the complete blockchain, but can only download the block header data of each block in the blockchain, and use the data contained in the block header as the verification root to verify the blockchain. authenticity of the transaction. Light nodes can attach to full nodes to access more features of the blockchain.
  • each blockchain node in the blockchain system 103 shown in FIG. 1 can serve as a full node; and the device 4 shown in FIG. 1 that is directly coupled to the blockchain system can serve as a light node , attached to each full node in the blockchain system 103 .
  • the blockchain node may be a physical device or a virtual device implemented in a server or server cluster; for example, the blockchain node device may be a physical host in a server cluster, or It is a virtual machine created after virtualizing the hardware resources carried by a server or server cluster based on virtualization technology.
  • Each blockchain node can be coupled together through various types of communication methods (such as TCP/IP) to form a network to carry one or more blockchains.
  • the server side 102 may include a BaaS platform (also referred to as a BaaS cloud) for providing blockchain services (BaaS, Blockchain as a Service).
  • the BaaS platform can target client-side computing devices coupled to the BaaS platform by providing pre-written software for activities that take place on the blockchain, such as subscriptions and notifications, user authentication, database management, and remote updates.
  • Simple and easy to use, one-click deployment, fast verification, flexible and customizable blockchain services which can accelerate the development, testing, and launch of blockchain business applications, and help the implementation of blockchain business application scenarios in various industries.
  • software such as MQ (Message Queue, message queue) services can be provided with the BaaS platform; client-side computing devices coupled with the BaaS platform can subscribe to the blockchain system coupled with the BaaS platform
  • MQ Message Queue, message queue
  • the smart contract deployed on a certain blockchain in the middle of the world generates contract events on the blockchain after the execution is triggered; the BaaS platform can monitor the events generated on the blockchain after the smart contract is triggered and executed, and then based on the MQ
  • the software related to the service adds the contract event to the message queue in the form of a notification message, so that the client-side computing device subscribed to the message queue can obtain the notification related to the above-mentioned contract event.
  • the BaaS platform can also provide enterprise-level platform services based on blockchain technology to help enterprise-level customers build a secure and stable blockchain environment and easily manage the deployment, operation, and maintenance of blockchains and development.
  • the BaaS platform can implement rich security policies and multi-tenant isolation environments based on cloud technology, provide advanced security protection based on chip encryption technology, and provide end-to-end services that can be quickly expanded without interruption based on highly reliable data storage.
  • high-availability services on the client side in another example, enhanced management capabilities to help customers build enterprise-grade blockchain network environments; and native support for standard blockchain applications and data, such as Hyperledger Fabric and Enterprise Ethereum-Quorum's mainstream open source blockchain technology to build an open and inclusive technology ecosystem.
  • Blockchains are generally divided into three types: Public Blockchain, Private Blockchain and Consortium Blockchain.
  • the public chain is represented by Bitcoin and Ethereum.
  • Participants who join the public chain (also called nodes in the blockchain) can read the data records on the chain, participate in transactions, and compete for the accounting rights of new blocks, etc. .
  • each node can freely join or leave the network and perform related operations.
  • the private chain is on the contrary, the write permission of the network is controlled by an organization or institution, and the data read permission is regulated by the organization.
  • a private chain can be a weakly centralized system with strict restrictions on nodes and a small number of nodes.
  • This type of blockchain is more suitable for internal use within a specific institution.
  • the consortium chain is a blockchain between the public chain and the private chain, which can achieve "partial decentralization".
  • Each node in the alliance chain usually has a corresponding entity or organization; the node joins the network through authorization and forms a stakeholder alliance to jointly maintain the operation of the blockchain.
  • the blockchain is usually composed of several blocks. Timestamps corresponding to the creation time of the blocks are respectively recorded in these blocks, and all blocks form a time-ordered data chain strictly according to the timestamps recorded in the blocks.
  • the real data generated in the physical world it can be constructed into a standard transaction format supported by the blockchain, and then published to the blockchain, and the node devices in the blockchain will perform consensus processing on the received transactions , and after reaching a consensus, the node device in the blockchain as the accounting node will package the transaction into the block and store the certificate persistently in the blockchain.
  • the consensus algorithms supported in the blockchain can include: the first type of consensus algorithm, that is, the consensus algorithm in which node devices need to compete for the accounting rights of each round of accounting cycles, such as Proof of Work (POW), equity Consensus algorithms such as Proof of Stake (POS) and Delegated Proof of Stake (DPOS); the second type of consensus algorithm is to pre-select billing nodes for each round of billing cycle (no need to compete for billing rights). Consensus algorithms, such as Practical Byzantine Fault Tolerance (PBFT) and other consensus algorithms.
  • POP Proof of Work
  • POS Proof of Stake
  • DPOS Delegated Proof of Stake
  • Consensus algorithms such as Practical Byzantine Fault Tolerance (PBFT) and other consensus algorithms.
  • all node devices competing for the right to bookkeeping can execute the transaction after receiving the transaction.
  • One of the node devices competing for the accounting right may win in the process of competing for the accounting right in this round and become an accounting node.
  • the accounting node can package the received transaction with other transactions to generate the latest block, and send the generated latest block or the block header of the latest block to other node devices for consensus.
  • the node equipment with accounting rights has been negotiated before this round of accounting. Therefore, after the node device receives the transaction, if it is not the accounting node of the current round, it can send the transaction to the accounting node.
  • the transaction may be executed during or before the process of packaging the transaction with other transactions to generate the latest block.
  • the accounting node After the accounting node generates the latest block, it can send the latest block or the block header of the latest block to other node devices for consensus.
  • the accounting node of this round can package the received transaction to generate the latest block, and use the generated latest block or the latest block
  • the block header is sent to other node devices for consensus verification. If other node devices receive the latest block or the block header of the latest block and verify that there is no problem, the latest block can be appended to the end of the original blockchain, thereby completing the blockchain accounting process. In the process of verifying the new block or block header sent by the accounting node, other nodes can also execute the transactions contained in the block.
  • FIG. 2 is a flowchart of a blockchain-based asset management method shown in an exemplary embodiment of this specification.
  • the above-mentioned blockchain-based asset management method can be applied to node devices in the blockchain; the method may include the following steps: Step 202, receiving assets accessing the blockchain The first asset definition transaction issued by the management party; wherein the first asset definition transaction includes an asset model defined by the asset management party and corresponding to the target asset type; the asset model includes an asset model corresponding to the target asset type The asset creation information; Step 204, in response to the first asset definition transaction, save the asset model on the blockchain, so that the asset creator docked with the asset manager is based on the asset model.
  • the asset creation information, and the asset format corresponding to the target asset type create standardized blockchain assets in the blockchain.
  • converting non-monetary physical assets in the real world into virtual assets on the blockchain usually refers to "anchoring" the physical assets with virtual assets on the blockchain as these virtual assets.
  • the user can create a virtual asset on the blockchain that matches the value of the real-world non-monetary physical asset and circulate it on the blockchain; for example, the Users can convert non-monetary physical assets, such as real estate, stocks, loan contracts, bills and accounts receivable, into virtual assets with matching value and circulate on the blockchain.
  • non-monetary physical assets such as real estate, stocks, loan contracts, bills and accounts receivable
  • the blockchain operator may define one or more asset types in the blockchain, and asset formats corresponding to each asset type respectively.
  • the transaction types supported by the above-mentioned blockchain can be extended to extend an asset-defining transaction for defining an asset model in the blockchain.
  • the transaction types supported by the blockchain usually include: ordinary transfer transactions, transactions that create smart contracts, and transactions that invoke smart contracts; in this case, on the basis of the above three types of transactions, the above blocks A new type of transaction is extended in the chain, that is, the asset definition transaction used to define the asset model, and the above four types of transactions are all used as transaction types supported by the blockchain.
  • the node devices in the blockchain can execute these types of transactions in the local virtual machine to run the native code of the blockchain corresponding to these types of transactions, to achieve The logic dictated by these native codes.
  • the logic indicated by the native code corresponding to the above-mentioned transfer transaction is usually the logic of executing the transfer operation based on information such as the transfer-out account, the transfer-in account, and the transfer amount in the transfer transaction; the native code corresponding to the above-mentioned smart contract creation transaction
  • the indicated logic is usually the logic of creating a contract account corresponding to the smart contract and anchoring the contract code of the smart contract to the contract account.
  • the code hash of the contract code in the block can be filled to the corresponding In the code field in the contract account of the smart contract; the logic indicated by the native code corresponding to the transaction that calls the smart contract above is usually to load the contract code of the smart contract from the contract account corresponding to the called smart contract, and run the load
  • the contract code in the contract code implements the logic indicated by the contract code. For example, you can search for the corresponding contract code in the block based on the code hash filled in the code field in the contract account; the native code corresponding to the above asset definition transaction indicates Logic is the logic that defines the asset model in the blockchain.
  • the asset management party can access the above-mentioned blockchain in advance, that is, it can establish a communication connection with the node device in the blockchain. Subsequently, the asset manager may use the asset definition transaction (called the first asset type) for defining an asset model corresponding to a certain asset type (called the target asset type) defined by the operator of the blockchain in the blockchain. An asset-defining transaction) is posted to the blockchain.
  • the first asset definition transaction may include an asset model defined by the asset manager and corresponding to the target asset type; the asset model may include asset creation information corresponding to the target asset type.
  • the blockchain asset to be created corresponding to the target asset type can be used as an object, and the asset model is the class used to create the blockchain asset corresponding to the target asset type. That is, the asset model is an instance of the blockchain asset corresponding to the target asset type.
  • the above-mentioned asset management party can define an asset model corresponding to this asset type in the above-mentioned blockchain.
  • one asset type can correspond to multiple asset models; these asset models can be defined in the blockchain by different asset managers.
  • the asset model may include asset creation information corresponding to the asset type. In this case, based on the asset creation information and the asset format corresponding to the asset type, a blockchain asset corresponding to the asset type can be created in the above-mentioned blockchain (that is, the aforementioned can be created on the blockchain. circulating virtual assets).
  • the asset model defined based on the first asset-defining transaction can be saved on the blockchain, so as to be compatible with the first asset-defining transaction.
  • the asset creator connected to the asset management party may be based on the asset creation information stored in the asset model on the blockchain and the target asset type defined in the blockchain by the blockchain operator.
  • the corresponding asset format create a blockchain asset corresponding to the target asset type in the blockchain.
  • hash value can also be calculated for the above-mentioned blockchain asset created, and the calculated hash value can be used as the asset identifier of the blockchain asset.
  • the operator of the above-mentioned blockchain defines the asset type and the asset format corresponding to the asset type in the above-mentioned blockchain
  • all asset managers accessing the blockchain define in the blockchain the same
  • the asset model corresponding to the asset type all instructs the creation of blockchain assets according to the asset format corresponding to the asset type. Therefore, for the asset creators connected with any of the asset management parties, these asset creators are in this block.
  • the asset format of the blockchain asset corresponding to the asset type created on the chain is the same, and it is the asset format corresponding to the asset type defined in the blockchain by the operator of the blockchain; in this case below, the above-mentioned blockchain assets created in the above-mentioned blockchains can be regarded as standardized blockchain assets.
  • the operator of the above-mentioned blockchain may include a blockchain service platform; the above-mentioned asset management party may include a financial institution that accesses the blockchain service platform; the above-mentioned asset creator may include a user client that provides asset services by the financial institution. .
  • the above-mentioned blockchain operator, the above-mentioned asset manager and the above-mentioned asset creator may refer to the same entity, for example, these three are a financial institution or an individual; or, may refer to different entities.
  • the above-mentioned blockchain may include the blockchain system 103 in the network environment; the node devices in the blockchain may include the blockchain nodes 1, 1 and 1 in the blockchain system 103 Block chain node 2, block chain node 3, block chain node 4, block chain node i, etc.; the block chain service platform as the operator of the above block chain may include the server 102 in the network environment , that is, the electronic device corresponding to the blockchain service platform can be the server 102 in the network environment; in order to ensure the data security of the above-mentioned blockchain and facilitate the management and maintenance of the blockchain, as the above-mentioned asset management
  • the financial institution of the other party usually does not directly establish a communication connection with the node device in the blockchain, but accesses the blockchain by establishing a communication connection with the blockchain service platform; in this case, the financial institution The institution may include Device 1, Device 2, Device 3 or Device 5 in the client-side computing device 101 in the network environment, that is, the electronic device corresponding to the financial institution
  • the electronic device corresponding to the financial institution is device 5
  • the electronic device corresponding to the user client can be device 1 or device 2
  • the user client may be a user client that establishes a communication connection with Device 1, Device 2, or Device 3.
  • the creation of the target asset type in the above blockchain in this embodiment corresponds to the target asset type.
  • the process of the blockchain asset is explained.
  • the blockchain operator may define one or more asset types in the blockchain, and asset formats corresponding to each asset type respectively.
  • the operator of the above-mentioned blockchain may define one or more asset types in the blockchain based on a general programming language, and asset formats corresponding to each asset type respectively.
  • the asset manager of the blockchain can, based on the general programming language, perform operations on the blockchain defined by the blockchain operator in the blockchain.
  • the asset type and the asset format corresponding to the asset type are parsed, and a blockchain asset is created in the blockchain according to the parsing result.
  • the general-purpose programming language may include a general-purpose declarative programming language; further, the general-purpose declarative programming language may include domain-specific languages (DSL). That is, the general programming language may specifically include a domain-specific language; using the domain-specific language to define asset types and asset formats can improve code development efficiency and reduce programming workload.
  • DSL domain-specific languages
  • the operator of the above-mentioned blockchain can define asset types such as "real estate", "stock” and “accounts receivable” in the above-mentioned blockchain; and, the asset format corresponding to the "real estate” asset type, Asset formats such as the asset format corresponding to the "stock” asset type and the asset format corresponding to the "accounts receivable” asset type.
  • the asset format may include: several asset attribute fields; and a data structure used when assembling attribute values corresponding to the several asset attribute fields into a blockchain asset.
  • the asset attribute fields of the asset may include: on-chain identifier, off-chain identifier, asset type , amount, validity end date, financial institution, receivable and payable, etc.; in this case, the "Accounts Receivable” asset type can be defined using a declarative programming language as shown below, as well as the “Accounts Receivable” asset type
  • “StandardAR” is the type identifier of the "Accounts Receivable” asset type; the "idOnChain” field represents the on-chain identifier, the “idOffChain” field represents the off-chain identifier, the “assetType” field represents the asset type, the “amount” field represents the amount, " The validDateUntil field indicates the end date of the validity period, the "financeEnterprise” field indicates the financial institution, the “receivablesEnterprise” field indicates the receivable party, and the “payableEnterpsie” field indicates the payable party; “idOnChain”, “idOffChain”, “assetType”, “financeEnterprise”, “ receivablesEnterpsie” and “payableEnterpsie” are fields of type string, “amount” is a field of type long, and “validDateUntil” is a field of type date.
  • the transaction types supported by the above-mentioned blockchain can be extended to extend an asset-defining transaction for defining an asset model in the blockchain.
  • the transaction types supported by the blockchain usually include ordinary transfer transactions, transactions that create smart contracts, and transactions that invoke smart contracts; in this case, on the basis of the above three types of transactions, the blockchain A new type of transaction is expanded in , that is, the asset definition transaction used to define the asset model, and the above four types of transactions are all used as the transaction types supported by the blockchain.
  • the node devices in the blockchain can execute these types of transactions in the local virtual machine to run the native code of the blockchain corresponding to these types of transactions, and realize The logic dictated by these native codes.
  • the logic indicated by the native code corresponding to the above-mentioned transfer transaction is usually the logic of executing the transfer operation based on information such as the transfer-out account, the transfer-in account, and the transfer amount in the transfer transaction; the native code corresponding to the above-mentioned smart contract creation transaction
  • the indicated logic is usually the logic of creating a contract account corresponding to the smart contract and anchoring the contract code of the smart contract to the contract account.
  • the code hash of the contract code in the block can be filled into the corresponding In the code field in the contract account; the logic indicated by the native code corresponding to the above-mentioned transaction calling the smart contract, usually loads the contract code of the smart contract from the contract account corresponding to the called smart contract, and runs the loaded
  • the contract code implements the logic indicated by the contract code.
  • the corresponding contract code can be searched in the block; corresponding to the above-mentioned asset definition transaction used to define the asset model
  • the logic indicated by the native code is the logic for defining the asset model in the blockchain. Since the above asset definition transaction is not a transaction of calling a contract, when the node device in the blockchain executes the asset definition transaction in the local virtual machine, there is no need to call the logic indicated by the contract code in the smart contract deployed on the blockchain. .
  • the asset management party can access the above-mentioned blockchain in advance, that is, can establish a communication connection with the node device in the blockchain.
  • the asset manager may use the asset definition transaction (called the first asset type) for defining an asset model corresponding to a certain asset type (called the target asset type) defined by the operator of the blockchain in the blockchain.
  • An asset-defining transaction is posted to the blockchain.
  • the first asset definition transaction may include an asset model defined by the asset manager and corresponding to the target asset type; the asset model may include asset creation information corresponding to the target asset type.
  • the asset management party may define an asset model corresponding to the target asset type based on the general programming language.
  • the above-mentioned asset management party can define an asset model corresponding to the asset type in the above-mentioned blockchain.
  • one asset type can correspond to multiple asset models; these asset models can be defined in the blockchain by different asset managers.
  • the asset model may include asset creation information corresponding to the asset type; in this case, the asset creation information may be based on the asset type and the asset format corresponding to the asset type , and create a blockchain asset corresponding to the asset type in the above blockchain.
  • the above asset creation information may include: verification rules for attribute values corresponding to several asset attribute fields; state machines corresponding to the blockchain assets to be created; and the like.
  • the asset creator may submit attribute values corresponding to several asset attribute fields in the asset format corresponding to the asset type;
  • the attribute values submitted by the asset creator are assembled, so that the assembled attribute values corresponding to these asset attribute fields can be used as the blockchain assets created in the blockchain; , update the state corresponding to the created blockchain asset, and store the blockchain asset in association with the state of the blockchain asset.
  • an asset model corresponding to the "Accounts Receivable” asset type can be defined using a declarative programming language:
  • “StandardAR” is the type identifier of the “Accounts Receivable” asset type
  • “stdAr” is the model identifier of the asset model
  • “STD-FUNCTIONALITY” indicates that when creating a blockchain asset based on the asset model, use the aforementioned and All asset attribute fields in the asset format corresponding to the "accounts receivable” asset type; that is, the created blockchain asset corresponding to the "accounts receivable” asset type contains attributes corresponding to all the above asset attribute fields value
  • the "VALIDATION” part indicates the validation rules for attribute values corresponding to all the above asset attribute fields
  • the "STATE-MACHINE” part indicates the state machine corresponding to the blockchain asset to be created.
  • the state machine corresponding to the blockchain asset to be created in the asset model corresponding to the "accounts receivable” asset type includes: “NULL” means stateless; After the block chain asset, the state of the block chain asset is set to the "READY” state; after the block chain asset is confirmed (CONFIRM), the state of the block chain asset is switched from the "READY” state to the "READY” state.
  • CONFIRMED state
  • the settlement (SETTLE) of the blockchain asset switch the state of the blockchain asset from the “CONFIRMED” state to the "PARTIAL_SETTLE” state, or keep the state of the blockchain asset in " PARTIAL_SETTLE” state
  • the blockchain asset is mortgaged (MORTGAGE)
  • the state of the blockchain asset is switched from the "CONFIRMED” state to the "BACKED” state, or the state of the blockchain asset is changed from "PARTIAL_SETTLED” " state is switched to "BACKED” state
  • the blockchain asset is cleared (CLEAR)
  • the state of the blockchain asset is switched from “BACKED” state to "CLEARED” state.
  • the node device in the above-mentioned blockchain when the node device in the above-mentioned blockchain receives the above-mentioned first asset-defining transaction, in response to the first asset-defining transaction, execute the first asset-defining transaction in the local virtual machine to Run the native code of the blockchain corresponding to the first asset definition transaction to save the asset model defined based on the first asset definition transaction on the blockchain, so that the asset creator connected with the above asset management party can Based on the above-mentioned asset creation information in the asset model stored on the blockchain, and the asset format corresponding to the above-mentioned target asset type defined in the blockchain by the operator of the blockchain, in the blockchain Create a blockchain asset corresponding to the target asset type in .
  • the transaction type supported by the An asset-defining transaction for defining asset types is extended in the blockchain.
  • the transaction types supported by the blockchain at this time may include: ordinary transfer transactions, transactions for creating smart contracts, transactions for invoking smart contracts, and the above-mentioned asset definition transactions for defining asset models; in this case, you can On the basis of the above four types of transactions, a new type of transaction is extended in the above blockchain, that is, the asset definition transaction used to define the asset type, and the above five types of transactions are used as the Transaction types supported by the blockchain.
  • the logic of the native code indication corresponding to the asset definition transaction used to define the asset model above is the logic of defining the asset model in the blockchain; the native code instruction corresponding to the asset definition transaction used to define the asset type. , which is the logic of defining asset types in the blockchain.
  • the operator of the above-mentioned blockchain may publish an asset-defining transaction (referred to as a second asset-defining transaction) for defining the above-mentioned target asset type to the above-mentioned blockchain.
  • an asset-defining transaction referred to as a second asset-defining transaction
  • the second asset definition transaction may include: the target asset type defined by the operator of the blockchain, and an asset format corresponding to the target asset type.
  • the node device in the above-mentioned blockchain receives the above-mentioned second asset-defining transaction, in response to the second asset-defining transaction, execute the second asset-defining transaction in the local virtual machine to run and the second asset.
  • the native code of the blockchain corresponding to the transaction is defined, and the target asset type defined based on the second asset definition transaction and the asset format corresponding to the target asset type are stored on the blockchain.
  • these blockchain systems usually use Merkle trees; or, data structures based on Merkle trees to store and maintain data; where the data in Merkle trees are usually in the form of Merkle trees. It is stored in the form of key-value key-value pairs. That is, in one embodiment, the above-mentioned asset type and the asset format corresponding to the asset type can be saved in the Merkle state tree of the above-mentioned blockchain in the form of a key-value key-value pair; In the form of key-value key-value pairs, the asset model is saved to the Merkle state tree of the above blockchain. For example, the hash value of the asset model can be used as the key, and the asset model itself can be stored as the value in the Merkle state tree of the blockchain.
  • the above-mentioned blockchain may include the blockchain system 103 in the network environment; the node devices in the blockchain may include the blockchain nodes 1, The blockchain node 2, the blockchain node 3, the blockchain node 4, the blockchain node i, etc.; the above-mentioned blockchain operator may include the server 102 in the network environment; the above-mentioned asset management party may include the Device 5 in client-side computing device 101 in a network environment.
  • the above-mentioned asset management party can access the blockchain system 103 through the device 5 in the client-side computing device 101 in advance; the first asset definition transaction used to define the asset model corresponding to the above-mentioned target asset type can be subsequently published through the device 5 to the blockchain system 103.
  • the first asset definition transaction may include an asset model defined by the asset manager and corresponding to the target asset type; the asset model may include asset creation information corresponding to the target asset type; the first asset definition transaction is an extension Types of transactions supported by the blockchain.
  • the node device in the blockchain system 103 When the node device in the blockchain system 103 receives the above-mentioned first asset definition transaction, in response to the first asset definition transaction, execute the first asset definition transaction in the local virtual machine to run and the first asset definition transaction.
  • the native code of the blockchain corresponding to the asset definition transaction realizes that the asset model defined based on the first asset definition transaction is saved in the blockchain system 103, so that the asset creator connected with the above-mentioned asset management party can be based on the block chain.
  • the above-mentioned asset creation information in the asset model saved in the blockchain system 103, and the asset format corresponding to the target asset type defined in the blockchain system 103 by the operator of the blockchain, in the blockchain system 103 Create a blockchain asset corresponding to the target asset type.
  • the device 5 in the client-side computing device 101 can send the first asset definition request (the first asset definition request) initiated by the asset manager. including the asset model defined by the asset manager and corresponding to the above target asset type) is sent to the server side 102, and the server side 102 packages the first asset definition request into the above-mentioned first asset definition transaction, and the first asset definition
  • the transaction is published to the blockchain system 103; in this case, the node device in the blockchain system 103 that has established a communication connection with the server 102 can first receive the first asset definition transaction, and then the first asset Define the transaction to be sent to other node devices in the blockchain system 103 .
  • Each node device such as the blockchain node 1, blockchain node 2, blockchain node 3, blockchain node 4, and blockchain node i in the blockchain system 103 receives the first asset definition transaction.
  • consensus processing can be performed on the first asset definition transaction, and after reaching a consensus, the first asset definition transaction is packaged into a block, and the certificate is persistently stored in the blockchain system 103 .
  • the node device in the blockchain system 103 can respond to the first asset definition transaction and execute the first asset definition transaction in the local virtual machine to run and execute the first asset definition transaction.
  • the native code of the blockchain corresponding to the first asset definition transaction realizes that the asset model defined by the first asset definition transaction is saved in the blockchain system 103, so that the asset creator connected with the above-mentioned asset management party can be based on
  • the above-mentioned asset creation information in the asset model saved in the blockchain system 103, and the asset format corresponding to the target asset type defined in the blockchain system 103 by the operator of the blockchain, are stored in the blockchain system 103.
  • a blockchain asset corresponding to the target asset type is created.
  • the operator of the above-mentioned blockchain may publish the second asset definition transaction for defining the above-mentioned target asset type to the blockchain system 103 through the server 102 .
  • the second asset definition transaction may include: the target asset type defined by the operator of the blockchain and an asset format corresponding to the target asset type; the second asset definition transaction is an extended transaction type supported by the blockchain .
  • the node device in the blockchain system 103 When the node device in the blockchain system 103 receives the above-mentioned second asset definition transaction, in response to the second asset definition transaction, execute the second asset definition transaction in the local virtual machine to run and the second asset definition transaction.
  • the native code of the blockchain corresponding to the asset definition transaction realizes that the above-mentioned target asset type defined based on the second asset definition transaction and the asset format corresponding to the target asset type are stored in the blockchain system 103 .
  • the server 102 can package the target asset type defined by the operator of the blockchain and the asset format corresponding to the target asset type Create the above-mentioned second asset definition transaction, and publish the second asset definition transaction to the blockchain system 103; in this case, the node device in the blockchain system 103 that has established a communication connection with the server 102 can After receiving the second asset definition transaction, the second asset definition transaction is sent to other node devices in the blockchain system 103 .
  • Each node device such as blockchain node 1, blockchain node 2, blockchain node 3, blockchain node 4, and blockchain node i in the blockchain system 103 receives the second asset definition transaction.
  • consensus processing can be performed on the second asset definition transaction, and after reaching a consensus, the second asset definition transaction is packaged into a block, and the certificate is persistently stored in the blockchain system 103 .
  • the node device in the blockchain system 103 can respond to the second asset definition transaction, and execute the second asset definition transaction in the local virtual machine to run and the second asset definition transaction.
  • the native code of the blockchain corresponding to the second asset definition transaction realizes that the above-mentioned target asset type defined based on the second asset definition transaction and the asset format corresponding to the target asset type are stored in the blockchain system 103 .
  • the operator of the above-mentioned blockchain can pre-write the above-mentioned target asset type and the asset format corresponding to the target asset type into the native code of the blockchain system 103 through the server 102; subsequently, The above asset management party can access the blockchain system 103 through the device 5 in the client-side computing device 101, and publish the second asset definition transaction for defining the target asset type to the blockchain system 103 through the device 5.
  • the second asset defines a transaction as an extended transaction type supported by the blockchain.
  • the node device in the blockchain system 103 When the node device in the blockchain system 103 receives the above-mentioned second asset definition transaction, in response to the second asset definition transaction, execute the second asset definition transaction in the local virtual machine to run and the second asset.
  • the native code of the blockchain corresponding to the transaction realize reading the above target asset type and the asset format corresponding to the target asset type from the native code of the blockchain system 103, and save it in the blockchain system 103 The read target asset type above, and the asset format corresponding to the target asset type.
  • the transaction type supported by the An asset creation transaction for creating blockchain assets is extended from the blockchain.
  • the transaction types supported by the blockchain at this time may include: ordinary transfer transactions, transactions for creating smart contracts, transactions for invoking smart contracts, and the above-mentioned asset definition transactions for defining asset models; in this case, you can On the basis of the above four types of transactions, a new type of transaction is extended in the above blockchain, that is, an asset creation transaction for creating blockchain assets, and the above five types of transactions are all As the transaction type supported by this blockchain.
  • the logic indicated by the native code corresponding to the asset definition transaction used to define the asset model above is the logic of defining the asset model in the blockchain
  • the logic indicated by the native code corresponding to the above asset creation transaction is the logic indicated by the native code.
  • the transaction types supported by the blockchain can also include: ordinary transfer transactions, transactions that create smart contracts, and transactions that call smart contracts.
  • the asset creator connected with the above-mentioned asset management party can publish the asset creation transaction for creating the asset corresponding to the above-mentioned target asset type to the above-mentioned blockchain.
  • the asset creation transaction may include the type identifier of the target asset type.
  • the node device in the blockchain can execute the asset creation transaction in the local virtual machine in response to the asset creation transaction to run the blockchain corresponding to the asset creation transaction.
  • obtain the asset format stored in the blockchain corresponding to the asset type indicated by the type identifier in the asset creation transaction that is, obtain the asset stored in the blockchain corresponding to the above target asset type
  • obtaining the asset model stored in the blockchain corresponding to the asset type indicated by the type identifier in the asset creation transaction that is, obtaining the asset model stored in the blockchain corresponding to the target asset type ;
  • a blockchain asset corresponding to the target asset type can be created in the blockchain;
  • the created blockchain asset calculates the hash value, and uses the calculated hash value as the asset identifier of the blockchain asset.
  • the asset management party may deploy an asset-related smart contract on the blockchain in advance; the asset creator connected with the asset management party may call the contract for invoking the smart contract to a transaction Publish to this blockchain.
  • the contract invocation transaction may include the type identifier of the above-mentioned target asset type.
  • the node device in the above-mentioned blockchain When the node device in the above-mentioned blockchain receives the above-mentioned contract invocation transaction, it can call the query logic in the above-mentioned smart contract in response to the contract invocation transaction, and inquire about the type stored in the blockchain and in the contract invocation transaction.
  • the creation logic in the smart contract creates a blockchain asset corresponding to the target asset type in the blockchain based on the queried asset creation information in the asset model and the asset format corresponding to the target asset type ;
  • the hash value can be calculated for the created blockchain asset, and the calculated hash value can be used as the asset identifier of the blockchain asset.
  • the operator of the above-mentioned blockchain defines the asset type and the asset format corresponding to the asset type in the above-mentioned blockchain, all asset managers accessing the blockchain are in this block.
  • the asset model corresponding to the asset type defined in the chain all instructs the creation of blockchain assets according to the asset format corresponding to the asset type. Therefore, for the asset creator connected with any of the asset managers, these assets are
  • the asset format of the blockchain assets corresponding to the asset type created by the creator on the blockchain is the same, and they are all assets corresponding to the asset type defined in the blockchain by the blockchain operator Format; in this case, the above-mentioned blockchain assets created in the above-mentioned blockchains can be regarded as standardized blockchain assets.
  • the asset creator docked with the device 5 as the asset manager may include device 1 or device 2 in the client-side computing device 101 in the network environment.
  • the above-mentioned asset creator can publish the asset creation transaction for creating an asset corresponding to the above-mentioned target asset type to the above-mentioned blockchain through the device 1 .
  • the asset creation transaction may include the type identifier of the target asset type; the asset creation transaction is an extended transaction type supported by the blockchain.
  • the node device in the blockchain system 103 can execute the asset creation transaction in the local virtual machine in response to the asset creation transaction to run the block corresponding to the asset creation transaction.
  • the native code of the chain obtains the asset format stored in the blockchain system 103 corresponding to the above-mentioned target asset type indicated by the type identifier in the asset creation transaction;
  • the asset model corresponding to the target asset type subsequently, based on the acquired asset creation information in the asset model and the asset format corresponding to the target asset type, create a block chain system 103 corresponding to the target asset type
  • the hash value can be calculated for the created blockchain asset, and the calculated hash value can be used as the asset identifier of the blockchain asset.
  • the device 1 can send the asset creation request initiated by the above-mentioned asset creator (the asset creation includes the type identifier of the above-mentioned target asset type) to the device 5, and the device 5
  • the asset creation request is sent to the server 102, and the server 102 packages the asset creation request into the above asset creation transaction, and publishes the asset creation transaction to the blockchain system 103; in this case, with the server
  • the node device in the blockchain system 103 where the terminal 102 has established a communication connection can first receive the asset creation transaction, and then send the asset creation transaction to other node devices in the blockchain system 103 .
  • each node device such as blockchain node 1, blockchain node 2, blockchain node 3, blockchain node 4, and blockchain node i in the blockchain system 103 receives the asset creation transaction
  • Consensus processing can be performed on the asset creation transaction, and after a consensus is reached, the asset creation transaction is packaged into a block, and a persistent certificate is stored in the blockchain system 103 .
  • the node device in the blockchain system 103 can respond to the asset creation transaction and execute the asset creation transaction in the local virtual machine to run the asset creation transaction corresponding to the asset creation transaction.
  • the native code of the blockchain obtains the asset format stored in the blockchain system 103 and corresponding to the above-mentioned target asset type indicated by the type identifier in the asset creation transaction; on the other hand, obtains the blockchain system 103
  • the asset model corresponding to the target asset type saved in the asset model; subsequently, based on the acquired asset creation information in the asset model and the asset format corresponding to the target asset type, create a block chain system 103 corresponding to the target asset type.
  • the blockchain asset corresponding to the asset type; in addition, the hash value can be calculated for the created blockchain asset, and the calculated hash value can be used as the asset identifier of the blockchain asset.
  • the above-mentioned asset manager can deploy the smart contract related to the asset in the blockchain system 103 through the device 5 in advance; the above-mentioned asset creator can call the contract for calling the smart contract through the device 1 that has established a communication connection with the device 5. Transactions are posted to the blockchain system 103 .
  • the contract invocation transaction may include the type identifier of the above-mentioned target asset type.
  • the node device in the blockchain system 103 When the node device in the blockchain system 103 receives the above-mentioned contract invocation transaction, it can call the query logic in the above-mentioned smart contract in response to the contract invocation transaction, and query the data stored in the blockchain system 103 and the contract invocation transaction.
  • the asset creation information in the asset model and the asset format corresponding to the target asset type create a blockchain asset corresponding to the target asset type in the blockchain system 103;
  • the asset calculates the hash value, and uses the calculated hash value as the asset identifier of the blockchain asset.
  • the asset format corresponding to a certain asset type defined in the above-mentioned blockchain by the operator of the above-mentioned blockchain may include several asset attribute fields of the asset type; the above-mentioned asset management party is in this area
  • the asset creation information in the asset model corresponding to the asset type defined in the blockchain may include verification rules for attribute values corresponding to the above-mentioned several asset attribute fields; the above-mentioned asset creation transaction initiated by the above-mentioned asset creator or the above-mentioned
  • the contract invocation transaction may include attribute values submitted by the asset creator and corresponding to the above-mentioned several asset attribute fields.
  • the verification rule for the attribute values corresponding to the above-mentioned several asset attribute fields is to verify the attribute values corresponding to these asset attribute fields submitted by the above-mentioned asset creator; format, and assemble the attribute values submitted by the asset creator, so that the assembled attribute values corresponding to these asset attribute fields can be used as the blockchain assets created in the blockchain.
  • the asset model indicates the use of the asset format corresponding to the "Accounts Receivable” asset type. All the asset attribute fields of the blockchain asset are created; but in practical applications, the asset model can also instruct the use of some asset attribute fields to create blockchain assets; this specification does not limit this.
  • the asset creation information in the asset model corresponding to the asset type defined by the asset management party in the blockchain may include: a state corresponding to the blockchain asset to be created machine.
  • the created blockchain can be updated and created according to the state machine corresponding to the blockchain asset to be created in the above-mentioned asset model
  • the state corresponding to the asset is stored in association with the state of the blockchain asset.
  • the asset creation information in the asset model corresponding to the asset type defined by the asset management party in the above-mentioned blockchain may include: verification rules for attribute values corresponding to the above-mentioned several asset attribute fields; And, the state machine corresponding to the blockchain asset to be created.
  • the attribute values corresponding to these asset attribute fields submitted by the above-mentioned asset creator may be verified first according to the verification rules for the attribute values corresponding to the above-mentioned several asset attribute fields in the above-mentioned asset model; After the verification is passed, the attribute values submitted by the asset creator can be assembled according to the asset format corresponding to the asset type, so that the assembled attribute values corresponding to these asset attribute fields can be used as the block chain. Afterwards, the state corresponding to the blockchain asset to be created can be updated according to the state machine corresponding to the blockchain asset to be created in the asset model, and the blockchain asset Associated storage with the state of the blockchain asset.
  • an asset creation transaction that creates an asset corresponding to the "Accounts Receivable” asset type can be constructed using a declarative programming language as follows:
  • StandardAR is the type identifier of the “Accounts Receivable” asset type
  • stdAr is the model identifier of the asset model.
  • the node device in the above blockchain can respond to the asset creation transaction and execute the asset creation transaction in the local virtual machine to run the native code of the blockchain corresponding to the asset creation transaction.
  • the verification rule in the asset model corresponding to the "Accounts receivable” asset type is used to verify the attribute value corresponding to the asset attribute field in the asset creation transaction; for example, according to the verification rule "AMOUNT:RULE_GREATER_THAN_ZERO", Verify whether the attribute value corresponding to the "amount” (ie balance) field in the asset creation transaction is greater than 0; and, according to the verification rule "VALID_DATE_UNTIL:RULE_GREATER_THAN_30”, verify the asset creation transaction and " Whether the interval between the attribute value corresponding to the validDateUntil" (that is, the end date of the validity period) field and the current date is greater than 30.
  • a transaction can be created based on the asset for several asset attribute fields in the asset format corresponding to the "Accounts Receivable” asset type used in the asset model corresponding to the "Accounts Receivable” asset type
  • the attribute values corresponding to these asset attribute fields contained in the , and the asset format corresponding to the "Accounts Receivable” asset type create a blockchain asset corresponding to the "Accounts Receivable” asset type in this blockchain;
  • the asset attribute fields used in the asset model corresponding to the "Accounts Receivable” asset type include all the asset attribute fields in the asset format corresponding to the "Accounts Receivable” asset type, namely on-chain identification, off-chain identification , Asset Type, Amount, Validity End Date, Financial Institution, Receivable, and Payable; attribute values corresponding to these asset attribute fields include: “12345”, “12345”, “StandardAR”, 10000000, "2021.01.01” , "Enterprise A", “Enterprise B", “Enterprise C”.
  • the blockchain asset created in the blockchain can be The state is set to the "READY" state.
  • the transaction types supported by the blockchain can be further extended, so as to extend an asset transfer transaction for transferring blockchain assets in the blockchain, and transfer the transaction to the blockchain.
  • Asset transfer transactions are also included as transaction types supported by this blockchain.
  • the asset transfer party connected with the above-mentioned asset management party can publish the asset transfer transaction for transferring blockchain assets to the above-mentioned blockchain.
  • the asset transfer transaction may include the asset identifier of the blockchain asset to be transferred.
  • the node device in the above-mentioned blockchain receives the above-mentioned asset transfer transaction, in response to the asset transfer transaction, execute the asset transfer transaction in the local virtual machine to run the blockchain corresponding to the asset transfer transaction. , obtain the blockchain asset corresponding to the asset identifier in the asset transfer transaction stored in the blockchain, and transfer the obtained blockchain asset.
  • the blockchain asset can be transferred from the account of the payer to the account of the receivable.
  • the asset management party may deploy an asset-related smart contract on the blockchain in advance; the asset transfer party connected with the asset management party may call the contract for invoking the smart contract to a transaction Publish to this blockchain.
  • the contract invocation transaction may include the asset identifier of the blockchain asset to be transferred.
  • the node device in the above-mentioned blockchain receives the above-mentioned contract invocation transaction, in response to the contract invocation transaction, the node device can invoke the query logic in the above-mentioned smart contract to inquire about the assets stored in the blockchain and in the asset transfer transaction.
  • the corresponding blockchain asset is identified, and after the blockchain asset is queried, the transfer logic in the smart contract is further invoked to transfer the queried blockchain asset.
  • the above smart contract for transferring blockchain assets and the aforementioned smart contract for creating blockchain assets can be the same smart contract (that is, the contract code of the smart contract indicates the query logic, creation logic, transfer logic, etc.), or two different smart contracts; this specification does not limit this.
  • a target asset type and an asset format corresponding to the target asset type can be defined in the blockchain by the operator of the blockchain; the node device in the blockchain can receive the asset management
  • the asset model corresponding to the target asset type defined by the asset management party in the first asset definition transaction is saved on the blockchain , so that the asset creator docked with the asset manager can create in the blockchain based on the asset creation information in the asset model saved on the blockchain and the asset format corresponding to the target asset type.
  • Standardized blockchain assets since the operator of the above-mentioned blockchain defines the asset type in the above-mentioned blockchain and the asset format corresponding to the asset type, all asset managers accessing the blockchain are in this blockchain.
  • the asset model corresponding to the asset type defined in the blockchain all instructs the creation of blockchain assets according to the asset format corresponding to the asset type. Therefore, for the asset creator connected with any of the asset managers,
  • the asset format of the blockchain assets corresponding to the asset type created by these asset creators on the blockchain is the same, and they are defined in the blockchain by the blockchain operator and correspond to the asset type.
  • the asset format thus, the creation of standardized blockchain assets in the blockchain is realized, so that the created blockchain assets can be circulated on the blockchain.
  • this specification also provides an embodiment of a blockchain-based asset management apparatus.
  • the embodiments of the blockchain-based asset management apparatus in this specification can be applied to electronic devices.
  • the apparatus embodiment may be implemented by software, or may be implemented by hardware or a combination of software and hardware.
  • a device in a logical sense is formed by reading the corresponding computer program instructions in the non-volatile memory into the memory for operation by the processor of the electronic device where the device is located.
  • this specification is a hardware structure diagram of the electronic equipment where the blockchain-based asset management device is located, except for the processor, memory, network interface, and non-volatile hardware shown in Figure 4
  • the electronic device in which the apparatus in the embodiment is located usually may also include other hardware according to the actual function of the blockchain-based asset management, which will not be repeated here.
  • FIG. 5 is a block diagram of a blockchain-based asset management apparatus shown in an exemplary embodiment of this specification.
  • the blockchain-based asset management apparatus 50 can be applied to an electronic device as shown in FIG. 4 , and the electronic device can be used as a node device in a blockchain; wherein, the transaction types supported by the blockchain include a type used to define The first asset definition transaction of the asset model; the operator of the blockchain defines an asset type and an asset format corresponding to the asset type in the blockchain; the blockchain-based asset management device 50 can It includes: a first receiving module 501, which receives the first asset definition transaction issued by an asset management party accessing the blockchain; wherein the first asset definition transaction includes a target asset defined by the asset management party The asset model corresponding to the type; the asset model includes asset creation information corresponding to the target asset type; the first definition module 502, in response to the first asset definition transaction, saves the asset on the blockchain A model, so that the asset creator docked with the asset manager creates a standardized block in the blockchain based on
  • the transaction type supported by the blockchain further includes a second asset definition transaction for defining an asset type;
  • the apparatus 50 further includes: a second receiving module 503, which receives the data released by the operator. the second asset definition transaction; wherein, the second asset definition transaction includes the target asset type defined by the operator and an asset format corresponding to the target asset type; the second definition module 504, in response to the The second asset definition transaction saves the target asset type and the asset format corresponding to the target asset type on the blockchain.
  • the first definition module 502 saves the asset model in the form of key-value pairs in the Merkle state tree of the blockchain;
  • the second definition module 504 Save the target asset type and the asset format corresponding to the target asset type in the Merkle state tree of the blockchain in the form of key-value pairs.
  • the transaction type supported by the blockchain further includes an asset creation transaction for creating an asset corresponding to the target asset type;
  • the apparatus 50 further includes: a third receiving module 505, which receives the The asset creation transaction sent by the asset creator connected by the asset management party; wherein, the asset creation transaction includes the type identifier of the target asset type; the first creation module 506, in response to the asset creation transaction, obtains the block The asset format corresponding to the target asset type indicated by the type identifier and the asset model corresponding to the target asset type stored in the chain, and the asset creation information based on the asset model and the target asset The asset format corresponding to the type, and standardized blockchain assets are created in the blockchain.
  • the asset management party may deploy an asset-related smart contract on the blockchain; the device 50 may further include: a fourth receiving module 507 for receiving a contract sent by an asset creator connected to the asset management party Invoke transaction, the contract invocation transaction includes the type identifier of the target asset type; the second creation module 508 invokes the query logic in the smart contract in response to the contract invocation transaction, and inquires about the and The asset format corresponding to the target asset type indicated by the type identifier and the asset model corresponding to the target asset type, and the asset format corresponding to the target asset type and the asset format corresponding to the target asset type are queried.
  • the creation logic in the smart contract is further invoked, and based on the asset creation information in the asset model and the asset format corresponding to the target asset type, a standardized blockchain is created in the blockchain assets.
  • the asset creation information includes asset attribute information; the creation module 506 or 508: based on the asset attribute information in the asset model and the asset format corresponding to the target asset type, in the Create standardized blockchain assets in the blockchain.
  • the asset format includes several asset attribute fields;
  • the asset creation transaction or the contract invocation transaction includes attribute values submitted by the asset creator and corresponding to the several asset attribute fields;
  • the asset The creation information includes verification rules for attribute values corresponding to the several asset attribute fields;
  • the creating module 506 or 508 based on the verification rules in the asset model, perform verification on the verification rules submitted by the asset creator and the several asset attribute fields.
  • the attribute value corresponding to the asset attribute field is verified; if the verification is passed, a standardized blockchain asset is created in the blockchain based on the attribute value and the asset format corresponding to the target asset type. .
  • the asset creation information includes a state machine corresponding to the blockchain asset; the creation module 506 or 508: after creating a standardized blockchain asset in the blockchain, based on the The state machine in the asset model is used to update the asset state corresponding to the blockchain asset.
  • the transaction type supported by the blockchain further includes an asset transfer transaction for transferring the blockchain asset;
  • the apparatus 50 further includes: a fifth receiving module 509 for receiving the asset management party The asset transfer transaction sent by the connected asset transfer party; wherein, the asset transfer transaction includes the asset identifier of the blockchain asset to be transferred; the first transfer module 510, in response to the asset transfer transaction, obtains the blockchain Save the blockchain asset corresponding to the asset identifier, and perform asset transfer on the blockchain asset corresponding to the asset identifier.
  • the asset management party has deployed an asset-related smart contract on the blockchain;
  • the device 50 further includes: a sixth receiving module 511 for receiving the asset transfer docked by the asset management party The contract invocation transaction sent by the party; wherein, the contract invocation transaction includes the asset identifier of the blockchain asset; the second transfer module 512, in response to the contract invocation transaction, invokes the query logic in the smart contract to query The blockchain asset stored in the blockchain and corresponding to the asset identifier, and after the blockchain asset corresponding to the asset identifier is queried, the transfer logic in the smart contract is further invoked to correct the The blockchain asset corresponding to the asset identifier performs asset transfer.
  • the asset type and the asset format corresponding to the asset type may be defined in the blockchain by the operator based on a general programming language; the asset model may be defined by the asset manager based on the general programming language.
  • the general-purpose programming language may include a general-purpose declarative programming language.
  • the general-purpose declarative programming language may include a domain-specific language.
  • the operator may include a blockchain service platform; the asset manager includes a financial institution accessing the blockchain service platform; and the asset creator includes a user client provided by the financial institution with asset services.
  • a typical implementing device is a computer, which may be in the form of a personal computer, laptop computer, cellular phone, camera phone, smart phone, personal digital assistant, media player, navigation device, email sending and receiving device, game control desktop, tablet, wearable device, or a combination of any of these devices.
  • a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
  • Memory may include forms of non-persistent memory, random access memory (RAM) and/or non-volatile memory in computer readable media, such as read only memory (ROM) or flash memory (flash RAM).
  • RAM random access memory
  • ROM read only memory
  • flash RAM flash memory
  • Computer-readable media includes both persistent and non-permanent, removable and non-removable media.
  • Information storage can be implemented by any method or technology.
  • Information may be computer readable instructions, data structures, modules of programs, or other data.
  • Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read only memory (ROM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Flash Memory or other memory technology, Compact Disc Read-Only Memory (CD-ROM), Digital Versatile Disc (DVD) or other optical storage, magnetic Tape cartridges, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices.
  • computer-readable media does not include transitory computer-readable media, such as modulated data signals and carrier waves.
  • first, second, third, etc. may be used in this specification to describe various information, such information should not be limited by these terms. These terms are only used to distinguish the same type of information from each other.
  • first information may also be referred to as the second information, and similarly, the second information may also be referred to as the first information without departing from the scope of one or more embodiments of the present specification.
  • word "if” as used herein can be interpreted as "at the time of" or "when” or "in response to determining.”

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Theoretical Computer Science (AREA)
  • General Physics & Mathematics (AREA)
  • Databases & Information Systems (AREA)
  • Accounting & Taxation (AREA)
  • Physics & Mathematics (AREA)
  • Finance (AREA)
  • General Business, Economics & Management (AREA)
  • Strategic Management (AREA)
  • Computing Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Data Mining & Analysis (AREA)
  • General Engineering & Computer Science (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)

Abstract

Un ou plusieurs modes de réalisation de la présente description concernent un procédé et un appareil de gestion d'actifs basée sur une chaîne de blocs, et un dispositif électronique, appliqués à un dispositif de nœud dans la chaîne de blocs. Un type de transaction pris en charge par la chaîne de blocs comprend une première transaction de définition d'actifs destinée à définir un modèle d'actif ; un opérateur de la chaîne de blocs définit un type d'actif et un format d'actif correspondant au type d'actif dans la chaîne de blocs. Le procédé consiste : à recevoir une première transaction de définition d'actifs émise par un gestionnaire d'actifs ; la première transaction de définition d'actifs comprenant un modèle d'actif défini par le gestionnaire d'actifs et correspondant à un type d'actif cible ; le modèle d'actif comprenant des informations de création d'actif correspondant au type d'actif cible ; et en réponse à la première transaction de définition d'actifs, à stocker le modèle d'actif sur la chaîne de blocs de sorte qu'un créateur d'actif crée un actif de chaîne de blocs standardisé dans la chaîne de blocs sur la base des informations de création d'actif dans le modèle d'actif, et un format d'actif correspondant au type d'actif cible.
PCT/CN2022/076779 2021-03-30 2022-02-18 Gestion d'actifs basée sur une chaîne de blocs WO2022206209A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN202110343358.4A CN113095824B (zh) 2021-03-30 2021-03-30 基于区块链的资产管理方法、装置及电子设备
CN202110343358.4 2021-03-30

Publications (1)

Publication Number Publication Date
WO2022206209A1 true WO2022206209A1 (fr) 2022-10-06

Family

ID=76671336

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2022/076779 WO2022206209A1 (fr) 2021-03-30 2022-02-18 Gestion d'actifs basée sur une chaîne de blocs

Country Status (2)

Country Link
CN (1) CN113095824B (fr)
WO (1) WO2022206209A1 (fr)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113095824B (zh) * 2021-03-30 2022-05-31 支付宝(杭州)信息技术有限公司 基于区块链的资产管理方法、装置及电子设备

Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN106815764A (zh) * 2017-01-18 2017-06-09 中钞信用卡产业发展有限公司北京智能卡技术研究院 一种基于联盟链的数字资产的管理方法及系统
US20170206523A1 (en) * 2015-11-06 2017-07-20 Cable Television Laboratories, Inc Systems and methods for digital asset security ecosystems
CN108416675A (zh) * 2018-02-14 2018-08-17 阿里巴巴集团控股有限公司 资产管理方法及装置、电子设备
CN109242675A (zh) * 2018-07-27 2019-01-18 阿里巴巴集团控股有限公司 基于区块链的资产发布方法及装置、电子设备
CN110147987A (zh) * 2019-05-23 2019-08-20 北京亿生生网络科技有限公司 基于区块链的动态资产管理方法及装置
WO2019161023A1 (fr) * 2018-02-14 2019-08-22 Alibaba Group Holding Limited Procédé et appareil de gestion de ressources, et dispositif électronique
CN110766550A (zh) * 2019-09-05 2020-02-07 阿里巴巴集团控股有限公司 基于区块链的资产查询方法及装置、电子设备
CN112308553A (zh) * 2020-09-16 2021-02-02 电子科技大学 一种基于区块链的数字资产分类管理方法
CN113095824A (zh) * 2021-03-30 2021-07-09 支付宝(杭州)信息技术有限公司 基于区块链的资产管理方法、装置及电子设备

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108335206B (zh) * 2018-02-14 2020-12-22 创新先进技术有限公司 资产管理方法及装置、电子设备
CN108711104A (zh) * 2018-05-09 2018-10-26 北京磁云数字科技有限公司 基于区块链的实物资产信息流转方法、装置和设备
CN110020936B (zh) * 2019-01-03 2021-04-27 创新先进技术有限公司 基于区块链的资产管理方法及装置、电子设备
US10937096B2 (en) * 2019-07-15 2021-03-02 Advanced New Technologies Co., Ltd. Transaction processing in a service blockchain
CN110648123A (zh) * 2019-09-11 2020-01-03 杭州秘猿科技有限公司 一种数字资产的构建方法、装置及电子设备
CN110910000A (zh) * 2019-11-14 2020-03-24 腾讯科技（深圳）有限公司 一种区块链资产管理方法和装置
CN111340628A (zh) * 2020-03-13 2020-06-26 普洛斯科技(重庆)有限公司 基于区块链的资产信息管理方法和装置
CN111738738A (zh) * 2020-07-31 2020-10-02 支付宝(杭州)信息技术有限公司 基于区块链的生物资产对象管理方法及装置
CN112200568B (zh) * 2020-10-09 2022-05-13 支付宝(杭州)信息技术有限公司 基于区块链的账户创建方法、装置及电子设备

Patent Citations (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20170206523A1 (en) * 2015-11-06 2017-07-20 Cable Television Laboratories, Inc Systems and methods for digital asset security ecosystems
CN106815764A (zh) * 2017-01-18 2017-06-09 中钞信用卡产业发展有限公司北京智能卡技术研究院 一种基于联盟链的数字资产的管理方法及系统
CN108416675A (zh) * 2018-02-14 2018-08-17 阿里巴巴集团控股有限公司 资产管理方法及装置、电子设备
WO2019161023A1 (fr) * 2018-02-14 2019-08-22 Alibaba Group Holding Limited Procédé et appareil de gestion de ressources, et dispositif électronique
CN109242675A (zh) * 2018-07-27 2019-01-18 阿里巴巴集团控股有限公司 基于区块链的资产发布方法及装置、电子设备
CN110147987A (zh) * 2019-05-23 2019-08-20 北京亿生生网络科技有限公司 基于区块链的动态资产管理方法及装置
CN110766550A (zh) * 2019-09-05 2020-02-07 阿里巴巴集团控股有限公司 基于区块链的资产查询方法及装置、电子设备
CN112308553A (zh) * 2020-09-16 2021-02-02 电子科技大学 一种基于区块链的数字资产分类管理方法
CN113095824A (zh) * 2021-03-30 2021-07-09 支付宝(杭州)信息技术有限公司 基于区块链的资产管理方法、装置及电子设备

Also Published As

Publication number Publication date
CN113095824A (zh) 2021-07-09
CN113095824B (zh) 2022-05-31

Similar Documents

Publication Publication Date Title
US11921682B2 (en) Extracting data from a blockchain network
US11876910B2 (en) Systems, methods, and apparatuses for implementing a multi tenant blockchain platform for managing Einstein platform decisions using distributed ledger technology (DLT)
CN110471984B (zh) 基于区块链的业务处理方法及装置、电子设备
US11728992B2 (en) Cryptlet binding key graph
EP3622662B1 (fr) Contrat intelligent d'applet cryptographique
US11176246B2 (en) Enclave pool shared key
CN111213340B (zh) 选择用于密码功能的证明委托并使其安全
US11853291B2 (en) Privacy preserving architecture for permissioned blockchains
US20180330079A1 (en) Enclave pool management
CN110458631B (zh) 基于区块链的票据号码分配方法、装置及电子设备
US11397919B1 (en) Electronic agreement data management architecture with blockchain distributed ledger
WO2022077186A1 (fr) Procédé et appareil d'exécution d'un contrat intelligent dans une chaîne de blocs, et dispositif électronique
US20180330077A1 (en) Enclave pools
WO2022206210A1 (fr) Gestion d'actifs basée sur une chaîne de blocs
CN110738566A (zh) 一种基于区块链的资产筛选方法、装置及电子设备
CN112883109B (zh) 基于区块链的数字商品交易方法和装置
CN111327613A (zh) 分布式服务的权限控制方法、装置及计算机可读存储介质
US20220121466A1 (en) System and method for facilitating participation in a blockchain environment
WO2020112029A1 (fr) Système et procédé pour faciliter la participation dans un environnement de chaîne de blocs
Garcia Bringas et al. BlockChain platforms in financial services: current perspective
WO2022206209A1 (fr) Gestion d'actifs basée sur une chaîne de blocs
CN113762940A (zh) 基于区块链的资产管理方法、装置及电子设备
WO2023225744A1 (fr) Asik : interface modulaire pour une chaîne de blocs
CN112837043B (zh) 基于区块链的数据处理方法、装置及电子设备
US12015715B2 (en) Trusted aggregation with data privacy based on zero-knowledge-proofs

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 22778394

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 22778394

Country of ref document: EP

Kind code of ref document: A1