CN113706087A

CN113706087A - Project management method and device based on block chain and electronic equipment

Info

Publication number: CN113706087A
Application number: CN202010443709.4A
Authority: CN
Inventors: 姚文洲
Original assignee: Zhejiang Jianlian Zhixin Technology Co ltd
Current assignee: Zhejiang Jianlian Zhixin Technology Co ltd
Priority date: 2020-05-22
Filing date: 2020-05-22
Publication date: 2021-11-26

Abstract

The specification provides a project management method and device based on a block chain and electronic equipment, which are applied to a project management system built based on the block chain; the project contracting party and the multi-level project contractor of the target project respectively create project accounts corresponding to the target project in the blockchain; the first level project contractor holding a first level voucher created based on the first level unpaid credit; the method comprises the following steps: receiving a target project yield value uploaded by any target project contractor which is not the first level, and storing the target project yield value to a block chain; in response to a yield confirmation transaction initiated by a superior project contractor of the target project contractor, invoking an intelligent contract, determining a target unpaid credit for the superior project contractor for the target project contractor based on the target project yield, and splitting a target voucher corresponding to the target unpaid credit from vouchers stored in a project account of the superior contractor to store the target voucher to the project account of the target contractor.

Description

Project 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 a method and an apparatus for project management based on a 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 specification provides a project management method based on a block chain, which is applied to a project management system built based on the block chain; the project management system comprises a project contracting party and a multi-level project contracting party of the target project; the project contracting party and the multi-level project contractor respectively create project accounts corresponding to the target project in the blockchain; wherein a project account of a first level project contractor of the multi-level project contractors has stored therein a first level credential created based on a first level unpaid charge of the project contractor for the first level project contractor; the method comprises the following steps:

receiving target project output value data uploaded by any target project contractor in the multi-level project contractors that is not the first level project contractor, and publishing the target project output value data to the blockchain for storage;

in response to a yield confirmation transaction initiated by a superior project contractor of the target project contractor for the target project yield data, invoking credential splitting logic declared in an intelligent contract deployed on the blockchain, determining a target unpaid credit for the superior project contractor for the target project contractor based on the target project yield data, and splitting a target credential corresponding to the target unpaid credit from the superior credential to store the target credential to a project account of the target project contractor; wherein the superior voucher is a voucher stored in a project account of the superior project contractor.

Optionally, the method further comprises:

receiving total project production value data uploaded by the first-level project contractor, and publishing the total project production value data to the block chain for storage;

in response to a yield validation transaction initiated by the project contracting party for the total production value data for the project, invoking voucher creation logic declared in a smart contract deployed on the blockchain, determining a first level of unpaid accounts of the project contracting party for the first level of project contractors based on the total production value data for the project, and creating a first level of vouchers based on the first level of unpaid accounts to store the first level of vouchers to project accounts of the first level of project contractors.

Optionally, the splitting a target voucher corresponding to the target unpaid account from the primary voucher to store the target voucher to a project account of the target project contractor comprises:

determining whether the amount of the target unpaid account exceeds the amount of the upper-level voucher;

if the amount of the target unpaid account does not exceed the amount of the upper-level voucher, splitting a target voucher corresponding to the target unpaid account from the upper-level voucher so as to store the target voucher to a project account of the target project contractor.

Optionally, the method further comprises:

and if the amount of the target unpaid account exceeds the amount of the upper-level voucher, generating a splitting failure event, and outputting a notification message indicating voucher splitting failure when the upper-level project contract monitors the splitting failure event.

Optionally, the yield confirmation transaction comprises a target paid account by a superior project contractor set by the superior project contractor for the target project contractor;

the determining a target unpaid bill of the superior project contractor for the target project contractor based on the target project outcome data comprises:

calculating a difference between the target project yield data and the target paid account and determining a target unpaid account for the target project contractor by the superior project contractor based on the difference.

Optionally, the project management system is a supply chain financial system; the project contracting party or the first level project contractor is a core enterprise in the supply chain financial system; the supply chain financial system further comprises a financial institution; wherein the voucher is for initiating a loan to the financial institution.

Optionally, the method further comprises:

receiving a loan transaction sent by any project contractor needing loan in the multi-stage project contractors, and issuing the loan transaction to the block chain for storage; wherein the loan transaction comprises a preset loan amount;

invoking, in response to the loan transaction, credential creation logic declared in an intelligent contract deployed on the blockchain, to split a loan credential corresponding to the loan amount from credentials stored in project accounts of project contractors for the loan required, to store the loan credential to a blockchain account created by the financial institution in the blockchain, thereby causing the financial institution to deliver a loan to the project contractors for the loan required based on the credit line of the loan credential.

Optionally, the method further comprises:

