Asset transfer method and device based on blockchain, and electronic device

Abstract

A blockchain-based asset transfer method and device, and electronic equipment. The asset circulation system includes an asset issuer and multi-level asset holders; the first-level asset holder among the multi-level asset holders holds a first asset object created based on a first account payable between the asset issuer and the first-level asset holder; including: receiving a first transaction sent by the first-level asset holder; the first transaction includes a second account payable between the first-level asset holder and the second-level asset holder; in response to the first transaction, matching the first account payable with the second account payable, and when the amount of the second account payable is not greater than the amount of the first account payable, calling the asset splitting logic declared in the smart contract, splitting the second asset object matching the second account payable from the first asset object; transferring the split second asset object to the second-level asset holder for holding.

Description

Technical Field

[0001] One or more embodiments of this specification relate to the field of blockchain technology, and in particular, to a blockchain-based asset transfer method and device, and electronic device. Background Art

[0002] Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices jointly participate in "bookkeeping" and jointly maintain a complete distributed database. Blockchain technology has been widely used in many fields because of its decentralized, open and transparent characteristics, each computing device can participate in database records, and data can be quickly synchronized between computing devices. Summary of the invention

[0003] This specification proposes a blockchain-based asset transfer method, which is applied to an asset circulation system built on blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; wherein the first-level asset holder among the multi-level asset holders holds a first asset object created based on a first account payable between the asset issuer and the first-level asset holder; the method includes:

[0004] receiving a first transaction sent by the first-level asset holder; the first transaction comprising a second account payable between the first-level asset holder and a second-level asset holder among the multiple-level asset holders;

[0005] In response to the first transaction, the first account payable is matched with the second account payable, and when the amount of the second account payable is not greater than the amount of the first account payable, the asset splitting logic declared in the smart contract published on the blockchain is called to split the first asset object, and a second asset object matching the second account payable is split from the first asset object;

[0006] The split second asset object is transferred to the second-level asset holder for holding.

[0007] Optionally, the method further includes:

[0008] If the amount of the second accounts payable is greater than the amount of the first accounts payable, a notification message of asset transfer failure is returned to the first-level asset holder.

[0009] Optionally, the method further includes:

[0010] receiving a second transaction sent by the asset issuer; the second transaction includes the first accounts payable;

[0011] In response to the second transaction, calling the asset creation logic declared in the smart contract published on the blockchain, creating the first asset object based on the first accounts payable, and transferring the created first asset object to the first-level asset holder for holding; and

[0012] Generate an asset creation record corresponding to the first asset object, and publish the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the first accounts payable and the first asset object.

[0013] Optionally, before creating the first asset object based on the first accounts payable, the method further includes:

[0014] Determine whether the blockchain stores the first accounts payable created by the asset issuer for the first-level asset holder and confirmed by the first-level asset holder; if so, further create the first asset object based on the first accounts payable.

[0015] Optionally, creating the first asset object based on the first accounts payable includes:

[0016] Obtaining the amount of the first accounts payable;

[0017] Convert the amount of the first account payable into the amount of assets;

[0018] Create an asset object equal to the asset amount to obtain the first asset object.

[0019] Optionally, before splitting the first asset object, the method further includes:

[0020] Determine whether the blockchain stores the second accounts payable created by the first-level asset holder for the second-level asset holder and confirmed by the second-level asset holder; if so, further split the first asset object.

[0021] Optionally, splitting the first asset object to separate a second asset object matching the second accounts payable from the first asset object includes:

[0022] Obtaining the amount of the second accounts payable;

[0023] Convert the amount of the second accounts payable into the amount of assets;

[0024] An asset object having an amount equal to the asset is split from the first asset object to obtain the second asset object.

[0025] Optionally, also include:

[0026] After splitting the second asset object matching the second accounts payable from the first asset object, generating an asset creation record corresponding to the second asset object, and publishing the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the second asset object and the second accounts payable;

[0027] After the split second asset object is transferred to the second-level asset holder for holding, an asset transfer record corresponding to the first asset object is generated, and the generated asset transfer record is published to the blockchain for evidence storage; wherein the asset transfer record includes the first asset object, the second asset object split from the first asset object, and the correspondence between the second asset holder holding the second asset object.

[0028] Optionally, the asset circulation system is a supply chain finance system; the supply chain finance system includes a core enterprise as an asset issuer, multi-level suppliers as asset holders, and financial institutions; wherein the asset object is used to initiate financing loans to the financial institution.

[0029] Optionally, the method further includes:

[0030] receiving a third transaction sent by any target supplier among the multi-level suppliers; the third transaction includes a third asset object used to initiate a financing loan to the financial institution;

[0031] In response to the third transaction, the third asset object is transferred to the financial institution for holding, so that after the financial institution confirms the third accounts payable corresponding to the third asset object, it converts the asset amount of the third asset object into a capital amount, and issues a loan to the target supplier based on the converted capital amount.

[0032] This specification also proposes a blockchain-based asset transfer device, which is applied to an asset circulation system built on a blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; wherein a first-level asset holder among the multi-level asset holders holds a first asset object created based on a first account payable between the asset issuer and the first-level asset holder; the device includes:

[0033] A receiving module receives a first transaction sent by the first-level asset holder; the first transaction includes a second account payable between the first-level asset holder and a second-level asset holder among the multiple-level asset holders;

[0034] a splitting module, in response to the first transaction, matching the first account payable with the second account payable, and when the amount of the second account payable is not greater than the amount of the first account payable, calling the asset splitting logic declared in the smart contract published on the blockchain, splitting the first asset object, and splitting a second asset object matching the second account payable from the first asset object;

[0035] The transfer module transfers the split second asset object to the second-level asset holder for holding.

[0036] Optionally, the splitting module further:

[0037] If the amount of the second accounts payable is greater than the amount of the first accounts payable, a notification message of asset transfer failure is returned to the first-level asset holder.

[0038] Optionally, the receiving module further:

[0039] receiving a second transaction sent by the asset issuer; the second transaction includes the first accounts payable;

[0040] The device also includes:

[0041] a creation module, in response to the second transaction, calling the asset creation logic declared in the smart contract published on the blockchain, creating the first asset object based on the first accounts payable, and transferring the created first asset object to the first-level asset holder for holding; and

[0042] Generate an asset creation record corresponding to the first asset object, and publish the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the first accounts payable and the first asset object.

[0043] Optionally, the creation module further:

