CN112150157B

CN112150157B - Method and device for issuing receivable certificate through block chain

Info

Publication number: CN112150157B
Application number: CN202011338150.5A
Authority: CN
Inventors: 张宇航; 杨俊�
Original assignee: Alipay Hangzhou Information Technology Co Ltd
Current assignee: Alipay Hangzhou Information Technology Co Ltd
Priority date: 2020-11-25
Filing date: 2020-11-25
Publication date: 2021-03-02
Anticipated expiration: 2040-11-25
Also published as: CN112967055A; CN112150157A

Abstract

The embodiment of the specification provides a method for issuing receivable vouchers through a blockchain, wherein intelligent contracts are deployed in the blockchain, issuing logic for the receivable vouchers is included, the logic relates to a plurality of role parties and at least comprises a holder of the receivable vouchers, and the method is executed by a first entity corresponding to any role party; the method comprises the following steps: obtaining issue data including identification information of a plurality of entities corresponding to the plurality of persona parties and a plurality of credential shares held by a plurality of entities corresponding to the holding party; encrypting the issuing data by using a first private key to obtain a first digital signature; forming a first data package based on the first digital signature and the release data; and based on the first data packet, sending a first calling request to a first node in the blockchain network for calling the issuing logic of the intelligent contract, so that each node in the blockchain network executes the issuing logic based on the first data packet, and thus, the issuing data is recorded in the blockchain.

Description

Method and device for issuing receivable certificate through block chain

Technical Field

One or more embodiments of the present disclosure relate to the field of computer technologies, and in particular, to a method and an apparatus for issuing receivable vouchers through a blockchain, a method and an apparatus for transferring shares of receivable vouchers through a blockchain, a method and an apparatus for financing through a blockchain, a method and an apparatus for invalidating shares of receivable vouchers through a blockchain, a method and an apparatus for invalidating receivable vouchers through a blockchain, and a method for performing circulation processing on receivable vouchers through a blockchain.

Background

With the development of society, more and more service entities promote the service level of the service entities through various cooperation or cooperation modes, so that the user experience is improved. For example, an upstream enterprise in the supply chain provides raw materials to a downstream enterprise, the downstream enterprise manufactures goods by using the raw materials for users, and the downstream enterprise promises to pay the payment of the raw materials to the upstream enterprise within a preset period, so that the downstream enterprise can have more sufficient time to manufacture and produce the goods meeting the requirements of the users, and the user experience is improved. In the cooperation process, the service entity determines whether the appointed affair is real and effective, if both parties respectively hold a word, the information provided by the party is effective, the quality and the completeness of cooperation are influenced, and the service provided by the entity to the user is influenced if the service entity of cooperation is influenced.

Therefore, a method is needed to improve the security and reliability of related business data in the process of the collaboration of the service entities, ensure the smooth operation of the business, and further improve the trust and user experience of the service entities.

Disclosure of Invention

One or more embodiments of the present specification describe a method and a corresponding apparatus for performing service processing related to a certificate to be received through a blockchain, and by using the method and the apparatus, security and reliability of related service data can be improved, and a trust level of a service entity for cooperation is improved, thereby improving user experience.

According to a first aspect, there is provided a method of issuing vouchers receivable through a blockchain, the blockchain having deployed therein an intelligent contract comprising issuing logic for vouchers, the issuing logic involving a plurality of personas including at least a holder of the vouchers, the method being performed by a first entity to which either persona corresponds; the method comprises the following steps: obtaining issue data including identification information of a plurality of entities corresponding to the plurality of persona parties and a plurality of credential shares held by a plurality of entities corresponding to the holding party; encrypting the issuing data by using a first private key to obtain a first digital signature; forming a first data package based on the first digital signature and the release data; and based on the first data packet, issuing a first calling request to a first node in the blockchain network for calling the issuing logic of the intelligent contract, so that each node in the blockchain network executes the issuing logic based on the first data packet, and the issuing data is recorded in the blockchain.

In one embodiment, the plurality of persona parties further includes at least one of: the issuing party, the guarantee party, the clearing and distributing party of the receivable voucher and the platform party providing issuing service; wherein the smart contract is created by the platform side.

In a specific embodiment, when the first entity corresponds to the issuer, the acquiring the issue data includes: acquiring the input information of the issuer aiming at the receivable certificate; obtaining the issuing data according to the input information; when the first entity corresponds to the platform side, the obtaining of the issue data comprises: receiving the release data from the issuer; when the first entity corresponds to a party other than the issuer and the platform, the obtaining of the issue data includes: and receiving the issuing data forwarded by the platform side.

In one embodiment, the release data further comprises at least one of: the exchange relationship between the certificate to be received and the resource outside the chain, the date of the corresponding cashing of the certificate to be received, and the issue of the certificate to be received.

In one embodiment, the issuing logic comprises: verifying the first digital signature using the release data and a first public key corresponding to the first private key; judging whether a plurality of digital signatures corresponding to the plurality of entities pass verification; if both pass the verification, the issue data is recorded in the blockchain.

In one embodiment, the first data packet further includes a first public key corresponding to the first private key.

In one embodiment, the first invocation request corresponds to a first transaction, and the data fields of the first transaction include the following variable assignment information: assigning the identifier of each entity in the plurality of entities to the entity identifier variable of the corresponding role party; assigning the plurality of credential shares to a plurality of holding share variables corresponding to the plurality of entities.

According to a second aspect, there is provided a method for transferring a share of a receivable voucher through a blockchain, the blockchain having deployed therein an intelligent contract comprising transfer logic for the share of the receivable voucher, the transfer logic involving a transferor and a transferee, the method being performed by a second entity to which either of the parties corresponds; the method comprises the following steps: acquiring transfer data, wherein the transfer data comprises an entity identifier of the transfer party, an entity identifier of the transferee and a transfer share transferred to the transferee by the transfer party based on the held share of the transfer party for the first receipt; encrypting the transfer data by using a second private key to obtain a second digital signature; forming a second data package based on the second digital signature and the assignment data; and sending a second calling request to a second node in the blockchain network based on the second data packet, wherein the second calling request is used for calling the transfer logic of the intelligent contract, so that each node in the blockchain network executes the transfer logic based on the second data packet, and the transfer data is recorded in the blockchain.

In one embodiment, when the second entity corresponds to the transfer-out party, the acquiring transfer data comprises: acquiring roll-out information input by the roll-out party based on the first receipt; obtaining the assignment data according to the transfer-out information; when the second entity corresponds to the transferee, the acquiring transfer data comprises: and receiving transfer data forwarded by a platform side providing transfer service, wherein the intelligent contract is created by the platform side.

In one embodiment, the assignment logic comprises: verifying the second digital signature using the assignment data and a second public key corresponding to the second private key; judging whether the digital signatures corresponding to the roll-out party and the transferee both pass verification; and if the transfer data passes the verification, updating the holding shares of the transferor and the transferee according to the transfer data.

In one embodiment, the second data packet further includes a second public key corresponding to the second private key.

In a specific embodiment, the second invocation request corresponds to a second transaction, and the data field of the second transaction includes the following variable assignment information: respectively assigning the entity identifications of the roll-out party and the roll-in party to a roll-out entity identification variable and a roll-in entity identification variable; assigning the transfer share to a transfer share variable; the updating of the holding shares of the transferor and the transferee according to the transfer data comprises: updating the holding share variable corresponding to the transfer party into a difference value between the original variable value and the variable value of the transfer share variable; and updating the holding share variable corresponding to the transfer party into a sum value between the original variable value and the variable value of the transfer share variable.

According to a third aspect, a method for financing through a blockchain is provided, wherein an intelligent contract is deployed in the blockchain, the intelligent contract comprises financing logic for financing based on a certificate to be collected, the financing logic relates to an applicant and a sponsor, and the method is executed by a third entity corresponding to any party; the method comprises the following steps: acquiring financing data, wherein the financing data comprises an entity identifier of the applicant, an entity identifier of the sponsor and financing share of financing applied to the sponsor by the applicant based on the holding share of the first acceptance certificate of the applicant; encrypting the financing data by using a third private key to obtain a third digital signature; forming a third data package based on the third digital signature and the financing data; and based on the third data packet, sending a third call request to a third node in the blockchain network, wherein the third call request is used for calling the financing logic of the intelligent contract, so that each node in the blockchain network executes the financing logic based on the third data packet, and the financing data is recorded in the blockchain.

In one embodiment, when the third entity corresponds to the claimant, the obtaining financing data comprises: acquiring financing information input by the applicant based on the first receipt certificate; obtaining the financing data according to the financing information; when the third entity corresponds to the sponsor, the acquiring financing data comprises: and receiving financing data forwarded by a platform side providing financing service, wherein the intelligent contract is created by the platform side.

In one embodiment, the financing logic comprises: verifying the third digital signature using the financing data and a third public key corresponding to the third private key; judging whether the digital signatures corresponding to the applicant and the financing party pass verification or not; and if the data passes the verification, updating the holding shares of the applicant and the financing party according to the financing data.

In one embodiment, the third invocation request corresponds to a third transaction, and the data field of the third transaction includes the following variable assignment information: respectively assigning the entity identifications of the applicant and the sponsor to an application entity identification variable and a funding entity identification variable; assigning the financing share to a financing share variable; the updating of the holding shares of the applicant and the financing party according to the financing data comprises: updating the holding share variable corresponding to the applicant to be the difference value between the original variable value and the variable value of the financing share variable; and updating the holding share variable corresponding to the fund producer to be the sum value between the original variable value and the variable value of the financing share variable.