receiving repayment transaction aiming at the loan voucher sent by the project contracting party, issuing the repayment transaction to the block chain for storage, so that when the financial institution monitors the repayment transaction, the financial institution performs transfer processing from a fund account of the project contracting party to a management account of the financial institution based on the amount of the loan voucher, and removes the loan voucher from a block chain account created in the block chain by the financial institution;

or receiving repayment transactions aiming at the loan vouchers sent by the project contractors needing loan, issuing the repayment transactions to the block chain for storage, so that when the financial institution monitors the repayment transactions, the financial institution transfers the loan vouchers from the fund accounts of the project contractors needing loan to the management accounts of the financial institution based on the limit of the loan vouchers, and transfers the loan vouchers from the block chain accounts established in the block chain by the financial institution to the project accounts of the project contractors needing loan.

The specification also provides a project management device based on the block chain, wherein the device is applied to a project management system built based on the block chain; the project management system comprises a project contracting party and a multi-level project contracting party of the target project; the project contracting party and the multi-level project contractor respectively create project accounts corresponding to the target project in the blockchain; wherein a project account of a first level project contractor of the multi-level project contractors has stored therein a first level credential created based on a first level unpaid charge of the project contractor for the first level project contractor; the device comprises:

a first receiving module, configured to receive target project yield data uploaded by any target project contractor of the multi-level project contractors that is not the first level project contractor, and publish the target project yield data to the block chain for storage;

a splitting module to invoke credential splitting logic declared in an intelligent contract deployed on the blockchain in response to a yield confirmation transaction initiated by a superior project contractor of the target project contractor for the target project yield data, to determine a target unpaid credit for the target project contractor based on the target project yield data, and to split a target credential corresponding to the target unpaid credit from the superior credential to store the target credential to a project account of the target project contractor; wherein the superior voucher is a voucher stored in a project account of the superior project contractor.

Optionally, the apparatus further comprises:

the second receiving module is used for receiving the project total production value data uploaded by the first-level project contractor and publishing the project total production value data to the block chain for storage;

a creation module to invoke voucher creation logic declared in an intelligent contract deployed on the blockchain in response to a yield validation transaction initiated by the project contracting party for the total project yield data, to determine a first level of unpaid accounts of the project contracting party for the first level of project contractors based on the total project yield data, and to create a first level of voucher based on the first level of unpaid accounts to store the first level of voucher to a project account of the first level of project contractors.

Optionally, the splitting module is specifically configured to:

Optionally, the splitting module is further configured to:

the splitting module is specifically configured to:

Optionally, the apparatus further comprises:

the third receiving module is used for receiving loan transactions sent by any project contractor needing loan in the multi-level project contractors and issuing the loan transactions to the block chain for storage; wherein the loan transaction comprises a preset loan amount;

and the loan module is used for responding to the loan transaction, calling voucher creating logic declared in an intelligent contract arranged on the block chain, splitting loan vouchers corresponding to the loan amount from vouchers stored in project accounts of project contractors needing loan, and storing the loan vouchers into block chain accounts created in the block chain by the financial institution so as to enable the financial institution to deliver loan to the project contractors needing loan based on the amount of the loan vouchers.

Optionally, the apparatus further comprises:

the repayment module is used for receiving repayment transactions aiming at the loan vouchers sent by the project contracting party and issuing the repayment transactions to the block chain for storage, so that when the financial institution monitors the repayment transactions, the financial institution transfers the loan vouchers from the fund accounts of the project contracting party to the management accounts of the financial institution based on the amount of the loan vouchers and removes the loan vouchers from the block chain accounts established in the block chain by the financial institution;

or the loan voucher payment transaction is received and issued to the blockchain for storage, so that when the financial institution monitors the payment transaction, the financial institution transfers the loan voucher from the fund account of the project contractor needing loan to the management account of the financial institution based on the amount of the loan voucher, and transfers the loan voucher from the blockchain account created in the blockchain by the financial institution to the project account of the project contractor needing loan.

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 above method by executing the executable instructions.

The present specification also contemplates a computer-readable storage medium having stored thereon computer instructions which, when executed by a processor, implement the steps of the above-described method.

In the above technical solution, when the project contracting party confirms the total project value uploaded by the first-level project contractor in the supply chain financial system, a voucher corresponding to the unpaid account of the project contracting party for the first-level project contractor is generated, and the voucher is split according to the unpaid account of the first-level project contractor for the second-level project contractor, and so on, so that each level of project contractor in the supply chain financial system can obtain a voucher corresponding to the project value which is reported by the project contracting party but is not yet paid. Therefore, the method can ensure that the project contracting party pays the full amount of the unpaid money of the first-level project contractor or the upper-level project contractor for the lower-level project contractor in the engineering project construction, and ensure the basic benefit of the project contractor.

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 project management system shown in an exemplary embodiment of the present specification;