[0044] Before creating the first asset object based on the first accounts payable, determine whether the first accounts payable created by the asset issuer for the first-level asset holder and confirmed by the first-level asset holder is stored on the blockchain; if so, further create the first asset object based on the first accounts payable.

[0045] Optionally, the creation module:

[0046] Obtaining the amount of the first accounts payable;

[0047] Convert the amount of the first account payable into the amount of assets;

[0048] Create an asset object equal to the asset amount to obtain the first asset object.

[0049] Optionally, the splitting module further:

[0050] Before splitting the first asset object, determine whether the blockchain stores evidence of the second accounts payable created by the first-level asset holder for the second-level asset holder and confirmed by the second-level asset holder; if so, further split the first asset object.

[0051] Optionally, the splitting module:

[0052] Obtaining the amount of the second accounts payable;

[0053] Convert the amount of the second accounts payable into the amount of assets;

[0054] An asset object having an amount equal to the asset is split from the first asset object to obtain the second asset object.

[0055] Optionally, the device further comprises:

[0056] A generation module, after splitting the second asset object matching the second account payable from the first asset object, generates an asset creation record corresponding to the second asset object, and publishes the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the second asset object and the second account payable;

[0057] After the split second asset object is transferred to the second-level asset holder for holding, an asset transfer record corresponding to the first asset object is generated, and the generated asset transfer record is published to the blockchain for evidence storage; wherein the asset transfer record includes the first asset object, the second asset object split from the first asset object, and the correspondence between the second asset holder holding the second asset object.

[0058] Optionally, the asset circulation system is a supply chain finance system; the supply chain finance system includes a core enterprise as an asset issuer, multi-level suppliers as asset holders, and financial institutions; wherein the asset object is used to initiate financing loans to the financial institution.

[0059] Optionally, the receiving module further:

[0060] receiving a third transaction sent by any target supplier among the multi-level suppliers; the third transaction includes a third asset object used to initiate a financing loan to the financial institution;

[0061] The transfer module further:

[0062] In response to the third transaction, the third asset object is transferred to the financial institution for holding, so that after the financial institution confirms the third accounts payable corresponding to the third asset object, it converts the asset amount of the third asset object into a capital amount, and issues a loan to the target supplier based on the converted capital amount.

[0063] This specification also proposes an electronic device, which is applied to an asset circulation system built on a blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; wherein a first-level asset holder among the multi-level asset holders holds a first asset object created based on a first account payable between the asset issuer and the first-level asset holder; including:

[0064] processor;

[0065] memory for storing machine-executable instructions;

[0066] Wherein, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0067] receiving a first transaction sent by the first-level asset holder; the first transaction comprising a second account payable between the first-level asset holder and a second-level asset holder among the multiple-level asset holders;

[0068] In response to the first transaction, the first account payable is matched with the second account payable, and when the amount of the second account payable is not greater than the amount of the first account payable, the asset splitting logic declared in the smart contract published on the blockchain is called to split the first asset object, and a second asset object matching the second account payable is split from the first asset object;

[0069] The split second asset object is transferred to the second-level asset holder for holding. BRIEF DESCRIPTION OF THE DRAWINGS

[0070] Figure 1 It is a flowchart of a blockchain-based asset transfer method provided by an exemplary embodiment.

[0071] Figure 2 It is a schematic structural diagram of an electronic device provided by an exemplary embodiment.

[0072] Figure 3It is a block diagram of a blockchain-based asset transfer device provided by an exemplary embodiment. DETAILED DESCRIPTION

[0073] This specification aims to propose a technical solution in which, in an asset circulation system consisting of asset issuers and multi-level asset holders built on blockchain, accounts payable between asset issuers and first-level asset holders can be further split in the form of digital assets based on accounts payable between the first asset holder and lower-level asset holders, and then circulated to lower-level asset holders.

[0074] During implementation, the first-level asset holder among the above-mentioned multiple-level asset holders may hold a first asset object created based on a first account payable between the asset issuer and the first-level asset holder.

[0075] The first-level asset holder can construct a transaction based on the second accounts payable between the first-level asset holder and the second-level asset holder in the multi-level asset holders, and publish the transaction in the blockchain to call the smart contract deployed on the blockchain to complete the split transfer of the first asset object.

[0076] After receiving the transaction, the node device in the blockchain can respond to the transaction and match the first accounts payable with the above-mentioned second accounts payable; if after matching, it is confirmed that the amount of the above-mentioned second accounts payable is not greater than the amount of the above-mentioned first accounts payable, the asset splitting logic declared in the smart contract published on the blockchain can be called to split the first asset object, split the second asset object matching the above-mentioned second accounts payable from the first asset object, and transfer the split second asset object to the above-mentioned second-level asset holder for holding.

[0077] The second-level asset holder can perform the same operation as the first-level asset holder, and continue to build transactions based on the third accounts payable between the third-level asset holder and the multi-level asset holder, and publish the transaction in the blockchain to call the smart contract deployed on the blockchain to complete the split transfer of the second asset object. Similarly, the asset objects held can be continuously split and transferred to the lower-level asset holders.

[0078] Through the above technical solution, it is possible to realize that the first accounts payable between the asset issuer and the first-level asset holder can be split in the form of digital assets based on the accounts payable between the first asset holder and the lower-level asset holder, and then continue to circulate to the lower-level asset holder; thus, in the case that the first accounts payable between the asset issuer and the first-level asset holder have not yet been paid, the asset holders at all levels can use the second accounts payable between the upper-level asset holder and the asset issuer as digital assets, and continue to transfer them to the lower-level asset holders to replace the flow of funds, thereby minimizing the impact on the normal operation of the lower-level asset holders caused by the unpaid accounts payable between the upper-level asset holder and the asset issuer.

[0079] The present specification is described below through specific embodiments and in combination with specific application scenarios.

[0080] Please refer to Figure 1 , Figure 1 This is a blockchain-based asset transfer method provided in an embodiment of this specification, which is applied to an asset circulation system built on blockchain; the asset circulation system includes an asset issuer and multi-level asset holders, and performs the following steps:

[0081] Step 102, receiving a first transaction sent by the first-level asset holder; the first transaction includes a second account payable between the first-level asset holder and a second-level asset holder in the multi-level asset holders;

[0082] Step 104: In response to the first transaction, the first account payable is matched with the second account payable, and when the amount of the second account payable is not greater than the amount of the first account payable, the asset splitting logic declared in the smart contract published on the blockchain is called to split the first asset object, and a second asset object matching the second account payable is split from the first asset object;