In one embodiment, the intelligent contract is created by a platform party, the financing data further comprising a financing service share paid by the applicant to the platform party.

In a particular embodiment, the financing logic comprises: verifying the third digital signature using the financing data and a third public key corresponding to the third private key; judging whether the digital signatures corresponding to the applicant and the financing party pass verification or not; and if the data passes the verification, updating the holding shares of the applicant party, the financing party and the platform party according to the financing data.

In a more specific embodiment, the third invocation request corresponds to a third transaction, and the data field of the third transaction includes the following variable assignment information: respectively assigning the entity identifications of the applicant and the sponsor to an application entity identification variable and a funding entity identification variable; assigning the financing share to a financing share variable; assigning the financing service share to a financing service share variable; updating the holding shares of the applicant party, the financing party and the platform party according to the financing data comprises the following steps: updating the holding share variable corresponding to the applicant to be a difference value obtained by respectively subtracting the variable values of the financing share variable and the financing service share variable from the original variable value; updating the holding share variable corresponding to the funder to be the sum value between the original variable value and the variable value of the financing share variable; and updating the holding share variable corresponding to the platform side into a sum value between the original variable value and the variable value of the financing service share variable.

In one embodiment, the third data packet further includes a third public key corresponding to the third private key.

According to a fourth aspect, there is provided a method for invalidating a receivable credential share through a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract includes share invalidation logic for a receivable credential, the share invalidation logic relates to an inventory party, and the method is performed by an inventory entity corresponding to the inventory party, and includes: determining that a first holding entity of the receivable certificate obtains an off-link resource corresponding to a first quota; acquiring share invalid data, wherein the share invalid data comprises the first share and an entity identifier corresponding to the first holding entity; based on the share invalid data, issuing a fourth call request to a fourth node in the blockchain network for calling the share invalid logic of the intelligent contract, so that each node in the blockchain network executes the share invalid logic based on the share invalid data, thereby recording the first share as invalid in the blockchain.

In one embodiment, the determining that the first holding entity of the receivable certificate acquires the off-chain resource corresponding to the first quota includes: receiving a resource transfer message indicating that an issuing entity has transferred an off-link resource corresponding to the total amount of the receivable documents to an off-link account of the liquidation entity; and allocating a part of the resources corresponding to the first quota in the out-of-chain resources to the first holding entity based on the resource transfer-in message.

In a specific embodiment, obtaining the share invalid data comprises: generating the share invalid data after the allocating to the first owning entity.

According to a fifth aspect, there is provided a method for invalidating receivable credentials by a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract includes credential invalidation logic for the receivable credentials, the credential invalidation logic relates to a platform side, the method is performed by a platform entity corresponding to the platform side, and the platform entity is a node in a blockchain network; the method comprises the following steps:

generating an inquiry transaction for inquiring whether each certificate share of the receivable certificates recorded in the block chain is valid; and if the certificate shares are invalid, generating a target transaction for calling the certificate invalidation logic of the intelligent contract, so that each node in the block chain network executes the certificate invalidation logic, and the receivable certificate is recorded as global invalid in the block chain.

According to a sixth aspect, there is provided a method for performing circulation processing on receivable certificates through a blockchain, where the circulation processing includes a plurality of links, an intelligent contract is deployed in the blockchain, the intelligent contract includes first processing logic corresponding to an arbitrary first link, the first processing logic relates to a plurality of actors, the method includes first processing for the first link and is executed by a fourth entity corresponding to any actor, and the first processing includes:

acquiring link data corresponding to the first link, wherein the link data comprises identification information of a plurality of entities corresponding to the plurality of role parties and circulation information of the certificate to be received in the first link; encrypting the link data by using a fourth private key to obtain a fourth digital signature; forming a fourth data packet based on the fourth digital signature and the link data; and sending a fourth calling request to a fourth node in the blockchain network based on the fourth data packet, wherein the fourth calling request is used for calling the first processing logic of the intelligent contract, so that each node in the blockchain network executes the first processing logic based on the fourth data packet, and the link data is recorded in the blockchain.

According to a seventh aspect, there is provided an apparatus for issuing receivables via a blockchain, the blockchain having deployed therein an intelligent contract comprising issuing logic for receivables, the issuing logic involving a plurality of personals including at least a holder of the receivables, the apparatus being integrated with a first entity corresponding to any persona; the device comprises:

a data acquisition unit configured to acquire issue data including identification information of a plurality of entities corresponding to the plurality of persona parties and a plurality of credential shares held by a plurality of entities corresponding to the holding party; the digital signature unit is configured to encrypt the issuing data by using a first private key to obtain a first digital signature; a packet forming unit configured to form a first packet based on the first digital signature and the issue data; and the calling unit is configured to issue a first calling request to a first node in the blockchain network based on the first data packet, and the first calling request is used for calling the issuing logic of the intelligent contract, so that each node in the blockchain network executes the issuing logic based on the first data packet, and the issuing data is recorded in the blockchain.

According to an eighth aspect, there is provided an apparatus for transferring a share of a receivable certificate through a blockchain, the blockchain having disposed therein an intelligent contract comprising transfer logic for the share of the receivable certificate, the transfer logic involving a transferor and a transferee, the apparatus being integrated with a second entity to which either of the transferor and the transferee corresponds; the device comprises:

a data acquisition unit configured to acquire transfer data including an entity identifier of the transferor, an entity identifier of the transferee, and a transfer share to be transferred to the transferee based on a held share of the transferor for the first receipt; the digital signature unit is configured to encrypt the assignment data by using a second private key to obtain a second digital signature; a data package forming unit configured to form a second data package based on the second digital signature and the assignment data; and the calling unit is configured to issue a second calling request to a second node in the blockchain network based on the second data packet, and the second calling request is used for calling the transfer logic of the intelligent contract, so that each node in the blockchain network executes the transfer logic based on the second data packet, and the transfer data is recorded in the blockchain.

According to a ninth aspect, there is provided a device for financing through a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract comprises financing logic for financing based on a certificate to be collected, the financing logic relates to an applicant and a sponsor, and the device is integrated with a third entity corresponding to any one of the two parties; the device comprises:

the data acquisition unit is configured to acquire financing data, wherein the financing data comprises an entity identifier of the applicant, an entity identifier of the sponsor and a financing share of financing applied to the sponsor by the applicant based on the holding share of the first application receipt; the digital signature unit is configured to encrypt the financing data by using a third private key to obtain a third digital signature; a data packet forming unit configured to form a third data packet based on the third digital signature and the financing data; and the calling unit is configured to send a third calling request to a third node in the blockchain network based on the third data packet, and the third calling request is used for calling the financing logic of the intelligent contract, so that each node in the blockchain network executes the financing logic based on the third data packet, and the financing data is recorded in the blockchain.

According to a tenth aspect, there is provided an apparatus for invalidating a credential receivable share through a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract comprises share invalidation logic for a credential receivable, the share invalidation logic relates to an inventory party, and the apparatus is integrated with an inventory entity corresponding to the inventory party, and includes: the determining unit is configured to determine that the first holding entity of the receivable certificate obtains the off-chain resource corresponding to the first quota; the data acquisition unit is configured to acquire share invalid data, wherein the share invalid data comprises the first share and an entity identifier corresponding to the first holding entity; and the calling unit is configured to issue a fourth calling request to a fourth node in the blockchain network based on the share invalid data, and the fourth calling request is used for calling share invalid logic of the intelligent contract, so that each node in the blockchain network executes the share invalid logic based on the share invalid data, and the first share is recorded as invalid in the blockchain.

According to an eleventh aspect, there is provided an apparatus for invalidating receivable credentials by a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract includes credential invalidation logic for the receivable credentials, the credential invalidation logic relates to a platform side, the apparatus is integrated with a platform entity corresponding to the platform side, and the platform entity is a node in a blockchain network; the device comprises:

the inquiry transaction generating unit is configured to generate inquiry transactions for inquiring whether the certificate shares of the receivable certificates recorded in the block chain are valid or not; and the target transaction generating unit is configured to generate a target transaction for calling the certificate invalidation logic of the intelligent contract if the certificate shares are invalid, so that each node in the block chain network executes the certificate invalidation logic, and the receivable certificate is recorded as global invalid in the block chain.

According to a twelfth aspect, an apparatus for performing flow processing on a receipt through a blockchain is provided, where the flow processing includes a plurality of links, an intelligent contract is deployed in the blockchain, the intelligent contract includes first processing logic corresponding to an arbitrary first link, the first processing logic relates to a plurality of role parties, the apparatus is integrated in a fourth entity corresponding to an arbitrary role party, and the apparatus implements the first processing on the first link by:

a data obtaining unit, configured to obtain link data corresponding to the first link, where the link data includes identification information of a plurality of entities corresponding to the plurality of role parties and circulation information of the receivable certificate in the first link; the digital signature unit is configured to encrypt the link data by using a fourth private key to obtain a fourth digital signature; a packet forming unit configured to form a fourth packet based on the fourth digital signature and the link data; and the calling unit is configured to issue a fourth calling request to a fourth node in the blockchain network based on the fourth data packet, and the fourth calling request is used for calling the first processing logic of the intelligent contract, so that each node in the blockchain network executes the first processing logic based on the fourth data packet, and the link data is recorded in the blockchain.

According to a thirteenth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed in a computer, causes the computer to perform the method of any of the first to sixth aspects.

According to a fourteenth aspect, there is provided a computing device comprising a memory and a processor, wherein the memory has stored therein executable code, and the processor, when executing the executable code, implements the method of any of the first to sixth aspects.