FIG. 5 is a schematic diagram of a project contractor shown in an exemplary embodiment of the present description;

FIG. 6 is a flow chart illustrating a method for blockchain based project management in an exemplary embodiment of the present description;

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

fig. 8 is a block diagram of an item management apparatus based on a blockchain according to an exemplary embodiment of the present specification.

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 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.

Alternatively, the calling result generated by the intelligent contract in the calling process may be recorded in the contract log of the intelligent contract in the form of an event, and stored in the storage space of the node device. And 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 contract log of the intelligent contract stored in the storage space of the node equipment.

Referring to fig. 4, fig. 4 is a schematic diagram of a project management system based on a block chain according to an exemplary embodiment of the present disclosure.

As shown in FIG. 4, the blockchain-based project management system may be a blockchain system consisting of project contractors, project contractors and financial institutions.

The electronic device used by the project contracting party can be used as a node device to be added into the block chain, or the electronic device used by the project contracting party can be connected with the node device in the block chain so as to access the block chain through the node device; likewise, electronic devices used by the project contractor may join the blockchain as node devices, or the electronic devices used by the project contractor may establish a connection with a node device in the blockchain to access the blockchain through the node device; the electronic device used by the financial institution may also join the blockchain as a node device, or the electronic device used by the financial institution may establish a connection with a node device in the blockchain to access the blockchain through the node device. The electronic device may be a server, a computer, a mobile phone, a tablet device, a notebook computer, a palmtop computer (PDAs), or the like, which is not limited in this specification.

In the construction process of an engineering project, project contractors may be contractually entrusted to the construction of the engineering project by project contractors, and project contractors may further contractually hire employees to perform specific work in the construction of the engineering project.

In practical applications, as shown in FIG. 5, the project contractors may be specifically a general term for multi-level project contractors; wherein the first level project contractor may be a general contractor, the second level project contractor may be a plurality of subcontractors, and the third level project contractor may be a materials supplier, a labor company, an equipment supplier, and the like. For a certain project contracted by a general contracting party, the general contracting party can subcontract part of the work in the project to a subcontracting party with corresponding qualifications, and the subcontracting party constructs the project according to the contract agreement of the subcontracting party; the subcontractor can purchase materials from the materials suppliers needed for the construction of the engineering project, can also entrust the labor company to hire employees, perform a portion of the work their undertake in the engineering project by the hired employees, and manage the hired employees by the labor company.

On the one hand, when the construction of the project at a certain stage is completed, the first stage project contractor of the multi-stage project contractors may report the total project value corresponding to the project at the stage to the project contracting party according to the contract agreement, and the project contracting party confirms the total project value reported by the first stage project contractor, for example: the total contracting party (i.e. the first-level project contractor) can report the total project value corresponding to the project constructed in the time period from the previous 1 th to the current 1 st of the month to the project contracting party according to the contract agreement of the contract on 1 st of the month, and the project contracting party confirms the total project value reported by the total contracting party. If the project contracting party confirms the total project value, the project contracting party is indicated that the first stage project contractor should pay the same amount of funds as the total project value as the project money.

On the other hand, any one of the first-level project contractors (referred to as the target contractor) may report the project yield value within a certain period to the previous-level project contractor of the target project contractor according to the contract agreement of the corresponding contract, and the previous-level project contractor may confirm the project yield value reported by the target project contractor, for example: the material supplier (i.e., the third-level project contractor) shown in fig. 5 may report the total value of the materials supplied to the engineering project within the period from the previous 1 th day to the current 1 th day as a project output value on 1 st day per month according to the contract of the supply to the subcontractor (i.e., the second-level project contractor) interfacing with the material supplier, and the subcontractor may confirm the project output value reported from the material supplier. If the superior project contractor confirms the project output, it is indicated that the superior project contractor should pay the target project contractor an amount of money equal to the project output.

Referring to fig. 6, fig. 6 is a flowchart illustrating a block chain based project management method according to an exemplary embodiment of the present disclosure. The project management method based on the block chain can be applied to the project management system shown in FIG. 4, and comprises the following steps:

step 601, receiving target project output value data uploaded by any target project contractor which is not the first-level project contractor in the multi-level project contractor, and publishing the target project output value data to the block chain for storage;

step 602, in response to a yield confirmation transaction initiated by a superior project contractor of the target project contractor for the target project yield data, invoking credential splitting logic declared in a smart contract deployed on the blockchain, determining a target unpaid credit for the target project contractor based on the target project yield data, and splitting a target credential corresponding to the target unpaid credit from the superior credential to store the target credential to a project account of the target project contractor; wherein the superior voucher is a voucher stored in a project account of the superior project contractor.