[0083] Step 106: Transfer the split second asset object to the second-level asset holder for holding.

[0084] The blockchain described in this specification may specifically include any type of blockchain network that can cover asset objects among the supported objects.

[0085] For example, in a traditional blockchain, the supported objects usually only include account objects and contract objects (i.e., smart contracts). In this specification, the objects supported by the blockchain can be expanded, and an asset object can be further expanded based on the existing support of the blockchain such as account objects and contract objects.

[0086] It should be noted that the type of blockchain described in this specification is not particularly limited and may be a private chain, a public chain, a consortium chain, etc.

[0087] For example, in one scenario, the blockchain can be a consortium chain consisting of asset issuers and multi-level asset holders as consortium members. The operator of the consortium chain can build an asset circulation system consisting of asset issuers and multi-level asset holders based on the consortium chain, and use the accounts payable between asset issuers and multi-level asset holders as digital assets to circulate in the asset circulation system.

[0088] The above-mentioned smart contracts are also called contract objects in the blockchain based on the account model. Specifically, they can include smart contract programs published by the target members in the blockchain and recorded in the distributed database of the blockchain (i.e., the blockchain ledger) for managing the asset objects supported by the blockchain. Users who access the blockchain can create an asset object on the blockchain by calling the above-mentioned smart contracts, and complete the online management and transfer of the asset objects held on the blockchain.

[0089] The transaction described in this specification refers to a piece of data created by a user through a blockchain client and ultimately published to the distributed database of the blockchain.

[0090] Transactions in the blockchain are usually divided into narrow transactions and broad transactions. A transaction in the narrow sense refers to a value transfer published by a user to the blockchain. A transaction in the broad sense refers to a business data with business intent published by a user to the blockchain; for example, an operator can build a consortium chain based on actual business needs, and rely on the consortium chain to deploy some other types of online services that are not related to value transfer (for example, anti-counterfeiting verification business, rental business, vehicle dispatch business, insurance claims business, credit services, medical services, etc.), and in this type of consortium chain, a transaction can be a business message or business request with business intent published by a user in the consortium chain.

[0091] The above-mentioned asset objects may correspond to any type of real assets of the user in the real world; or other forms of objects that can be circulated and transferred as digital assets;

[0092] For example, the above-mentioned asset objects may specifically be real assets such as funds, real estate, stocks, etc., or they may be data such as loan contracts, bills, accounts payable, etc. that are suitable for being packaged into digital assets for circulation and transfer.

[0093] The following takes the above-mentioned asset circulation system as a supply chain financial system built on blockchain as an example to describe the technical solution of this specification in detail.

[0094] Among them, it should be emphasized that the supply chain financial system based on the above-mentioned asset circulation system built on the blockchain is only an example and is not used to limit the technical solution of this specification; obviously, in actual applications, technical personnel in this field can flexibly build the above-mentioned asset circulation system based on actual needs.

[0095] In this specification, the supply chain finance system may include a core enterprise as an asset issuer, multiple levels of suppliers as asset holders, and financial institutions (such as banks).

[0096] Among them, the core enterprise can create a first asset object for the first-tier supplier among the multi-tier suppliers based on the first account payable before the first account payable between the core enterprise and the first-tier supplier is paid, and the first-tier supplier shall hold the first asset object;

[0097] The above-mentioned first-tier supplier can split the above-mentioned first asset object based on the second accounts payable between it and the second-tier supplier in the above-mentioned multi-tier suppliers, split the second asset object matching the above-mentioned second accounts payable from the first asset object, and transfer the split second asset object to the above-mentioned second-tier supplier for holding.

[0098] The second-level supplier in the above-mentioned multi-level supplier can perform the same action as the first-level supplier, and continue to split the above-mentioned second asset object based on the third accounts payable between the supplier and the third-level supplier, and continue to transfer the split asset object to the lower-level supplier, and so on. Ultimately, the above-mentioned first asset object can be continuously transferred to the lower-level supplier based on the debt relationship between suppliers at all levels.

[0099] The above-mentioned financial institutions can provide financing services to suppliers at all levels. For any first-tier supplier, when the above-mentioned first accounts payable mature, based on the amount of the assets held, they can collect the corresponding amount of accounts payable funds from the above-mentioned core enterprise; or, before the above-mentioned first accounts payable mature, they can transfer the assets held to the above-mentioned financial institutions to initiate financing from the financial institutions.

[0100] The operators of the above-mentioned blockchains can expand the objects supported by the blockchain when building a blockchain network.

[0101] In traditional blockchains, the objects supported by blockchains usually only include account objects and contract objects (i.e. smart contracts). In this specification, the objects supported by blockchains can be expanded to further expand an asset object based on the existing account objects and contract objects.

[0102] That is, in this specification, the objects supported by the above blockchain can include three categories: account objects, contract objects, and asset objects. In this way, when core enterprises, multi-level suppliers, and financial institutions join the blockchain as blockchain member nodes, in addition to completing the creation of accounts and smart contracts on the blockchain, they can also create a digital asset on the blockchain.

[0103] In this specification, core enterprises can pre-develop smart contracts for managing asset objects (of course, they can also be developed by the operator of the blockchain or a third party), and declare executable logic for managing asset objects in the smart contract (for example, executable functions, codes, etc.).

[0104] Among them, in this specification, the executable logic declared in the above-mentioned smart contract may specifically include asset creation logic for creating asset objects, asset splitting logic for splitting asset objects, etc.

[0105] Of course, in actual applications, technicians in this field can also declare other forms of executable logic in addition to asset creation logic and asset splitting logic in the smart contract based on actual business needs, which is not specifically limited in this specification.

[0106] When the core enterprise completes the development of the smart contract, it can publish the developed smart contract in the form of a transaction in the blockchain; after receiving the transaction, the node devices in the blockchain can reach a consensus on the transaction based on the consensus algorithm supported by the blockchain, and after the consensus is passed, the smart contract can be included in the distributed database of the blockchain to complete the deployment of the smart contract.

[0107] The consensus processing process of the node devices in the blockchain on the received transactions will not be described in detail in this specification, and those skilled in the art can refer to the records in the relevant technology.

[0108] Once the above-mentioned smart contract is deployed in the blockchain, the core enterprises, multi-level suppliers and financial institutions in the above-mentioned supply chain financial system can call the executable logic declared in the smart contract by issuing transactions to the blockchain to complete operations such as the creation and splitting of asset objects.