According to the method and the device provided by the embodiment of the specification, the circulation data of the certificate to be received is recorded in the block chain, so that the circulation data cannot be tampered, and the authenticity and the validity of the circulation data are guaranteed.

Drawings

In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.

FIG. 1A is a schematic diagram of a process for creating an intelligent contract in a blockchain network;

FIG. 1B is a schematic diagram of a process for invoking the intelligent contract created in FIG. 1A in a blockchain network;

FIG. 2 is a schematic diagram illustrating an implementation scenario of an embodiment disclosed herein;

FIG. 3 illustrates a flow diagram of a method for issuing receivables through a blockchain in one embodiment;

FIG. 4 illustrates a flow diagram of a method for transferring accounts receivable shares through a blockchain in one embodiment;

FIG. 5 illustrates a flow diagram of a method for financing by blockchain in one embodiment;

FIG. 6 illustrates a flow diagram of a method for invalidating accounts receivable credential shares by blockchain in one embodiment;

FIG. 7 illustrates a flow diagram of a method for invalidating receivables by blockchain in one embodiment;

FIG. 8 illustrates a flow diagram of a method for flow processing of the corresponding receipts via a blockchain in one embodiment;

FIG. 9 is a diagram illustrating an exemplary architecture of a device for issuing receivables via a blockchain in one embodiment;

FIG. 10 illustrates a block diagram of an apparatus for transferring accounts receivable shares via a blockchain in one embodiment;

FIG. 11 illustrates a block diagram of an apparatus for financing by blockchain in one embodiment;

FIG. 12 is a block diagram illustrating an apparatus for invalidating entitled shares via blockchains in one embodiment;

FIG. 13 is a block diagram illustrating an exemplary embodiment of a device for invalidating receivables via a blockchain;

fig. 14 is a schematic diagram illustrating an apparatus for performing a flow process on a corresponding voucher through a blockchain in one embodiment.

Detailed Description

The scheme provided by the specification is described below with reference to the accompanying drawings.

As mentioned above, in the process of the existing collaboration of multiple service entities, the service entities store the related service data, and if any one or more parties tamper the stored data, fraud is performed, which will result in difficulty in distinguishing true and false and cause loss of funds, time, etc. of the victim. In view of this, in the embodiments of the present specification, it is proposed to record and store the service data by using a block chain technology and an intelligent contract, so that the service data is traceable and is not falsifiable, and the validity is guaranteed.

As known to those skilled in the art, a blockchain network is a distributed storage and recording system, which includes a plurality of nodes, and each node can communicate transaction data with each other, where a transaction Tx is a basic storage unit in a block, and various data to be stored in a chain is generally recorded in the form of a transaction Tx as a carrier. In the current mainstream blockchain, one block can store hundreds of transactions. It should be noted that a node referred to herein, which may also be referred to as a full node or accounting node, is a computing device that may generate new blocks and link the blocks based on the transaction Tx. Typically, the blockchain network may be a federation chain, in which a plurality of organizations are agreed as accounting nodes, and the transactions to be recorded next are agreed by agreed consensus mechanisms, such as PoS equity certification agreement, bft (byzantine Fault tolerance agreement), etc., and the transaction contents are packaged into blocks and mounted on the blockchain.

Further, more and more blockchain networks support intelligent contracts, thereby enabling richer functionality in blockchains. An intelligent contract is program logic that can be automatically executed, and is written into a blockchain in a digital form after being issued or created, and is executed by each node in the blockchain network.

FIG. 1A is a schematic diagram of a process for creating an intelligent contract in a blockchain network. More specifically, FIG. 1A is described in connection with an Etherhouse. Suppose a node, Bob wants to issue a piece of smart Contract 1, which contains operations on variables x, y. Bob may issue the contract in the form of a transaction. Specifically, Bob can initiate a transaction Tx, the from field of the initiator in the transaction content is Bob (more specifically, the address of Bob), and the to field of the receiver is set to null; the transaction content also includes a Data field containing a code after compiling the intelligent contract into byte codes. After Bob publishes such a transaction to the blockchain network, the accounting node adds it to the blockchain through a consensus mechanism. In this process, a contract address, such as 0x6f …, is also assigned to the smart contract according to an algorithm, such as hashing based on the publisher address. Thus, an intelligent contract corresponds to a contract address, which is not formally different from the user's account address.

After the above intelligent contract is packed and linked, the user in the blockchain network can call the intelligent contract. Fig. 1B is a schematic diagram of a process for invoking the intelligent contract created in fig. 1A in a blockchain network. Assuming that Alice in the blockchain network wants to invoke the above intelligent contract, the node can initiate a transaction to make the contract invocation.

Specifically, in the transaction content, the from field may be the address of the caller Alice, and the to field is the contract address 0x6f … of the intelligent contract, which represents the intelligent contract invoked by the transaction. In the Data field, the method or function name in the contract to be called and the incoming parameters, e.g., the value x0 of variable x, are contained. After other nodes receive the transaction, the virtual machine in the node executes the operation corresponding to the contract logic, and realizes the change of the contract state on the network through a consensus mechanism, including the change of the variable value in the contract. When any node in the network looks at the variable of the contract, it finds that the value of the variable x in the contract becomes x 0.

Based on the above characteristics of the blockchain and the intelligent contract, in the embodiment of the present specification, cooperation or cooperation between the service entities is realized by the intelligent contract. Specifically, mapping resources outside the blockchain (such as currency, cloud storage space, traffic, and the like) into the blockchain to obtain the receivable vouchers implemented based on the blockchain token mechanism, for example, mapping accounts payable (such as 1000 ten thousand) generated by an enterprise in the supply chain against an upstream provider in a real trade context to the blockchain to obtain the receivable vouchers with a total amount of 1000. Thus, the issuance (or issuance) of the receivable certificate can be realized. Further, in correspondence with the business of off-chain resource transfer, financing, liquidation, and the like, transfer of the voucher to be received, application for financing, destruction of the voucher, and the like may be performed on the blockchain.

For ease of understanding, the combination of uplink and downlink traffic will be described below. Fig. 2 is a schematic diagram of an implementation scenario of an embodiment disclosed in this specification, in which an entity D (platform side) creates an intelligent contract, and deploys the intelligent contract in a blockchain to provide issuing services, transfer services, financing services, liquidation services, and the like of receivable vouchers implemented based on the blockchain for other entities. As shown in fig. 2, at step 1, entity a (issuer) issues a receivable certificate with a total share of 1000 to entity B (holder); in step 2, entity B (the transferor) transfers 100 of its 1000 shares to entity C (the transferee), at which time, the shares held by entity B and entity C for the receivable certificates are 900 and 100, respectively; in step 3, the entity C (applicant) applies for financing to the entity E (sponsor) based on 100 shares held by the entity C, the entity D charges 1 share of service fee, the entity E obtains 99 shares, and after deducting 4 shares as interest, the entity C is issued the resources under the chain corresponding to the residual 95 certificate shares to the entity C; in step 4, the entity a transfers the off-chain resources corresponding to 500 credential shares into the off-chain account of the entity F (clearing party) within the appointed time limit, the entity F respectively holds 400 shares, 1 share and 99 shares according to the holding conditions of the receivable credential shares recorded in the block chain, the entity B, the entity D and the entity E correspondingly distribute the off-chain resources transferred by the entity a to each holding party, and the receivable credential is destroyed in the block chain.

The above-mentioned services are introduced below.

For the issue link of the receivable certificate, fig. 3 shows a flow chart of a method for issuing the receivable certificate through the blockchain in one embodiment. The method flow is implemented based on an intelligent contract deployed in a blockchain, the intelligent contract including at least issuing logic of receivable credentials. It should be noted that the deployment of the intelligent contract may be that of any node in the blockchain network, or that of any node in the blockchain network, such as an enterprise and a structure outside the blockchain network.

The issuing logic involves multiple personals, including at least the holder of the receivable credentials. The holder holds all or part of the certificate shares of the certificate to be received, and accordingly, the holding entity (a specific certain enterprise or organization) corresponding to the holder can be one or more. In one embodiment, the plurality of character parties may further include an issuer of the receivable certificate, the issuer needs to pay the equivalent off-chain resource to the holder of the receivable certificate within a predetermined time limit, it should be noted that a conversion relationship or conversion ratio between the receivable certificate and the off-chain resource (for example, 1 certificate share is equal to 1 ten thousand famous coins) may be set and recorded in the blockchain at the certificate issuing stage, or the conversion ratio between the receivable certificate and the off-chain resource is 1:1 by default. In another embodiment, the plurality of persona parties may also include a vouchers receivable vouchers, and if the issuer does not redeem the equivalent off-chain resources after the vouchers receivable vouchers have expired, the vouchers fulfill the redemption transaction or assume responsibility. In another embodiment, the plurality of role parties may further include a clearing party, the issuer transfers the redeemed off-link resources to the off-link accounts of the clearing party, and the clearing party transfers the received off-link resources to the off-link accounts of the respective credential holders according to the distribution of the credential shares recorded in the block chain. In a further embodiment, the plurality of persona parties further includes a platform party providing a publishing service, and the intelligent contract is created by the platform party.

The method for issuing the receivable certificate may be executed by an entity (referred to as a first entity in the text for a differentiation description) corresponding to any one of the plurality of actors involved in the issuing logic. As shown in fig. 3, the method comprises the steps of:

step S310, obtaining issue data, wherein the issue data includes identification information of a plurality of entities corresponding to the plurality of role parties and a plurality of credential shares held by a plurality of entities corresponding to the holding party; step S320, encrypting the issue data by using a first private key to obtain a first digital signature; step S330, forming a first data packet based on the first digital signature and the issue data; step S340, based on the first data packet, sending a first call request to a first node in the blockchain network, where the first call request is used to call the issue logic of the intelligent contract, so that each node in the blockchain network executes the issue logic based on the first data packet, and thus records the issue data in the blockchain.

In the above steps, it should be noted that, in the terms "first" in the "first private key", "first digital signature", and "first node", and the like, and the terms "second" and "third" in the following are used for distinguishing the same kind of things, and do not have other limiting functions such as ordering.

The steps are as follows:

first, in step S310, issue data is obtained, which includes identification information of a plurality of entities corresponding to the plurality of persona parties, and a plurality of credential shares held by a plurality of entities corresponding to the holding party.

It is to be understood that the entities may be organizations in the real world, such as enterprises, institutions, etc. The identification information includes an identification of each of the plurality of entities, and an identification can be used to locate the corresponding unique entity, for example, the identification can be an entity name (e.g., xx corporation), or a number, or a combination of letters and numbers, or an organization code, or a transaction account of the entity in the blockchain. "several" of the above-described "several entities" may be referred to herein as one or more.

The issue data may include contents agreed by a plurality of role parties in advance, and specifically may include a conversion relationship between the receivable vouchers and the resources outside the chain (for example, 1 voucher share =1T storage space), a date of redemption corresponding to the receivable vouchers (for example, a future time), and an issue of the receivable vouchers (for example, entity B provides 1000 tons of steel to entity a).

In one embodiment, when the first entity corresponds to an issuer, the step may include: acquiring input information of a receipt corresponding to an issuer policy; the issue data is obtained based on the entry information. In a specific embodiment, the issuer can use the voucher issuing service based on the client provided by the platform side and enter information in the relevant service interface. In a specific embodiment, the entered information may include entity names of entities corresponding to each of the plurality of role parties, total shares corresponding to the certificate to be received, the shares of the entities corresponding to the holder, and background information of the certificate to be received (such as text description, or scanned documents of offline contracts).

In one embodiment, when the first entity corresponds to a platform side, the step may include: the issue data is received from the issuer. In a specific embodiment, the issuing data is obtained in response to confirmation of the entry information by the issuer. In another specific embodiment, the release data is received in response to an issuer transmission confirmation of the release data.

In one embodiment, when the first entity corresponds to another party other than the issuer and the platform, the step may include: and receiving the publishing data forwarded by the platform side or receiving the publishing data sent by the publisher.

Thus, the acquisition of the distribution data can be realized.

Next, in step S320, the issued data is encrypted by using a first private key to obtain a first digital signature; and, in step S330, a first data package is formed based on the first digital signature and the issue data.

It should be noted that the digital signature is a digital string that can only be generated by the sender of the information and cannot be forged by others, and the digital string is also a valid proof of the authenticity of the information sent by the sender of the information. In one way of generating a digital signature, a first entity may hash issue data to obtain a corresponding hash, and then encrypt the hash with a first private key held by the first entity to obtain the first digital signature. In another mode, the first entity may hash the release data a plurality of times, and then encrypt the hashes obtained by the plurality of hashes by using a first private key held by the first entity, so as to obtain the first digital signature.

The first data packet includes at least the first digital signature and the issue data. In one embodiment, the first public key may be included in the first data packet, considering that the verification of the digital signature requires the first public key corresponding to the first private key. It should be noted that the first public key and the first private key are a pair of keys generated by using asymmetric encryption technology, and one of the keys is used for encryption and the other key is used for decryption. In another embodiment, there are multiple ways for each node in the blockchain network to obtain the first public key, for example, the first entity broadcasts the first public key held by the first entity to each node in the blockchain network, so that each node can obtain the first public key associated with the first entity in advance.

After the first data packet is formed above, in step S340, a first call request is issued to a first node in the blockchain network based on the first data packet, so as to call the issue logic of the intelligent contract, so that each node in the blockchain network executes the issue logic based on the first data packet, thereby recording the issue data in the blockchain. It should be noted that, for the first entity, in one embodiment, it may be a node in the blockchain network, and in this case, it may serve as the first node, and issue the first transaction based on the first data packet, where the first transaction corresponds to the first invocation request. In another embodiment, it is not a node in the blockchain network, and in this case, it may issue a first invocation request by means of any first node in the blockchain network, so that the first node issues a first transaction in the blockchain for invoking the issue logic based on the first invocation request. At this time, the first invocation request also corresponds to the first transaction.

In a specific embodiment, the data field of the first transaction includes the following variable assignment information: assigning the identifier of each entity in the plurality of entities to the entity identifier variable of the corresponding role party; assigning the plurality of credential shares to a plurality of holding share variables corresponding to the plurality of entities. Wherein several entities correspond to a owner role.

In one embodiment, the issuing logic may include: verifying the first digital signature using the issue data and a first public key corresponding to the first private key; judging whether a plurality of digital signatures corresponding to the plurality of entities pass verification or not; if both pass the verification, the issue data is recorded in the blockchain. In one particular implementation, verifying the digital signature (or simply the signature) may include: and decrypting the first digital signature by using the first public key, comparing the decrypted data with a hash obtained by hashing the issued data, and if the decrypted data is consistent with the issued data, passing the verification, and if the decrypted data is inconsistent with the issued data, failing to pass the verification. In one embodiment, recording in the blockchain may include packaging the first transaction uplink.

In this manner, issuance of receivables in blockchains may be enabled.

In summary, by using the method for issuing the receivable certificate through the blockchain disclosed in the embodiments of the present specification, the resource in the real world can be mapped into the blockchain, so as to implement the issuance of the receivable certificate, and the issuance data is recorded in the blockchain, so that the method is not falsifiable, thereby ensuring the authenticity and validity of the issuance data, and improving the trust level of each participant of the issuance of the certificate.

For the transfer link of the receivable vouchers, fig. 4 shows a flow chart of a method for transferring the shares of the receivable vouchers through the blockchain in one embodiment. The method flow is implemented based on intelligent contracts deployed in blockchains, the intelligent contracts including at least transfer logic for receivable credential shares. In one embodiment, the intelligent contract on which the method of FIG. 4 is based may be the same as or separate from the intelligent contract on which the method of FIG. 3 is based.

The assignment logic relates to the transferor and the transferee, and the method is performed by a second entity corresponding to either party. As shown in fig. 4, the method comprises the steps of:

step S410, obtaining assignment data, which includes the entity identifier of the transferor, the entity identifier of the transferee, and an assignment share that the transferor transfers to the transferee based on the holding share of the first receipt by the transferor; step S420, encrypting the assignment data by using a second private key to obtain a second digital signature; step S430, forming a second data packet based on the second digital signature and the assignment data; step S440, based on the second data packet, sending a second call request to a second node in the blockchain network, where the second call request is used to call the transfer logic of the intelligent contract, so that each node in the blockchain network executes the transfer logic based on the second data packet, and thus the transfer data is recorded in the blockchain.

The steps are as follows:

first, in step S410, assignment data is acquired. In one embodiment, the assignment data may also include an identification of the first voucher. Specifically, in the case where the transfer logic in the smart contract is not for a single receivable voucher, but can process multiple different receivable vouchers simultaneously, the corresponding receivable voucher needs to be located through the voucher identification. In one embodiment, the assignment logic further relates to other personals, such as a guarantor, and accordingly, the assignment data may further include entity identifications of the other personals, and the execution subject of the method may also be the other personals. In one embodiment, transfer background or transfer event may also be included in the transfer data.

In one embodiment, when the second entity corresponds to a roll-out party, the step may include: acquiring roll-out information input by a roll-out party based on a first receipt; transfer data is obtained based on the transfer-out information. In a specific embodiment, the roll-out party can use the share transfer service based on the client provided by the platform party and perform information entry in the relevant service interface. In a specific embodiment, the entry information may include an entity name of one or more entities corresponding to the transfer-in party, one or more transfer-out shares, and background information of the transfer-out (such as a text description, or a scan file of the off-line contract, etc.).

In one embodiment, when the second entity corresponds to a transferee, the method may include: and receiving transfer data forwarded by a platform side providing transfer service, wherein the intelligent contract containing the transfer logic is created by the platform side.

In the above, assignment data can be acquired. Next, in step S420, encrypting the assignment data by using a second private key to obtain a second digital signature; then, in step S430, a second data package is formed based on the second digital signature and the assignment data. In one embodiment, the second data packet may further include a second public key corresponding to the second private key.

After the second data packet is formed, in step S440, a second call request is issued to a second node in the blockchain network based on the second data packet, so as to call the transfer logic of the smart contract, so that each node in the blockchain network executes the transfer logic based on the second data packet, thereby recording the transfer data in the blockchain. In one embodiment, the second node may be the same node as the first node or a different node.

In one embodiment, the assignment logic may include: verifying the second digital signature by using the assignment data and a second public key corresponding to the second private key; judging whether the digital signatures corresponding to the transferor and the transferee both pass the verification; and if the transfer data passes the verification, updating the holding shares of the transferor and the transferee according to the transfer data. In a particular embodiment, the assignment logic may further include: and judging whether the roll-out share is not larger than the held share of the roll-out party to the first acceptance certificate, and correspondingly, if the roll-out share is not larger than the held share of the roll-out party to the first acceptance certificate and the first acceptance certificate passes verification, updating the held shares of the roll-out party and the transferee according to the transfer data. In the case where the transfer logic also relates to another role party, such as the platform party or the security party, it is also necessary to determine whether the digital signature corresponding to the other role party passes the verification.

