A method, device and electronic device for processing default assets based on blockchain

Abstract

This specification proposes a method, device and electronic device for handling defaulted assets based on blockchain, including: receiving a target transaction sent by an asset management platform during the life of a securitized asset; the target transaction includes a target underlying asset that defaults in an underlying asset pool during the life of the securitized asset; in response to the target transaction, calling the asset default handling logic in the smart contract deployed on the blockchain, and publishing the default refund information of the target underlying asset to the blockchain, so that after the custodial bank system monitors the default refund information, based on the default refund information, the target underlying asset is refunded from the investment account of the original equity holder of the target underlying asset to the equity holder of the target underlying asset; when the fund refund record corresponding to the target underlying asset published to the blockchain by the custodial bank system is obtained, the equity holder of the target underlying asset is updated to the original equity holder.

Description

Technical Field

[0001] One or more embodiments of this specification relate to the field of blockchain technology, and in particular, to a method, device, and electronic device for processing defaulted assets based on blockchain. 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 method for handling defaulted assets based on blockchain, which is applied to a node device of the blockchain and includes:

[0004] Receiving a target transaction sent by an asset management platform during the life of a securitized asset; wherein the securitized asset is an asset issued on the blockchain with an underlying asset pool as value support; and the target transaction includes a target underlying asset that has defaulted in the underlying asset pool during the life of the securitized asset;

[0005] In response to the target transaction, the asset default processing logic in the smart contract deployed on the blockchain is called to publish the default refund information of the target underlying asset to the blockchain, so that after the custodian bank system monitors the default refund information, the target underlying asset is refunded from the investment account of the original equity holder of the target underlying asset to the equity holder of the target underlying asset based on the default refund information;

[0006] When the fund refund record corresponding to the target underlying asset published to the blockchain by the custodial bank system is obtained, the beneficiary of the target underlying asset is updated to the original beneficiary.

[0007] Optionally, publishing the default refund information of the target underlying asset to the blockchain for evidence storage includes:

[0008] Generate a confirmation event for the target underlying asset to be confirmed as a default by the equity holder and the original equity holder of the target underlying asset, so that when the client monitors the confirmation event, it prompts the equity holder and the original equity holder of the target underlying asset to confirm the default of the target underlying asset;

[0009] When the default confirmation information of the target underlying asset by the equity holder and the original equity holder of the target underlying asset is monitored and published to the blockchain by the client, the default refund information of the target underlying asset is published to the blockchain for evidence storage.

[0010] Optionally, the blockchain is connected to the judicial chain through a cross-chain relay; the method further includes:

[0011] After the equity holder of the target underlying asset is updated to the original equity holder, the contract agreement related to the target underlying asset is published to the judicial chain through the cross-chain relay for evidence storage.

[0012] Optionally, the cross-chain relay is an oracle oracle.

[0013] Optionally, the investment account is a custodial account opened by the original beneficiary in a custodial bank; the securitized assets are bonds or funds; and the underlying assets are underlying debt assets.

[0014] This specification proposes a default asset processing device based on blockchain, which is applied to a node device of the blockchain, and includes:

[0015] A receiving module receives a target transaction sent by an asset management platform during the life of a securitized asset; wherein the securitized asset is an asset issued on the blockchain using an underlying asset pool as value support; and the target transaction includes a target underlying asset that has defaulted in the underlying asset pool during the life of the securitized asset;

[0016] The calling module, in response to the target transaction, calls the asset default processing logic in the smart contract deployed on the blockchain, publishes the default refund information of the target underlying asset to the blockchain, so that after the custodian bank system monitors the default refund information, it completes the fund refund of the target underlying asset from the investment account of the original equity holder of the target underlying asset to the equity holder of the target underlying asset based on the default refund information;

[0017] The updating module updates the beneficiary of the target underlying asset to the original beneficiary when obtaining the fund refund record corresponding to the target underlying asset published to the blockchain by the custodian bank system.

[0018] Optionally, the calling module generates a confirmation event for the target underlying asset's equity holder and original equity holder to confirm the target underlying asset's default, so that when the client monitors the confirmation event, it prompts the equity holder and original equity holder of the target underlying asset to confirm the target underlying asset's default;

[0019] When the default confirmation information of the target underlying asset by the equity holder and the original equity holder of the target underlying asset is monitored and published to the blockchain by the client, the default refund information of the target underlying asset is published to the blockchain for evidence storage.

[0020] Optionally, the device further comprises:

[0021] The publishing module, after updating the equity holder of the target underlying asset to the original equity holder, publishes the contract agreement related to the target underlying asset to the judicial chain through the cross-chain relay for evidence storage.

[0022] Optionally, the cross-chain relay is an oracle oracle.

[0023] Optionally, the investment account is a custodial account opened by the original beneficiary in a custodial bank; the securitized assets are bonds or funds; and the underlying assets are underlying debt assets.

[0024] In the above technical solution, after receiving the target transaction carrying the defaulted target underlying asset, the node device of the blockchain can call the smart contract to publish the default refund information of the target underlying asset to the blockchain, so that after the custodial bank monitors the default refund information, it can realize the refund repurchase of the original equity holder, thereby realizing the automatic repurchase of the defaulted underlying asset based on the blockchain.

[0025] In addition, after changing the rights holder of the defaulting underlying asset, the node device of the blockchain can also publish the relevant contractual agreement of the defaulting underlying asset as evidence to the judicial chain for storage through cross-chain relay, so that users can trace the relevant contractual agreement of the defaulting underlying asset through the judicial chain, and provide evidence support for subsequent arbitration lawsuits. BRIEF DESCRIPTION OF THE DRAWINGS

