CN111383121A

CN111383121A - Asset management method and device based on block chain and electronic equipment

Info

Publication number: CN111383121A
Application number: CN202010479993.0A
Authority: CN
Inventors: 周徽; 陆旭明; 陈锐发
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-05-29
Filing date: 2020-05-29
Publication date: 2020-07-07

Abstract

One or more embodiments of the present specification provide an asset management method, an asset management apparatus, and an electronic device based on a blockchain, which are applied to a node device in a blockchain, and include: receiving an asset rating transaction corresponding to the securitized asset sent by a client; sending the asset rating transaction to other node devices in the blockchain to perform consensus processing on the asset rating transaction; and after the asset rating trading consensus passes, executing contract codes of intelligent contracts called by the asset rating trading stored in the block chain, acquiring asset information of the securitized assets stored in the block chain at the latest moment, and performing asset rating processing on the securitized assets based on a preset asset rating rule and the asset information so as to store asset rating results corresponding to the securitized assets into the block chain.

Description

Asset management method and device based on block chain and electronic equipment

Technical Field

One or more embodiments of the present disclosure relate to the field of blockchain technologies, and in particular, to an asset management method and apparatus based on blockchain, and an electronic device.

Background

The block chain technology, also called distributed ledger technology, is an emerging technology in which several computing devices participate in "accounting" together, and a complete distributed database is maintained together. The blockchain technology has been widely used in many fields due to its characteristics of decentralization, transparency, participation of each computing device in database records, and rapid data synchronization between computing devices.

Disclosure of Invention

The present specification proposes an asset management method based on a block chain; wherein a securitized asset is an asset that is issued on a blockchain with a pool of base assets created based on base assets stored in a blockchain ledger maintained by node devices in the blockchain as value; the method is applied to the node equipment in the block chain and comprises the following steps:

receiving an asset rating transaction corresponding to the securitized asset sent by a client;

sending the asset rating transaction to other node devices in the blockchain to perform consensus processing on the asset rating transaction;

and after the asset rating trading consensus passes, executing contract codes of intelligent contracts called by the asset rating trading stored in the block chain, acquiring asset information of the securitized assets stored in the block chain at the latest moment, and performing asset rating processing on the securitized assets based on a preset asset rating rule and the asset information so as to store asset rating results corresponding to the securitized assets into the block chain.

Optionally, the receiving the asset rating transaction corresponding to the securitized asset sent by the client includes:

and receiving the asset rating transaction which is periodically sent by the client and corresponds to the securitized asset according to a preset time period.

and receiving asset rating trading corresponding to the securitized asset, which is sent by a client when monitoring the asset information of the securitized asset stored in the latest block of the block chain.

Optionally, the asset ranking the securitized asset based on a preset asset ranking rule and the asset information to output an asset ranking report corresponding to the securitized asset, including:

based on a preset asset rating rule, performing asset rating processing on the securitized asset according to the asset information;

pricing the securitized asset based on the asset rating of the securitized asset;

generating an asset rating report corresponding to the securitized asset and storing the asset rating report to the blockchain; wherein the asset rating report includes an asset rating and an issue price for the securitized asset.

Optionally, the asset rating rule is a monte carlo method.

Optionally, the securitized asset is a bond or fund; the underlying assets are underlying debt assets.

The specification also provides an asset management device based on the block chain; wherein a securitized asset is an asset that is issued on a blockchain with a pool of base assets created based on base assets stored in a blockchain ledger maintained by node devices in the blockchain as value; the device is applied to the node equipment in the block chain and comprises the following components:

the receiving module is used for receiving the asset rating transaction which is sent by the client and corresponds to the securitized asset;

the consensus module is used for sending the asset rating transaction to other node equipment in the block chain so as to perform consensus processing on the asset rating transaction;

and the execution module executes contract codes of intelligent contracts called by the asset rating trading after the asset rating trading consensus passes, the contract codes are stored in the block chain, asset information of the securitized assets stored in the block chain at the latest moment is acquired, and the securitized assets are subjected to asset rating processing based on a preset asset rating rule and the asset information so as to store asset rating results corresponding to the securitized assets into the block chain.

Optionally, the receiving module is specifically configured to:

Optionally, the execution module is specifically configured to:

Optionally, the asset rating rule is a monte carlo method.

This specification also proposes an electronic device including:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the steps of the method as described in any one of the above by executing the executable instructions.

The present specification also proposes a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of the preceding claims.