In one embodiment, the second invocation request corresponds to a second transaction, and the data field of the second transaction includes the following variable assignment information: assigning the entity identifiers of the transfer-out party and the transfer-in party to a transfer-out entity identifier variable and a transfer-in entity identifier variable respectively; the transfer share is assigned to a transfer share variable. Updating the holding shares of the transferors and the transferees according to the transfer data in the transfer logic comprises the following steps: updating the holding share variable corresponding to the transfer party into a difference value between the original variable value and the variable value of the transfer share variable; and updating the holding share variable corresponding to the transfer party into a sum value between the original variable value and the variable value of the transfer share variable.

Therefore, the transfer of the share of the receivable vouchers can be realized by adopting the method for transferring the share of the receivable vouchers through the blockchain disclosed by the embodiment of the specification. Meanwhile, the transfer data is recorded in the block chain and cannot be tampered, and authenticity and effectiveness of the transfer data are guaranteed.

For the financing segment of the receivables, FIG. 5 shows a flow diagram of a method of financing by blockchain in one embodiment. The method flow is implemented based on intelligent contracts deployed in blockchains, the intelligent contracts including at least financing logic to finance based on receivable credential shares. The intelligent contract on which the method of fig. 5 is based may be the same as or separate from the intelligent contract on which the method of fig. 3 is based.

The financing logic relates to an applicant and a sponsor, and the method is executed by a third entity corresponding to any one of the parties. As shown in fig. 5, the method comprises the steps of:

step S510, obtaining financing data, which includes the entity identifier of the applicant, the entity identifier of the sponsor, and the financing share of the applicant applying financing to the sponsor based on the holding share of the first receipt certificate by the applicant; step S520, encrypting the financing data by using a third private key to obtain a third digital signature; step S530, forming a third data packet based on the third digital signature and the financing data; step S540, based on the third data packet, sending a third call request to a third node in the blockchain network, where the third call request is used to call the financing logic of the intelligent contract, so that each node in the blockchain network executes the financing logic based on the third data packet, and thus records the financing data in the blockchain.

The steps are as follows:

first, in step S510, financing data is acquired. In one embodiment, the identification of the first receipt credential may also be included in the financing data. Specifically, in the case that the financing logic in the intelligent contract is not for a single receivable certificate, but can process a plurality of different receivable certificates at the same time, the corresponding receivable certificate needs to be located through the certificate identifier. In one embodiment, the intelligent contract containing financing logic is created by the platform side, and the financing data further includes a financing service share paid to the platform side as a service charge.

In one embodiment, when the third entity corresponds to the applicant, the step may include: acquiring financing information input by an applicant based on a first receipt; and obtaining financing data according to the financing information. In a specific embodiment, the applicant can use the financing service based on the client provided by the platform side and perform information entry in the relevant service interface. In a specific embodiment, the entered information may include an entity name of the entity corresponding to the sponsor, a financing share, and financing background information (e.g., a textual description, or a scanned document of an offline financing contract, etc.).

In one embodiment, when the third entity corresponds to a sponsor, the step may include: and receiving financing data forwarded by a platform side providing financing service, wherein the intelligent contract containing financing logic is created by the platform side.

In the above, financing data can be acquired. Next, in step S520, encrypting the financing data by using a third private key to obtain a third digital signature; and, in step S530, a third data package is formed based on the third digital signature and the financing data. In one embodiment, the third data packet may further include a third public key corresponding to the third private key.

The forming the third data includes, at step S540, issuing a third invocation request to a third node in the blockchain network for invoking the financing logic of the intelligent contract. In one embodiment, the third node may be the same node as the first node or a different node.

In one embodiment, the financing logic may include: verifying the third digital signature using the financing data and a third public key corresponding to the third private key; judging whether the digital signatures corresponding to the applicant and the financing party pass verification or not; and if the data passes the verification, updating the holding shares of the applicant and the financing party according to the financing data. In a specific embodiment, the third invocation request corresponds to a third transaction, and the data field of the third transaction includes the following variable assignment information: respectively assigning the entity identifiers of the applicant and the sponsor to an application entity identifier variable and a sponsor entity identifier variable; assigning the financing share to a financing share variable; moreover, the updating of the holding shares of the applicant and the financing party according to the financing data mentioned in the financing logic specifically includes: updating the holding share variable corresponding to the applicant to be the difference value between the original variable value and the variable value of the financing share variable; and updating the holding share variable corresponding to the fund producer to be the sum value between the original variable value and the variable value of the financing share variable.

In a specific embodiment, the financing logic may further include, before verifying the third digital signature, determining whether the financing share is not greater than a holding share of the applicant for the first receipt. Further, if so, the third digital signature is verified.

In another embodiment, the intelligent contract is created by a platform side, the financing data further includes a financing service share paid by the platform side, and accordingly, the financing logic may include: verifying the third digital signature using the financing data and a third public key corresponding to a third private key; judging whether the digital signatures corresponding to the applicant and the financing party pass verification or not; and if the data passes the verification, updating the holding shares of the applicant party, the financing party and the platform party according to the financing data.

Further, in a specific embodiment, the third invocation request corresponds to a third transaction, and the data field of the third transaction includes the following variable assignment information: respectively assigning the entity identifiers of the applicant and the sponsor to an application entity identifier variable and a sponsor entity identifier variable; assigning the financing share to a financing share variable; assigning the financing service share to a financing service share variable; and, the holding share update mentioned in the financing logic specifically includes: updating the holding share variable corresponding to the applicant to be a difference value obtained by respectively subtracting the variable values of the financing share variable and the financing service share variable from the original variable value; updating the holding share variable corresponding to the fund producer to be the sum value between the original variable value and the variable value of the financing share variable; and updating the holding share variable corresponding to the platform side into a sum value between the original variable value and the variable value of the financing service share variable.

In a specific embodiment, the financing logic may further include, before verifying the third digital signature, determining whether a sum of the financing share and the financing service share is not greater than a held share of the applicant for the first receipt credential. Further, if so, the third digital signature is verified.

Therefore, the financing method through the block chain disclosed by the embodiment of the specification can realize the financing based on the receivable certificate. Meanwhile, the financing data is recorded in the block chain and cannot be tampered, and the authenticity and the effectiveness of the financing data are also guaranteed.

For the invalidation of the receivable certificate, fig. 6 shows a flowchart of a method for invalidating the receivable certificate shares by a blockchain in one embodiment. The method flow is implemented based on an intelligent contract deployed in a blockchain, the intelligent contract including at least share invalidation logic for receivable credentials. The intelligent contract on which the method of fig. 6 is based may be the same as or separate from the intelligent contract on which the method of fig. 3 is based.

The share invalidation logic relates to the liquiders, and the method is executed by corresponding liquiders. As shown in fig. 6, the method comprises the steps of:

step S610, determining that the first holding entity of the receivable certificate obtains the off-link resource corresponding to the first quota; step S620, obtaining the share invalid data, which includes the first share and the entity identifier corresponding to the first holding entity; step S630, based on the share invalid data, sending a fourth call request to a fourth node in the blockchain network, where the fourth call request is used to call a share invalid logic of the intelligent contract, so that each node in the blockchain network executes the share invalid logic based on the share invalid data, thereby recording the first share as invalid in the blockchain.

The steps are as follows:

first, in step S610, it is determined that the first owning entity of the receivable certificate acquires the off-link resource corresponding to the first quota.

In one embodiment, this step may include: receiving a resource transfer message indicating that an issuing entity has transferred an off-link resource corresponding to the total amount of the receivable certificate to an off-link account of the liquidation entity; and allocating a part of the resources corresponding to the first quota in the out-of-chain resources to the first holding entity based on the resource transfer-in message. In a specific embodiment, after the redemption for the receivable certificate expires, the issuing party of the receivable certificate transfers the off-link resource corresponding to the total share of the receivable certificate to the off-link account of the clearing party who inquires about the share distribution of the receivable certificate recorded in the block link, including the first share held by the first holding entity. Accordingly, the liquidator transfers the out-link resources corresponding to the first quota to the out-link account of the first holding entity based on the resources transferred by the opening cube, so that the first holding entity which is supposed to receive the certificate can be determined to acquire the out-link resources corresponding to the first quota, or the liquidator can be determined to receive the out-link resources corresponding to the first quota according to receipt information sent by the first holding entity.

In one embodiment, this step may include: and receiving a message sent by the first holding entity, wherein the message indicates that the first holding entity receives the off-link resources corresponding to the first quota.

Next, in step S620, the share invalid data is obtained, wherein the share invalid data includes the first share and the entity identifier corresponding to the first holding entity. In one embodiment, this step may include: after the portion of the out-of-chain resources corresponding to the first share is allocated to the first owning entity, the share invalid data is generated.

Then, based on the obtained share invalidation data, in step S630, a fourth call request is issued to a fourth node in the blockchain network for calling the share invalidation logic of the intelligent contract, so that each node in the blockchain network executes the share invalidation logic based on the share invalidation data, thereby recording the first share as invalid in the blockchain. In one embodiment, the fourth node may be the same node as the first node or a different node.

In one embodiment, the share invalidation logic may comprise: it is determined whether the account address from which the transaction was initiated is an account address of an inventory party and, if so, the holding share of the first holding entity (i.e., the first share) is recorded as invalid.

Therefore, by adopting the method for invalidating the receivable certificates through the block chain disclosed in the embodiment of the present specification, the invalidation of the corresponding receivable certificate shares can be realized. Meanwhile, the invalid state of the share of the receivable certificate is recorded in the block chain, so that the share cannot be tampered, and the authenticity and the validity of the share invalid data are guaranteed.