The technical solution of the present application is described in detail below by taking the above project management system as an example of a supply chain financial system built based on a block chain.

It should be noted that the project management system is a supply chain financial system built based on a block chain, which is only exemplary and is not used to limit the technical solution of the present application; obviously, in practical application, a person skilled in the art can flexibly set up the project management system based on actual requirements.

In the embodiment, the supply chain financial system may include a project contracting party and a multi-stage project contracting party, and may further include a financial institution (e.g., a bank). Wherein the core enterprise in the supply chain financial system may be a project contracting party in the supply chain financial system or a first level project contractor in a multi-level project contractor.

It should be noted that the project contracting parties and the multi-level project contracting parties for establishing the same project belong to the same supply chain financial system; project contractors and project contractors that underwent different engineering projects belong to different supply chain financial systems. That is, there is a correspondence between supply chain financial systems and engineering projects; for a supply chain financial system, the supply chain financial system corresponds to a project underwritten by a project sponsor and a multi-level project contractor therein.

When the operator of the block chain builds a block chain network, the operator can expand the objects supported by the block chain.

In particular, in one aspect, in a conventional blockchain (e.g., an etherhouse), objects supported by the blockchain typically include only two classes, an account object (i.e., an account created by a user in the blockchain) and a contract object (i.e., a smart contract). In this specification, the objects supported by the above block chain may be extended, and a specific object (i.e. the credential in this specification) may be further extended on the basis of the existing account object and contract object. That is, the objects supported by the blockchain may include three classes, an account object, a contract object, and an extended special object.

On the other hand, in a conventional blockchain (e.g., etherhouse), the Balance field (i.e., address field) of an object supported by the blockchain is typically used to indicate the number of tokens held by the object. In this specification, the meaning of the Balance field of the account object supported by the block chain may be extended, and the Balance field may be extended to address information for maintaining a credential held by the object. In practical applications, the Balance field of one account object may maintain address information of multiple credentials.

In this case, the project contractor and the multi-level project contractor in the supply chain financial system may create account objects (referred to as project accounts) corresponding to the project (referred to as target project) built by the block chain after joining the block chain as member nodes of the block chain. For a project contracting party or any project contractor in the supply chain financial system, address information for the vouchers they hold may be stored in the Balance field of their project account.

In this embodiment, the voucher may be used to initiate a loan to a financial institution in the supply chain financial system. The supply chain financial system corresponds to the target project, the voucher corresponds to the target project, and the voucher can only circulate through the supply chain financial system. For a project contractor or any project contractor in the supply chain financial system, the financial institution in the supply chain financial system needs to base the project yield of the target project and the core enterprise's credit to credit it based on the credentials.

The core enterprise in the supply chain financial system (which may also be the operator or a third party of the block chain) may develop an intelligent contract for asset management in advance and declare program code (e.g., some program methods or functions available for invocation) in the intelligent contract that is related to the execution logic of asset management.

The execution logic of asset management may specifically include a credential creation logic for creating a credential, a credential splitting logic for splitting a credential, and the like.

In practical applications, those skilled in the art may declare, based on actual business requirements, execution logic of asset management other than the credential creation logic and the credential splitting logic in the smart contract, which is not particularly limited in this specification.

After the core enterprise completes the development of the intelligent contract, the intelligent contract can be issued in the block chain in a transaction form; after receiving the transaction, the node device in the blockchain may perform consensus on the transaction based on a consensus algorithm supported by the blockchain, and after the consensus passes, record the intelligent contract into the distributed database of the blockchain to complete deployment of the intelligent contract.

After the intelligent contract is deployed in the blockchain, the project contracting party, the multi-level project contracting party and the financial institution in the supply chain financial system can complete operations such as creating and splitting of the certificate by issuing a transaction to the blockchain and calling the execution logic of asset management declared in the intelligent contract.

For a specific process of creating and invoking the intelligent contract, reference may be made to a process of creating and invoking an intelligent contract shown in fig. 1, fig. 2, and fig. 3, which is not described herein again.

In this embodiment, on the one hand, when the construction of the target project at a certain stage is completed, the first-stage project contractor of the multi-stage project contractors may determine the total project production value corresponding to the project at the stage according to the contract agreement, and upload data (referred to as total project production value data) including the total project production value to the node device in the blockchain, and the node device issues the total project production value data to the blockchain for storage. Specifically, referring to the aforementioned process of persisting evidence-storing data in the blockchain, the node device may construct the total item production data into a standard transaction format supported by the blockchain, issue the constructed transaction to the blockchain, perform consensus processing on the transaction by the node device in the blockchain, and after the consensus is achieved, package the transaction into a block by the node device serving as an accounting node in the blockchain, and perform persisted evidence-storing in the blockchain.

