WO2020082877A1

WO2020082877A1 - Blockchain-based remittance method and device

Info

Publication number: WO2020082877A1
Application number: PCT/CN2019/101938
Authority: WO
Inventors: 马宝利; 刘正; 张文彬; 李漓春; 殷山
Original assignee: 阿里巴巴集团控股有限公司
Priority date: 2018-10-26
Filing date: 2019-08-22
Publication date: 2020-04-30
Also published as: TW202016822A; CN109508970A; CN111899012A; CN111899012B; TWI723357B; CN109508970B

Abstract

Provided in one or more embodiments of the present specification are a blockchain-based remittance method and device applied to a user terminal device in a blockchain. An account balance in a user account is at least divided into a contingency balance and a reserve balance. The user account comprises a dynamically updated contingency fund list. The contingency fund list comprises multiple contingency fund amounts. The method comprises: in response to a remittance operation initiated by a user, allocating, according to a current contingency fund list, a corresponding contingency fund amount to a remittance amount indicated by the user; and constructing a remittance transaction on the basis of the contingency fund amount allocated to the remittance amount, and transmitting the remittance transaction to a blockchain, such that the remittance amount is deducted from both the account balance and the contingency balance after the remittance transaction has been authenticated by node equipment in the blockchain.

Description

Remittance method and device based on blockchain

Technical field

One or more embodiments of this specification relate to the field of blockchain technology, and in particular, to a blockchain-based remittance method and device.

Background technique

Blockchain is a tamper-proof, shared digital ledger used to record transactions in public or private peer-to-peer networks. The ledger is distributed to all member nodes in the network, and the historical records of asset transactions occurring in the network are permanently recorded in the block. Since the ledger is completely public, the blockchain ledger itself has no privacy protection function, and additional technology is needed to protect the privacy of asset transactions. The existing privacy protection schemes all use zero-knowledge proof technology to ensure that the transaction amount is within a reasonable range. Unlike the UTXO model, the application of zero-knowledge proof technology under the account model will cause serious transaction concurrency problems, because the above zero-knowledge proof technology is closely related to the existing balance of the account, and the account balance will be sent in a certain transaction concurrently After being verified, it changes, causing other transactions that have not been verified and sent in parallel with the original account balance as a zero-knowledge proof to fail verification, thus seriously hindering the actual landing application of the privacy protection scheme under the account model.

An existing solution is to generate a reserve list containing multiple reserve amounts based on the account balance of the blockchain user, and assign the multiple reserve amounts available in the reserve list to multiple remittance transactions; block The nodes of the chain verify whether each remittance transaction is sufficient for the amount of reserves included in each remittance exchange, and verify each remittance transaction independently without affecting each other, so that the blockchain based on the account model can be sent in parallel Multiple remittance transactions. The above technical solution has a problem: the user's account transaction needs to be suspended when the reserve list is initialized, and subsequent transactions cannot be performed until the initialization is completed, which still affects the concurrency of remittance transactions to a certain extent.

Summary of the invention

In view of this, one or more embodiments of this specification provide a blockchain-based remittance method and apparatus, electronic equipment, and computer-readable storage medium.

To achieve the above purpose, one or more embodiments of this specification provide technical solutions as follows:

According to the first aspect of one or more embodiments of this specification, a blockchain-based remittance method is proposed, which is applied to the user equipment of the blockchain, and the account balance of the user account is divided into at least a reserve balance and A reserve balance; wherein, the user account includes a dynamically updated reserve list; the reserve list includes multiple reserve amounts;

The method includes:

In response to the remittance operation initiated by the user, a corresponding reserve amount is allocated to the remittance amount submitted by the user according to the current reserve list; a remittance transaction is constructed based on the remittance amount and the allocated reserve amount, and the remittance transaction is transferred Post to the blockchain to deduct the remittance amount from both the account balance and the reserve balance after the remittance transaction is verified by the node device in the blockchain;

Among them, the process of creating and updating the reserve list includes:

Step A: Obtain the current reserve balance and obtain a reserve list according to the current reserve balance;

Step B: dynamically monitor whether the amount of reserves available for allocation in the current reserve list is lower than a preset threshold, and if so, after switching the current reserve balance to the reserve balance, perform step A.

According to a second aspect of one or more embodiments of this specification, a blockchain-based remittance device is proposed, which is applied to the user equipment of the blockchain, and the account balance of the user account is divided into at least a reserve balance and A reserve balance; wherein, the user account includes a dynamically updated reserve list; the reserve list includes multiple reserve amounts;

The device includes:

The reserve amount allocation unit, in response to the remittance operation initiated by the user, allocates the corresponding reserve amount to the remittance amount submitted by the user according to the current reserve list provided by the reserve list creation unit;

The remittance transaction construction and release unit, constructs a remittance transaction based on the remittance amount and the allocated reserve amount, and publishes the remittance transaction to the blockchain, so that the remittance transaction is used by the node device in the blockchain After the verification is passed, the remittance amount is deducted from both the account balance and the reserve balance;

Wherein, the reserve fund list creation unit includes:

The reserve list generation module obtains the current reserve balance and obtains the reserve list according to the current reserve balance;

The reserve list monitoring module dynamically monitors whether the amount of reserves available for distribution in the current reserve list is lower than a preset threshold.

According to a third aspect of one or more embodiments of this specification, a computer device is proposed, including: a memory and a processor; a computer program executable by the processor is stored on the memory; the processor runs the computer During the procedure, the above-mentioned blockchain-based remittance method is executed.

According to a fourth aspect of one or more embodiments of the present specification, a computer-readable storage medium is provided on which a computer program is stored, and when the computer program is executed by a processor, the above-mentioned blockchain-based remittance method is executed The steps described.

The blockchain-based remittance method and device provided in this manual divide the account balance of the user account into at least a reserve balance and a reserve balance, generate a reserve list based on the reserve balance, and the reserve list can include multiple The reserve amount is allocated to multiple remittance transactions and supports multiple concurrent remittance transactions; when the reserve amount available for distribution in the reserve list is lower than the preset threshold, the client device switches the above reserve balance to a reserve balance and A new reserve list is generated based on the switched reserve balance. After the new reserve list is generated, the original reserve list is updated and replaced, and a new remittance transaction can be initiated based on the reserve amount in the new reserve list.

In the remittance method and device provided in this specification, the above-mentioned reserve balance can start the initialization operation of the new reserve list when the reserve amount in the original reserve list is consumed to a preset threshold, after the new reserve list is generated , Can immediately switch to generate remittance transactions based on the new reserve list; remittance transactions sent by users during the generation of the new reserve list (or verified by the blockchain consensus) are still generated based on the amount of reserves available for allocation in the original reserve list ; The above process of switching the reserve balance and initializing the new reserve list may follow the use of the existing reserve list (whether the amount of reserve available for distribution is below the preset threshold), or the new reserve that should be received The gold list construction instruction is executed cyclically, so there is no need to suspend the transaction of sending remittances throughout the process, improve the concurrency of the transaction, and avoid transaction interruption, maximizing the throughput of blockchain transactions.