[0109] In one embodiment shown, the core enterprise may create a first account payable for a first-tier supplier among the multi-tier suppliers based on the debt relationship between the core enterprise and the first-tier supplier, sign the created first account payable based on the private key held, and send the signed first account payable to the first-tier supplier, which will then perform the ownership confirmation process.

[0110] The so-called title confirmation refers to the confirmation of the collection rights of accounts receivable corresponding to accounts payable. In actual applications, the accounts payable can be signed by the private key held to confirm the collection rights of the accounts receivable corresponding to the accounts payable.

[0111] After the first-tier supplier receives the first accounts payable created by the core enterprise for the first-tier supplier, it can first verify the private key of the first accounts payable based on the public key corresponding to the private key held by the core enterprise. After the verification is passed, the first accounts payable can be further signed based on the private key held by the first-tier supplier to complete the title confirmation process for the first accounts payable. The first accounts payable after title confirmation can then be published in the form of a transaction in the blockchain for evidence storage.

[0112] Correspondingly, for the above-mentioned first-tier supplier, a second account payable can also be created for the second-tier supplier based on the debt relationship between the supplier and the second-tier supplier in the above-mentioned multi-tier supplier, and the created second account payable can be sent to the second-tier supplier for title confirmation. Then, the second-tier supplier will also publish the second account payable information after title confirmation in the blockchain for evidence storage, and so on.

[0113] In this way, any first-level supplier of the above-mentioned multi-level suppliers can create accounts payable for the subordinate suppliers based on the debt relationship between them and the subordinate suppliers, send the created accounts payable to the subordinate suppliers for title confirmation, and then store them on the blockchain.

[0114] In this specification, the core enterprise can construct a transaction for creating an asset object based on the first accounts payable before the first accounts payable are paid, carry the first accounts payable in the transaction, and publish the transaction on the blockchain to call the deployed smart contract to create a first asset object for the first-tier supplier.

[0115] In one example, the first accounts payable carried in the transaction may specifically be the data content of the first accounts payable, or may be only the identification information of the first accounts payable; for example, a hash value obtained by performing a hash calculation on the data content of the first accounts payable.

[0116] After receiving the transaction sent by the core enterprise, the node device in the blockchain can respond to the transaction, perform consensus processing on the transaction, and after the consensus is passed, call the asset creation logic declared in the above-mentioned smart contract deployed in the blockchain to create the first asset object based on the above-mentioned first accounts payable.

[0117] Among them, in one embodiment shown, before the node device calls the asset creation logic declared in the above-mentioned smart contract deployed in the blockchain and creates the first asset object based on the above-mentioned first accounts payable, it can also further search the data stored in the blockchain to confirm whether the blockchain currently has evidence of the first accounts payable created by the core enterprise for the first-level supplier and confirmed by the first-level supplier; if so, it proves that the right to collect the above-mentioned first accounts payable has been transferred to the above-mentioned first-level supplier, and at this time, the above-mentioned first asset object is created based on the above-mentioned first accounts payable.

[0118] In this way, before creating the first asset object for the first-tier supplier based on the first accounts payable, it is possible to check whether the first accounts payable is a real accounts payable that has been confirmed by the first-tier supplier, thereby avoiding losses caused by creating asset objects for the first-tier supplier based on false accounts payable or accounts payable for which the first-tier supplier does not have the right to collect payment.

[0119] In one embodiment shown, when the node device calls the asset creation logic declared in the above-mentioned smart contract deployed in the blockchain and creates the first asset object based on the above-mentioned first account payable, it can specifically obtain the amount of the first account payable, convert the amount of the first account payable into the asset amount according to the preset conversion rule, and then create an asset object equal to the converted asset amount to obtain the above-mentioned first asset object. The above-mentioned conversion rule is not particularly limited in this specification; for example, it can be equal amount conversion or non-equal amount conversion.

[0120] After the node device creates the first asset object based on the first accounts payable by calling the asset creation logic declared in the above smart contract, the created first asset object can be transferred to the above first-tier supplier (that is, the creditor of the first accounts payable) for holding.

[0121] For example, during implementation, the asset object created by the smart contract will usually have unique address information; in this case, transferring the created first asset object to the first-tier supplier is the process of adding the address information of the first asset object to the corresponding account object of the first-tier supplier on the blockchain.

[0122] Furthermore, after completing the creation of the above-mentioned first asset object, or transferring the above-mentioned first asset object to the above-mentioned first-level asset holder for holding, the node device can also generate an asset creation record corresponding to the above-mentioned first asset object, and publish the generated asset creation record to the blockchain for evidence storage.

[0123] Among them, the asset creation record corresponding to the above-mentioned first asset object includes the corresponding relationship between the above-mentioned first accounts payable and the above-mentioned first asset object.

[0124] In this specification, the first-tier supplier can also construct a transaction for transferring asset objects based on the second accounts payable between the first-tier supplier and the second-tier supplier in the multi-tier suppliers before the first accounts payable are paid, carry the second accounts payable in the transaction, and publish the transaction on the blockchain to call the deployed smart contract, split the first asset object held, and transfer the second asset object split from the first asset object that matches the second accounts payable to the second-tier supplier for holding, so as to complete the second accounts payable between the second-tier supplier and the second-tier supplier as a data asset and circulate it to the lower-level supplier to replace the flow of funds.

[0125] After receiving the transaction sent by the core enterprise, the node device in the blockchain can respond to the transaction, conduct consensus processing on the transaction, and match the first account payable with the second account payable after the consensus is passed; if it is confirmed through matching that the amount of the second account payable is not greater than the amount of the first account payable, the asset splitting logic declared in the smart contract deployed in the blockchain can be called to split the first asset object held by the first-tier supplier, and split the second asset object matching the second account payable from the first asset object;

[0126] Of course, if it is confirmed through matching that the amount of the second account payable is greater than the amount of the first account payable, since the debt scale between the first-tier supplier and the second-tier supplier is greater than the debt scale between the core enterprise and the first-tier supplier, the first asset object held by the first-tier supplier cannot be split at this time, and a notification message of asset transfer failure can be returned to the first-tier asset holder;

[0127] For example, in actual applications, the notification message may be a text prompt such as "Insufficient balance in the asset pool, asset transfer failed".