[0026] Figure 1 is a schematic diagram of creating a smart contract as shown in an exemplary embodiment of this specification;

[0027] Figure 2 is a schematic diagram of calling a smart contract as shown in an exemplary embodiment of this specification;

[0028] Figure 3 It is a schematic diagram of creating and calling a smart contract as shown in an exemplary embodiment of this specification;

[0029] Figure 4 It is a schematic diagram of a default asset processing system based on blockchain shown in an exemplary embodiment of this specification;

[0030] Figure 5It is a flowchart of a method for handling defaulted assets based on blockchain, shown in an exemplary embodiment of this specification;

[0031] Figure 6 is a schematic diagram of the structure of an electronic device shown in an exemplary embodiment of this specification;

[0032] Figure 7 It is a default asset processing device based on blockchain as shown in an exemplary embodiment of this specification. DETAILED DESCRIPTION

[0033] Exemplary embodiments will be described in detail herein, examples of which are shown in the accompanying drawings. When the following description refers to the drawings, the same numbers in different drawings represent the same or similar elements unless otherwise indicated. The implementations described in the following exemplary embodiments do not represent all implementations consistent with one or more embodiments of this specification. Instead, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

[0034] It should be noted that: in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the steps included in the method may be more or less than those described in this specification. In addition, 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 be combined into a single step for description in other embodiments.

[0035] Blockchain is generally divided into three types: public blockchain, private blockchain and consortium blockchain. In addition, there can also be a combination of the above types, such as private blockchain + consortium blockchain, consortium blockchain + public blockchain, etc.

[0036] Among them, the most decentralized is the public chain. Public chains are represented by Bitcoin and Ethereum. Participants who join the public chain (also called nodes in the blockchain) can read data records on the chain, participate in transactions, and compete for the right to record new blocks. Moreover, each node can freely join or exit the network and perform related operations.

[0037] On the contrary, the private chain has a network whose write permission is controlled by a certain organization or institution, and the data read permission is regulated by the organization. In simple terms, 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 use within a specific institution.

[0038] The consortium chain is a blockchain between the public chain and the private chain, which can achieve "partial decentralization". Each node in the consortium chain usually has a corresponding entity or organization; the nodes join the network through authorization and form a stakeholder alliance to jointly maintain the operation of the blockchain.

[0039] Based on the basic characteristics of blockchain, blockchain is usually composed of several blocks. In each of these blocks, a timestamp corresponding to the creation time of the block is recorded. All blocks strictly follow the timestamp recorded in the block to form a data chain that is ordered in time.

[0040] The real data generated in the physical world can be constructed into a standard transaction format supported by the blockchain, and then published to the blockchain. The node devices in the blockchain will perform consensus processing on the received transactions. After reaching a consensus, the node devices in the blockchain that serve as accounting nodes will package the transaction into blocks and store it persistently in the blockchain.

[0041] Among them, the consensus algorithms supported in blockchain can include:

[0042] The first type of consensus algorithm is the consensus algorithm in which node devices need to compete for the right to record in each accounting cycle; for example, consensus algorithms such as Proof of Work (POW), Proof of Stake (POS), and Delegated Proof of Stake (DPOS);

[0043] The second type of consensus algorithm is a consensus algorithm that elects accounting nodes in advance for each accounting cycle (without the need to compete for accounting rights); for example, consensus algorithms such as Practical Byzantine Fault Tolerance (PBFT).

[0044] In a blockchain network that uses the first type of consensus algorithm, node devices competing for the right to record transactions can execute the transaction after receiving it. Among the node devices competing for the right to record transactions, one node device may win in this round of competition for the right to record transactions and become a record node. The record 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.

[0045] In a blockchain network that uses the second type of consensus algorithm, the node devices with the right to record accounts have been agreed upon before this round of accounting. Therefore, after receiving a transaction, if the node device itself is not a record node for this round, it can send the transaction to the record node. For the record node of this round, the transaction can be executed before or during the process of packaging the transaction with other transactions to generate the latest block. After generating the latest block, the record node can send the latest block or the block header of the latest block to other node devices for consensus.

[0046] As described above, no matter which consensus algorithm shown above is adopted by the blockchain, the accounting node of this round can package the received 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 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 accounting process of the blockchain. In the process of other nodes verifying the new block or block header sent by the accounting node, the transactions contained in the block can also be executed.

[0047] In practical applications, whether it is a public chain, a private chain or a consortium chain, it may provide the function of smart contract. Smart contracts on the blockchain are contracts that can be triggered and executed by transactions on the blockchain. Smart contracts can be defined in the form of code.

[0048] Taking Ethereum as an example, it supports users to create and call some complex logic in the Ethereum network. As a programmable blockchain, Ethereum is centered on the Ethereum Virtual Machine (EVM), and each Ethereum node can run EVM. EVM is a Turing-complete virtual machine that can implement various complex logics. Users publish and call smart contracts in Ethereum on EVM. In fact, EVM directly runs virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"), so the smart contracts deployed on the blockchain can be bytecode.

[0049] like Figure 1 As shown in the figure, after Bob sends a transaction containing the information of creating a smart contract to the Ethereum network, each node can execute this transaction in the EVM. Among them, the From field of the transaction in Figure 1 is used to record the address of the account that initiated the creation of the smart contract, the contract code stored in the field value of the Data field of the transaction can be bytecode, and the field value of the To field of the transaction is a null account. When the nodes reach an agreement through the consensus mechanism, the smart contract is successfully created, and subsequent users can call this smart contract.