BRIEF DESCRIPTION

FIG. 1 is a flowchart of a blockchain-based remittance method provided by an exemplary embodiment.

FIG. 2 is a flowchart of a process of creating and updating a reserve list provided by an exemplary embodiment.

FIG. 3 is a schematic diagram of implementing a remittance transaction in a blockchain network provided by an exemplary embodiment.

FIG. 4 is a flowchart of implementing an updated reserve list and remittance transaction in a blockchain network provided by an exemplary embodiment.

FIG. 5 is a schematic diagram of a user ’s account status on a blockchain provided by an exemplary embodiment.

FIG. 6 is a schematic diagram of a blockchain-based user equipment provided by an exemplary embodiment.

7 is a schematic diagram of a blockchain-based remittance device provided by an exemplary embodiment.

detailed description

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

It should be noted that in other embodiments, the steps of the corresponding method are not necessarily performed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. In addition, the single step described in this specification may be decomposed into multiple steps for description in other embodiments; and the multiple steps described in this specification may also be combined into a single step in other embodiments description.

FIG. 1 is a flowchart of a blockchain-based remittance method provided by an exemplary embodiment, which is applied to a user terminal device of a blockchain, and the account balance of a user account is divided into at least a reserve balance and a reserve balance ; Wherein the user account includes a dynamically updated reserve list; the reserve list includes multiple reserve amounts.

The blockchain described in the above embodiment may specifically refer to a P2P network system with distributed data storage structure reached by each node device through a consensus mechanism, and the data distribution in the blockchain is connected one by one in time. Within the "block", the latter block contains the data summary of the previous block, and according to the specific consensus mechanism (such as POW, POS, DPOS or PBFT, etc.), all or part of the data of the node is reached. Backup. Those skilled in the art are familiar with the fact that since the blockchain system operates under the corresponding consensus mechanism, the data already included in the blockchain database is difficult to be tampered with by any node. For example, the blockchain using Pow consensus requires at least the entire network Only an attack of 51% of the computing power is possible to tamper with the existing data, so the blockchain system has the characteristics of ensuring data security and preventing attack and tampering that other centralized database systems cannot match. It can be seen that in the embodiments provided in this specification, the remittance transactions and other transactions included in the distributed database of the blockchain are not easy to be attacked or tampered, so that they are distributed to the distributed database of the blockchain The transaction was deposited.

The client device that executes the blockchain-based remittance method described in this embodiment may be the node device of the above-mentioned blockchain, or a client device connected to the node device of the above-mentioned blockchain, in this specification Not limited.

Using the above blockchain as a universal decentralized platform for managing object state transitions, user accounts are stateful objects, and the content included in the user account can be the content included in the state of the above user account. The user account contains account balance information and a list of reserves to support remittance transactions. In this specification, in order to support users to send remittance transactions without suspension, a dynamically updated reserve list is included in the user account, and the reserve list includes multiple reserve amounts.

The above multiple reserve amounts can be allocated to different remittance transactions, providing each remittance transaction with sufficient proof of payment of the remittance amount. It is worth noting that the "account" described in this specification is not limited to all external accounts (EOA) and contract accounts (Contract), and does not limit the specific manifestation of the above reserve list, as long as it contains or manages the above multiple reserves The data organization forms of amounts, such as one-dimensional tables, two-dimensional tables, tree-shaped data structures, etc., all belong to the reserve list described in this manual. The value of the reserve balance and reserve balance described in this specification may not be displayed in the user account status of the blockchain, but as content that can be displayed or managed by the user client; of course, the value of the reserve balance and reserve balance mentioned above It can be displayed in the user account status of the blockchain, and is not limited in this specification.

As shown in Figure 1, the above remittance method may include the following steps:

Step 102, in response to the remittance operation initiated by the user, allocate a corresponding reserve amount to the remittance amount submitted by the user according to the current reserve list;

Step 104: Construct a remittance transaction based on the remittance amount and the allocated reserve amount, and publish the remittance transaction to the blockchain, so that after the remittance transaction is verified by the node device in the blockchain, The remittance amount is deducted from both the account balance and the reserve balance.

In the above embodiment, the amount of the reserve fund corresponding to the remittance amount is at least one, and the sum of the amount of the reserve fund corresponding to the remittance amount should not be less than the remittance amount of the transaction, thereby providing sufficient proof for the remittance transaction. For example, the current reserve list contains {5,10,15,20} four reserve amounts. For remittance transactions with a remittance amount of 10, the client device can select one reserve from the above four reserve amounts Amount of 10 (or 15 or 20), the above one reserve amount of 10 (or 15 or 20) is allocated to the above remittance transaction; corresponding to the remittance transaction of the remittance amount of 12, the user equipment can choose from the above four reserve amounts Select a reserve amount of 15 (or 20), allocate the above reserve amount of 15 (or 20) to the above remittance transaction, or you can choose two reserve amounts of 5 and 10 from the above four reserve amounts (Or 5 and 15), allocate the above two reserve amounts 15 (or 20) to the above remittance transaction, and use the sum of the two reserve amounts to provide sufficient proof of payment for the remittance transaction.

In an embodiment, the remittance user and the recipient user may agree to transfer (or referred to as transfer) an asset certificate corresponding to the remittance amount from the remittance blockchain account to the recipient blockchain account. Asset certificates can correspond to smart assets such as tokens and digital assets in the blockchain. Asset certificates can also correspond to off-chain assets such as cash, securities, coupons, and real estate outside the blockchain. This manual is not correct. This is restricted.

After the construction of the remittance transaction is completed, it is sent to the blockchain by the user terminal device and receives the verification of the node device in the blockchain. Since the blockchain-based remittance method provided in this specification can be applied to blockchains based on multiple types of consensus mechanisms, this specification does not limit the number and types of blockchain nodes that perform verification on the above remittance transactions , Does not limit the content or process included in the above verification. However, those skilled in the art should know that the above verification includes at least verifying whether the sum of the reserves in the remittance transaction is greater than or equal to the remittance amount of the remittance transaction, to verify whether the user account has sufficient balance to pay the remittance transaction. After the above remittance transaction is verified by the node device of the blockchain, the remittance amount is deducted from the user's account balance and reserve balance.

FIG. 2 illustrates the process of creating and updating the reserve list in the above embodiment. As shown in FIG. 2, the process can be summarized as two loop steps connected to each other:

After the user registers as a user of the above-mentioned blockchain, the user may divide the account balance into at least an initialized reserve balance and an initialized reserve balance. The user equipment first performs the above-mentioned step A based on the initialized reserve balance process.