The item contracting party can monitor the data stored in the blockchain, so that the transaction comprising the data of the total value of the item can be monitored. When monitoring the transaction, the item contracting party can confirm the total item production value data in the transaction. Specifically, the total project production value data may include, in addition to the total project production value, data such as a project name, a construction progress, and a name of a first-level project contractor, and the project contracting party may confirm the total project production value data based on the data.

When the project packing-out party confirms the project total output value data, the project packing-out party can send the output value confirmation information (i.e. the information indicating that the project packing-out party has confirmed the project total output value data) corresponding to the project total output value data to the node device of the block chain, and the node device issues the output value confirmation information to the block chain for storage. Specifically, referring to the aforementioned process of persisting the evidence-storing data in the blockchain, the node device may construct the yield confirmation information into a standard transaction format supported by the blockchain, issue the constructed transaction (referred to as a yield confirmation transaction) to the blockchain, perform consensus processing on the yield confirmation transaction by the node device in the blockchain, package the yield confirmation transaction into a block by the node device serving as an accounting node in the blockchain after the consensus is achieved, and perform persisted evidence storage in the blockchain.

For the yield confirmation transaction packed into a blockchain, node devices in the blockchain may, in response to the yield confirmation transaction, invoke credential creation logic declared in the intelligent contract deployed on the blockchain, determine unpaid accounts (referred to as first level unpaid accounts) of the project contractors for the first level project contractors based on the total project yield data, and create credentials (referred to as first level credentials) based on the first level unpaid accounts to store the first level credentials to a project account of the first level project contractors, thereby enabling the first level project contractors to hold the first level credentials. Specifically, the amount of the first-level voucher is equal to the amount of the first-level unpaid account; the address information for the first level credentials may be added to the Balance field of the project account for the first level project contractor.

In one illustrated embodiment, an electronic device used by a project contracting party may provide a user interface to the project contracting party in which the project contracting party may enter the amount of paid accounts (referred to as first degree paid accounts) that have been paid to first degree project contractors in a manner other than by vouchers (e.g., cash) and confirm the total value of the project through the user interface. In this case, in the above-mentioned yield confirmation transaction initiated by the item contracting party, in addition to the above-mentioned yield confirmation information, a first-level paid account may be included; further, when determining the first-level unpaid account based on the total item value data, a difference between the total item value and the first-level paid account may be calculated, and the difference may be determined as the first-level unpaid account, that is: the amount of the first-level unpaid account is equal to the total value of the items-the amount of the first-level paid account.

On the other hand, any one of the first-level project contractors (referred to as the target contractor) may determine the project yield in a certain stage according to the contract agreement of the first-level project contractor, upload data including the project yield (referred to as target project yield data) to the node devices in the block chain, and distribute the target project yield data to the block chain for storage. Specifically, referring to the aforementioned process of persisting evidence-storing data in the blockchain, the node device may construct the target project production data into a standard transaction format supported by the blockchain, issue the constructed transaction to the blockchain, perform consensus processing on the transaction by the node devices in the blockchain, package the transaction into a block by the node device serving as an accounting node in the blockchain after the consensus is achieved, and perform persisted evidence-storing in the blockchain.

The previous contractor for the target contractor may monitor the data stored in the blockchain, so as to monitor the transaction including the data of the target project value. The contractor of the previous project can confirm the target project value data in the transaction when monitoring the transaction. Specifically, the target project yield data may include, in addition to the project yield, data such as the name of the project (e.g., material supply), supply volume, and the name of the target project contractor, based on which the superior project contractor may identify the target project yield data.

When the previous-level project contractor confirms the target project output value data, output value confirmation information corresponding to the target project output value data (i.e., information indicating that the previous-level project contractor has confirmed the target project output value data) may be transmitted to the node devices of the blockchain, and the node devices issue the output value confirmation information to the blockchain for storage. Specifically, referring to the aforementioned process of persisting the evidence-storing data in the blockchain, the node device may construct the yield confirmation information into a standard transaction format supported by the blockchain, issue the constructed transaction (referred to as a yield confirmation transaction) to the blockchain, perform consensus processing on the yield confirmation transaction by the node device in the blockchain, package the yield confirmation transaction into a block by the node device serving as an accounting node in the blockchain after the consensus is achieved, and perform persisted evidence storage in the blockchain.