[0050] After a smart contract is created, a contract account corresponding to the smart contract appears on the blockchain and has a specific address; for example, Figure 1 The "0x68e12cf284..." in each node represents the address of the created contract account; the contract code (Code) and account storage (Storage) will be saved in the account storage of the contract account. The behavior of the smart contract is controlled by the contract code, and the account storage of the smart contract saves the state of the contract. In other words, the smart contract generates a virtual account on the blockchain that contains the contract code and account storage.

[0051] As mentioned above, the Data field of the transaction that creates a smart contract can store the bytecode of the smart contract. The bytecode consists of a series of bytes, each of which can identify an operation. Based on development efficiency, readability and other considerations, developers can choose a high-level language to write smart contract code instead of writing bytecode directly. For example, high-level languages ​​can be Solidity, Serpent, LLL, etc. For smart contract code written in a high-level language, it can be compiled by a compiler to generate bytecode that can be deployed on the blockchain.

[0052] Taking Solidity as an example, the contract code written in it is very similar to the class in object-oriented programming language. Multiple members can be declared in a contract, including state variables, functions, function modifiers, events, etc. State variables are values ​​permanently stored in the account storage field of the smart contract, which are used to save the state of the contract.

[0053] like Figure 2 As shown in the figure, still taking Ethereum as an example, after Bob sends a transaction containing the information of calling a smart contract to the Ethereum network, each node can execute the transaction in the EVM. Figure 2 The From field of the transaction is used to record the address of the account that initiates the call to the smart contract, the To field is used to record the address of the smart contract being called, and the Data field of the transaction is used to record the method and parameters of calling the smart contract. After calling the smart contract, the account status of the contract account may change. Later, a platform can connect to the blockchain node (for example Figure 2 Node 1) in the contract account to view the account status.

[0054] Smart contracts can be executed independently on each node in the blockchain network in a prescribed manner, and all execution records and data are stored on the blockchain. Therefore, when such a transaction is executed, the blockchain will store transaction credentials that cannot be tampered with or lost.

[0055] The schematic diagram of creating and calling smart contracts is as follows: Figure 3 To create a smart contract in Ethereum, you need to go through the process of writing the smart contract, converting it into bytecode, and deploying it to the blockchain. To call a smart contract in Ethereum, you initiate a transaction pointing to the smart contract address. The EVM of each node can execute the transaction separately, and the smart contract code is distributed and run in the virtual machine of each node in the Ethereum network.

[0056] In the field of blockchain, an important concept is account. Taking Ethereum as an example, Ethereum usually divides accounts into two categories: external accounts and contract accounts. External accounts are accounts directly controlled by users, also known as user accounts. Contract accounts are accounts created by users through external accounts and contain contract codes (i.e. smart contracts). Of course, for some blockchain projects derived from the Ethereum architecture (such as Ant Blockchain), the account types supported by the blockchain can be further expanded, which is not specifically limited in this manual.

[0057] For accounts in the blockchain, a structure is usually used to maintain the account status. When a transaction in a block is executed, the status of the account related to the transaction in the blockchain will usually change.

[0058] Taking Ethereum as an example, the structure of an account usually includes fields such as Balance, Nonce, Code and Storage. Among them:

[0059] The Balance field is used to maintain the current account balance of the account;

[0060] The Nonce field is used to maintain the number of transactions for the account. It is a counter used to ensure that each transaction can and can only be processed once, effectively avoiding replay attacks.

[0061] The Code field is used to maintain the contract code of the account. In actual applications, the Code field usually only maintains the hash value of the contract code. Therefore, the Code field is also often called the Codehash field.

[0062] The Storage field is used to maintain the storage content of the account (the default field value is empty); for a contract account, an independent storage space is usually allocated to store the storage content of the contract account; this independent storage space is usually referred to as the account storage of the contract account. The storage content of the contract account is usually constructed into an MPT (MerklePatricia Trie) tree data structure and stored in the above-mentioned independent storage space; among them, the MPT tree constructed based on the storage content of the contract account is also usually referred to as a Storage tree. The Storage field usually only maintains the root node of the Storage tree; therefore, the Storage field is also usually referred to as the StorageRoot field.

[0063] For an external account, the field values ​​of the Code field and the Storage field shown above are both empty.

[0064] Traditional blockchain projects, represented by Ethereum, usually support the conversion of real-world currencies into virtual tokens that can circulate on the chain in order to achieve "value transfer" on the blockchain.

[0065] In the blockchain field, some blockchain projects derived from the Ethereum architecture (such as Ant Blockchain) generally no longer support the function of converting real-world currencies into virtual tokens that can circulate on the chain; instead, in these blockchain projects, some non-monetary physical assets in the real world can be converted into virtual assets that can circulate on the blockchain.

[0066] Among them, it should be noted that 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 the value support of these virtual assets, and then generating virtual assets on the blockchain that match the value of the physical assets and can be circulated between blockchain accounts on the blockchain.

[0067] During implementation, the account types supported by the blockchain can be expanded, and based on the account types supported by the blockchain, an asset account (also called an asset object) can be expanded; for example, based on the external accounts and contract accounts supported by Ethereum, an asset account can be expanded; the expanded asset account is a virtual asset that can use non-monetary physical assets in the real world as value support and can circulate between blockchain accounts.