For the invalidation of receivables, fig. 7 shows a flow diagram of a method for invalidating receivables by a blockchain in one embodiment. The method flow is implemented based on an intelligent contract deployed in a blockchain, the intelligent contract including at least credential invalidation logic for receivable credentials. The intelligent contract on which the method of fig. 7 is based may be the same as or separate from the intelligent contract on which the method of fig. 3 is based.

The share invalidation logic relates to a platform side, and the method is executed by a platform entity corresponding to the platform side, wherein the platform entity is a node in a block chain network. As shown in fig. 7, the method comprises the steps of:

first, in step S710, a query transaction is generated for querying whether each credential share of the receivable credentials recorded in the blockchain is valid. In one embodiment, the query transaction may include a credential identification of the receivable credential.

Then, in step S720, if the respective credential shares are invalid, a target transaction is generated for invoking the credential invalidation logic of the intelligent contract, so that each node in the blockchain network executes the credential invalidation logic, thereby recording the receivable credentials as globally invalid in the blockchain.

In one embodiment, the credential invalidation logic may comprise: and judging whether the initiating account of the target transaction is the account of the platform side, and if so, recording the receivable certificate as global invalidity in the block chain. In another embodiment, the above-mentioned credential invalidation logic includes determining whether an originating account of the target transaction is an account of the platform side, if so, querying whether each credential share of the receivable credential recorded in the blockchain is valid, and if not, recording the receivable credential as globally invalid in the blockchain.

Therefore, by adopting the method for invalidating the receivable certificate through the block chain disclosed in the embodiment of the present specification, the invalidation of the corresponding receivable certificate can be realized. Meanwhile, the global invalid state of the receivable certificate is recorded in the block chain and cannot be tampered, and authenticity and validity of the invalid state are guaranteed.

The above introduces the issuing link, the transferring link, the financing link and the invalidation link of the receipt. It should be noted that the intelligent contracts based on the above links may be the same. And the intelligent contract can be set to only support business processing on a single receipt certificate at the same time, correspondingly, the participants of each link can realize corresponding logic by calling interfaces of different logics in the intelligent contract, and can definitely know that the execution of the logic is based on the receipt certificate when the intelligent contract is called again after the receipt certificate is successfully issued, and the transaction data for calling the intelligent contract only needs to contain the address of the intelligent contract without containing the identification of the receipt certificate.

In fact, more circulation processing of the receivable documents can be realized, such as the opening cube change of the receivable documents. Thus, fig. 8 is a flow diagram illustrating a method for performing a flow process on a corresponding voucher through a blockchain in one embodiment, where the flow process includes multiple links. In one embodiment, the plurality of links may include a distribution link, an assignment link, a financing link, an invalidation link, and an evolution link.

The method comprises a first process aiming at the first link and executed by a fourth entity corresponding to any role party, wherein the first process comprises the following steps:

step S810, acquiring link data corresponding to the first link, wherein the link data includes identification information of a plurality of entities corresponding to the plurality of role parties, and circulation information of the receivable voucher in the first link. In one embodiment, the first link is a distribution link, and accordingly, the circulation information may include a number of holding shares of a number of entities corresponding to the holder.

Step S820, encrypting link data by using a fourth private key to obtain a fourth digital signature; and, in step S830, a fourth data packet is formed based on the fourth digital signature and the link data.

Step S840, based on the fourth data packet, sends a fourth call request to a fourth node in the blockchain network, where the fourth call request is used to call the first processing logic of the intelligent contract, so that each node in the blockchain network executes the first processing logic based on the fourth data packet, and records the link data in the blockchain.

Therefore, by adopting the method for performing the circulation processing on the certificate to be received through the blockchain disclosed by the embodiment of the specification, the circulation data of the certificate to be received is recorded in the blockchain, and cannot be tampered, so that the authenticity and the validity of the circulation data are ensured.

Corresponding to the processing method for the receivable certificate, the embodiment of the present specification further discloses a processing apparatus, which specifically includes:

FIG. 9 is a block diagram illustrating an apparatus for issuing receivables via a blockchain in which intelligent contracts are deployed in one embodiment, the intelligent contracts including issuing logic for receivables that involves multiple personals including at least a holder of the receivables, the apparatus 900 being integrated with a first entity corresponding to any persona; the apparatus 900 comprises:

a data obtaining unit 910 configured to obtain issue data including identification information of a plurality of entities corresponding to the plurality of persona parties, and a plurality of credential shares held by a plurality of entities corresponding to the holding party; a digital signature unit 920 configured to encrypt the issue data with a first private key to obtain a first digital signature; a packet forming unit 930 configured to form a first packet based on the first digital signature and the issue data; a calling unit 940, configured to issue a first call request to a first node in the blockchain network based on the first data packet, so as to call the issuing logic of the intelligent contract, so that each node in the blockchain network executes the issuing logic based on the first data packet, thereby recording the issuing data in the blockchain.

In a specific embodiment, when the first entity corresponds to the issuer, the data obtaining unit 910 is specifically configured to: acquiring the input information of the issuer aiming at the receivable certificate; obtaining the issuing data according to the input information; when the first entity corresponds to the platform side, the data obtaining unit 910 is specifically configured to: receiving the release data from the issuer; when the first entity corresponds to another party other than the issuer and the platform, the data obtaining unit 910 is specifically configured to: and receiving the issuing data forwarded by the platform side.

Fig. 10 is a schematic diagram of an apparatus for transferring accounts receivable voucher shares through a blockchain in which smart contracts are deployed in one embodiment, the smart contracts including transfer logic for the accounts receivable voucher shares, the transfer logic involving a transferor and a transferee, the apparatus 1000 being integrated with a second entity to which either party corresponds; the apparatus 1000 comprises:

a data obtaining unit 1010 configured to obtain assignment data including an entity identifier of the transferor, an entity identifier of the transferee, and a transfer share to be transferred to the transferee based on a held share of the transferor for the first receipt; a digital signature unit 1020 configured to encrypt the assignment data by using a second private key to obtain a second digital signature; a data package forming unit 1030 configured to form a second data package based on the second digital signature and the assignment data; the invoking unit 1040 is configured to issue a second invocation request to a second node in the blockchain network based on the second data packet, so as to invoke the transfer logic of the smart contract, so that each node in the blockchain network executes the transfer logic based on the second data packet, thereby recording the transfer data in the blockchain.

In an embodiment, when the second entity corresponds to the roll-out party, the data obtaining unit 1010 is specifically configured to: acquiring roll-out information input by the roll-out party based on the first receipt; obtaining the assignment data according to the transfer-out information; when the second entity corresponds to the transferee, the data obtaining unit 1010 is specifically configured to: and receiving transfer data forwarded by a platform side providing transfer service, wherein the intelligent contract is created by the platform side.

In one embodiment, the second invocation request corresponds to a second transaction, and the data field of the second transaction includes the following variable assignment information: respectively assigning the entity identifications of the roll-out party and the roll-in party to a roll-out entity identification variable and a roll-in entity identification variable; assigning the transfer share to a transfer share variable; the updating of the holding shares of the transferor and the transferee according to the transfer data comprises: updating the holding share variable corresponding to the transfer party into a difference value between the original variable value and the variable value of the transfer share variable; and updating the holding share variable corresponding to the transfer party into a sum value between the original variable value and the variable value of the transfer share variable.

FIG. 11 illustrates an apparatus for financing by blockchain in one embodiment, the blockchain having deployed therein an intelligent contract comprising financing logic for financing based on receivables, the financing logic involving an applicant and a sponsor, the apparatus 1100 being integrated with a third entity corresponding to either party; the apparatus 1100 comprises:

a data obtaining unit 1110, configured to obtain financing data, which includes an entity identifier of the applicant, an entity identifier of the sponsor, and a financing share of financing applied to the sponsor by the applicant based on a holding share of the first receipt for the applicant; a digital signature unit 1120 configured to encrypt the financing data by using a third private key to obtain a third digital signature; a data packet forming unit 1130 configured to form a third data packet based on the third digital signature and the financing data; a calling unit 1140 configured to issue a third call request to a third node in the blockchain network based on the third data packet, for calling the financing logic of the intelligent contract, so that each node in the blockchain network executes the financing logic based on the third data packet, thereby recording the financing data in the blockchain.

In an embodiment, when the third entity corresponds to the applicant, the data obtaining unit 1110 is specifically configured to: acquiring financing information input by the applicant based on the first receipt certificate; obtaining the financing data according to the financing information; when the third entity corresponds to the sponsor, the data obtaining unit 1110 is specifically configured to: and receiving financing data forwarded by a platform side providing financing service, wherein the intelligent contract is created by the platform side.

In a specific embodiment, the third invocation request corresponds to a third transaction, and the data field of the third transaction includes the following variable assignment information: respectively assigning the entity identifications of the applicant and the sponsor to an application entity identification variable and a funding entity identification variable; assigning the financing share to a financing share variable; the updating of the holding shares of the applicant and the financing party according to the financing data comprises: updating the holding share variable corresponding to the applicant to be the difference value between the original variable value and the variable value of the financing share variable; and updating the holding share variable corresponding to the fund producer to be the sum value between the original variable value and the variable value of the financing share variable.