In the above technical solution, when receiving an asset rating transaction sent by a client and corresponding to a securitized asset issued on a blockchain, a node device in the blockchain may invoke an intelligent contract deployed on the blockchain to perform asset rating processing on the securitized asset in response to the asset rating transaction, and store an asset rating result to the blockchain. In this way, the asset rating process of the securitized asset can be automatically executed through the intelligent contract, and the asset rating of the securitized asset can be determined, so that the related information such as the issuance price of the securitized asset can be conveniently determined by using the asset rating.

Drawings

FIG. 1 is a schematic diagram of a creation flow of an intelligent contract shown herein;

FIG. 2 is a schematic diagram illustrating the call flow of an intelligent contract shown in this specification;

FIG. 3 is a schematic diagram of the creation and invocation flow of an intelligent contract shown in the present specification;

FIG. 4 is a schematic diagram of a blockchain-based asset securitization system shown in an exemplary embodiment of the present description;

FIG. 5 is a flow chart of a blockchain-based asset management method shown in an exemplary embodiment of the present description;

fig. 6 is a schematic structural diagram of an electronic device shown in an exemplary embodiment of the present specification;

fig. 7 is a block diagram of an asset management device based on a blockchain in accordance with an exemplary embodiment of the present disclosure.

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 (PrivateBlockchain) 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 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 (MerklePatricia 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.

For most blockchain items, a Merkle tree is typically used; alternatively, the data is stored and maintained based on the data structure of the Merkle tree. Taking etherhouses as an example, the etherhouses use MPT tree (a Merkle tree variation) as a data organization form for organizing and managing important data such as account status, transaction information, and the like.

The Etherhouse designs three MPT trees, namely an MPT state tree, an MPT transaction tree and an MPT receipt tree, aiming at data needing to be stored and maintained in a block chain. In addition to the above three MPT trees, there is actually a Storage tree constructed based on the Storage content of the contract account.

An MPT state tree, which is an MPT tree organized by account state data of all accounts in a blockchain; an MPT transaction tree, which is an MPT tree organized by transaction (transaction) data in a blockchain; the MPT receipt tree is organized into transaction (receipt) receipts corresponding to each transaction generated after the transactions in the block are executed. The hash values of the root nodes of the MPT state tree, the MPT transaction tree, and the MPT receipt tree shown above are eventually added to the block header of the corresponding block.

The MPT transaction tree and the MPT receipt tree correspond to the blocks, namely each block has the MPT transaction tree and the MPT receipt tree. The MPT state tree is a global MPT tree, which does not correspond to a specific tile, but covers account state data of all accounts in the tile chain.

It should be noted that, each time a latest block is generated in the blockchain, after a transaction in the latest block is executed, the account status of the accounts (which may be an external account or a contract account) related to the executed transaction in the blockchain is usually changed;

for example, when a "transfer transaction" is completed in a block, the balances of the transferring party account and the transferring party account associated with the "transfer transaction" (i.e., the field values of the Balance fields of these accounts) are usually changed.

After the transaction in the latest block generated by the blockchain is completed, the node device needs to construct an MPT state tree according to the current account state data of all accounts in the blockchain because the account state in the current blockchain changes, so as to maintain the latest state of all accounts in the blockchain.

That is, each time a latest block is generated in the block chain and the account status in the block chain changes after the transaction in the latest block is completed, the node device needs to reconstruct an MPT status tree based on the latest account status data of all accounts in the block chain. In other words, each block in the block chain has a corresponding MPT state tree; the MPT status tree maintains the latest account status of all accounts in the blockchain after the transaction in the block is completed.

In practical applications, whether public, private, or alliance, it is possible to provide the functionality of a smart contract (smartcontact). 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 may perform 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 byte code, 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 client 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.

The event mechanism of the intelligent contract is a mode for the interaction between the intelligent contract and the out-of-chain entity. For intelligent contracts deployed on blockchains, direct interaction with out-of-chain entities is generally not possible; for example, the intelligent contract cannot generally send the call result of the intelligent contract to the call initiator of the intelligent contract point to point after the call is completed.

The call results (including intermediate results and final call results) generated by the intelligent contract in the call process are usually recorded in the form of events (events) to the transaction log (transaction logs) of the transaction that called the intelligent contract, and stored in the storage space of the node device. The entity outside the chain which needs to interact with the intelligent contract can acquire the calling result of the intelligent contract by monitoring the transaction log stored in the storage space of the node equipment;

for example, in the case of an Etherhouse, the transaction log will eventually be stored in the MPT receipt tree described above as part of the receipt (receipt) of the transaction pen transaction that invoked the smart contract. And the entity outside the chain interacting with the intelligent contract can monitor the transaction receipts stored in the storage space of the node device on the MPT receipt tree and acquire the events generated by the intelligent contract from the monitored transaction receipts.

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 issuing a transaction into the blockchain network by the client, which is performed by a node device in the blockchain in the local 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.

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 issuing a transaction for invoking the intelligent contract into the blockchain network by the client, executing the transaction in the local EVM by the node device in the blockchain, and running a 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.

The specification aims to provide a technical scheme that when an asset rating transaction corresponding to a securitized asset sent by a client is received by a node device in a blockchain, an intelligent contract deployed on the blockchain is called to perform asset rating processing on the securitized asset so as to determine the asset rating of the securitized asset.

In a specific implementation, for a securitized asset, a manager of the securitized asset may initiate an asset rating application for the securitized asset through a client corresponding to the manager to perform an asset rating process on the securitized asset, and the client may send a corresponding asset rating transaction to a node device in a block chain interfaced with the client, so that the node device sends the asset rating transaction to other node devices in the block chain. Each node device in the blockchain may perform consensus processing on the asset rating transaction upon receiving the asset rating transaction. After the consensus is achieved, the node device in the blockchain can respond to the asset rating transaction, execute contract codes of intelligent contracts called by the asset rating transaction and stored in the blockchain, acquire asset information of the securitized asset stored in the blockchain at the latest moment, and perform asset rating processing on the securitized asset based on preset asset rating rules and the asset information.

After the asset rating process by calling the contract code of the intelligent contract is completed, the calling result (called asset rating result) generated in the calling process of the intelligent contract can be recorded to the transaction log of the asset purchase transaction or the contract log of the intelligent contract in the form of an event and stored in the storage space of the node device in the block chain.

Referring to fig. 4, fig. 4 is a schematic diagram of a blockchain-based asset securitization system in accordance with an exemplary embodiment of the present disclosure.

The Asset securitization refers to a process of taking cash flow generated in the future of a basic Asset as repayment support, carrying out credit enhancement through structured design, and issuing Asset-Backed Securities (ABS) on the basis; it is a financing form that issues tradeable securities in favor of a particular portfolio of assets or a particular cash flow.

In summary, the basic process of securitization financing in one complete transaction generally includes: the initiator (i.e., the original beneficiary) may sell the securitable base asset to the manager, or may actively purchase the securitable base asset by the manager; then the management party can collect the basic Assets into a basic asset Pool (Assets Pool), and issues securities financing on the financial market by taking cash flow generated by the basic asset Pool as repayment support; finally, the cash flow generated by the underlying asset pool can be utilized to liquidate the issued securities.

The administrator may be a Special Purpose organization (SPV).

In the block chain-based asset securitization system as shown in fig. 4, the original rights beneficiary can publish the basic assets held by the original rights beneficiary to the block chain for credentialing, and the management party can purchase the basic assets from the original rights beneficiary and assemble the basic assets credentialed in the block chain into a basic asset pool, i.e., create a basic asset pool based on the basic assets.

In particular, the management may enable the creation of a pool of base assets based on these base assets by invoking intelligent contracts deployed on the blockchain. In this case, the base asset pool may be a collection of identifications of several screened base assets generated by the intelligent contract. The set may be stored in an account Storage space (e.g., Storage field) of the contract account corresponding to the intelligent contract, or in an account Storage space of the blockchain account of the administrator.

Subsequently, the manager can issue securitized assets on the blockchain with the base pool as a value support, i.e., future cash flows generated by the base pool are used as reimbursements to support the issuance of securitized assets.

Wherein the basic assets can be basic debt assets (e.g., accounts receivable); the securitized asset may be ABS (e.g., bond or fund); the management party supports the process of issuing the securitized assets on the block chain by using the basic asset pool as a value, and may refer to the process of creating the virtual assets on the block chain, which is not described herein again.

The investor can buy the securitized assets issued by the manager by paying a certain amount of funds to the manager; that is, a manager may fund an investor who purchases the securitized asset by issuing the securitized asset. In one aspect, the manager may make a second investment with funds paid by the investor to obtain a corresponding cash flow, which may be considered the cash flow generated by the underlying asset pool. On the other hand, the manager can pay the investor a certain amount of money from the cash flow as the profit obtained by the investor to purchase the securitized asset, at a rate agreed in advance with the investor.

For example, assuming that the amount of money paid by the investor to purchase the aforementioned securitized asset issued by the manager is 10000 yuan, and the rate agreed by the manager and the investor for the securitized asset is 3.65% (annual profit margin), the manager may pay the investor 1 yuan per day as the profit obtained by the investor to purchase the securitized asset.

It should be noted that, for a securitized asset, the management side of the securitized asset may apply for asset rating of the securitized asset to the asset rating mechanism, and issue an asset rating report corresponding to the securitized asset by the asset rating mechanism, so that the management side of the securitized asset may perform pricing processing on the securitized asset according to the asset rating report to determine the issue price of the securitized asset.

Referring to fig. 5, fig. 5 is a flowchart illustrating a method for blockchain-based asset management according to an exemplary embodiment of the present disclosure. The block chain-based asset management method can be applied to the block chain-based asset securitization system shown in fig. 4, and is used as a node device added to an electronic device of the block chain; the electronic device may be a server, a computer, a mobile phone, a tablet device, a notebook computer, a Personal Digital Assistants (PDAs), and the like, which is not limited in this specification. The block chain-based asset management method may include the steps of:

step 502, receiving an asset rating transaction corresponding to the securitized asset sent by a client;

step 504, sending the asset rating transaction to other node devices in the block chain to perform consensus processing on the asset rating transaction;

step 506, after the asset rating trade consensus passes, executing a contract code of the intelligent contract called by the asset rating trade stored in the block chain, acquiring asset information of the securitized asset stored in the block chain at the latest moment, and performing asset rating processing on the securitized asset based on a preset asset rating rule and the asset information to store an asset rating result corresponding to the securitized asset to the block chain.

In this embodiment, with continued reference to the blockchain-based asset securitization system shown in fig. 4, a client of a manager of the securitized asset (i.e., the manager that issued the securitized asset) (i.e., the client used by the manager) may establish a connection with a certain node device in the blockchain.

For a securitized asset, a manager of the securitized asset can issue asset information (such as asset name, net share value, total asset value, etc.) of the securitized asset to the blockchain for storage through a client corresponding to the manager. In particular, the client may provide the management party with a user interface for uploading asset information of the securitized asset, in which the management party may enter the asset information of the securitized asset; referring to the process of persisting the evidence storing data in the blockchain, after the client acquires the asset information, the asset information can be constructed into a standard transaction format supported by the blockchain, and the constructed transaction is issued to the blockchain for evidence storing, so that the asset information is stored in the blockchain.

In practical applications, the manager of the securitized asset may initiate an asset rating application for the securitized asset through the client to perform an asset rating process on the securitized asset.

Specifically, referring to the aforementioned process of persisting the evidence-storing data in the blockchain, the client corresponding to the management party may construct the asset rating application for the securitized asset initiated by the management party into a standard transaction format supported by the blockchain, and issue the constructed transaction (referred to as an asset rating transaction) to the blockchain for evidence-storing.

In one embodiment, the client may periodically build the asset rating transaction according to a preset time period and issue the asset rating transaction to the blockchain for storage. The time period may be preset by a technician, or may be a default value of a system default, which is not limited in this specification.

In another embodiment shown, data published to the blockchain may be monitored by the client, so that the asset rating transaction may be constructed and published to the blockchain for credentialing when asset information of the securitized asset stored in the latest block of the blockchain is monitored.

That is, the node device in the blockchain interfacing with the client may receive the asset rating transaction first and then send the asset rating transaction to other node devices in the blockchain. Each node device in the blockchain may perform consensus processing on the asset rating transaction upon receiving the asset rating transaction. After agreement is reached, node devices in the blockchain may package the asset rating transaction into blocks in which persistent storage is conducted.

For the asset rating transaction packaged into a block, a node device in the block chain may execute contract code of an intelligent contract called by the asset rating transaction stored in the block chain to perform asset rating processing on the securitized asset in response to the asset rating transaction.

Wherein the contract code of the intelligent contract invoked by the asset rating transaction may be, in particular, program code (e.g., some program methods or functions available for invocation) declared in the intelligent contract that is related to the execution logic for performing the asset rating process on the certified asset; the process of creating and invoking the intelligent contract may refer to the process of creating and invoking the intelligent contract, which is not described herein again.

In an embodiment, when the securitized assets are subjected to the asset ranking process, the asset information of the securitized asset stored in the block chain at the latest time may be acquired, and then the securitized assets may be subjected to the asset ranking process according to the acquired asset information based on an asset ranking rule preset by a technician. Wherein the asset rating rule may specifically be a Monte Carlo Method; the specific steps of the asset rating process for securitized assets based on the monte carlo method may refer to the steps in the related art, and the description is not repeated herein.

In the event that the asset rating of the securitized asset is calculated, the securitized asset may be further priced based on the asset rating to determine an issue price of the securitized asset. Wherein, the issue price of the securitized asset may be the net share of the securitized asset.

Subsequently, an asset rating report corresponding to the securitized asset may be generated and stored to the blockchain. Wherein in the asset rating report, the asset rating and the issuance price of the securitized asset may be recorded.

In this case, the interested party of the securitized asset may query the blockchain for the asset rating report corresponding to the securitized asset, so that the asset rating of the securitized asset and the change in the issue price may be known.

In correspondence with the foregoing embodiments of the blockchain-based asset management method, the present specification also provides embodiments of a blockchain-based asset management apparatus.

The embodiment of the block chain-based asset management device can be applied to the 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 hardware structure diagram of the electronic device where the asset management device based on the block chain is located in this specification is shown, except for the processor, the memory, the network interface, and the nonvolatile memory shown in fig. 6, the electronic device where the device is located in the embodiment may also include other hardware according to the actual function of the asset management based on the block chain, which is not described again.

Referring to fig. 7, fig. 7 is a block diagram of an asset management device based on a block chain according to an exemplary embodiment of the present disclosure. The blockchain-based asset management apparatus 70 may be applied to the electronic device shown in fig. 6, which may join the blockchain as a node device; wherein the securitized asset is an asset issued on the blockchain that supports as value a pool of base assets created based on base assets stored in a blockchain ledger maintained by node devices in the blockchain. The blockchain-based asset management device 70 may include:

a receiving module 701, configured to receive an asset rating transaction sent by a client and corresponding to the securitized asset;

a consensus module 702, configured to send the asset rating transaction to other node devices in the block chain to perform consensus processing on the asset rating transaction;

the execution module 703 is configured to execute a contract code of an intelligent contract called for the asset rating trade stored in the block chain after the asset rating trade consensus passes, acquire asset information of the securitized asset stored in the block chain at the latest moment, and perform asset rating processing on the securitized asset based on a preset asset rating rule and the asset information, so as to store an asset rating result corresponding to the securitized asset to the block chain.

In this embodiment, the receiving module 701 is specifically configured to:

In this embodiment, the executing module 703 is specifically configured to:

In this embodiment, the asset rating rule is a Monte Carlo method.

In this embodiment, the securitized asset is a bond or fund; the underlying assets are underlying debt assets.

The implementation process of the functions and actions of each module in the above device is specifically described in the implementation process of the corresponding step in the above method, and is not described herein again.

For the device embodiments, since they substantially correspond to the method embodiments, reference may be made to the partial description of the method embodiments for relevant points. The above-described embodiments of the apparatus are merely illustrative, wherein the modules described as separate parts may or may not be physically separate, and the parts displayed as modules may or may not be physical modules, may be located in one place, or may be distributed on a plurality of network modules. Some or all of the modules can be selected according to actual needs to achieve the purpose of the solution in the specification. One of ordinary skill in the art can understand and implement it without inventive effort.

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.

Claims

1. An asset management method based on a block chain; wherein a securitized asset is an asset that is issued on a blockchain with a pool of base assets created based on base assets stored in a blockchain ledger maintained by node devices in the blockchain as value; the method is applied to the node equipment in the block chain and comprises the following steps:

2. The method of claim 1, the receiving a client-sent asset rating transaction corresponding to the securitized asset, comprising:

3. The method of claim 1, the receiving a client-sent asset rating transaction corresponding to the securitized asset, comprising:

4. The method of claim 1, wherein the asset ranking of the securitized assets based on preset asset ranking rules and the asset information to publish asset ranking results corresponding to the securitized assets to the blockchain for crediting comprises:

5. The method of claim 1, the asset rating rule being a monte carlo method.

6. The method of claim 1, the securitized asset being a bond or fund; the underlying assets are underlying debt assets.

7. An asset management device based on a blockchain; wherein a securitized asset is an asset that is issued on a blockchain with a pool of base assets created based on base assets stored in a blockchain ledger maintained by node devices in the blockchain as value; the device is applied to the node equipment in the block chain and comprises the following components:

8. The apparatus of claim 7, the receiving module being specifically configured to:

9. The apparatus of claim 7, the receiving module being specifically configured to:

10. The apparatus of claim 7, the execution module to:

11. The apparatus of claim 7, the asset rating rule being a Monte Carlo method.

12. The apparatus of claim 7, the securitized asset being a bond or fund; the underlying assets are underlying debt assets.

13. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

wherein the processor implements the steps of the method of any one of claims 1 to 6 by executing the executable instructions.

14. A computer readable storage medium having stored thereon computer instructions which, when executed by a processor, carry out the steps of the method according to any one of claims 1 to 6.