For the yield confirmation transaction packed into a blockchain, the node devices in the blockchain may, in response to the yield confirmation transaction, invoke credential splitting logic declared in the intelligent contract deployed on the blockchain, determine unpaid accounts (referred to as target unpaid accounts) of the above-mentioned upper project contractor for the above-mentioned target project contractor based on the target project yield data, and split credentials (referred to as target credentials) corresponding to the target unpaid accounts from credentials (referred to as upper credentials) stored in project accounts of the upper project contractor to store the target credentials to the project accounts of the target project contractor, thereby enabling the target project contractor to hold the target credentials. Specifically, the amount of the target voucher is equal to the amount of the target unpaid account; the address information for the target voucher may be added to the Balance field of the project account for the target project contractor.

It should be noted that, after the target credential is split from the previous credential, the amount of the separated previous credential is the difference between the amount of the previous credential before the split and the amount of the target credential, that is: and the quota of the split previous-level certificate is the quota of the previous-level certificate before splitting-the quota of the target certificate.

In one illustrated embodiment, the electronic devices used by the superior project contractor may provide the superior project contractor with a user interface in which the superior project contractor may enter the amount of paid accounts (referred to as target paid accounts) that have been paid to the target project contractor in a manner other than by vouchers (e.g., cash) and confirm the project value uploaded by the target project contractor through the user interface. In this case, in the above-mentioned yield confirmation transaction initiated by the upper-level project contractor, in addition to the above-mentioned yield confirmation information, a target paid account may be included; further, when the target unpaid account is determined based on the target item yield data, a difference between the amount of the item yield in the target item yield data and the amount of the target paid account may be calculated, and the difference may be determined as the amount of the target unpaid account, that is: the amount of the target unpaid account is the amount of the item value-the amount of the target paid account.

In one embodiment, when the previous voucher is divided, it may be determined whether the amount of the target unpaid account exceeds the amount of the previous voucher.

If the amount of the target unpaid account does not exceed the amount of the upper-level voucher, the target voucher can be separated from the upper-level voucher so as to store the target voucher to a project account of a target project contractor.

However, if the amount of the target unpaid account exceeds the amount of the upper-level voucher, the voucher cannot be split, and referring to the event mechanism of the intelligent contract, a split failure event may be generated at this time, and the split failure event may be recorded in the transaction log of the yield confirmation transaction or the contract log of the intelligent contract, and stored in the storage space of the node device in the block chain. The upper level project contractor may obtain the splitting failure event by monitoring the transaction log or the contract log stored in the storage space of the node device in the block chain, and may output a notification message indicating that the credential splitting fails to remind the upper level project contractor of failing to complete the payment of the account for the target project contractor.

In practical application, since the first-level project contractor uploads the total project production value data in each stage, a corresponding first-level voucher is created for each stage, and each stage of project contractor can obtain a plurality of vouchers respectively corresponding to different stages, that is, there may be a plurality of vouchers stored in the project accounts of each stage of project contractor.

In this case, when determining whether the amount of the target unpaid account exceeds the amount of the upper voucher, the total amount of all vouchers stored in the project account of the upper project contractor may be counted, and then it is determined whether the amount of the target unpaid account exceeds the total amount, and if not, all vouchers stored in the project account of the upper project contractor may be combined and split.

For example, assume that the second level project contractors of the multi-level project contractors collectively hold 3 credentials (i.e., the number of all credentials stored in the project account of the second level project contractors is 3), which are: a voucher 1 (with an amount of 200 ten thousand yuan) corresponding to a time period of 1 month and 1 day to 2 months and 1 day, a voucher 2 (with an amount of 100 ten thousand yuan) corresponding to a time period of 2 months and 1 day to 3 months and 1 day, and a voucher 3 (with an amount of 150 ten thousand yuan) corresponding to a time period of 3 months and 1 day to 4 months and 1 day; further assuming that the amount of unpaid accounts of the second-level project contractor for the third-level project contractor (i.e., the next-level project contractor of the second-level project contractor) for the time period from 3 month 1 day to 4 month 1 day is 300 ten thousand dollars, then since 200 ten thousand dollars +100 ten dollars +150 ten thousand dollars is 450 ten thousand dollars > 300 ten thousand dollars, the voucher 1 and the voucher 2 can be directly stored into the project account of the third-level project contractor, while the project account of the second-level project contractor only stores the voucher 3, which is equivalent to splitting the voucher 1 and the voucher 2 from the sum of the vouchers 1, 2 and 3; alternatively, the voucher 3 and the voucher 4 (with an amount of 150 ten thousand yuan) separated from the voucher 1 may be stored in a project account of a third-level project contractor, and the divided voucher 1 (with an amount of 50 ten thousand yuan) and the divided voucher 2 may be stored in a project account of a second-level project contractor, which corresponds to separation of the voucher 3 and the voucher 4 from the total of the voucher 1, the voucher 2, and the voucher 3.