[0068] For users who access this type of blockchain, in addition to completing the creation of user accounts and smart contracts on the blockchain, they can also create a virtual asset on the blockchain that matches the value of a non-monetary physical asset in the real world and circulate it on the blockchain;

[0069] For example, users can convert their non-monetary physical assets such as real estate, stocks, loan contracts, bills, accounts receivable, etc. into virtual assets with matching value and circulate them on the blockchain.

[0070] Among them, for the above asset accounts, the account status can also be maintained through a structure. The content contained in the structure of the above asset account can be the same as that of Ethereum, and of course it can also be designed based on actual needs;

[0071] In one implementation, taking the example that the structure of the asset account contains the same content as Ethereum, the structure of the asset account may also include the fields such as Balance, Nonce, Code and Storage described above.

[0072] It should be noted that in Ethereum, the Balance field is usually used to maintain the current account balance of the account; and for blockchain projects derived from the Ethereum architecture, since they may not support the conversion of real-world currencies into virtual tokens that can circulate on the chain, the meaning of the Balance field can be expanded in such blockchains, no longer indicating the "balance" of the account, but used to maintain the address information of the asset account corresponding to the "virtual assets" held by the account. Among them, in actual applications, the Balance field can maintain the address information of the asset accounts corresponding to multiple "virtual assets".

[0073] In this case, the external accounts, contract accounts, and asset accounts shown above can all hold the virtual assets by adding the address information of the asset account corresponding to the "virtual asset" to be held in the Balance field. In other words, in addition to external accounts and contract accounts, asset accounts themselves can also hold virtual assets.

[0074] For asset accounts, the field values ​​of the Nonce and Code fields can be null (or not null); and the field value of the Storage field can no longer be null; the Storage field can be used to maintain the asset status of the "virtual assets" corresponding to the asset account. Among them, the specific method of maintaining the asset status of the "virtual assets" corresponding to the asset account in the Storage field can be flexibly designed based on needs and will not be repeated here.

[0075] In blockchain projects derived from the Ethereum architecture, users can create a virtual asset on the blockchain that matches the value of a non-monetary physical asset in the real world through the following implementation method:

[0076] In one implementation, the transaction types supported by the blockchain can be expanded to include a transaction for creating virtual assets. For example, the transaction types supported by Ethereum generally include ordinary transfer transactions, transactions for creating smart contracts, and transactions for calling smart contracts. Based on the above three types of transactions, a transaction for creating virtual assets can be expanded.

[0077] In this case, the user can publish a transaction for creating virtual assets to the blockchain network through the platform, and the node device in the blockchain executes the transaction in the local EVM to create virtual assets for the user. When the node devices reach an agreement through the consensus mechanism, the virtual asset is successfully created, and an asset account corresponding to the virtual asset appears on the blockchain with a specific address.

[0078] In another implementation, a smart contract for creating virtual assets may also be deployed on the blockchain; the process of deploying a smart contract for creating virtual assets will not be described in detail.

[0079] In this case, the user can publish a transaction to call the smart contract to the blockchain network through the platform, and the node device in the blockchain will execute the transaction in the local EVM and run the contract code related to the smart contract in the EVM to create virtual assets for the user. When the node devices reach an agreement through the consensus mechanism, the virtual asset is successfully created, and an asset account corresponding to the virtual asset appears on the blockchain with a specific address.

[0080] Of course, for some blockchain projects derived from the Ethereum architecture, if they also support the function of converting real-world currencies into virtual tokens that can circulate on the chain, then some non-monetary physical assets in the real world can still be converted into virtual tokens that can circulate on the blockchain and circulate on the blockchain. This will not be elaborated in this manual.

[0081] In addition, in cross-chain scenarios, multiple blockchains can achieve cross-chain docking through cross-chain relays.

[0082] Among them, the cross-chain relay can connect to multiple blockchains through a bridging interface, and complete the cross-chain data synchronization between the multiple blockchains based on the implemented data transfer logic.

[0083] The cross-chain technology used to implement the above-mentioned cross-chain relay is not specifically limited in this specification; for example, in actual applications, multiple blockchains can be connected through cross-chain mechanisms such as side chain technology and notary technology.

[0084] When multiple blockchains are connected through cross-chain relays, blockchains can read and authenticate data on other blockchains, and can also call smart contracts deployed on other blockchains through cross-chain relays.

[0085] As the business scenarios of blockchain continue to expand, in addition to businesses closely related to value transfer such as transfers, more and more blockchain projects are beginning to introduce some business scenarios that are not related to value transfer; for example, blockchain is connected with asset management platforms, financial institutions, etc., to complete business scenarios such as asset securitization on the blockchain.

[0086] Asset securitization refers to the process of issuing asset-backed securities (ABS) based on the future cash flow generated by the underlying assets, enhancing credit through structured design, and on this basis.

[0087] The basic process of asset securitization includes: the original equity holder of the underlying assets sells the underlying assets to the SPV (Special Purpose Vehicle), or the SPV actively purchases the underlying assets. Then, the SPV collects the purchased underlying assets into an underlying asset pool, and then issues securitized assets in the financial market for financing with the cash flow generated by the underlying asset pool as the value support, and finally uses the cash flow generated by the underlying asset pool to repay the issued securities.

[0088] Among them, the above-mentioned underlying assets may be underlying debt assets, such as accounts receivable.

[0089] The above-mentioned securitized assets may refer to securities whose value is supported by the underlying assets in the underlying asset pool. For example, the securitized assets may be bonds, funds, etc. The securitized assets are only explained here as examples without specific limitations.