In a more specific embodiment, the third invocation request corresponds to a third transaction, and the data field of the third transaction includes the following variable assignment information: respectively assigning the entity identifications of the applicant and the sponsor to an application entity identification variable and a funding entity identification variable; assigning the financing share to a financing share variable; and assigning the financing service share to a financing service share variable. Updating the holding shares of the applicant party, the financing party and the platform party according to the financing data comprises the following steps: updating the holding share variable corresponding to the applicant to be a difference value obtained by respectively subtracting the variable values of the financing share variable and the financing service share variable from the original variable value; updating the holding share variable corresponding to the funder to be the sum value between the original variable value and the variable value of the financing share variable; and updating the holding share variable corresponding to the platform side into a sum value between the original variable value and the variable value of the financing service share variable.

Fig. 12 is a schematic diagram illustrating an apparatus for invalidating a credential receivable share through a blockchain, in one embodiment, where an intelligent contract is deployed in the blockchain, the intelligent contract includes share invalidation logic for a credential receivable, the share invalidation logic relates to an inventory party, and the apparatus 1200 is integrated with an inventory entity corresponding to the inventory party, and includes:

a determining unit 1210 configured to determine that a first holding entity of the receivable credential acquires an off-chain resource corresponding to a first quota; a data obtaining unit 1220, configured to obtain the share invalid data, which includes the first share and an entity identifier corresponding to the first holding entity; a calling unit 1230 configured to issue a fourth call request to a fourth node in the blockchain network based on the share invalidation data, for calling the share invalidation logic of the intelligent contract, so that each node in the blockchain network executes the share invalidation logic based on the share invalidation data, thereby recording the first share as invalid in the blockchain.

In one embodiment, the determining unit 1210 is specifically configured to: receiving a resource transfer message indicating that an issuing entity has transferred an off-link resource corresponding to the total amount of the receivable documents to an off-link account of the liquidation entity; and allocating a part of the resources corresponding to the first quota in the out-of-chain resources to the first holding entity based on the resource transfer-in message.

In a more specific embodiment, the data obtaining unit 1220 is specifically configured to: generating the share invalid data after the allocating to the first owning entity.

Fig. 13 is a schematic diagram of an apparatus for invalidating receivable credentials in one embodiment by a blockchain, where an intelligent contract is deployed, the intelligent contract comprising credential invalidation logic for the receivable credentials, the credential invalidation logic involving a platform side, and the apparatus 1300 is integrated with a platform entity corresponding to the platform side, and the platform entity is a node in a blockchain network; the apparatus 1300 comprises:

a query transaction generating unit 1310 configured to generate a query transaction for querying whether each credential share of the receivable credentials recorded in the blockchain is valid; a target transaction generating unit 1320, configured to generate a target transaction if the respective credential shares are invalid, for invoking the credential invalidation logic of the intelligent contract, so that each node in the blockchain network executes the credential invalidation logic, thereby recording the receivable credential as globally invalid in the blockchain.

Fig. 14 is a schematic structural diagram illustrating an apparatus for performing a flow processing on a receipt through a blockchain in one embodiment, where the flow processing includes a plurality of links, and an intelligent contract is deployed in the blockchain, and the intelligent contract includes a first processing logic corresponding to an arbitrary first link, the first processing logic relates to a plurality of actors, the apparatus 1400 is integrated with a fourth entity corresponding to an arbitrary actor, and the apparatus 1400 implements the first processing on the first link by:

a data obtaining unit 1410 configured to obtain link data corresponding to the first link, where the link data includes identification information of a plurality of entities corresponding to the plurality of actors and circulation information of the receivable certificate in the first link; a digital signature unit 1420 configured to encrypt the link data with a fourth private key to obtain a fourth digital signature; a packet forming unit 1430 configured to form a fourth packet based on the fourth digital signature and the link data; the invoking unit 1440 is configured to issue a fourth invoking request to a fourth node in the blockchain network based on the fourth data packet, so as to invoke the first processing logic of the smart contract, so that each node in the blockchain network executes the first processing logic based on the fourth data packet, thereby recording the link data in the blockchain.

According to an embodiment of another aspect, there is also provided a computer readable storage medium having stored thereon a computer program which, when executed in a computer, causes the computer to perform the method described in connection with fig. 3, 4, 5, 6, 7 or 8.

According to an embodiment of yet another aspect, there is also provided a computing device comprising a memory having stored therein executable code, and a processor that, when executing the executable code, implements the method described in conjunction with fig. 3, fig. 4, fig. 5, fig. 6, fig. 7, or fig. 8.

Those skilled in the art will recognize that, in one or more of the examples described above, the functions described in this invention may be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, the functions may be stored on or transmitted over as one or more instructions or code on a computer-readable medium.

The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

Claims

1. A method of issuing receivables via a blockchain, the blockchain having deployed therein an intelligent contract comprising issuing logic for receivables, the issuing logic involving a plurality of personals including at least a holder of the receivables, the method being performed by a first entity to which either persona corresponds; the method comprises the following steps:

obtaining issue data including identification information of a plurality of entities corresponding to the plurality of persona parties and a plurality of credential shares held by a plurality of entities corresponding to the holding party;

encrypting the issuing data by using a first private key to obtain a first digital signature; forming a first data package based on the first digital signature and the release data;

based on the first data packet, issuing a first calling request to a first node in the blockchain network for calling the issuing logic of the intelligent contract, so that each node in the blockchain network executes the issuing logic based on the first data packet, and the issuing data is recorded in the blockchain;

wherein the issuing logic comprises:

verifying the first digital signature using the release data and a first public key corresponding to the first private key;

judging whether a plurality of digital signatures corresponding to the plurality of entities pass verification;

if both pass the verification, the issue data is recorded in the blockchain.

2. The method of claim 1, wherein the plurality of persona parties further comprise at least one of:

the issuing party, the guarantee party, the clearing and distributing party of the receivable voucher and the platform party providing issuing service;

wherein the smart contract is created by the platform side.

3. The method of claim 2, wherein,

when the first entity corresponds to the issuer, the obtaining the issue data includes: acquiring the input information of the issuer aiming at the receivable certificate; obtaining the issuing data according to the input information;

when the first entity corresponds to the platform side, the obtaining of the issue data comprises: receiving the release data from the issuer;

when the first entity corresponds to a party other than the issuer and the platform, the obtaining of the issue data includes: and receiving the issuing data forwarded by the platform side.

4. The method of claim 1, wherein the release data further comprises at least one of: the exchange relationship between the certificate to be received and the resource outside the chain, the date of the corresponding cashing of the certificate to be received, and the issue of the certificate to be received.

5. The method of claim 1, wherein the first data packet further comprises a first public key corresponding to the first private key.

6. The method of claim 1, wherein the first invocation request corresponds to a first transaction, the data fields of the first transaction including the following variable assignment information:

assigning the identifier of each entity in the plurality of entities to the entity identifier variable of the corresponding role party;

assigning the plurality of credential shares to a plurality of holding share variables corresponding to the plurality of entities.

7. A method for transferring accounts receivable voucher shares through a blockchain, wherein the blockchain is provided with an intelligent contract, the intelligent contract comprises transfer logic aiming at the accounts receivable voucher shares, the transfer logic relates to a transferor and a transferee, and the method is executed by a second entity corresponding to any one party; the method comprises the following steps:

acquiring transfer data, wherein the transfer data comprises an entity identifier of the transfer party, an entity identifier of the transferee and a transfer share transferred to the transferee by the transfer party based on the held share of the transfer party for the first receipt;

encrypting the transfer data by using a second private key to obtain a second digital signature; forming a second data package based on the second digital signature and the assignment data;

sending a second calling request to a second node in the blockchain network based on the second data packet, wherein the second calling request is used for calling transfer logic of the intelligent contract, so that each node in the blockchain network executes the transfer logic based on the second data packet, and the transfer data is recorded in the blockchain;

wherein the assignment logic comprises:

verifying the second digital signature using the assignment data and a second public key corresponding to the second private key;

judging whether the digital signatures corresponding to the roll-out party and the transferee both pass verification;

and if the transfer data passes the verification, updating the holding shares of the transferor and the transferee according to the transfer data.

8. The method of claim 7, wherein,

when the second entity corresponds to the transfer party, the acquiring transfer data comprises: acquiring roll-out information input by the roll-out party based on the first receipt; obtaining the assignment data according to the transfer-out information;

when the second entity corresponds to the transferee, the acquiring transfer data comprises: and receiving transfer data forwarded by a platform side providing transfer service, wherein the intelligent contract is created by the platform side.

9. The method according to any one of claims 7 or 8, wherein the second data packet further comprises a second public key corresponding to the second private key.

10. The method of claim 7, wherein the second invocation request corresponds to a second transaction, the data fields of the second transaction including the following variable assignment information:

respectively assigning the entity identifications of the roll-out party and the roll-in party to a roll-out entity identification variable and a roll-in entity identification variable;

assigning the transfer share to a transfer share variable;

the updating of the holding shares of the transferor and the transferee according to the transfer data comprises:

updating the holding share variable corresponding to the transfer party into a difference value between the original variable value and the variable value of the transfer share variable;

and updating the holding share variable corresponding to the transfer party into a sum value between the original variable value and the variable value of the transfer share variable.

11. A method for financing through a blockchain is characterized in that an intelligent contract is deployed in the blockchain, the intelligent contract comprises financing logic for financing based on a certificate to be collected, the financing logic relates to an applicant and a sponsor, and the method is executed by a third entity corresponding to any party; the method comprises the following steps:

acquiring financing data, wherein the financing data comprises an entity identifier of the applicant, an entity identifier of the sponsor and financing share of financing applied to the sponsor by the applicant based on the holding share of the first acceptance certificate of the applicant;