[0128] Among them, in one embodiment shown, before calling the asset splitting logic declared in the above-mentioned smart contract deployed in the blockchain and splitting the first asset object held by the above-mentioned first-level supplier, the node device can also further search the data stored in the blockchain to confirm whether the blockchain currently stores the second accounts payable created by the first-level supplier for the second-level supplier and confirmed by the second-level supplier; if so, it proves that the collection rights corresponding to the corresponding accounts payable should be transferred to the second-level supplier, and at this time the first asset object held by the above-mentioned first-level supplier is split.

[0129] In one embodiment shown, when the node device calls the asset splitting logic declared in the above-mentioned smart contract deployed in the blockchain and splits the first asset object held by the above-mentioned first-tier supplier, it can specifically obtain the amount of the above-mentioned second accounts payable, convert the amount of the above-mentioned second accounts payable into the asset amount, and then split the asset object equal to the asset amount from the above-mentioned first asset object to obtain the above-mentioned second asset object.

[0130] After the node device splits the second asset object matching the second accounts payable from the first asset object by calling the asset splitting logic declared in the smart contract, the split second asset object can be transferred to the second-tier supplier (that is, the creditor of the second accounts payable) for holding; for example, the address information of the split second asset object can still be added to the corresponding account object of the second-tier supplier on the blockchain.

[0131] It should be noted that if it is confirmed through matching that the amount of the second accounts payable is exactly the same as the amount of the first accounts payable, the asset amounts of the first asset object and the second asset object are also exactly the same; therefore, the above-described process of splitting out the second asset object matching the second accounts payable from the first asset object and transferring the second asset object to the second-tier supplier for holding is actually equivalent to the process of transferring the first asset object as a whole to the second-tier supplier.

[0132] That is to say, the debt scale of accounts payable between the core enterprise and the first-tier suppliers is exactly the same as the debt scale of accounts payable between the first-tier suppliers and the second-tier suppliers. The first-tier suppliers can transfer the collection rights of the above-mentioned first accounts payable to the second-tier suppliers as a whole, and the subsequent first-tier suppliers will no longer have the collection rights of the above-mentioned first accounts payable.

[0133] Furthermore, after splitting the second asset object matching the second accounts payable from the first asset object, the node device may also generate an asset creation record corresponding to the second asset object, and publish the generated asset creation record to the blockchain for evidence storage;

[0134] That is, splitting the second asset object matching the second accounts payable from the first asset object is equivalent to the process in which the first-tier supplier creates a second asset object for the second-tier supplier based on the second accounts payable between the first-tier supplier and the second-tier supplier.

[0135] The asset creation record corresponding to the second asset object includes a corresponding relationship between the second asset object and the second accounts payable.

[0136] In addition, after transferring the split second asset object to the second-level asset holder for holding, the node device may also generate an asset transfer record corresponding to the first asset object, and publish the generated asset transfer record to the blockchain for evidence storage;

[0137] That is, the first asset object is split, and the split second asset object is further transferred to the lower-level supplier, which is equivalent to transferring part of the asset objects in the first asset object to the lower-level supplier to complete the asset transfer.

[0138] The asset transfer record includes the correspondence between the first asset object, the second asset object split from the first asset object, and the second-tier supplier holding the second asset object.

[0139] Correspondingly, for the second-level supplier in the above-mentioned multi-level suppliers, the same actions as the first-level supplier can also be performed. If there is still a debt relationship based on accounts payable between the second-level supplier and the third-level supplier, the second asset object can be split in the same way based on the third accounts payable between the second-level supplier and the third-level supplier, and the split asset object can be transferred to the lower-level supplier. Ultimately, the first asset object can be continuously transferred to the lower-level supplier based on the debt relationship between suppliers at all levels.

[0140] Finally, the first asset object created based on the first accounts payable will be continuously split and transferred through the splitting process described above, and will be distributed to suppliers at all levels for holding. When the first accounts payable corresponding to the first asset object is about to expire, the core enterprise can initiate a clearing process for the first asset object, and by querying the asset transfer records generated by suppliers at all levels stored on the blockchain, clarify the distribution of the first asset object among suppliers at all levels, determine the suppliers at all levels that hold the asset objects split from the first asset object, and then complete the payment of accounts payable based on the actual amount of asset objects split from the first asset object held by suppliers at all levels.

[0141] In other words, since the first accounts payable is actually split into several parts in the form of an asset object and held by suppliers at all levels; suppliers at all levels have obtained the right to collect part of the above-mentioned first accounts payable; therefore, when the core enterprise redeems the above-mentioned first accounts payable, it can redeem them separately based on the actual shares of the above-mentioned first accounts payable held by suppliers at all levels, and pay the accounts payable to suppliers at all levels.

[0142] In this specification, for any first-level target supplier among the multi-level suppliers in the above-mentioned supply chain financial system, in addition to collecting the corresponding amount of accounts payable funds from the above-mentioned core enterprise based on the amount of the asset objects held when the above-mentioned first accounts payable expires, since the asset objects held by suppliers at all levels are anchored to the real accounts payable, suppliers at all levels can also transfer the asset objects held and the accounts payable corresponding to the asset objects held as collateral to banks and other financial institutions to initiate financing loans.

[0143] In this case, the target supplier can construct a transaction for financing loans based on the third asset object it holds (which is also an asset object split from the first asset object), publish the transaction on the blockchain, and transfer the third asset object it holds to the financial institution.

[0144] After receiving the transaction sent by the above-mentioned target supplier, the node device in the blockchain can respond to the transaction, conduct consensus processing on the transaction, and execute the transaction after the consensus is passed, and transfer the above-mentioned third asset object to the financial institution for holding; for example, the address information of the above-mentioned third asset object can be added to the corresponding account object of the above-mentioned financial institution on the blockchain.

[0145] Subsequently, when the first accounts payable mature, the financial institution may collect a corresponding amount of accounts payable funds from the core enterprise based on the amount of the asset objects held.

[0146] When the financial institution receives the third asset object transferred by the target supplier, it can further confirm whether the third accounts payable corresponding to the third asset object has been transferred to the financial institution and has been confirmed by the financial institution;

[0147] For example, during implementation, the above-mentioned transaction may also include the asset ID of the above-mentioned third asset object. The financial institution may query the asset creation record of the third asset object stored on the blockchain based on the asset ID of the third asset object to obtain the third accounts payable corresponding to the third asset object, and then confirm whether the above-mentioned target supplier has transferred the third accounts payable to the financial institution and has confirmed the ownership of the third accounts payable.