[0090] However, during the life of the securitized asset, if the underlying asset in the underlying asset pool that supports the value of the securitized asset defaults, the original equity holder as the subordinated party will redeem the defaulted underlying asset.

[0091] Based on this, this specification proposes a technical solution for the original equity holder to repurchase the target underlying asset based on the smart contract deployed on the blockchain when it is determined that the target underlying asset in the underlying asset pool has defaulted.

[0092] In a specific implementation, a node device of the blockchain receives a target transaction sent by an asset management platform during the life of a securitized asset, and the target transaction includes a target underlying asset that has defaulted in the underlying asset pool during the life of the securitized asset.

[0093] The node device of the blockchain can respond to the target transaction, call the asset default processing logic in the smart contract deployed on the blockchain, and publish the default refund information of the target underlying asset to the blockchain, so that after the custodian bank system monitors the default refund information, it can complete the fund refund of the target underlying asset from the investment account of the original equity holder of the target underlying asset to the equity holder of the target underlying asset based on the default refund information.

[0094] When the node device of the blockchain obtains the fund refund record corresponding to the target underlying asset published to the blockchain by the bank system, the beneficiary of the target underlying asset is updated to the original beneficiary.

[0095] In the above technical solution, after receiving the target transaction carrying the defaulted target underlying asset, the node device of the blockchain can call the smart contract to publish the default refund information of the target underlying asset to the blockchain, so that after the custodial bank monitors the default refund information, it can realize the refund repurchase of the original equity holder, thereby realizing the automatic repurchase of the defaulted underlying asset based on the blockchain.

[0096] In addition, after changing the rights holder of the defaulting underlying asset, the node device of the blockchain can also publish the relevant contractual agreement of the defaulting underlying asset as evidence to the judicial chain for storage through cross-chain relay, so that users can trace the relevant contractual agreement of the defaulting underlying asset through the judicial chain, and provide evidence support for subsequent arbitration lawsuits.

[0097] See also Figure 4 , Figure 4 It is a schematic diagram of a blockchain-based default asset processing system shown as an exemplary embodiment of this specification.

[0098] The blockchain-based default asset processing system includes: a blockchain, an asset management platform connected to the blockchain, and a custodial bank system.

[0099] Among them, the asset management platform is used to deploy smart contracts for default asset processing on the blockchain, and trigger the node devices of the blockchain to execute the default asset processing process by publishing target transactions carrying default target underlying assets. Of course, the asset management platform also has other functions, such as publishing screening rules for underlying assets to the blockchain, etc. Here, the functions of the asset management platform are only exemplified and not specifically limited.

[0100] The custodial bank system is used to maintain the accounts of the original beneficiaries and investors, transfer funds, etc. Here, the functions of the custodial bank system are only exemplarily described, and the functions of the custodial bank system are not specifically limited.

[0101] The asset management platform, custodial bank system and blockchain are connected, and the three work together to complete the processing of the above-mentioned defaulted assets.

[0102] The following is a detailed description of the blockchain-based method for handling defaulted assets provided in this specification.

[0103] See also Figure 5 , Figure 5 This is a flowchart of a method for handling defaulted assets based on blockchain, shown as an exemplary embodiment of this specification. The method can be applied to a node device of blockchain and may include the following steps.

[0104] Step 502: The node device of the blockchain receives the target transaction sent by the asset management platform during the life of the securitized asset; wherein the securitized asset is an asset issued on the blockchain with the underlying asset pool as value support; the target transaction includes the target underlying asset that defaults in the underlying asset pool during the life of the securitized asset.

[0105] Step 504: The node device of the blockchain responds to the target transaction, calls the asset default processing logic in the smart contract deployed on the blockchain, and publishes the default refund information of the target underlying asset to the blockchain, so that after the custodial bank system monitors the default refund information, it completes the fund refund of the target underlying asset from the investment account of the original equity holder of the target underlying asset to the equity holder of the target underlying asset based on the default refund information.

[0106] Step 506: When the node device of the blockchain obtains the fund refund record corresponding to the target underlying asset published to the blockchain by the bank system, the node device of the blockchain updates the beneficiary of the target underlying asset to the original beneficiary.

[0107] Among them, this specification does not specifically limit the above-mentioned underlying assets, and the underlying assets may be underlying debt assets, such as accounts receivable.

[0108] The above-mentioned investment account may refer to the custodial account opened by the original beneficiary at the custodial bank.

[0109] The above-mentioned securitized assets may refer to securities whose value is supported by the underlying assets in the underlying asset pool. For example, the securitized assets may be bonds, funds, etc. The securitized assets are only explained here as examples without specific limitations.

[0110] The above-mentioned basic asset pool can be a collection of identifiers of several selected basic assets generated by the smart contract on the blockchain. The basic assets in the basic asset pool can be used as value support to issue securitized assets. The basic asset pool can be stored in the storage space (Storage) of the contract account corresponding to the smart contract, or in the account storage space of the blockchain account of the asset manager (such as an SPV institution). The storage location of the basic asset pool is not specifically limited here.

[0111] In addition, a smart contract for handling defaulted assets is deployed on the blockchain. The deployed smart contract can include the logic for handling asset defaults.

[0112] The asset default processing logic is used to determine the default refund information of the target underlying asset based on the target transaction carrying the default target underlying asset, and publish the default refund information of the target underlying asset to the blockchain, so that the custodial bank system can complete the allocation of the refund funds after monitoring the default refund information.