In one embodiment, any one of the multi-level project contractors that needs to loan (i.e., any one of the first level project contractor and the target project contractor that needs to loan) may send a loan request including the loan amount to the node devices of the block chain, which issue the loan request to the block chain for storage. Specifically, referring to the aforementioned process of persisting the evidence-holding data in the block chain, the node device may construct the loan request into a standard transaction format supported by the block chain, issue the constructed transaction (referred to as a loan transaction) to the block chain, perform consensus processing on the loan transaction by the node devices in the block chain, and package the loan transaction into a block by the node device serving as an accounting node in the block chain after the consensus is achieved, and perform persistent evidence-holding in the block chain.

For the loan transaction packaged into a block, the node devices in the block chain may invoke, in response to the loan transaction, credential splitting logic declared in an intelligent contract deployed on the block chain, to split out credentials corresponding to the loan amount (referred to as loan credentials) from credentials stored in project accounts of the project contractor, to store the loan credentials to block chain accounts created by the financial institution in the block chain, such that the financial institution may consider unpaid credit with the loan credentials as mortgage, issuing a loan to the project contractor based on the amount of the loan credentials. In particular, the financial institution may conduct a transfer process from the financial institution's administrative account to the project contractor's financial account (e.g., an account provisioned at the financial institution) based on the amount of the loan document.

In practical applications, when the voucher stored in the project account of the project contractor is divided, it may be determined whether the loan amount exceeds the limit of the voucher stored in the project account of the project contractor.

If the loan amount does not exceed the amount of the credentials stored in the project account of the project contractor, the loan credentials corresponding to the loan amount may be split from the credentials stored in the project account of the project contractor to store the loan credentials to the blockchain account created in the blockchain by the financial institution.

However, if the loan amount exceeds the amount of the voucher stored in the project account of the project contractor, the voucher cannot be split, and referring to the event mechanism of the intelligent contract, a loan failure event may be generated, and the loan failure event may be recorded in the transaction log of the loan transaction or the contract log of the intelligent contract and stored in the storage space of the node device in the block chain. The project contractor may obtain the loan failure event by monitoring the transaction log or the contract log stored in the storage space of the node device in the block chain, and may output a notification message indicating that the loan has failed to complete the loan successfully.

In one illustrated embodiment, a repayment transaction for the loan voucher may be initiated by the project issuer. The node device in the blockchain can issue the repayment transaction to the blockchain for storage, so that the financial institution performs transfer processing from a fund account of the project sponsor to a management account of the financial institution based on the amount of the loan voucher when monitoring the repayment transaction, and removes the loan voucher from a blockchain account created in the blockchain by the financial institution.

Alternatively, a repayment transaction for the loan voucher may be initiated by the project contractor who needs the loan and has successfully completed the loan. The node devices in the blockchain may issue the repayment transaction to the blockchain for storage, so that the financial institution may perform a transfer process from the fund account of the project contractor to the management account of the financial institution based on the amount of the loan voucher when monitoring the repayment transaction, and transfer the loan voucher from the blockchain account created by the financial institution in the blockchain to the project account of the project contractor.

In correspondence with the foregoing embodiments of the project management method based on blockchain, the present specification also provides embodiments of project management apparatuses based on blockchain.

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

Referring to fig. 8, fig. 8 is a block diagram of an item management device based on a block chain according to an exemplary embodiment of the present disclosure. The project management device 80 based on the block chain can be applied to the electronic equipment in the project management system based on the block chain building as shown in fig. 7; the project management system comprises a project contracting party and a multi-level project contracting party of the target project; the project contracting party and the multi-level project contractor respectively create project accounts corresponding to the target project in the blockchain; wherein a project account of a first level project contractor of the multi-level project contractors has stored therein a first level credential created based on a first level unpaid charge of the project contractor for the first level project contractor; the block chain-based item management apparatus 80 may include:

a first receiving module 801, configured to receive target project value data uploaded by any target project contractor of the multi-level project contractors that is not the first level project contractor, and publish the target project value data to the block chain for storage;

a split module 802 for invoking credential splitting logic declared in an intelligent contract deployed on the blockchain in response to a yield confirmation transaction initiated by a superior project contractor of the target project contractor for the target project yield data, determining a target unpaid credit for the superior project contractor for the target project contractor based on the target project yield data, and splitting a target credential corresponding to the target unpaid credit from the superior credential to store the target credential to a project account of the target project contractor; wherein the superior voucher is a voucher stored in a project account of the superior project contractor.

In this embodiment, the apparatus 80 further includes:

a second receiving module 803, configured to receive the total project production value data uploaded by the first-level project contractor, and issue the total project production value data to the blockchain for storage;