[0148] If the financial institution confirms that the above-mentioned target supplier has transferred the third accounts payable to the financial institution, and the financial institution has also confirmed the ownership of the third accounts payable, the financial institution can convert the asset amount of the above-mentioned third asset object into a capital amount, and issue a loan to the above-mentioned target supplier based on the converted capital amount.

[0149] Among them, it should be noted that after the financial institution issues loans to the above-mentioned target suppliers, it can also generate financing and loan records corresponding to the above-mentioned target suppliers, and publish the generated financing and loan records to the blockchain for evidence storage.

[0150] In the above technical scheme, the first accounts payable between the asset issuer and the first-level asset holder can be realized in the form of digital assets, and after further splitting the accounts payable between the first asset holder and the lower-level asset holder, it can continue to circulate to the lower-level asset holder; thus, in the case that the first accounts payable between the asset issuer and the first-level asset holder have not yet been paid, the asset holders at all levels can use the second accounts payable between the upper-level asset holder and the asset issuer as digital assets, and continue to transfer them to the lower-level asset holders to replace the flow of funds, thereby minimizing the impact on the normal operation of the lower-level asset holders caused by the unpaid accounts payable between the upper-level asset holder and the asset issuer.

[0151] For example, taking the asset issuer as the core enterprise, the first-level asset holder of the multi-level asset holders as the first-level supplier with which the core enterprise has a debt relationship, and the second-level asset holder as the second-level supplier with which the first-level supplier has a debt relationship, assuming that the core enterprise needs to complete the purchase from the first-level supplier, the core enterprise can create an asset object on the blockchain based on the first accounts payable between the core enterprise and the first-level supplier, and transfer the created asset object to the first-level supplier to complete the purchase (that is, if the purchase amount has not yet been paid, the purchase amount is paid in the form of the created digital assets).

[0152] Correspondingly, assuming that the first-tier supplier also needs to complete the purchase of goods from the second-tier supplier, the first-tier supplier can continue to split the digital assets based on the second accounts payable between the first-tier supplier and the second-tier supplier, and transfer the split digital assets to the second-tier supplier to complete the purchase.

[0153] Therefore, for the lower-level suppliers at all levels, on the premise that the core enterprise has not yet redeemed the above-mentioned first accounts payable, they can continue to transfer the accounts payable between them and the upper-level asset holders as digital assets to the lower-level asset holders to replace the flow of funds to complete normal procurement without affecting their own normal business operations.

[0154] Corresponding to the above method embodiments, this specification also provides an embodiment of an asset transfer device based on blockchain. The device can be applied to a distributed exchange built on blockchain; the distributed exchange includes several distributed trading centers. The embodiment of the asset transfer device based on blockchain in this specification can be applied to electronic devices. The device embodiment can be implemented through software, or through hardware or a combination of software and hardware. Taking software implementation as an example, as a device in a logical sense, it is formed by the processor of the electronic device in which it is located reading the corresponding computer program instructions in the non-volatile memory into the memory for execution. From a hardware perspective, if Figure 2 The figure is a hardware structure diagram of the electronic device where the blockchain-based asset transfer device of this specification is located, except Figure 2 In addition to the processor, memory, network interface, and non-volatile memory shown, the electronic device in which the device in the embodiment is located may also include other hardware according to the actual function of the electronic device, which will not be described in detail.

[0155] Figure 3 It is a block diagram of an asset transfer device based on blockchain shown in an exemplary embodiment of this specification.

[0156] Please refer to Figure 3 The asset transfer device 30 based on blockchain can be applied in the aforementioned Figure 2 In the electronic device shown, the electronic device can be applied to an asset circulation system built on a blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; wherein the first-level asset holder in the multi-level asset holder holds a first asset object created based on a first account payable between the asset issuer and the first-level asset holder; the asset transfer device 30 based on the blockchain includes:

[0157] A receiving module 301 receives a first transaction sent by the first-level asset holder; the first transaction includes a second account payable between the first-level asset holder and a second-level asset holder in the multi-level asset holders;

[0158] A splitting module 302, in response to the first transaction, matches the first account payable with the second account payable, and when the amount of the second account payable is not greater than the amount of the first account payable, calls the asset splitting logic declared in the smart contract published on the blockchain, splits the first asset object, and splits the second asset object matching the second account payable from the first asset object;

[0159] The transfer module 303 transfers the split second asset object to the second-level asset holder for holding.

[0160] In this specification, the splitting module 302 further:

[0161] If the amount of the second accounts payable is greater than the amount of the first accounts payable, a notification message of asset transfer failure is returned to the first-level asset holder.

[0162] In this specification, the receiving module 301 further:

[0163] receiving a second transaction sent by the asset issuer; the second transaction includes the first accounts payable;

[0164] The device 30 further comprises:

[0165] Create a module ( Figure 3 (not shown), in response to the second transaction, calling the asset creation logic declared in the smart contract published on the blockchain, creating the first asset object based on the first accounts payable, and transferring the created first asset object to the first-level asset holder for holding; and

[0166] Generate an asset creation record corresponding to the first asset object, and publish the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the first accounts payable and the first asset object.

[0167] In this specification, the creation module further:

[0168] Before creating the first asset object based on the first accounts payable, determine whether the first accounts payable created by the asset issuer for the first-level asset holder and confirmed by the first-level asset holder is stored on the blockchain; if so, further create the first asset object based on the first accounts payable.

[0169] In this specification, the creation module:

[0170] Obtaining the amount of the first accounts payable;

[0171] Convert the amount of the first account payable into the amount of assets;

[0172] Create an asset object equal to the asset amount to obtain the first asset object.

[0173] In this specification, the splitting module 302 further:

[0174] Before splitting the first asset object, determine whether the blockchain stores evidence of the second accounts payable created by the first-level asset holder for the second-level asset holder and confirmed by the second-level asset holder; if so, further split the first asset object.

[0175] In this specification, the splitting module 302:

[0176] Obtaining the amount of the second accounts payable;

[0177] Convert the amount of the second accounts payable into the amount of assets;

[0178] An asset object having an amount equal to the asset is split from the first asset object to obtain the second asset object.

[0179] In this specification, the device 30 also includes:

[0180] Generate module ( Figure 3 (not shown), after splitting the second asset object matching the second account payable from the first asset object, generating an asset creation record corresponding to the second asset object, and publishing the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the second asset object and the second account payable;

[0181] After the split second asset object is transferred to the second-level asset holder for holding, an asset transfer record corresponding to the first asset object is generated, and the generated asset transfer record is published to the blockchain for evidence storage; wherein the asset transfer record includes the first asset object, the second asset object split from the first asset object, and the correspondence between the second asset holder holding the second asset object.

[0182] In this specification, the asset circulation system is a supply chain finance system; the supply chain finance system includes a core enterprise as an asset issuer, multi-level suppliers as asset holders, and financial institutions; wherein the asset object is used to initiate financing loans to the financial institution.

[0183] In this specification, the receiving module 301 further:

[0184] receiving a third transaction sent by any target supplier among the multi-level suppliers; the third transaction includes a third asset object used to initiate a financing loan to the financial institution;

[0185] The transfer module 303 further:

[0186] In response to the third transaction, the third asset object is transferred to the financial institution for holding, so that after the financial institution confirms the third accounts payable corresponding to the third asset object, it converts the asset amount of the third asset object into a capital amount, and issues a loan to the target supplier based on the converted capital amount.

[0187] In this specification, transferring an asset object to any level-one asset holder among the multiple levels of asset holders, or to the financial institution for holding, includes:

[0188] The address information of the asset object is added to the account object corresponding to any first-level asset holder among the multiple levels of asset holders, or the financial institution.

[0189] The implementation process of the functions and effects of each module in the above-mentioned device is specifically described in the implementation process of the corresponding steps in the above-mentioned method, which will not be repeated here.

[0190] For the device embodiment, since it basically corresponds to the method embodiment, the relevant parts can refer to the partial description of the method embodiment. The device embodiment described above is only schematic, wherein the modules described as separate components may or may not be physically separated, and the components displayed as modules may or may not be physical modules, that is, they may be located in one place, or they may be distributed on multiple network modules. Some or all of the modules may be selected according to actual needs to achieve the purpose of the scheme of this specification. A person of ordinary skill in the art can understand and implement it without paying creative labor.

[0191] The systems, devices, modules or modules described in the above embodiments may be implemented by computer chips or entities, or by products with certain functions. A typical implementation device is a computer, which may be in the form of a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email transceiver, a game console, a tablet computer, a wearable device, or a combination of any of these devices.

[0192] Corresponding to the above method embodiment, this specification also provides an embodiment of an electronic device. The electronic device can be applied to an asset circulation system built on blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; wherein the first-level asset holder among the multi-level asset holders holds a first asset object created based on the first accounts payable between the asset issuer and the first-level asset holder; the electronic device includes: a processor and a memory for storing machine executable instructions; wherein the processor and the memory are usually interconnected through an internal bus. In other possible implementations, the device may also include an external interface to enable communication with other devices or components.

[0193] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0194] receiving a first transaction sent by the first-level asset holder; the first transaction comprising a second account payable between the first-level asset holder and a second-level asset holder among the multiple-level asset holders;

[0195] In response to the first transaction, the first account payable is matched with the second account payable, and when the amount of the second account payable is not greater than the amount of the first account payable, the asset splitting logic declared in the smart contract published on the blockchain is called to split the first asset object, and a second asset object matching the second account payable is split from the first asset object;

[0196] The split second asset object is transferred to the second-level asset holder for holding.

[0197] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0198] If the amount of the second accounts payable is greater than the amount of the first accounts payable, a notification message of asset transfer failure is returned to the first-level asset holder.

[0199] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0200] receiving a second transaction sent by the asset issuer; the second transaction includes the first accounts payable;

[0201] In response to the second transaction, calling the asset creation logic declared in the smart contract published on the blockchain, creating the first asset object based on the first accounts payable, and transferring the created first asset object to the first-level asset holder for holding; and

[0202] Generate an asset creation record corresponding to the first asset object, and publish the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the first accounts payable and the first asset object.

[0203] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0204] Before creating the first asset object based on the first accounts payable, determine whether the first accounts payable created by the asset issuer for the first-level asset holder and confirmed by the first-level asset holder is stored on the blockchain; if so, further create the first asset object based on the first accounts payable.

[0205] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0206] Obtaining the amount of the first accounts payable;

[0207] Convert the amount of the first account payable into the amount of assets;

[0208] Create an asset object equal to the asset amount to obtain the first asset object.

[0209] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0210] Before splitting the first asset object, determine whether the blockchain stores evidence of the second accounts payable created by the first-level asset holder for the second-level asset holder and confirmed by the second-level asset holder; if so, further split the first asset object.

[0211] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0212] Obtaining the amount of the second accounts payable;

[0213] Convert the amount of the second accounts payable into the amount of assets;

[0214] An asset object having an amount equal to the asset is split from the first asset object to obtain the second asset object.

[0215] In this embodiment, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to:

[0216] After splitting the second asset object matching the second accounts payable from the first asset object, generating an asset creation record corresponding to the second asset object, and publishing the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the second asset object and the second accounts payable;

[0217] After the split second asset object is transferred to the second-level asset holder for holding, an asset transfer record corresponding to the first asset object is generated, and the generated asset transfer record is published to the blockchain for evidence storage; wherein the asset transfer record includes the first asset object, the second asset object split from the first asset object, and the correspondence between the second asset holder holding the second asset object.

[0218] In this embodiment, the asset circulation system is a supply chain finance system; the supply chain finance system includes a core enterprise as an asset issuer, multi-level suppliers as asset holders, and a financial institution; wherein the asset object is used to initiate a financing loan to the financial institution;

[0219] By reading and executing the machine-executable instructions stored in the memory corresponding to the control logic of blockchain-based asset transfer, the processor is caused to:

[0220] receiving a third transaction sent by any target supplier among the multi-level suppliers; the third transaction includes a third asset object used to initiate a financing loan to the financial institution;

[0221] In response to the third transaction, the third asset object is transferred to the financial institution for holding, so that after the financial institution confirms the third accounts payable corresponding to the third asset object, it converts the asset amount of the third asset object into a capital amount, and issues a loan to the target supplier based on the converted capital amount.

[0222] Those skilled in the art will readily appreciate other embodiments of the specification after considering the specification and practicing the invention disclosed herein. The specification is intended to cover any variations, uses, or adaptations of the specification that follow the general principles of the specification and include common knowledge or customary techniques in the art that are not disclosed in the specification. The specification and examples are to be considered exemplary only, and the true scope and spirit of the specification are indicated by the following claims.

[0223] It should be understood that the present description is not limited to the precise structures that have been described above and shown in the drawings, and that various modifications and changes may be made without departing from the scope thereof. The scope of the present description is limited only by the appended claims.