[0113] When the above-mentioned smart contract is deployed, the above-mentioned asset management platform can publish the target transaction constructed by the platform to the blockchain to call the above-mentioned smart contract deployed on the blockchain to complete the operation of publishing the default refund information of the target underlying asset to the blockchain.

[0114] In specific implementation, when the asset management platform detects that a target underlying asset in the underlying asset pool that supports the value of the securitized asset has defaulted during the term of the securitized asset, the asset management platform can construct a target transaction based on the defaulted target underlying asset, which carries the defaulted target underlying asset.

[0115] Then, the asset management platform can publish the target transaction to the blockchain. After receiving the target transaction, the node device of the blockchain can respond to the target transaction, call the asset default processing logic declared by the smart contract deployed on the blockchain, generate a default processing event based on the default refund information of the target underlying asset, and publish the default processing event containing the default refund information of the target underlying asset to the blockchain. The default processing event is used to enable the custodian bank system to complete the fund refund.

[0116] At the time of publication, on the one hand, the smart contract needs to obtain the default refund information of the defaulted target underlying asset.

[0117] An optional acquisition method is that when the asset management platform detects that the target underlying asset in the underlying asset pool defaults during the duration of the securitized asset, it can determine the default refund information of the target underlying asset (such as the default refund amount and other information). Then, the asset management platform can construct a target transaction based on the target underlying asset and the default refund information of the target underlying asset. The information of the target underlying asset carried by the target transaction may include: the target underlying asset identifier, the default refund information of the target underlying asset, etc. The smart contract can obtain the default refund information of the target underlying asset from the target transaction.

[0118] Another optional way to obtain the information is that the blockchain stores the identifier of the underlying asset and the transaction record of the underlying asset transaction information, and the identifier of the target underlying asset carried in the target transaction. The smart contract can obtain the identifier of the target underlying asset carried in the target transaction, and then obtain the transaction information corresponding to the identifier of the target underlying asset in the transaction record stored in the blockchain, and determine the default refund information based on the transaction information.

[0119] For example, assuming that the transaction information includes the transaction amount, and the default refund information includes the default refund amount, the following takes the determination of the default refund amount by the transaction amount as an example to exemplify the determination of the default refund information based on the transaction information.

[0120] When implemented, the smart contract can use the transaction amount as the default refund amount. Alternatively, the smart contract can calculate the default refund amount based on the transaction amount according to the conversion ratio between the transaction amount and the default refund amount agreed upon in the contract between the original equity holder and the equity holder of the target underlying asset (for example, the default refund amount agreed upon in the contract between the two parties is 1.1 times or 0.8 times the transaction amount, etc.).

[0121] On the other hand, when publishing, the smart contract also needs to initiate a default confirmation operation for the target underlying asset's equity holders and original equity holders. After the equity holders and original equity holders of the target underlying asset complete the default confirmation operation for the target underlying asset, the default refund information of the default target underlying asset can be published to the blockchain.

[0122] In specific implementation, the smart contract can generate a confirmation event for the target underlying asset to be defaulted by the equity holder and the original equity holder of the target underlying asset.

[0123] When the client corresponding to the smart contract deployed on the asset management platform monitors the confirmation event, it can remind the equity holder and the original equity holder of the target underlying asset to confirm the default of the target underlying asset. After the equity holder and the original equity holder of the target underlying asset confirm the default of the target underlying asset, the default confirmation information can be submitted to the client.

[0124] After the client receives the default confirmation information submitted by the equity holder and the original equity holder of the target underlying asset (such as the signature of the defaulted target underlying asset), the default confirmation information can be submitted to the smart contract.

[0125] When the smart contract receives the default confirmation information, it will publish the default refund information containing the target underlying asset to the blockchain.

[0126] When publishing the information about refunds for breach of contract, the smart contract can use the event mechanism to publish it. When the custodial bank system monitors the information about refunds for breach of contract, it can also monitor the information in the form of monitoring events.

[0127] Specifically, the smart contract can construct a default handling event based on the default refund information, and publish the default handling event containing the default refund information to the blockchain.

[0128] In the embodiment of this specification, the client corresponding to the smart contract deployed on the custodian bank system can monitor the default handling event published on the blockchain. When the custodian bank system monitors the default handling event, it can complete the fund refund of the target underlying asset from the investment account of the original equity holder of the target underlying asset to the equity holder of the target underlying asset.

[0129] Furthermore, the custodial bank system maintains the investment account of the original equity holder of the target underlying asset and the investment account of the equity holder of the target underlying asset.

[0130] The custodian bank's fund refund means that the custodian bank system transfers the fund refund from the original equity holder's investment account to the investment account of the equity holder of the target underlying asset.

[0131] When the custodial bank system completes the fund refund, the custodial bank system can submit the fund refund record of the target underlying asset to the above-mentioned smart contract.

[0132] When the smart contract on the node device of the blockchain receives the fund refund record corresponding to the target underlying asset published to the blockchain by the custodial bank system, the beneficiary of the target underlying asset can be updated to the original beneficiary.

[0133] In an optional update method, the target underlying asset's equity holder information is maintained on the blockchain node device. When the smart contract obtains the fund refund record corresponding to the target underlying asset, it updates the equity holder of the target underlying asset maintained on the blockchain node device to the original equity holder.