The above current reserve balance can generate the reserve amount in the new reserve list after switching; optionally, before being triggered to generate a new reserve list, the reserve balance can be used as a remittance balance to support user initiation Separate (not concurrent) remittance transactions can also be used as a collection balance to receive remittances from other accounts to this user account; and, when the account balance includes two or more backup balances, some of the backup balances You can not participate in remittances or collections, but only as a static balance, at a suitable time (such as the amount of reserves available for distribution in the reserve list generated based on the original reserve balance is lower than the preset threshold, or received by the user The new reserve list construction instruction sent is triggered to divide the reserve amount in the new reserve list.

In an illustrated embodiment, the process of obtaining a reserve list according to the current reserve balance described in step A includes:

Divide the current reserve balance to obtain multiple reserve amounts, and build a reserve list creation transaction based on the divided reserve amounts;

Publish the reserve list creation transaction to the blockchain, so that after the reserve list creation transaction is verified by the node device in the blockchain, multiple reserve funds obtained based on the division in the user account Amount to build a reserve list.

In the above embodiment, the current reserve balance can be divided to obtain multiple reserve amounts. To ensure that the multiple reserve amounts are verified by the consensus of the blockchain nodes, the reserve list creation exchange includes, based on The sum of the multiple reserve funds obtained by dividing the current reserve balance should not be greater than the reserve balance. Since the blockchain-based remittance method provided in this specification can be applied to blockchains based on multiple types of consensus mechanisms, this specification does not limit the blockchain nodes that perform verification on the above-mentioned reserve list creation transactions. The number and type also do not limit the content or process included in the above verification. However, those skilled in the art should know that the above verification includes at least verifying whether the sum of the reserves in the reserve list creation transaction is less than or equal to the current reserve balance (or when the user ’s account status does not display the reserve balance, at least It should be verified whether the sum of the reserve amount in the reserve list creation transaction is less than or equal to the current account balance) to verify the validity of the above reserve balance. After the above reserve fund list creation transaction is verified by the node device of the blockchain, a reserve fund list is constructed in the user account based on the multiple reserve fund amounts included in the exchange created by the reserve fund list creation.

In yet another illustrated embodiment, the above-mentioned obtaining of the reserve fund list according to the current reserve fund balance includes:

Divide the current reserve balance to obtain multiple reserve amounts, build a reserve list based on the divided reserve amounts, and construct a reserve list based on the reserve list to create a transaction;

Posting the reserve list creation transaction to the blockchain to update the reserve list to the user account after the reserve list creation transaction is verified by the node device in the blockchain.

In the above embodiment, the current reserve balance may be divided to obtain a plurality of reserve amounts, a reserve list is constructed based on the plurality of reserve amounts, and the above includes a plurality of reserves obtained based on the current reserve balance division The reserve list of the gold amount is included in the above reserve list creation transaction. In order to ensure that the above multiple reserve amounts are verified by the consensus of the blockchain nodes, the sum of the multiple reserve amounts included in the reserve list creation exchange based on the current reserve balance division should not be greater than the reserve balance. Since the blockchain-based remittance method provided in this specification can be applied to blockchains based on multiple types of consensus mechanisms, this specification does not limit the blockchain nodes that perform verification on the above-mentioned reserve list creation transactions. The number and type also do not limit the content or process included in the above verification. However, those skilled in the art should know that the above verification includes at least verifying whether the sum of the reserves in the reserve list creation transaction is less than or equal to the current reserve balance (or when the user ’s account status does not display the reserve balance, at least It should be verified whether the sum of the reserve amount in the reserve list creation transaction is less than or equal to the current account balance) to verify the validity of the above reserve balance. After the above reserve fund list creation transaction is verified by the node device of the blockchain, the reserve fund list included in the reserve fund list creation exchange is updated to the user account.

Those skilled in the art should know that each reserve amount in the reserve list is to provide a balance certificate sufficient for payment for the remittance transaction, and the remittance transaction that is repeatedly allocated based on the same reserve amount cannot pass the verification of the blockchain node. As more and more remittance transactions are issued, the amount of reserves available for allocation in the current reserve list in the user's account is decreasing. In order not to suspend sending remittance transactions when switching to prepare a new reserve list, you can set a threshold for the amount of reserves available for allocation in the existing reserve list. This threshold can be the total threshold of the reserve amount (ie The maximum remittance threshold that can be paid for the remaining available reserve amount), or it can be the threshold of the amount of the reserve amount (that is, the remaining available reserve balance can be used for the maximum number of remittance transactions sent), on the user side When the device dynamically detects that the amount of reserves available for distribution in the existing reserve list is lower than the preset threshold, the current reserve balance is switched to the reserve balance, and then the step A in the above embodiment is executed. process. Optionally, the above step of switching the current reserve balance to the reserve balance can also be triggered in response to an instruction issued by the user.

The process of the release of node devices (including user equipment) of the blockchain, consensus verification, and updating of the new reserve list in the state of the user account usually require a certain amount of time. The specific consumption time and the consensus mechanism of the blockchain, Block frequency and other related. During this period, if the user has a need to send a new remittance transaction, because the current reserve list in the user's account is still in effect, the remittance transaction can still be constructed based on the amount of reserve available for allocation in the current reserve list. After the new reserve fund list is updated to the user account, the new reserve fund list can be used as the current reserve fund list in the user account, and the user can construct a remittance transaction based on the current reserve fund list, and submit to the blockchain The remittance transaction is issued; accordingly, after the above remittance transaction is verified by the node device in the blockchain, the remittance amount is deducted from both the account balance and the switched reserve balance.

The remittance method provided in this manual, since there is always a valid reserve list in the user account, there is no need to suspend remittance transactions, which maximizes the transaction throughput.

In an illustrated embodiment, in order to distinguish the amount of reserves available for allocation in the reserve list, the usage status of the amount of reserves in the reserve list may be marked. When a remittance transaction including the reserve amount is verified by the node device in the blockchain, and the remittance transaction is included in the distributed database of the blockchain, and the account balance of the remittance user of the remittance transaction is updated, The amount of reserves included in the remittance exchange should be marked as used in the reserve list of the remittance account (state 3), as those skilled in the art are familiar with, the above remittances included in the distributed database of the blockchain The transaction may be referred to as "a completed remittance transaction". For new unfinished remittance transactions, the node device in the blockchain can verify whether the status of the reserve amount in the new unfinished remittance transaction in the remittance user account's reserve list is used: If it is in the used state, the verification fails, and the corresponding new outstanding remittance transaction can be returned; if it is not in the used state, the verification is passed. Similarly, when the new remittance transaction is verified and updated in the distributed database of the blockchain, the blockchain node should also reserve the amount of the reserve included in the new remittance transaction in the remittance user account. The gold list is updated to "used status".

More preferably, the client device can also mark the unused reserve amount that has not been allocated to any remittance transaction as unused in the reserve list (state 1); a reserve amount Once allocated to a remittance transaction, the amount of the reserve can be immediately marked as used in the reserve list of the user account (state 2), that is, the above reserve amount in the current reserve list saved on the user side Calibration is used (state 2). Therefore, the client device can only allocate the reserve amount in the unused state (state 1) for new remittance transactions, and after the allocation, the allocated reserve amount is immediately changed to the used state locally (state 2) ) To prevent double allocation of the same reserve amount.

