Detailed Description
Reference will now be made in detail to the exemplary embodiments, examples of which are illustrated in the accompanying drawings. When the following description refers to the accompanying drawings, like 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 the present specification. Rather, they are merely examples of apparatus and methods consistent with certain aspects of one or more embodiments of the specification, as detailed in the claims which follow.
It should be noted that: in other embodiments, the steps of the corresponding methods are not necessarily performed in the order shown and described herein. In some other embodiments, the method may include more or fewer steps than those described herein. Moreover, a single step described in this specification may be broken down into multiple steps for description in other embodiments; multiple steps described in this specification may be combined into a single step in other embodiments.
Blockchains are generally divided into three types: public chain (Public Blockchain), Private chain (Private Blockchain) and alliance chain (Consortium Blockchain). Furthermore, there may be a combination of the above types, such as private chain + federation chain, federation chain + public chain, and so on.
Among them, the most decentralized is the public chain. The public chain is represented by bitcoin and ether house, and participants (also called nodes in the block chain) joining the public chain can read data records on the chain, participate in transactions, compete for accounting rights of new blocks, and the like. Moreover, each node can freely join or leave the network and perform related operations.
Private chains are the opposite, with the network's write rights controlled by an organization or organization and the data read rights specified by the organization. Briefly, a private chain may 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 particular establishment.
A federation chain is a block chain between a public chain and a private chain, and "partial decentralization" can be achieved. Each node in a federation chain typically has a physical organization or organization corresponding to it; the nodes are authorized to join the network and form a benefit-related alliance, and block chain operation is maintained together.
Based on the basic characteristics of a blockchain, a blockchain is usually composed of several blocks. The time stamps corresponding to the creation time of the block are recorded in the blocks respectively, and all the blocks form a time-ordered data chain according to the time stamps recorded in the blocks strictly.
The real data generated by the physical world can be constructed into a standard transaction (transaction) format supported by a block chain, then is issued to the block chain, the node equipment in the block chain performs consensus processing on the received transaction, and after the consensus is achieved, the node equipment serving as an accounting node in the block chain packs the transaction into a block and performs persistent evidence storage in the block chain.
The consensus algorithm supported in the blockchain may include:
the first kind of consensus algorithm, namely the consensus algorithm that the node device needs to contend for the accounting right of each round of accounting period; consensus algorithms such as Proof of Work (POW), Proof of equity (POS), Proof of commission rights (DPOS), etc.;
the second kind of consensus algorithm, namely the consensus algorithm which elects accounting nodes in advance for each accounting period (without competing for accounting right); for example, a consensus algorithm such as a Practical Byzantine Fault Tolerance (PBFT) is used.
In a blockchain network employing a first type of consensus algorithm, node devices competing for billing rights can execute a transaction upon receipt. One of the node devices competing for the accounting right may win in the process of competing for the accounting right in the current round, and become an accounting node. The accounting node may package the received transaction with other transactions to generate a latest block and send the generated latest block or a block header of the latest block to other node devices for consensus.
In the block chain network adopting the second type of consensus algorithm, the node equipment with the accounting right is agreed before accounting in the current round. Thus, the node device, after receiving the transaction, may send the transaction to the accounting node if it is not the accounting node of its own round. For the accounting node of the current round, the transaction may be performed during or before packaging the transaction with other transactions to generate the latest block. After generating the latest block, the accounting node may send the latest block or a block header of the latest block to other node devices for consensus.
As described above, regardless of which consensus algorithm is used by the blockchain, the accounting node of the current round may pack the received transaction 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 no problem is verified after other node equipment receives the latest block or the block header of the latest block, the latest block can be added to the tail of the original block chain, so that the accounting process of the block chain is completed. The transaction contained in the block may also be performed by other nodes in verifying the new block or block header sent by the accounting node.
In practical applications, whether public, private, or alliance, it is possible to provide the functionality of a Smart contract (Smart contract). An intelligent contract on a blockchain is a contract on a blockchain that can be executed triggered by a transaction. An intelligent contract may be defined in the form of code.
Taking an Etherhouse as an example, a user is supported to create and call some complex logic in the Etherhouse network. The ethernet workshop is used as a programmable block chain, and the core of the ethernet workshop is an ethernet workshop virtual machine (EVM), and each ethernet workshop node can run the EVM. The EVM is a well-behaved virtual machine through which various complex logic can be implemented. The user issuing and invoking smart contracts in the etherhouse is running on the EVM. In fact, the EVM directly runs virtual machine code (virtual machine bytecode, hereinafter referred to as "bytecode"), so the intelligent contract deployed on the blockchain may be bytecode.
After Bob sends a Transaction (Transaction) containing information to create a smart contract to the ethernet network, each node can execute the Transaction in the EVM, as shown in fig. 1. In fig. 1, the From field of the transaction is used To record the address of the account initiating the creation of the intelligent contract, the contract code stored in the field value of the Data field of the transaction may be bytecode, and the field value of the To field of the transaction is a null account. After the nodes reach the agreement through the consensus mechanism, the intelligent contract is successfully created, and the follow-up user can call the intelligent contract.
After the intelligent contract is established, a contract account corresponding to the intelligent contract appears on the block chain, and the block chain has a specific address; for example, "0 x68e12cf284 …" in each node in fig. 1 represents the address of the contract account created; the contract Code (Code) and account store (Storage) will be maintained in the account store for that contract account. The behavior of the intelligent contract is controlled by the contract code, while the account storage of the intelligent contract preserves the state of the contract. In other words, the intelligent contract causes a virtual account to be generated on the blockchain that contains the contract code and account storage.
As mentioned above, the Data field containing the transaction that created the intelligent contract may hold the byte code of the intelligent contract. A bytecode consists of a series of bytes, each of which can identify an operation. Based on the multiple considerations of development efficiency, readability and the like, a developer can select a high-level language to write intelligent contract codes instead of directly writing byte codes. For example, the high-level language may employ a language such as Solidity, Serpent, LLL, and the like. For intelligent contract code written in a high-level language, the intelligent contract code can be compiled by a compiler to generate byte codes which can be deployed on a blockchain.
Taking the Solidity language as an example, the contract code written by it is very similar to a Class (Class) in the object-oriented programming language, and various members including state variables, functions, function modifiers, events, etc. can be declared in one contract. A state variable is a value permanently stored in an account Storage (Storage) field of an intelligent contract to save the state of the contract.
As shown in FIG. 2, still taking the Etherhouse as an example, after Bob sends a transaction containing the information of the calling intelligent contract to the Etherhouse network, each node can execute the transaction in the EVM. In fig. 2, the From field of the transaction is used To record the address of the account initiating the intelligent contract invocation, the To field is used To record the address of the intelligent contract invocation, and the Data field of the transaction is used To record the method and parameters of the intelligent contract invocation. After invoking the smart contract, the account status of the contract account may change. Subsequently, a platform may view the account status of the contract account through the accessed block link point (e.g., node 1 in fig. 2).
The intelligent contract can be independently executed at each node in the blockchain network in a specified mode, and all execution records and data are stored on the blockchain, so that after the transaction is executed, transaction certificates which cannot be tampered and lost are stored on the blockchain.
A schematic diagram of creating an intelligent contract and invoking the intelligent contract is shown in fig. 3. An intelligent contract is created in an Ethernet workshop and needs to be subjected to the processes of compiling the intelligent contract, changing the intelligent contract into byte codes, deploying the intelligent contract to a block chain and the like. The intelligent contract is called in the Ethernet workshop, a transaction pointing to the intelligent contract address is initiated, the EVM of each node can respectively execute the transaction, and the intelligent contract code is distributed and operated in the virtual machine of each node in the Ethernet workshop network.
In the field of blockchain, an important concept is Account (Account); taking an ether house as an example, the ether house generally divides an account into an external account and a contract account; the external account is an account directly controlled by the user and is also called as a user account; and the contract account is created by the user through an external account, the account containing the contract code (i.e. the smart contract). Of course, for some blockchain items derived from the ethernet-based architecture (such as ant blockchains), the account types supported by the blockchain may be further expanded, and are not particularly limited in this specification.
For accounts in a blockchain, the account status of the account is usually maintained through a structure. When a transaction in a block is executed, the status of the account associated with the transaction in the block chain is also typically changed.
Taking etherhouses as an example, the structure of an account usually includes fields such as Balance, Nonce, Code and Storage. Wherein:
a Balance field for maintaining the current account Balance of the account;
a Nonce field for maintaining a number of transactions for the account; the counter is used for guaranteeing that each transaction can be processed only once, and replay attack is effectively avoided;
a Code field for maintaining a contract Code for the account; in practical applications, only the hash value of the contract Code is typically maintained in the Code field; thus, the Code field is also commonly referred to as the Codhash field.
A Storage field for maintaining the Storage contents of the account (default field value is null); for a contract account, a separate storage space is usually allocated to store the storage content of the contract account; this separate storage space is often referred to as the account storage of the contract account. The storage content of the contract account is usually constructed into a data structure of an MPT (Merkle Patricia Trie) tree and stored in the independent storage space; in which, the Storage content based on the contract account is constructed into an MPT tree, which is also commonly referred to as a Storage tree. Whereas the Storage field typically maintains only the root node of the Storage tree; thus, the Storage field is also commonly referred to as the Storage root field.
Wherein, for the external account, the field values of the Code field and the Storage field shown above are both null values.
Conventional blockchain projects, represented by etherhouses, typically support conversion of real-world currency into virtual tokens that can be circulated through the chain in order to effect a "value transfer" over the blockchain.
In the blockchain field, for some blockchain items derived from the ethernet-based architecture (such as ant blockchains), the function of converting real-world currency into virtual tokens that can circulate on the chains is generally no longer supported; instead, in these blockchain projects, some non-monetary attributes of the physical assets in the real world may be converted into virtual assets that can be circulated over the blockchain.
It should be noted that converting an entity asset having a non-monetary attribute in the real world into a virtual asset on a blockchain generally refers to a process of "anchoring" the entity asset and a virtual asset on the blockchain to serve as a value support for the virtual assets, and further generating a virtual asset on the blockchain which is matched with the value of the entity asset and can be circulated between blockchain accounts on the blockchain.
In the implementation process, the account types supported by the blockchain can be expanded, and an asset account (also called an asset object) is expanded on the basis of the account types supported by the blockchain; for example, an asset account can be expanded on the basis of an external account and a contract account supported by an Ethernet; the expanded asset account is a virtual asset which can support the real-world non-monetary property of the physical asset as value and can be circulated between the blockchain accounts.
For users accessing such a blockchain, in addition to completing the creation of user accounts and intelligent contracts on the blockchain, a virtual asset matched with the entity asset value of non-monetary attributes of the real world is created on the blockchain, and circulation is performed on the blockchain;
for example, a user may convert physical assets of non-monetary attributes, such as real estate, stocks, loan contracts, notes, accounts receivable, etc., held to value-matched virtual assets for circulation over a blockchain.
The above asset account may be maintained by a structure, specifically, the account status of the account may be maintained by a structure. The content of the structure of the asset account may be the same as that of the ether house, and may be designed based on actual requirements;
in one implementation, for example, the content of the structure body of the asset account is the same as that of an ethernet bay, the structure body of the asset account may also include the fields of Balance, Nonce, Code, and Storage described above.
It should be noted that, in an ethernet, the Balance field is usually used to maintain the current account Balance of the account; for the block chain project derived based on the ethernet framework, since it may not support the conversion of real-world currency into virtual tokens that can be circulated on the chain, in such block chains, the meaning of the Balance field may be extended, and the Balance of the account is no longer represented, but is used to maintain the address information of the asset account corresponding to the "virtual asset" held by the account. In practical application, address information of asset accounts corresponding to multiple virtual assets can be maintained in the Balance field.
In this case, the external account, the contract account, and the asset account shown above can hold the virtual asset by adding address information of the asset account corresponding to the "virtual asset" that needs to be held in the Balance field. That is, in addition to the external account and the contract account, the asset account itself may hold the virtual asset.
For an asset account, Nonce, the field value of the Code field may or may not be null; and the field value of the Storage field may no longer be a null value; the Storage field may be used to maintain the asset status of the "virtual asset" corresponding to the asset account. The specific manner of maintaining the asset state of the "virtual asset" corresponding to the asset account in the Storage field can be flexibly designed based on requirements, and is not described in detail.
In the blockchain project derived based on the framework of the EtherFang, a user can create a virtual asset on the blockchain that matches the value of the real-world non-monetary attribute physical asset by the implementation shown below:
in one implementation, the transaction types supported by the blockchain may be extended to extend a transaction for creating virtual assets; for example, the types of transactions supported by the etherhouse typically include normal transfer transactions, transactions to create smart contracts, and transactions to invoke smart contracts, and a transaction to create virtual assets may be expanded based on the above three types of transactions.
In this case, a user may create a virtual asset for the user by the platform issuing a transaction into the blockchain network for creating the virtual asset, which transaction is performed in the local EVM by a node device in the blockchain. When the node devices reach the agreement through the consensus mechanism, the virtual asset is successfully created, and an asset account corresponding to the virtual asset appears on the blockchain and has a specific address.
In another implementation, intelligent contracts for creating virtual assets may also be deployed on blockchains; the process of deploying the intelligent contract for creating the virtual asset is not described in detail.
In this case, the user may create a virtual asset for the user by the platform issuing a transaction into the blockchain network for invoking the intelligent contract, executing the transaction in the local EVM by the node device in the blockchain, and running contract code associated with the intelligent contract in the EVM. When the node devices reach the agreement through the consensus mechanism, the virtual asset is successfully created, and an asset account corresponding to the virtual asset appears on the blockchain and has a specific address.
Of course, for some blockchain items derived based on the ethernet framework, if the blockchain items also support the function of converting real-world currency into virtual tokens that can circulate on the chain, some non-currency property entity assets in the real world can still be converted into a form of virtual tokens that can circulate on the blockchain, and the virtual tokens circulate on the blockchain, which is not described in detail in this specification.
In addition, in a cross-chain scenario, multiple blockchains may implement cross-chain docking through cross-chain relays.
The cross-link relay can be respectively connected with the block chains through the bridging interfaces, and the cross-link data synchronization among the block chains is completed based on the realized data carrying logic.
The chain-crossing technology used for realizing the chain-crossing relay is not particularly limited in this specification; for example, in practical applications, a plurality of block chains can be connected by a chain-crossing mechanism such as side chain technology, notary technology, and the like.
After a plurality of block chains are connected in a butt joint mode through cross-chain relays, data on other block chains can be read and authenticated between the block chains, and intelligent contracts deployed on other block chains can be called through the cross-chain relays.
With the continuous enrichment of service scenes of the blockchain, more and more blockchain projects begin to introduce some service scenes unrelated to value transfer besides the services related to value transfer, such as transfer and the like; for example, a blockchain interfaces with an asset management platform, financial institution, etc., completing a business scenario such as asset securitization on the blockchain.
The Asset securitization refers to a process of using cash flow generated in the future of a basic Asset as a value support, carrying out credit enhancement through structured design, and issuing Asset-backed Securities (ABS) on the basis.
The basic flow of asset securitization includes: the original stakeholders of the base assets sell the base assets to an SPV (Special Purpose organization), or the SPV actively purchases the base assets. Then, the SPV collects the purchased basic assets into a basic asset pool, then uses the cash flow generated by the basic asset pool as a value to support the issuance of securities on the financial market for financing, and finally uses the cash flow generated by the basic asset pool to settle the issued securities.
The basic assets may be basic debt assets, such as accounts receivable.
The securitized assets may refer to securities that are supported by a base asset in a base asset pool as a value, for example, the securitized assets may be bonds, funds, and the like, and the securitized assets are only exemplified and not particularly limited herein.
However, if a breach occurs in a base asset in a pool of base assets that is supported by the value of the securitized asset during the lifetime of the securitized asset, the breach of the base asset may involve the redemption of the breached base asset as an original equity person behind the deterioration.
Based on the above, the present specification proposes a technical solution for completing the repurchase of the original rights beneficiary to the target base asset based on the intelligent contract deployed on the blockchain when the target base asset in the base asset pool is determined to be violated.
In particular implementations, a node device of a blockchain receives a target trade sent by an asset management platform during the lifetime of a securitized asset, the target trade including a target base asset for which a breach has occurred in the pool of base assets during the lifetime of the securitized asset.
The node equipment of the block chain can respond to the target transaction, call asset default processing logic in an intelligent contract deployed on the block chain, and issue default refund information of the target basic asset to the block chain, so that after a managed banking system monitors the default refund information, the authorized persons of the target basic asset complete fund refund of the target basic asset from the investment account of the original authorized beneficiary of the target basic asset based on the default refund information
And when the node equipment of the block chain acquires the fund refund record which is issued to the block chain by the bank system and corresponds to the target basic asset, updating the rights and interests of the target basic asset to the original rights and interests.
In the technical scheme, after receiving a target transaction carrying a default target basic asset, the node device of the block chain can call an intelligent contract and issue default refund information of the target basic asset to the block chain, so that the escrow bank can realize refund and repurchase of an original beneficiary after monitoring the default refund information, and automatic repurchase of the default basic asset based on the block chain is realized.
In addition, after the rights and interests of the default basic assets are changed, the node equipment of the block chain can issue the related contract agreements of the default basic assets as evidences to the judicial chain for evidence storage through the cross-chain relay, so that the user can trace back the related contract agreements of the default basic assets through the judicial chain, and evidence support is provided for the follow-up possible arbitration prosecution.
Referring to fig. 4, fig. 4 is a schematic diagram of a block chain-based default asset handling system according to an exemplary embodiment of the present disclosure.
The block chain-based default asset processing system comprises: the system comprises a block chain, an asset management platform and an escrow bank system, wherein the asset management platform is in butt joint with the block chain.
The asset management platform is used for deploying intelligent contracts for processing the default assets on the blockchain, and triggering node equipment of the blockchain to execute processing flows of the default assets by issuing target transactions carrying the default target basic assets. Of course, the asset management platform has other functions, such as issuing screening rules of the underlying assets to the blockchain, and the like, and the functions of the asset management platform are only exemplarily illustrated and are not specifically limited.
And the escrow bank system is used for maintaining accounts of original rights beneficiaries and investors, transferring funds and the like. Here, the functions of the escrow bank system are merely exemplary and are not particularly limited.
And the asset management platform, the escrow bank system and the block chain are in butt joint, and the three work together to complete the processing of the default assets.
The method for processing default assets based on block chains provided in the present specification is described in detail below.
Referring to fig. 5, fig. 5 is a flowchart illustrating a block chain-based default asset handling method, which may be applied to a node device of a block chain, according to an exemplary embodiment of the present disclosure, and may include the following steps.
Step 502, the node equipment of the block chain receives a target transaction sent by an asset management platform in the storage life of the securitized asset; wherein the securitized assets are assets issued supporting a base pool of assets as value on the blockchain; the targeted transaction includes a targeted base asset for which a breach has occurred in the pool of base assets during the life of the securitized asset.
Step 504: and responding to the target transaction by the node equipment of the blockchain, calling asset default processing logic in an intelligent contract deployed on the blockchain, and issuing default refund information of the target basic asset to the blockchain, so that after a managed bank system monitors the default refund information, the authorized persons of the target basic asset finish fund refund of the target basic asset from the investment account of the original authorized beneficiary of the target basic asset based on the default refund information.
Step 506: and when acquiring a fund refund record which is issued to the block chain by the bank system and corresponds to the target basic asset, the node equipment of the block chain updates the rights and interests of the target basic asset to the original rights and interests.
The basic assets are not particularly limited in this specification, and may be basic debt assets such as accounts receivable.
The investment account may be an escrow account opened by the original rights beneficiary at an escrow bank.
The securitized assets may refer to securities that are supported by a base asset in a base asset pool as a value, for example, the securitized assets may be bonds, funds, and the like, and the securitized assets are only exemplified and not particularly limited herein.
The basic asset pool may be a set of identifications of a plurality of screened basic assets generated by an intelligent contract on a blockchain. The base assets in the base asset pool may serve as value supports for issuing securitized assets. The base asset pool may be stored in a Storage space (Storage) of a contract account corresponding to the intelligent contract, or may be stored in an account Storage space of a block chain account of an asset manager (e.g., SPV organization). The storage location of the underlying asset pool is not specifically limited herein.
In addition, intelligent contracts for carrying out default asset handling are deployed on the blockchain. In a deployed intelligent contract, asset breach processing logic may be included.
The asset default processing logic is used for determining default refund information of the target basic asset based on the target transaction of the target basic asset carrying default, and issuing the default refund information of the target basic asset to a block chain, so that the escrow bank system completes transfer of refund funds after monitoring the default refund information.
After the intelligent contract is deployed, the asset management platform may issue a platform-constructed target transaction to the blockchain to call the intelligent contract deployed on the blockchain, and complete an operation of issuing the default refund information of the target basic asset to the blockchain.
In specific implementation, when the asset management platform detects that a target default basic asset occurs in a basic asset pool supported by the value of the securitized asset within the storage period of the securitized asset, the asset management platform may construct a target transaction based on the default target basic asset, where the target transaction carries the default target basic asset.
The asset management platform may then publish the target transaction to the blockchain. After receiving the target transaction, the node device of the blockchain may invoke asset breach processing logic of the intelligent contract declaration disposed on the blockchain in response to the target transaction, generate a breach processing event based on the breach refund information of the target base asset, and issue the breach processing event containing the breach refund information of the target base asset to the blockchain. The default handling event is used to cause the escrow bank system to complete a fund refund.
At the time of release, on the one hand, the intelligent contract needs to acquire the default refund information of the default target base asset.
In an alternative obtaining manner, when the asset management platform detects a default of a target basic asset in the basic asset pool during the lifetime of the securitized asset, the asset management platform may determine default refund information (information such as the default refund amount) of the target basic asset. The asset management platform may then construct a target transaction based on the target base asset and the default refund information for the target base asset. The information of the target base asset carried by the target transaction may include: target base asset identification, default refund information for the target base asset, and the like. The intelligent contract may obtain default refund information for the target base asset from the target transaction.
Another optional obtaining manner is that the blockchain stores a base asset identifier and a transaction record of the base asset transaction information, and the identifier of the target base asset carried in the target transaction. The intelligent contract can acquire the identification of the target basic asset carried in the target transaction, then acquires the transaction information corresponding to the identification of the target basic asset in the transaction record of the block chain evidence, and determines default refund information based on the transaction information.
For example, assuming that the transaction information includes a transaction amount and the default refund information includes a default refund amount, the determination of the default refund amount based on the transaction information is exemplarily described below by taking the determination of the default refund amount based on the transaction amount as an example.
Upon implementation, the smart contract may treat the transaction amount as a default refund amount. Alternatively, the intelligent contract may calculate the default refund amount according to the conversion ratio of the agreed-upon transaction amount and the default refund amount of the original equity provider and equity provider contract of the target basic asset (for example, the agreed-upon refund amount of the two contracts is 1.1 times or 0.8 times of the transaction amount).
On the other hand, when issuing, the intelligent contract also needs to initiate the operation of confirming the default of the target basic asset by the authorized persons and the original authorized persons aiming at the default target basic asset, and after the authorized persons and the original authorized persons of the target basic asset finish the operation of confirming the default of the target basic asset, the default refund information of the default target basic asset can be issued to the block chain.
In particular implementations, the smart contract may generate a confirmation event that the target base asset is violated for determination by the stakeholder and the original stakeholder.
When the client deployed on the asset management platform and corresponding to the intelligent contract monitors the confirmation event, the client can remind the authorized persons and the original authorized persons of the target basic asset to carry out default confirmation on the target basic asset. The obligees and the original obligees of the target basic assets can submit default confirmation information to the client after the default confirmation of the target basic assets is carried out.
When the client receives the breach confirmation information (such as a signature for the breached target base asset) submitted by the target base asset's rightful persons and the original rightful persons, the breach confirmation information can be submitted to the smart contract.
And when receiving the default confirmation information, the intelligent contract issues default refund information containing the target basic assets to the block chain.
When the intelligent contract issues default refund information, an event mechanism can be adopted for issuing. The escrow bank system can monitor the default refund information in the form of monitoring events when monitoring the default refund information.
Specifically, the intelligent contract can construct a default handling event based on the default refund information and issue the default handling event containing the default refund information to the blockchain.
In an embodiment of the present specification, a client corresponding to the intelligent contract deployed on the hosted banking system may listen for a default handling event issued on the blockchain. After the escrow bank system monitors the breach handling event, the fund refund of the target underlying asset can be completed to the equiter of the target underlying asset from the investment account of the original equiter of the target underlying asset.
Further, the escrow bank system maintains investment accounts for original rights-beneficiaries of the target base asset, and investment accounts for rights-beneficiaries of the target base asset.
The escrow bank performs fund refund, which comprises the following steps: the escrow bank system transfers the fund refund from the investment account of the original equity beneficiary to the investment account of the equity beneficiary of the target base asset.
After the escrow bank system completes the fund refund, the escrow bank system may submit the fund refund record with the target base asset to the intelligent contract.
When the intelligent contract on the node equipment of the blockchain receives the fund refund record corresponding to the target basic asset, which is issued to the blockchain by the escrow bank system, the obligee of the target basic asset can be updated to the original obligee.
In an alternative update, the equiters information for the target base asset is maintained on the block-link point device. And updating the right beneficiary of the target basic asset maintained on the block chain node equipment to the original right beneficiary by the intelligent contract when the fund refund record corresponding to the target basic asset is obtained.
In another alternative updating mode, the information of the target base asset, which is the rights-holders, is maintained in the asset management platform. In updating the equiter information for the target base asset, the smart contract may generate an equiter update event for updating the equiter of the target base asset to the original equiter.
When the client side of the intelligent contract carried on the asset management platform monitors the right beneficiary updating event, the right beneficiary of the target basic asset maintained on the asset management platform can be updated to the original right beneficiary, and right beneficiary updating success information is submitted to the intelligent contract. After receiving the information of successful update of the obligee, the intelligent contractor can determine that the obliged obligee of the target base asset is updated to the original obligee.
As can be seen from the above description, after receiving a target transaction carrying a default target basic asset, a node device of a block chain may invoke an intelligent contract to issue default refund information of the target basic asset to the block chain, so that a hosting bank monitors the default refund information and then realizes refund and buyback of an original beneficiary, thereby realizing automatic buyback of the default basic asset based on the block chain.
In addition, in the embodiment of the present specification, after the equity beneficiary of the target base asset is updated to the original equity beneficiary, the node device of the blockchain may issue a contract agreement related to the target base asset to the judicial chain for evidence deposit through cross-chain relay. The user can trace back related contract agreements of the default basic assets through the judicial chain, and evidence support is provided for subsequent possible arbitration prosecution.
The inter-link relay can be respectively connected with the block links through the bridging interfaces, and inter-link data synchronization among the block links is completed based on the realized data carrying logic. For example, the cross-link relay may be an Oracle president machine, which is only exemplary and not particularly limited.
Corresponding to the above method embodiments, the present specification also provides embodiments of an apparatus.
Corresponding to the above method embodiments, the present specification also provides an embodiment of a block chain-based default asset handling device. The embodiment of the block chain-based default asset processing device can be applied to electronic equipment. The device embodiments may be implemented by software, or by hardware, or by a combination of hardware and software. Taking a software implementation as an example, as a logical device, the device is formed by reading, by a processor of the electronic device where the device is located, a corresponding computer program instruction in the nonvolatile memory into the memory for operation. From a hardware aspect, as shown in fig. 6, the block chain-based default asset processing apparatus in this specification is a hardware structure diagram of an electronic device in which the apparatus is located, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 6, the electronic device in which the apparatus is located in the embodiment may also include other hardware according to an actual function of the electronic device, which is not described again.
Referring to fig. 7, fig. 7 is a block chain-based default asset handling device according to an exemplary embodiment of the present disclosure. The default asset handling device can be applied to the node equipment of the block chain and can comprise the following modules.
A receiving module 701, configured to receive a target transaction sent by an asset management platform during a lifetime of a securitized asset; wherein the securitized assets are assets issued supporting a base pool of assets as value on the blockchain; the target trade comprises a target base asset for which a breach has occurred in the pool of base assets during a lifetime of the securitized asset;
a calling module 702, configured to, in response to the target transaction, call asset default processing logic in an intelligent contract deployed on the blockchain, and issue default refund information of the target basic asset to the blockchain, so that after a hosted banking system monitors the default refund information, a fund refund of the target basic asset is completed to a stakeholder of the target basic asset from an investment account of an original rights beneficiary of the target basic asset based on the default refund information;
the updating module 703 is configured to update the equity beneficiary of the target basic asset to the original equity beneficiary when acquiring the fund refund record corresponding to the target basic asset, which is issued to the block chain by the escrow bank system.
Optionally, the invoking module 702 generates a confirmation event for determining the breach of contract of the target base asset by the equity beneficiary and the original equity beneficiary of the target base asset, so that the client prompts the equity beneficiary and the original equity beneficiary of the target base asset to perform breach of contract confirmation on the target base asset when monitoring the confirmation event;
and when monitoring the default confirmation information of the target basic asset, which is issued to the blockchain by the client and is confirmed by the target basic asset's rights and interests and the original rights and interests, issuing the default refund information of the target basic asset to the blockchain for deposit evidence.
Optionally, the apparatus further comprises:
the issuing module 704 issues the contract agreement related to the target base asset to the judicial chain for evidence storage through the cross-chain relay after updating the equity beneficiary of the target base asset to the original equity beneficiary.
Optionally, the inter-link relay is an oracle.
Optionally, the investment account is an escrow account opened by the original rights beneficiary at an escrow bank; the securitized assets are bonds or funds; the underlying assets are underlying debt assets.
The systems, devices, modules or units illustrated in the above embodiments may be implemented by a computer chip or an entity, or by a product with certain functions. A typical implementation device is a computer, which may take the form of a personal computer, laptop computer, cellular telephone, camera phone, smart phone, personal digital assistant, media player, navigation device, email messaging device, game console, tablet computer, wearable device, or a combination of any of these devices.
In a typical configuration, a computer includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.
The memory may include forms of volatile memory in a computer readable medium, Random Access Memory (RAM) and/or non-volatile memory, such as Read Only Memory (ROM) or flash memory (flash RAM). Memory is an example of a computer-readable medium.
Computer-readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, 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 Discs (DVD) or other optical storage, magnetic cassettes, magnetic disk storage, quantum memory, graphene-based storage media or other magnetic storage devices, or any other non-transmission medium that can be used to store information that can be accessed by a computing device. As defined herein, a computer readable medium does not include a transitory computer readable medium such as a modulated data signal and a carrier wave.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The terminology used in the description of the one or more embodiments is for the purpose of describing the particular embodiments only and is not intended to be limiting of the description of the one or more embodiments. As used in one or more embodiments of the present specification and the appended claims, the singular forms "a," "an," and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It should also be understood that the term "and/or" as used herein refers to and encompasses any and all possible combinations of one or more of the associated listed items.
It should be understood that although the terms first, second, third, etc. may be used in one or more embodiments of the present description to describe various information, such information should not be limited to these terms. These terms are only used to distinguish one type of information from another. For example, first information may also be referred to as second information, and similarly, second information may also be referred to as first information, without departing from the scope of one or more embodiments herein. The word "if" as used herein may be interpreted as "at … …" or "when … …" or "in response to a determination", depending on the context.
The above description is only for the purpose of illustrating the preferred embodiments of the one or more embodiments of the present disclosure, and is not intended to limit the scope of the one or more embodiments of the present disclosure, and any modifications, equivalent substitutions, improvements, etc. made within the spirit and principle of the one or more embodiments of the present disclosure should be included in the scope of the one or more embodiments of the present disclosure.