[0134] In another optional updating method, the equity holder information of the target underlying asset is maintained on the asset management platform. When the equity holder information of the target underlying asset is updated, the smart contract can generate an equity holder update event for updating the equity holder of the target underlying asset to the original equity holder.

[0135] When the client of the smart contract on the asset management platform monitors the stakeholder update event, the stakeholder of the target underlying asset maintained on the asset management platform can be updated to the original stakeholder, and the stakeholder update success information can be submitted to the smart contract. After receiving the stakeholder update success information, the smart contract can determine that the stakeholder of the defaulted target underlying asset has been updated to the original stakeholder.

[0136] It can be seen from the above description that after receiving a target transaction carrying a defaulted target underlying asset, the node device of the blockchain can call a smart contract to publish the default refund information of the target underlying asset to the blockchain, so that after the custodial bank monitors the default refund information, it can realize the refund repurchase of the original equity holder, thereby realizing the automatic repurchase of the defaulted underlying asset based on the blockchain.

[0137] In addition, in the embodiments of this specification, after the equity holder of the target underlying asset is updated to the original equity holder, the node device of the blockchain can publish the contract agreement related to the target underlying asset to the judicial chain through cross-chain relay for evidence storage. This allows users to trace the relevant contract agreement of the defaulted underlying asset through the judicial chain, providing evidence support for possible subsequent arbitration prosecution.

[0138] Among them, the cross-chain relay can be connected to multiple blockchains through a bridge interface, and based on the implemented data transfer logic, complete the cross-chain data synchronization between the multiple blockchains. For example, the cross-chain relay can be an Oracle oracle. Here, the cross-chain relay is only exemplarily explained without specific limitation.

[0139] Corresponding to the above method embodiments, this specification also provides device embodiments.

[0140] Corresponding to the above method embodiments, this specification also provides an embodiment of a default asset processing device based on blockchain. The embodiment of the default asset processing 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 and running them. From the hardware level, if Figure 6The figure is a hardware structure diagram of the electronic device where the default asset processing device based on blockchain in this specification is located, except Figure 6 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.

[0141] See also Figure 7 , Figure 7 This is a default asset processing device based on blockchain as shown in an exemplary embodiment of this specification. The default asset processing device can be applied to the node device of the blockchain and may include the following modules.

[0142] The receiving module 701 receives a target transaction sent by the asset management platform during the duration of the securitized asset; wherein the securitized asset is an asset issued on the blockchain with the underlying asset pool as value support; and the target transaction includes a target underlying asset that has defaulted in the underlying asset pool during the duration of the securitized asset;

[0143] The calling module 702, in response to the target transaction, calls the asset default processing logic in the smart contract deployed on the blockchain, publishes the default refund information of the target underlying asset to the blockchain, so that after the custodian bank system monitors the default refund information, it completes the fund refund of the target underlying asset from the investment account of the original equity holder of the target underlying asset to the equity holder of the target underlying asset based on the default refund information;

[0144] The updating module 703 updates the beneficiary of the target underlying asset to the original beneficiary when obtaining the fund refund record corresponding to the target underlying asset published to the blockchain by the custodian bank system.

[0145] Optionally, the calling module 702 generates a confirmation event for the target underlying asset's equity holder and original equity holder to confirm the target underlying asset's default, so that when the client monitors the confirmation event, it prompts the equity holder and original equity holder of the target underlying asset to confirm the target underlying asset's default;

[0146] When the default confirmation information of the target underlying asset by the equity holder and the original equity holder of the target underlying asset is monitored and published to the blockchain by the client, the default refund information of the target underlying asset is published to the blockchain for evidence storage.

[0147] Optionally, the device further comprises:

[0148] The publishing module 704, after updating the equity holder of the target underlying asset to the original equity holder, publishes the contract agreement related to the target underlying asset to the judicial chain through the cross-chain relay for evidence storage.

[0149] Optionally, the cross-chain relay is an oracle oracle.

[0150] Optionally, the investment account is a custodial account opened by the original beneficiary in a custodial bank; the securitized assets are bonds or funds; and the underlying assets are underlying debt assets.

[0151] The systems, devices, modules or units 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.

[0152] In a typical configuration, a computer includes one or more processors (CPU), input / output interfaces, network interfaces, and memory.

[0153] The memory may include non-permanent storage in a computer-readable medium, random access memory (RAM) and / or non-volatile memory in the form of read-only memory (ROM) or flash RAM. The memory is an example of a computer-readable medium.

[0154] Computer-readable media include permanent and non-permanent, removable and non-removable media that can be used to store information by any method or technology. Information can be computer-readable instructions, data structures, program modules 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 cassettes, disk storage, quantum memory, graphene-based storage media or other magnetic storage devices or any other non-transmission media that can be used to store information that can be accessed by a computing device. As defined herein, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

[0155] It should also be noted that the terms "include", "comprises" or any other variations thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, commodity or device. In the absence of more restrictions, the elements defined by the sentence "comprises a ..." do not exclude the existence of other identical elements in the process, method, commodity or device including the elements.

[0156] The above is a description of a specific embodiment of the specification. Other embodiments are within the scope of the appended claims. In some cases, the actions or steps recorded in the claims can be performed in an order different from that in the embodiments and still achieve the desired results. In addition, the processes depicted in the drawings do not necessarily require the specific order or continuous order shown to achieve the desired results. In some embodiments, multitasking and parallel processing are also possible or may be advantageous.