[0224] The above description is only a preferred embodiment of this specification and is not intended to limit this specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of this specification should be included in the scope of protection of this specification.

Claims

1. A blockchain-based asset transfer method, applied to an asset circulation system built on blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; the i-1th level asset holder among the multi-level asset holders holds the i-1th asset object created based on the i-1th account payable between the i-2th level asset holder and the i-1th level asset holder; wherein, i=2,…,N; N is not greater than the number of asset holders; When i=2, the i-2th level asset holder is the asset issuer; the method includes: Receiving an asset transfer transaction sent by the i-1th level asset holder; the asset transfer transaction includes the amount of the i-th account payable between the i-1th level asset holder and the i-th level asset holder; In response to the asset transfer transaction, determine whether the blockchain has stored evidence of the i-th account payable created by the i-1th level asset holder for the i-th level asset holder and confirmed by the i-th level asset holder; if so, if the amount of the i-th account payable is not greater than the amount of the i-1th account payable, call the asset splitting logic declared in the smart contract published on the blockchain to split the i-th asset object matching the i-th account payable from the i-1th asset object; The split i-th asset object is transferred to the i-th level asset holder for holding.

2. The method according to claim 1, further comprising: If the amount of the i-th account payable is greater than the amount of the i-1-th account payable, a notification message of asset transfer failure is returned to the i-1-th level asset holder.

3. The method according to claim 1, further comprising: Receiving an asset creation transaction sent by the asset issuer; The asset creation transaction includes a first account payable; In response to the asset creation transaction, the asset creation logic declared in the smart contract published on the blockchain is called to create a first asset object matching the first account payable, and the created first asset object is transferred to the first-level asset holder for holding.

4. The method of claim 3, further comprising: Generate an asset creation record corresponding to the first asset object, and publish the generated asset creation record to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the first accounts payable and the first asset object.

5. The method according to claim 3, before creating the first asset object based on the first account payable, further comprising: Determine whether the blockchain stores the first accounts payable created by the asset issuer for the first-level asset holder and confirmed by the first-level asset holder; if so, further create the first asset object based on the first accounts payable.

6. The method according to claim 3, creating the first asset object based on the first account payable, comprising: Obtaining the amount of the first accounts payable; Convert the amount of the first account payable into the amount of assets; Create an asset object equal to the asset amount to obtain the first asset object.

7. The method according to claim 1, performing splitting processing on the i-1th asset object to split the i-th asset object matching the i-th account payable from the i-1th asset object, comprising: Get the amount of the i-th account payable; Convert the amount of the i-th account payable into the amount of assets; An asset object having an amount equal to the asset is split from the (i-1)th asset object to obtain the (i)th asset object.

8. The method according to claim 1, further comprising: After splitting the i-th asset object matching the i-th accounts payable from the i-1-th asset object, an asset creation record corresponding to the i-th asset object is generated, and the generated asset creation record is published to the blockchain for evidence storage; wherein the asset creation record includes the corresponding relationship between the i-th asset object and the i-th accounts payable.

9. The method of claim 8, further comprising: After the split i-th asset object is transferred to the i-th level asset holder for holding, an asset transfer record corresponding to the i-1th asset object is generated, and the generated asset transfer record is published to the blockchain for evidence storage; wherein the asset transfer record includes the correspondence between the i-1th asset object, the i-th asset object split from the i-1th asset object, and the i-th asset holder holding the i-th asset object.

10. According to the method of claim 1, the asset circulation system is a supply chain finance system; the supply chain finance system includes a core enterprise as an asset issuer, multi-level suppliers as asset holders, and financial institutions; wherein, The asset object is used to initiate a financing loan from the financial institution.

11. The method according to claim 10, further comprising: Receiving a loan transaction sent by any target supplier among the multi-level suppliers; the loan transaction specifies an asset object used to initiate a financing loan to the financial institution; In response to the loan transaction, the asset object specified in the loan transaction is transferred to the financial institution for holding, so that after the financial institution confirms the accounts payable corresponding to the asset object, it converts the asset amount of the asset object into a capital amount, and issues a loan to the target supplier based on the converted capital amount.

12. An asset transfer device based on blockchain, applied to an asset circulation system built on blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; the i-1th level asset holder among the multi-level asset holders holds the i-1th asset object created based on the i-1th account payable between the i-2th level asset holder and the i-1th level asset holder; wherein, i=2,…,N; N is not greater than the number of asset holders; When i=2, the i-2th level asset holder is the asset issuer; the device includes: A receiving module receives an asset transfer transaction sent by an i-1th level asset holder; the asset transfer transaction includes the amount of the i-th account payable between the i-1th level asset holder and the i-th level asset holder; a splitting module, in response to the asset transfer transaction, determining whether the blockchain has stored evidence of the i-th account payable created by the i-1th level asset holder for the i-th level asset holder and after the i-th level asset holder has confirmed the ownership; if so, in the case where the amount of the i-th account payable is not greater than the amount of the i-1th account payable, calling the asset splitting logic declared in the smart contract published on the blockchain to split the i-th asset object matching the i-th account payable from the i-1th asset object; The transfer module transfers the split i-th asset object to the i-th level asset holder for holding.

13. An electronic device, applied to an asset circulation system built on blockchain; the asset circulation system includes an asset issuer and multi-level asset holders; the i-1th level asset holder among the multi-level asset holders holds the i-1th asset object created based on the i-1th account payable between the i-2th level asset holder and the i-1th level asset holder; wherein, i=2,…,N; N is not greater than the number of asset holders; When i=2, the i-2th level asset holder is the asset issuer; the electronic device includes: processor; memory for storing machine-executable instructions; Wherein, by reading and executing the machine executable instructions corresponding to the control logic of blockchain-based asset transfer stored in the memory, the processor is prompted to: Receiving an asset transfer transaction sent by the i-1th level asset holder; the asset transfer transaction includes the amount of the i-th account payable between the i-1th level asset holder and the i-th level asset holder; In response to the asset transfer transaction, determine whether the blockchain has stored evidence of the i-th account payable created by the i-1th level asset holder for the i-th level asset holder and confirmed by the i-th level asset holder; if so, if the amount of the i-th account payable is not greater than the amount of the i-1th account payable, call the asset splitting logic declared in the smart contract published on the blockchain to split the i-th asset object matching the i-th account payable from the i-1th asset object; The split i-th asset object is transferred to the i-th level asset holder for holding.

Images