In an illustrated embodiment, after the reserve list is obtained according to the current reserve balance, the reserve balance before switching is switched to a reserve balance.

After the user equipment obtains the reserve list according to the current reserve amount according to the process described in the above embodiment, at this time, since the new reserve list has been used as the current reserve list for new remittance transactions, the original reserve list Can be used as a remittance transaction. Correspondingly, the original reserve balance can be switched to a standby balance, so that the reserve amount in the current current reserve list is lower than the preset threshold or a new reserve list construction instruction is received At this time, a new reserve list is constructed based on the current reserve balance.

More preferably, in order to optimize the management of each balance in the user account, the standby balance described in this specification can be used as the collection balance. When the remittance transaction initiated by the other user to the user account is verified by the node device of the blockchain, The amount of remittance in this remittance transaction will be added to the balance of the payment and the balance of the account.

In order to protect the privacy of the blockchain user's account, in some existing blockchains, the user's account balance and the transaction amount of the remittance transaction are encrypted; the remittance method provided in this manual can also be used in the privacy mode In the blockchain.

In an illustrated embodiment, the account balance of the blockchain user account, the amount of reserves in the reserve list, and the amount of remittance in the remittance transaction initiated by the user device are all encrypted in advance. Since the remittance amount and reserve amount included in the remittance exchange are encrypted, in order to ensure that the blockchain node can verify that the above reserve amount allocated to the remittance transaction is sufficient to pay for the remittance, the above remittance transaction should also include The proof is the first zero-knowledge proof that the sum of the reserves included in the remittance transaction is greater than or equal to the remittance amount of the remittance transaction.

Correspondingly, since the account balance of the user account and the multiple reserve amounts obtained by the user based on the switched reserve balance are encrypted in advance, in order to ensure that the blockchain node can verify the reserve list, the exchange included in the creation of the exchange The sum of the reserve amount does not exceed the user's account balance. The above reserve list creation transaction should also include a proof that the sum of the multiple reserve amounts divided based on the switched reserve balance is less than or equal to the user's account balance The second zero knowledge proof.

Zero-knowledge proof usually refers to that the prover (verified person) can make the verifier believe that an argument is correct without providing the verifier with any useful information. In this specification, the user equipment can provide the first zero-knowledge proof, so that the node (verifier) in the blockchain can believe that it is a remittance transaction without knowing the specific value of the remittance amount and reserve amount The sum of the specific value of the allocated reserve amount is greater than or equal to the specific value of the remittance amount, which is sufficient to pay for the above remittance transaction, that is, the node (verifier) in the blockchain is based on the zero-knowledge proof algorithm for the first A zero-knowledge certificate performs zero-knowledge verification to confirm whether the sum of the reserve funds allocated to the remittance exchange is greater than or equal to the remittance amount. In the same way, the client device can provide the second zero-knowledge proof so that the nodes (verifiers) in the blockchain do not know the account balance of the user account and the actual value of the reserve amount included in the reserve list. In the case of (clear text), it can be believed whether the sum of the amount of multiple reserves included in the reserve list creation transaction is not greater than the account balance of the above user account.

In the illustrated embodiment, when the reserve balance and reserve balance in the user account are also displayed in the status of the user account, that is, other nodes on the blockchain can learn the status of the user device by querying the status of the user account In the case of reserve balance and reserve balance, in order to protect the privacy of the user's account, the reserve balance and reserve balance of the user account are also encrypted in advance. At this time, the above second zero knowledge proof can be used to prove the preparation based on the switch The sum of the multiple reserve funds divided by the gold balance is less than or equal to the reserve balance after the switching. Since the reserve balance after the switch is based on the account balance, the reserve balance must be smaller than the account balance, so the above second zero knowledge proof can also be used for blockchain nodes to verify the reserve list and create an exchange. The sum of the gold amount is not greater than the account balance provides valid proof.

This specification does not limit the types of cryptographic encryption algorithms mentioned above, and can include addition homomorphic encryption algorithms or fully homomorphic encryption algorithms, and can also include homomorphic commitment algorithms (such as Pederson Commitment, etc.), as long as the encryption algorithm can meet the addition homology It can also support zero-knowledge proof that a plaintext data belongs to a certain range, so that the account balance (or reserve balance) of the encrypted sender user can be directly deducted from the encrypted remittance amount, and the account balance of the encrypted receiver user can be Directly increase the amount of encrypted remittances.

For example, the above-mentioned blockchain can support the Pedersen Commitment Commitment Algorithm based on elliptic curves to ensure that the encrypted amount in the blockchain can be verified in the encrypted state, and the addition homomorphism can be achieved.

This specification does not limit the specific types of the first zero-knowledge proof and the second zero-knowledge proof. For example, Range Proof technology in related technologies, such as the Bulletproofs scheme or the “zksnark” universal zero-knowledge proof technology, can be used.

In yet another illustrated embodiment, in order to prevent user nodes in the blockchain from maliciously attacking the blockchain, the above remittance transaction may also include a third zero knowledge proof to prove that the remittance amount is greater than or equal to zero, The above third zero-knowledge proof can be generated based on the encrypted remittance amount, so that the node (verifier) in the blockchain can verify the remittance amount of the remittance transaction without knowing the actual value of the remittance amount (clear text) Less than zero.

In another embodiment shown, in order to prevent user nodes in the blockchain from generating an invalid reserve amount, the reserve list creation transaction may also include each provision included in the reserve list creation exchange to prove The fourth zero knowledge proof that the gold amount is greater than or equal to zero. The above fourth zero knowledge proof can be generated based on each reserve amount, so that the nodes (verifiers) in the blockchain do not know the actual value of each reserve amount (clear text) ), You can verify that each reserve amount included in the reserve list creation transaction is greater than or equal to zero.

In another embodiment shown in this specification, the above-mentioned remittance transaction and reserve list creation transaction may further include a digital signature made by the user terminal device based on the private key of the user account to be used by the blockchain node to perform the electronic signature Verification to prevent other nodes from pretending to be the remittance party and publishing the above first transaction, publishing wrong information, and maliciously disturbing the order of the transaction.

The blockchain-based remittance method provided in this manual divides the account balance of the user account into at least a reserve balance and a reserve balance, and builds a reserve list containing multiple reserve amounts based on the reserve balance, which is a user account Concurrent remittance transactions provide proof of payment; when the available reserve amount in the above reserve list is lower than the preset threshold, or when a new reserve list construction instruction is received, the above reserve balance is switched to the reserve month, based on The above-mentioned switched reserve balance builds a new reserve list containing multiple reserve amounts; after the new reserve list is verified by the blockchain node and the new reserve list is updated to the user account, the user account Build new remittance transactions based on the new reserve list. In the process of switching the reserve list, the remittance transaction can still be constructed based on the original reserve list without suspension; and the process of switching the reserve balance and creating a new reserve list can be used according to the current use of the reserve list ( Whether the amount of reserves available for distribution is lower than the preset threshold), or the new reserve list construction instructions that should be received are executed cyclically, so there is no need to suspend the transaction of sending remittances throughout the process, improve the concurrency of transactions, and avoid transaction interruptions Maximized the throughput of blockchain transactions.