[0157] The terms used in one or more embodiments of this specification are only for the purpose of describing specific embodiments, and are not intended to limit one or more embodiments of this specification. The singular forms of "a", "said" and "the" used in one or more embodiments of this specification and the appended claims are also intended to include plural forms, unless the context clearly indicates other meanings. It should also be understood that the term "and / or" used herein refers to and includes any or all possible combinations of one or more associated listed items.

[0158] It should be understood that although the terms first, second, third, etc. may be used to describe various information in one or more embodiments of this specification, these information should not be limited to these terms. These terms are only used to distinguish the same type of information from each other. For example, without departing from the scope of one or more embodiments of this specification, the 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. Depending on the context, the word "if" as used herein may be interpreted as "at the time of" or "when" or "in response to determining".

[0159] The above description is merely a preferred embodiment of one or more embodiments of the present specification and is not intended to limit one or more embodiments of the present specification. Any modifications, equivalent substitutions, improvements, etc. made within the spirit and principles of one or more embodiments of the present specification shall be included in the scope of protection of one or more embodiments of the present specification.

Claims

1. A method for handling defaulted assets based on blockchain, the method comprising: Receiving a target transaction sent by an asset management platform during the life of a securitized asset; wherein the securitized asset is an asset issued on the blockchain using an underlying asset pool as value support; and the target transaction includes a target underlying asset that has defaulted in the underlying asset pool used to issue the securitized asset; In response to the target transaction, the asset default processing logic in the smart contract deployed on the blockchain is called to publish the default refund information of the target underlying asset to the blockchain, so that after the custodial bank system monitors the default refund information, based on the default refund information, the funds of the target underlying asset are refunded to the equity holder of the target underlying asset from the investment account of the original equity holder of the target underlying asset, and when the fund refund record corresponding to the target underlying asset submitted by the custodial bank system to the smart contract is obtained, the equity holder of the target underlying asset is updated to the original equity holder.

2. According to the method of claim 1, the step of publishing the default refund information of the target underlying asset to the blockchain comprises: Generate a confirmation event for the target underlying asset to be confirmed as a default by the equity holder and the original equity holder of the target underlying asset, so that when the client monitors the confirmation event, it prompts the equity holder and the original equity holder of the target underlying asset to confirm the default of the target underlying asset; When the default confirmation information of the target underlying asset by the equity holder and the original equity holder submitted by the client to the smart contract is obtained, the default refund information of the target underlying asset is published to the blockchain.

3. The method according to claim 1 or 2, publishing the default refund information of the target underlying asset to the blockchain so that the custodian bank system can monitor the default refund information, comprising: A default handling event is generated based on the default refund information of the target underlying asset, and the default handling event is published to the blockchain, so that when the custodian bank system monitors the default handling event, it can further obtain the default refund information contained in the default handling event.

4. According to the method of claim 1, the blockchain is connected to the judicial chain through a cross-chain relay; The method further comprises: After the equity holder of the target underlying asset is updated to the original equity holder, the contract agreement related to the target underlying asset is published to the judicial chain through the cross-chain relay for evidence storage.

5. According to the method of claim 4, the cross-chain relay is an oracle oracle.

6. According to the method of claim 1, the securitized assets are bonds or funds; and the underlying assets are underlying debt assets.

7. A default asset processing device based on blockchain, the device comprising: A receiving module, used to receive a target transaction sent by an asset management platform during the life of a securitized asset; wherein the securitized asset is an asset issued on the blockchain using an underlying asset pool as value support; and the target transaction includes a target underlying asset that has defaulted in the underlying asset pool used to issue the securitized asset; A calling module is used to call the asset default processing logic in the smart contract deployed on the blockchain in response to the target transaction, and publish the default refund information of the target underlying asset to the blockchain, so that after the custodial bank system monitors the default refund information, based on the default refund information, the funds of the target underlying asset are refunded to the equity holder of the target underlying asset from the investment account of the original equity holder of the target underlying asset, and when the fund refund record corresponding to the target underlying asset submitted by the custodial bank system to the smart contract is obtained, the equity holder of the target underlying asset is updated to the original equity holder.

8. According to the device of claim 7, the calling module, when publishing the default refund information of the target underlying asset to the blockchain, is used to generate a confirmation event for determining the default of the target underlying asset by the equity holder and the original equity holder of the target underlying asset, so that when the client monitors the confirmation event, the equity holder and the original equity holder of the target underlying asset are prompted to confirm the default of the target underlying asset; when the default confirmation information of the target underlying asset submitted by the client to the smart contract by the equity holder and the original equity holder is obtained, the default refund information of the target underlying asset is published to the blockchain.

9. According to the device of claim 7 or 8, the calling module is used to generate a default handling event based on the default refund information of the target underlying asset when publishing the default refund information of the target underlying asset to the blockchain so that the custodial bank system can monitor the default refund information, and publish the default handling event to the blockchain so that the custodial bank system can further obtain the default refund information contained in the default handling event when monitoring the default handling event.

10. The device according to claim 7, further comprising: The publishing module, after updating the equity holder of the target underlying asset to the original equity holder, publishes the contract agreement related to the target underlying asset to the judicial chain through cross-chain relay for evidence storage.

11. The device according to claim 10, wherein the cross-chain relay is an oracle oracle.

12. The device according to claim 7, wherein the securitized assets are bonds or funds; and the underlying assets are underlying debt assets.

13. An electronic device comprising: processor; a memory for storing processor-executable instructions; The processor implements the method according to any one of claims 1 to 6 by running the executable instructions.

14. A computer-readable storage medium having computer instructions stored thereon, characterized in that: When the instruction is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images