a creation module 804 for invoking voucher creation logic declared in an intelligent contract deployed on the blockchain in response to a value of production confirmation transaction initiated by the project contracting party for the total production data for the project, determining a first level of unpaid accounts of the project contracting party for the first level of project contractors based on the total production data for the project, and creating a first level of voucher based on the first level of unpaid accounts to store the first level of voucher to a project account of the first level of project contractors.

In this embodiment, the splitting module 802 is specifically configured to:

In this embodiment, the splitting module 802 is further configured to:

In this embodiment, the yield confirmation transaction includes a target paid account by a superior project contractor set by the superior project contractor for the target project contractor;

the splitting module 802 is specifically configured to:

In this embodiment, the project management system is a supply chain financial system; the project contracting party or the first level project contractor is a core enterprise in the supply chain financial system; the supply chain financial system further comprises a financial institution; wherein the voucher is for initiating a loan to the financial institution.

In this embodiment, the apparatus 80 further includes:

a third receiving module 805, configured to receive a loan transaction sent by any one of the multi-level project contractors that needs to loan, and issue the loan transaction to the blockchain for storage; wherein the loan transaction comprises a preset loan amount;

a loan module 806, configured to invoke credential creation logic declared in an intelligent contract deployed on the blockchain in response to the loan transaction, to split a loan credential corresponding to the loan amount from credentials stored in project accounts of project contractors requiring loan, to store the loan credential to a blockchain account created by the financial institution in the blockchain, so that the financial institution issues a loan to the project contractors requiring loan based on the amount of the loan credential.

In this embodiment, the apparatus 80 further includes:

a repayment module 807 for receiving the repayment transaction sent by the item issuer for the loan voucher and issuing the repayment transaction to the blockchain for storage, so that when the financial institution monitors the repayment transaction, the financial institution performs a transfer process from the fund account of the item issuer to the management account of the financial institution based on the amount of the loan voucher and removes the loan voucher from the blockchain account created in the blockchain by the financial institution;

In this embodiment, the voucher is used to initiate a financing loan to the financial institution.

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. A project management method based on a block chain is applied to a project management system built based on the block chain; the project management system comprises a project contracting party and a multi-level project contracting party of the target project; the project contracting party and the multi-level project contractor respectively create project accounts corresponding to the target project in the blockchain; wherein a project account of a first level project contractor of the multi-level project contractors has stored therein a first level credential created based on a first level unpaid charge of the project contractor for the first level project contractor; the method comprises the following steps:

2. The method of claim 1, further comprising:

3. The method of claim 1, the splitting a target voucher corresponding to the target unpaid credit from a previous voucher to store the target voucher to a project account of the target project contractor, comprising:

4. The method of claim 3, further comprising:

if the amount of the target unpaid account exceeds the amount of the upper level voucher, the upper level voucher is stored to a project account of the target project contractor, a payment incomplete event is generated, and a notification message indicating that the payment for the target project contractor is incomplete is output when the upper level project contractor monitors the payment incomplete event.

5. The method of claim 1, the yield confirmation transaction comprising a target paid charge by a superior project contractor set by the superior project contractor for the target project contractor;

6. The method of claim 1, the project management system being a supply chain financial system; the project contracting party or the first level project contractor is a core enterprise in the supply chain financial system; the supply chain financial system further comprises a financial institution; wherein the voucher is for initiating a loan to the financial institution.

7. The method of claim 6, further comprising:

8. The method of claim 7, further comprising:

9. A project management device based on a block chain is applied to a project management system built based on the block chain; the project management system comprises a project contracting party and a multi-level project contracting party of the target project; the project contracting party and the multi-level project contractor respectively create project accounts corresponding to the target project in the blockchain; wherein a project account of a first level project contractor of the multi-level project contractors has stored therein a first level credential created based on a first level unpaid charge of the project contractor for the first level project contractor; the device comprises:

10. The apparatus of claim 9, the apparatus further comprising:

11. The apparatus of claim 9, the splitting module to:

12. The apparatus of claim 11, the splitting module further to:

13. The apparatus of claim 9, the yield confirmation transaction comprising a target paid payment by a superior project contractor set by the superior project contractor for the target project contractor;

the splitting module is specifically configured to:

14. The apparatus of claim 9, the project management system being a supply chain financial system; the project contracting party or the first level project contractor is a core enterprise in the supply chain financial system; the supply chain financial system further comprises a financial institution; wherein the voucher is for initiating a loan to the financial institution.

15. The apparatus of claim 14, the apparatus further comprising:

16. The apparatus of claim 15, the apparatus further comprising:

17. An electronic device, comprising:

a processor;

a memory for storing processor-executable instructions;

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

18. 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 8.