In order to facilitate understanding, the following uses the remittance transaction in the blockchain network as an example to describe the technical solution of this specification in detail. FIG. 3 is a schematic diagram of implementing a remittance transaction and a reserve list transaction in a blockchain network provided by an exemplary embodiment. Assume that the exporter device used by user A is user device 1, for example, a user account corresponding to user A is registered on user device 1; similarly, the receiver device used by user B is user device 2. The user device 1 may run a client program of the blockchain, so that the user device 1 has a corresponding blockchain node in the blockchain network, such as the node 1 shown in FIG. 2. Similarly, the user equipment 2 may run a client program of the blockchain, so that the user equipment 2 has a corresponding blockchain node in the blockchain network, such as the node 2 shown in FIG. 3. There are other blockchain nodes in the blockchain network, such as the node i shown in Figure 3. Through the above node 1, node 2, node i, etc., the remittance transaction between user A and user B, and the reserve list creation transaction sent by user A can be implemented through the blockchain network, and related transaction information can be recorded to In the blockchain ledger maintained by each blockchain node, tampering can be avoided, and it is helpful for subsequent inspections.

For example, user A transfers blockchain money to user B. After user A registers an account, he should first send a reserve list to create a transaction to initialize the reserve list in his account. Among them, the "user" in this manual can be represented as the logged-in user account, and the user account can actually belong to an individual or organization, and this manual does not limit this.

As shown in FIG. 5, in the above blockchain, user A's account balance s_A is divided into two sub-balances: s_A_1 and s_A_2, and user B's account balance s_B is also divided into two sub-balances: s_B_1 and s_B_2. User A's account balances s_A, sub balances s_A_1 and s_A_2 and user B's account balances s_B, sub balances s_B_1 and s_B_2 are all encrypted based on the encryption algorithm:

S_A = HE (s_A), S_A_1 = HE (s_A_1), S_A_2 = HE (s_A_2);

S_B = HE (s_B), S_B_1 = HE (s_B_1), S_B_2 = HE (s_B_2).

In an embodiment, the above encryption algorithm may be a Pederson Commitment homomorphic commitment algorithm.

Initially, the sub balance s_A_1 is the reserve balance, s_A_2 is the collection balance, the sub balance s_B_1 is the reserve balance, and s_B_2 is the collection balance.

Figure 4 illustrates a user setting A M _A reserve list and initiate the process of remittance transactions based on the reserve list M _A. The process of setting up user A's reserve list M _A includes the following steps:

Step 401, establishing the reserve list of the user A M _A, M _A above the reserve list for user A includes sub-dividing the balance s_A_1 obtained is, a plurality of reserve based on the amount of M _A homomorphic encryption algorithm encryption HE [1 ], M _A [2], ..., M _A [L _A ], and the amount of the above reserves M _A [1], M _A [2], ..., M _A [L _A ] The use status is marked as "unused status".

In specific implementation, the user A may s_A_1 or sub-sub-balance balance balance s_A_1 portion is divided, to obtain a plurality of the above-described reserve amount plaintext _{_{m a [1], m a}} [2], ..., m a [L A] , And based on the above homomorphic encryption algorithm to encrypt the above multiple reserve amounts to obtain the reserve amount ciphertext M _A [1], M _A [2], ..., M _A [L _A ]; User A can also The ciphertext S_A_1 of the sub-balance s_A_1 is directly divided to obtain M _A [1], M _A [2], ..., M _A [L _A ], and based on the inverse operation of the above homomorphic encryption algorithm, the amount of the above reserve is obtained ciphertext corresponding to the plaintext _{_{m a [1], m a}} [2], ..., m a [L a]. User A may plaintext m above the reserve amount of _{_{a [1], m a [}} 2], ..., m a [L A] and ciphertext _{_{M A [1], M A}} [2], ..., M A [ The corresponding relationship of L _A ] is saved separately, so that user A can choose the appropriate reserve amount in the specific remittance transaction. Alternatively, user A can only save the plain text of the above reserve amount on the local user terminal. The user terminal periodically synchronizes the account data from the blockchain, and decrypts the encrypted data obtained from the blockchain to obtain the The amount of reserves used.

Step 402, the user A generates a zero-knowledge proof _{PF [s_A_1≥ (m a [1} ] + m a [2] + ... + m a [L A])], used to demonstrate the above-described reserve list of M _A M _A _{[1], m a [2} ], ..., m a [L a] corresponding to the reserve amount _{_{m a [1], m a}} [2], ..., m a [L a] of less than or equal to the user a the sub-balance s_A_1, the above-described zero-knowledge proof _{PF [s_A_1≥ (m a [1} ] + m a [2] + ... + m a [L a])] without the use of the reserve amount _{_{m a [1], m a}} [ _{2], ..., m a [} LA] and the value of s_A_1 can verifier believes _{_{m a [1], m a}} [2], ..., m a [L a] is less than or equal to the sum of s_A_1. In an embodiment, the above zero-knowledge proof PF [s_A_1≥ (m _a [1] + m _a [2] +… + m _a [L _A ])] can use general zero-knowledge proof technology such as zksnark or Bulletproof scheme, etc. Interval proof technology.

Step 403, the user A generates a zero-knowledge proof _{PF (m a [i] ≥0} ), to prove the above-described reserve list of M _A _{_{M A [1], M A}} [2], ..., M A [L A ] corresponding to the amount of reserve _{_{m a [1], m a}} [2], ..., m a [L a] is not less than zero. Above zero-knowledge proof _{PF (m a [i] ≥0} ) without the use of the reserve amount m _a [i] values to the verifier believes that the m _a [i] ≥0. In an embodiment, the above-mentioned zero-knowledge proof PF (m _a [i] ≥0) may use the interval proof technique such as the Borromean ring signature scheme or the general zero-knowledge proof technical scheme such as zksnark.

Step 404, the user _{A M A, PF [s_A_1≥ (} m a [1] + m a [2] + ... + m a [LA])], PF (m a [i] ≥0) generating a digital signature based Sign A _s.

In step 405, user A sends a transaction T _s to the blockchain to determine the above reserve list M _A , and the above transaction T _s includes M _A and PF [s_A_1≥ (m _a [1] + m _a [2] + … + M _a [L _A ])], PF (m _a [i] ≥ 0), where 1 <= i <= L_A, and Sign A _s .

Step 406, the node of the blockchain receives the above transaction T _s .

In step 407, the node of the blockchain performs the verification of the electronic signature Sign A _s of the above transaction T _s , and if it passes, the next step is performed.