encrypting the financing data by using a third private key to obtain a third digital signature; forming a third data package based on the third digital signature and the financing data;

based on the third data packet, sending a third call request to a third node in the blockchain network, wherein the third call request is used for calling the financing logic of the intelligent contract, so that each node in the blockchain network executes the financing logic based on the third data packet, and the financing data is recorded in the blockchain;

wherein the financing logic comprises:

verifying the third digital signature using the financing data and a third public key corresponding to the third private key;

judging whether the digital signatures corresponding to the applicant and the financing party pass verification or not;

and if the data passes the verification, updating the holding shares of the applicant and the financing party according to the financing data.

12. The method of claim 11, wherein,

when the third entity corresponds to the applicant, the acquiring financing data comprises: acquiring financing information input by the applicant based on the first receipt certificate; obtaining the financing data according to the financing information;

when the third entity corresponds to the sponsor, the acquiring financing data comprises: and receiving financing data forwarded by a platform side providing financing service, wherein the intelligent contract is created by the platform side.

13. The method of claim 11, wherein the third invocation request corresponds to a third transaction, the data fields of the third transaction including the following variable assignment information:

respectively assigning the entity identifications of the applicant and the sponsor to an application entity identification variable and a funding entity identification variable;

assigning the financing share to a financing share variable;

the updating of the holding shares of the applicant and the financing party according to the financing data comprises:

updating the holding share variable corresponding to the applicant to be the difference value between the original variable value and the variable value of the financing share variable;

and updating the holding share variable corresponding to the fund producer to be the sum value between the original variable value and the variable value of the financing share variable.

14. The method of claim 11, wherein the intelligent contract is created by a platform party, the financing data further comprising a financing service share paid by the applicant to the platform party.

15. The method of claim 14, wherein the financing logic further comprises:

and if the data passes the verification, updating the holding shares of the applicant party, the financing party and the platform party according to the financing data.

16. The method of claim 15, wherein the third invocation request corresponds to a third transaction, the data fields of the third transaction including the following variable assignment information:

assigning the financing share to a financing share variable;

assigning the financing service share to a financing service share variable;

updating the holding shares of the applicant party, the financing party and the platform party according to the financing data comprises the following steps:

updating the holding share variable corresponding to the applicant to be a difference value obtained by respectively subtracting the variable values of the financing share variable and the financing service share variable from the original variable value;

updating the holding share variable corresponding to the funder to be the sum value between the original variable value and the variable value of the financing share variable;

and updating the holding share variable corresponding to the platform side into a sum value between the original variable value and the variable value of the financing service share variable.

17. The method of any of claims 11-16, wherein a third public key corresponding to the third private key is further included in the third data packet.

18. A method for invalidating a credential receivable share through a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract comprises share invalidation logic for a credential receivable, the share invalidation logic relates to an inventory party, and the method is executed by an inventory entity corresponding to the inventory party, and comprises the following steps:

determining that a first holding entity of the receivable certificate obtains an off-link resource corresponding to a first quota;

acquiring share invalid data, wherein the share invalid data comprises the first share and an entity identifier corresponding to the first holding entity;

based on the share invalid data, issuing a fourth call request to a fourth node in the blockchain network for calling share invalid logic of the intelligent contract, so that each node in the blockchain network executes the share invalid logic based on the share invalid data, thereby recording the first share as invalid in the blockchain;

the quantum invalidation logic comprises: judging whether the account address for initiating the transaction is the account address of the liquidation party, and if so, recording the first quota as invalid;

wherein the determining that the first holding entity of the receivable certificate acquires the off-chain resource corresponding to the first quota comprises:

receiving a resource transfer message indicating that an issuing entity has transferred an off-link resource corresponding to the total amount of the receivable documents to an off-link account of the liquidation entity;

and allocating a part of the resources corresponding to the first quota in the out-of-chain resources to the first holding entity based on the resource transfer-in message.

19. The method of claim 18, wherein obtaining the quantum of invalid data comprises:

generating the share invalid data after the allocating to the first owning entity.

20. A method for invalidating receivable credentials by a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract comprises credential invalidation logic for the receivable credentials, the credential invalidation logic relates to a platform side, and the method is executed by a platform entity corresponding to the platform side, and the platform entity is a node in a blockchain network; the method comprises the following steps:

generating an inquiry transaction for inquiring whether each certificate share of the receivable certificates recorded in the block chain is valid;

if the certificate shares are invalid, generating a target transaction for calling a certificate invalid logic of the intelligent contract, so that each node in the block chain network executes the certificate invalid logic, and recording the receivable certificate as global invalid in the block chain;

the credential invalidation logic comprises:

judging whether the initiating account of the target transaction is the account of the platform side, if so, recording the receivable certificate as global invalidity in a block chain; or the like, or, alternatively,

and judging whether the initiating account of the target transaction is the account of the platform side, if so, inquiring whether the certificate shares of the receivable certificate recorded in the block chain are valid, and if not, recording the receivable certificate as global invalidity in the block chain.

21. An apparatus for issuing receivables via a blockchain, the blockchain having deployed therein an intelligent contract comprising issuing logic for receivables, the issuing logic involving a plurality of personals including at least a holder of the receivables, the apparatus being integrated with a first entity corresponding to any persona; the device comprises:

a data acquisition unit configured to acquire issue data including identification information of a plurality of entities corresponding to the plurality of persona parties and a plurality of credential shares held by a plurality of entities corresponding to the holding party;

the digital signature unit is configured to encrypt the issuing data by using a first private key to obtain a first digital signature;

a packet forming unit configured to form a first packet based on the first digital signature and the issue data;

a calling unit configured to issue a first calling request to a first node in a blockchain network based on the first data packet, for calling the issuing logic of the intelligent contract, so that each node in the blockchain network executes the issuing logic based on the first data packet, thereby recording the issuing data in a blockchain;

wherein the issuing logic comprises:

if both pass the verification, the issue data is recorded in the blockchain.

22. An apparatus for transferring a share of a receivable credential through a blockchain, the blockchain having deployed therein an intelligent contract comprising transfer logic for the share of the receivable credential, the transfer logic involving a transferor and a transferee, the apparatus being integrated with a second entity to which either party corresponds; the device comprises:

a data acquisition unit configured to acquire transfer data including an entity identifier of the transferor, an entity identifier of the transferee, and a transfer share to be transferred to the transferee based on a held share of the transferor for the first receipt;

the digital signature unit is configured to encrypt the assignment data by using a second private key to obtain a second digital signature;

a data package forming unit configured to form a second data package based on the second digital signature and the assignment data;

a calling unit, configured to issue a second call request to a second node in the blockchain network based on the second data packet, where the second call request is used to call transfer logic of the intelligent contract, so that each node in the blockchain network executes the transfer logic based on the second data packet, and thus the transfer data is recorded in the blockchain;

wherein the assignment logic comprises:

23. A device for financing through a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract comprises financing logic for financing based on a certificate to be collected, the financing logic relates to an applicant and a sponsor, and the device is integrated with a third entity corresponding to any party; the device comprises:

the data acquisition unit is configured to acquire financing data, wherein the financing data comprises an entity identifier of the applicant, an entity identifier of the sponsor and a financing share of financing applied to the sponsor by the applicant based on the holding share of the first application receipt;

the digital signature unit is configured to encrypt the financing data by using a third private key to obtain a third digital signature;

a data packet forming unit configured to form a third data packet based on the third digital signature and the financing data;

a calling unit, configured to issue a third call request to a third node in the blockchain network based on the third data packet, so as to call the financing logic of the intelligent contract, so that each node in the blockchain network executes the financing logic based on the third data packet, thereby recording the financing data in the blockchain;

wherein the financing logic comprises:

24. An apparatus for invalidating a share of a receivable credential through a blockchain, wherein the blockchain has deployed therein an intelligent contract comprising share invalidation logic for the receivable credential, the share invalidation logic relating to an inventory party, the apparatus being integrated with an inventory entity corresponding to the inventory party, comprising:

the determining unit is configured to determine that the first holding entity of the receivable certificate obtains the off-chain resource corresponding to the first quota;

the data acquisition unit is configured to acquire share invalid data, wherein the share invalid data comprises the first share and an entity identifier corresponding to the first holding entity;

a calling unit configured to issue a fourth call request to a fourth node in the blockchain network based on the share invalid data, for calling share invalid logic of the intelligent contract, so that each node in the blockchain network executes the share invalid logic based on the share invalid data, thereby recording the first share as invalid in the blockchain;

the determining unit is specifically configured to:

25. An apparatus for invalidating receivable credentials via a blockchain, wherein an intelligent contract is deployed in the blockchain, the intelligent contract comprises credential invalidation logic for the receivable credentials, the credential invalidation logic relates to a platform side, the apparatus is integrated with a platform entity corresponding to the platform side, and the platform entity is a node in a blockchain network; the device comprises:

the inquiry transaction generating unit is configured to generate inquiry transactions for inquiring whether the certificate shares of the receivable certificates recorded in the block chain are valid or not;

a target transaction generation unit configured to generate a target transaction for invoking a credential invalidation logic of the intelligent contract if the respective credential share is invalid, so that each node in a blockchain network executes the credential invalidation logic, thereby recording the receivable credential as globally invalid in a blockchain;

the credential invalidation logic comprises:

26. A computer-readable storage medium, having stored thereon a computer program which, when executed in a computer, causes the computer to perform the method of any of claims 1-20.

27. A computing device comprising a memory and a processor, wherein the memory has stored therein executable code that when executed by the processor implements the method of any of claims 1-20.