408, the step of block chain of nodes _{PF [s_A_1≥ (m a [1} ] + m a [2] + ... + m a [L A])] is zero-knowledge proof algorithm based on zero-knowledge proof to confirm m _a _{[1], m a [2} ], ..., m a [L a] is less than or equal to the sum of the sub-balance s_A_1 user a; if yes, performing next step.

Step 409, the nodes of the blockchain perform zero-knowledge verification on PF (m _a [i] ≥0) based on the zero-knowledge proof algorithm to confirm that (m _a [i] ≥0 is not less than zero, where 1 <= i < = L_A; if yes, go to the next step.

Step 410, the node of the blockchain records the verified transaction T _s into the distributed database of the blockchain, and updates the reserve list M _A to the account status of the user A.

At this point, the node of the blockchain has completed the update of user A's reserve list M _A. Those skilled in the art are familiar with the fact that in the actual implementation process of setting or updating user A's reserve list M _A , there may be many Other verification steps, such as anti-replay verification, etc., are not limited here; and this specification does not limit the sequence of generating each certificate or electronic signature, nor does it limit the nodes in the blockchain to the exporter. The sequence of verification of various certificates or electronic signatures in the transaction Ts. FIG. 4 is only an embodiment of a method for setting a user's reserve list provided in this specification, and this specification is not limited to this. The setting process of the reserve fund list MB in the user B account is similar to the above steps 401 to 410, and will not be repeated here.

The blockchain in Figure 4 performs the process of remittance and transfer from user A to user B as follows:

Step 411: User A generates a remittance amount ciphertext S _t = HE (s_t) based on the above homomorphic encryption algorithm, where s_t is the amount of remittance transferred from user A to user B.

In step 412, the user A selects an unused reserve ciphertext M _A [k] from the reserve list M _A whose plaintext m _A [k] is sufficient to pay the remittance amount s_t, and transfers the reserve amount The ciphertext M _A [k] is marked as being used so that M _A [k] can no longer be designated in other new remittance transactions.

Step 413, the user A generates a zero-knowledge proof _{Pf (m A [k] ≥s_t} ), to prove M _A [k] corresponding to the amount of reserve m _A [k] is sufficient to pay remittances this S_T; above-zero-knowledge proof Pf (m _A [k] ≥s_t) without using the values of m _A [k] and s_t can convince the verifier that m _A [k] ≥s_t.

Step 414: User A generates a zero-knowledge proof Pf (s_t≥0) to prove that the remittance amount s_t is not less than zero; the above-mentioned zero-knowledge proof Pf (s_t≥0) does not use the value of s_t, so that the verifier can believe s_t ≥0.

Step 415, the user A based _{St, M A [k],} Pf (m A [k] ≥s_t), Pf (s_t≥0) generating a digital signature Sign A _t.

In step 416, user A sends a transaction T _t to the blockchain to transfer money to user B. The transaction T _t includes S _t , M _A [k], Pf (m _A [k] ≥s_t), Pf (s_t≥ 0) and Sign a _t, the foregoing state are ciphertext, thus protecting the user a, B, privacy remittance transactions.

In step 417, the node of the blockchain receives the above transaction T _t .

Step 418, the node performs block chain to verify the signature Sign A _t T _t above electronic transaction, if passed, the next steps.

Step 419, the node of the blockchain verifies whether the _MA [k] contained in the above T _t is in the used state; if not, the next step is executed.

Step 420, the node of the blockchain performs zero-knowledge verification on PF (m _a [k] ≥s_t) based on the zero-knowledge proof algorithm to confirm whether the amount of reserves corresponding to M _A [k] is greater than or equal to the remittance amount; If yes, go to the next step.

Step 421, the node of the blockchain performs zero-knowledge verification on the PF (s_t≥0) based on the zero-knowledge proof algorithm to confirm that the actual value of the remittance amount corresponding to the remittance amount cipher text S _{t of} this remittance transaction is not less than zero; if it is To perform the next step.

Step 422, the node of the blockchain collects the verified transaction T _t into the distributed database of the blockchain, and based on the homomorphic operation in the account balance ciphertext S_A of user A and the subaccount balance ciphertext S_A_1 The property deducts the remittance amount ciphertext S _t , and the user B's account balance ciphertext S_B and sub-account balance ciphertext S_B_2 both increase the remittance amount ciphertext S _t based on the homomorphic computing property, so that the user A's account The balance is updated to (s_A-s_t), the balance of the remittance sub-account of A is updated to (s_A_1-s_t), the balance of the account of user B is updated to (s_B + s_t), and the balance of B's collection sub-account is updated to s_B_2 + s_t); and change the state corresponding to M _A [k] in the reserve list M _A of user A to the used state.

In addition, those skilled in the art are well aware that in the actual implementation of the remittance transaction, many other verification steps, such as anti-replay verification, etc., may also be included, which are not limited here; and this specification does not limit the generation of each certificate Or the sequence of electronic signatures, nor does it limit the sequence of nodes in the blockchain to the verification of the various certificates or electronic signatures in the transaction T _t proposed by the exporter. Figure 4 is only based on the blockchain provided in this specification. An embodiment of the remittance method, this description is not limited to this.

Although the continuous numbers in Figure 4 indicate the process of user A initializing the reserve list and user A's remittance to user B, this does not mean that user A needs to set up a reserve in his account before each remittance transaction is initiated. List. Those skilled in the art are familiar with the fact that before registering as a blockchain user for the first remittance transaction, users need to initialize the reserve list in their account; when the encrypted reserve amount in the above reserve list is After use, or the remaining encrypted reserve amount corresponding to the reserve amount is no longer enough to pay for the next remittance transaction, the user needs to reset the reserve list in his account; the user can also periodically according to their specific needs Update the above reserve list.

As the amount of remittance transactions sent by user A increases, the amount of reserves available in reserve list M _A gradually decreases, and device node 1 of user A monitors the sum of the amount of reserves available in reserve list M _A , or monitors The sum of the amount of reserves available in the reserve list M _A. When the sum of the above values, or the sum of the numbers is lower than the set threshold, user A switches their sub-accounts s_A_1 and s_A_2, based on the new The reserve balance s_A_2 to generate a new reserve list M _A '. The construction process of the new reserve list M _A 'is similar to steps 401-410, and will not be repeated here. After M _A ' is updated to user A's account, it will replace the original reserve list M _A as a new effective The reserve list provides proof of payment for remittance transactions.

Figure 2 illustrates the above process of creating and updating the reserve list in User A's account. It can be seen from Figure 2 that through the cyclic switching of sub-account balances, there is always a valid reserve list in User A's account for Concurrent remittance transactions provide multiple reserve amounts, so that user A does not need to suspend remittance transactions to update the reserve list, ensuring the maximum concurrent submission and execution of remittance transactions. Moreover, in the remittance transaction method provided in this embodiment, since two sub-account balances for remittance and remittance are separately set, it is assumed that when user A performs a remittance transaction to B, another user C is A initiates a remittance transaction, and all of these transactions can be submitted and executed at the same time; because the zero-knowledge proof used during the execution of the entire transaction is only related to the relevant reserve amount, the account balance can be increased or deducted at will.

It is worth noting that, as shown in FIG. 5, user A ’s sub-account balance S_A_2 is initially used as a collection transaction. When the user device detects that the amount of the reserve in the reserve list M _A is lower than the preset threshold, It is necessary to switch the functions of the sub-account balance S_A_1 and the sub-account balance S_A_2, S_A_1 as the payment balance and S_A_2 as the reserve balance. Before using S_A_2 as a reserve balance to execute the construction of a new reserve list, the user device needs to wait for a period of time until the transactions of the sub-account balance S_A_2 sent to user A by other users on the blockchain are updated and displayed before the above switch After user A's account balance S_A and sub-account balance S_A_2, after the value of sub-account balance S_A_2 no longer changes, then build a new reserve list based on S_A_2 to prevent the PF generated based on the value of S_A_2 due to the change of S_A_2 [s_A_2≥ (m _a [1] + m _a [2] +… + m _a [L _A ])] Cannot pass the verification of blockchain nodes. The above-mentioned waiting time may be determined according to the block-forming frequency of the blockchain, for example, waiting for about 3-5 block-forming times.

FIG. 6 is a schematic structural diagram of a device provided by an exemplary embodiment. Please refer to FIG. 6. At the hardware level, the device includes a processor 602, an internal bus 604, a network interface 606, a memory 608, and a non-volatile memory 610. Of course, it may include hardware required for other services. The processor 602 reads the corresponding computer program from the non-volatile memory 610 into the memory 608 and then runs it to form a blockchain transaction device at a logical level. Of course, in addition to the software implementation, one or more embodiments of this specification do not exclude other implementations, such as logic devices or a combination of hardware and software, etc., that is to say, the execution body of the following processing flow is not limited to each The logic unit may also be a hardware or logic device.

Please refer to FIG. 7, this specification also provides a blockchain-based remittance device 70, which is applied to the user equipment of the blockchain, and the account balance of the user account is divided into at least a reserve balance and a reserve balance; , The user account includes a dynamically updated reserve list; the reserve list includes multiple reserve amounts;

The device 70 includes:

The reserve amount allocation unit 702, in response to the remittance operation initiated by the user, allocates the corresponding reserve amount to the remittance amount submitted by the user according to the current reserve list provided by the reserve list creation unit 704;

The remittance transaction construction and release unit 706 builds a remittance transaction based on the remittance amount and the allocated reserve amount, and publishes the remittance transaction to the blockchain, so that the remittance transaction is a node in the blockchain After the device is verified, the remittance amount is deducted from both the account balance and the reserve balance;

Wherein, the reserve list creation unit 704 includes:

The reserve list generation module 7042 obtains the current reserve balance and obtains the reserve list according to the current reserve balance;

The reserve list monitoring module 7044 dynamically monitors whether the amount of reserves available for distribution in the current reserve list is lower than a preset threshold.

In an illustrated embodiment, the reserve list generation module 7042:

In an illustrated embodiment, the device 70 further includes:

The switching unit 708, after obtaining the reserve list based on the current reserve balance, switches the reserve balance before switching to the reserve balance.

In an illustrated embodiment, the standby balance is a collection balance; wherein, when another user initiates a remittance transaction to the user account and is verified by the node device of the blockchain, the remittance amount in the remittance transaction Will be added to the collection balance and the account balance.

In an illustrated embodiment, the account balance of the user account, the reserve amount, and the remittance amount are all encrypted in advance;

The remittance transaction also includes a first zero-knowledge certificate to prove that the sum of the reserves included for the remittance transaction is greater than or equal to the remittance amount of the remittance transaction;

The reserve list creation transaction also includes a second zero-knowledge proof to prove that the sum of the plurality of reserve amounts divided based on the switched reserve balance is less than or equal to the user's account balance.

In an illustrated embodiment, the reserve balance and reserve balance of the user account are encrypted in advance, and the second zero-knowledge proof is used to prove a plurality of reserves divided based on the reserve balance after switching The sum of the gold amounts is less than or equal to the reserve balance after the switch.

In an illustrated embodiment, the remittance transaction further includes a third zero-knowledge proof to prove that the remittance amount is greater than or equal to zero.

In an illustrated embodiment, the reserve list creation transaction further includes a fourth zero proof of knowledge to prove that a plurality of reserve amounts divided based on the switched reserve balance are all greater than or equal to zero.

For the implementation process of the functions and functions of each unit and module in the above device, please refer to the implementation process of the corresponding steps in the above method for specific details. For the relevant parts, please refer to the partial description of the method embodiment, which will not be repeated here.

The system, device, module or unit explained in the above embodiments may be specifically implemented by a computer chip or entity, or by a product having a certain function. A typical implementation device is a computer, and the specific form of the computer may be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email sending and receiving device, and a game control Desk, tablet computer, wearable device, or any combination of these devices.

Corresponding to the above method embodiments, the embodiments of the present specification also provide a computer device, which includes a memory and a processor. Among them, a computer program that can be executed by the processor is stored on the memory; when the processor runs the stored computer program, each step of the block chain-based remittance method in the embodiment of the present specification is executed. For a detailed description of the various steps of the blockchain-based remittance method, please refer to the previous content, and it will not be repeated.

Corresponding to the above method embodiments, the embodiments of the present specification also provide a computer-readable storage medium that stores computer programs on the storage medium. When these computer programs are executed by the processor, the computer program is executed based on The various steps of the blockchain remittance method. For a detailed description of the various steps of the blockchain-based remittance method, please refer to the previous content, and it will not be repeated.

The above are only the preferred embodiments of this specification and are not intended to limit this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principles of this specification should be included in this specification Within the scope of protection.

In a typical configuration, the computing device includes one or more processors (CPUs), input / output interfaces, network interfaces, and memory.

The memory may include non-permanent memory, random access memory (RAM) and / or non-volatile memory in computer-readable media, such as read only memory (ROM) or flash memory (flash RAM). Memory is an example of computer-readable media.

Computer-readable media, including permanent and non-permanent, removable and non-removable media, can store information by any method or technology. The information may be computer readable instructions, data structures, modules of programs, or other data.

Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, read-only compact disc read-only memory (CD-ROM), digital versatile disc (DVD) or other optical storage, Magnetic tape cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include temporary computer-readable media (transitory media), such as modulated data signals and carrier waves.

It should also be noted that the terms "include", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or device that includes a series of elements not only includes those elements, but also includes Other elements not explicitly listed, or include elements inherent to such processes, methods, goods, or equipment. Without more restrictions, the element defined by the sentence "include one ..." does not exclude that there are other identical elements in the process, method, commodity, or equipment that includes the element.

Those skilled in the art should understand that the embodiments of the present specification may be provided as methods, systems, or computer program products. Therefore, the embodiments of the present specification may take the form of an entirely hardware embodiment, an entirely software embodiment, or an embodiment combining software and hardware. Moreover, the embodiments of this specification may take the form of computer program products implemented on one or more computer usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer usable program code .

Claims

A blockchain-based remittance method is applied to the user equipment of the blockchain. The account balance of the user account is divided into at least a reserve balance and a reserve balance; wherein, the user account includes a dynamically updated reserve Gold list; the reserve fund list includes multiple reserve fund amounts;

The method includes:

In response to the remittance operation initiated by the user, a corresponding reserve amount is allocated to the remittance amount submitted by the user according to the current reserve list; a remittance transaction is constructed based on the remittance amount and the allocated reserve amount, and the remittance transaction is transferred Post to the blockchain to deduct the remittance amount from both the account balance and the reserve balance after the remittance transaction is verified by the node device in the blockchain;

Among them, the process of creating and updating the reserve list includes:

Step A: Obtain the current reserve balance and obtain a reserve list according to the current reserve balance;

Step B: dynamically monitor whether the amount of reserves available for allocation in the current reserve list is lower than a preset threshold, and if so, after switching the current reserve balance to the reserve balance, perform step A.
The method according to claim 1, the obtaining a reserve list according to the current reserve balance includes:

Divide the current reserve balance to obtain multiple reserve amounts, and build a reserve list creation transaction based on the divided reserve amounts;

Publish the reserve list creation transaction to the blockchain, so that after the reserve list creation transaction is verified by the node device in the blockchain, multiple reserve funds obtained based on the division in the user account Amount to build a reserve list.
The method according to claim 1, the obtaining a reserve list according to the current reserve balance includes:

Divide the current reserve balance to obtain multiple reserve amounts, build a reserve list based on the divided reserve amounts, and construct a reserve list based on the reserve list to create a transaction;

Posting the reserve list creation transaction to the blockchain to update the reserve list to the user account after the reserve list creation transaction is verified by the node device in the blockchain.
The method of claim 1, further comprising:

After obtaining the reserve list according to the current reserve balance, the reserve balance before switching is switched to the reserve balance.
The method according to claim 4, wherein the standby balance is a remittance balance; wherein, when another user initiates a remittance transaction to the user account and is verified by the node device of the blockchain, the remittance amount in the remittance transaction Will be added to the collection balance and the account balance.
According to the method of claim 2 or 3, the account balance of the user account, the reserve amount and the remittance amount are all encrypted in advance;

The remittance transaction also includes a first zero-knowledge certificate to prove that the sum of the reserves included for the remittance transaction is greater than or equal to the remittance amount of the remittance transaction;

The reserve list creation transaction also includes a second zero-knowledge proof to prove that the sum of the plurality of reserve amounts divided based on the switched reserve balance is less than or equal to the user's account balance.
The method according to claim 2 or 3, the reserve balance and reserve balance of the user account are encrypted in advance, and the second zero-knowledge proof is used to prove a plurality of reserves divided based on the reserve balance after switching The sum of the gold amounts is less than or equal to the reserve balance after the switch.
According to the method of claim 6, the remittance transaction further includes a third zero-knowledge proof to prove that the remittance amount is greater than or equal to zero.
According to the method of claim 6, the reserve list creation transaction further includes a fourth zero proof of knowledge to prove that a plurality of reserve amounts divided based on the switched reserve balance are all greater than or equal to zero.
A blockchain-based remittance device is applied to the user equipment of the blockchain. The account balance of the user account is divided into at least a reserve balance and a reserve balance; wherein, the user account includes a dynamically updated reserve Gold list; the reserve fund list includes multiple reserve fund amounts;

The device includes:

The reserve amount allocation unit, in response to the remittance operation initiated by the user, allocates the corresponding reserve amount to the remittance amount submitted by the user according to the current reserve list provided by the reserve list creation unit;

The remittance transaction construction and release unit, constructs a remittance transaction based on the remittance amount and the allocated reserve amount, and publishes the remittance transaction to the blockchain, so that the remittance transaction is used by the node device in the blockchain After the verification is passed, the remittance amount is deducted from both the account balance and the reserve balance;

Wherein, the reserve fund list creation unit includes:

The reserve list generation module obtains the current reserve balance and obtains the reserve list according to the current reserve balance;

The reserve list monitoring module dynamically monitors whether the amount of reserves available for distribution in the current reserve list is lower than a preset threshold.
The apparatus according to claim 10, the reserve fund list generation module:

Divide the current reserve balance to obtain multiple reserve amounts, and build a reserve list creation transaction based on the divided reserve amounts;

Publish the reserve list creation transaction to the blockchain, so that after the reserve list creation transaction is verified by the node device in the blockchain, multiple reserve funds obtained based on the division in the user account Amount to build a reserve list.
The apparatus according to claim 10, the reserve fund list generation module:

Divide the current reserve balance to obtain multiple reserve amounts, build a reserve list based on the divided reserve amounts, and construct a reserve list based on the reserve list to create a transaction;

Posting the reserve list creation transaction to the blockchain to update the reserve list to the user account after the reserve list creation transaction is verified by the node device in the blockchain.
The apparatus according to claim 10, further comprising:

The switching unit, after obtaining the reserve list according to the current reserve balance, switches the reserve balance before switching to the reserve balance.
The device according to claim 13, wherein the standby balance is a remittance balance; wherein, when another user initiates a remittance transaction to the user account and is verified by the node device of the blockchain, the remittance amount in the remittance transaction Will be added to the collection balance and the account balance.
The apparatus according to claim 11 or 12, the account balance of the user account, the reserve amount and the remittance amount are all encrypted in advance;

The remittance transaction also includes a first zero-knowledge certificate to prove that the sum of the reserves included for the remittance transaction is greater than or equal to the remittance amount of the remittance transaction;

The reserve list creation transaction also includes a second zero-knowledge proof to prove that the sum of the plurality of reserve amounts divided based on the switched reserve balance is less than or equal to the user's account balance.
The apparatus according to claim 11 or 12, the reserve balance and the reserve balance of the user account are encrypted in advance, and the second zero-knowledge proof is used to prove a plurality of reserves divided based on the reserve balance after switching The sum of the gold amounts is less than or equal to the reserve balance after the switch.
According to the apparatus of claim 15, the remittance transaction further includes a third zero-knowledge proof to prove that the remittance amount is greater than or equal to zero.
According to the apparatus of claim 15, the reserve list creation transaction further includes a fourth zero proof of knowledge to prove that a plurality of reserve amounts divided based on the switched reserve balance are all greater than or equal to zero.
A computer device comprising: a memory and a processor; a computer program executable by the processor is stored on the memory; when the processor runs the computer program, the computer program according to any one of claims 1 to 9 is executed method.
A computer-readable storage medium on which a computer program is stored, and when the computer program is executed by a processor, executes the method according to any one of claims 1 to 9.