WO2020037927A1

WO2020037927A1 - Negotiable block chain transaction method, apparatus, device, and storage medium

Info

Publication number: WO2020037927A1
Application number: PCT/CN2018/124439
Authority: WO
Inventors: 谢丹力; 贾牧; 陆陈一帆
Original assignee: 深圳壹账通智能科技有限公司
Priority date: 2018-08-24
Filing date: 2018-12-27
Publication date: 2020-02-27
Also published as: CN109345251A

Abstract

A negotiable block chain transaction method, belonging to the field of block chain technology. The transaction in said method comprises: receiving a transaction request, in a transaction, initiated from a fund transfer-out party to a block chain (step 01); verifying the received request (step 02), and if the verification succeeds, writing all the content contained in said request into a temporary account block corresponding to the transaction request; receiving a feedback request initiated from an opposite party of the request initiating party to the block chain (step 03), and if the feedback request is a transaction modification request, repeating the previous step; if the feedback request is a transaction closing request, then identifying the type of the transaction closing request (step 04); if the transaction closing request is a transaction accepting request, writing a formal account balance into a formal account block (step 05); if the transaction closing request is a transaction rejecting request, adding, in the temporary account block, a transaction amount contained in the latest request onto a temporary account balance and the formal account balance of both transacting parties (step 06). The present solution solves the problem that negotiation cannot be performed online in the traditional block chain transaction mode.

Description

Negotiable blockchain transaction method, device, device and storage medium

This application affirms the priority of the Chinese patent application filed on August 24, 2018 with the application number 201810972002.5 and the name "negotiable blockchain transaction method, device, device and storage medium", the entirety of the Chinese patent application The contents are incorporated herein by reference.

Technical field

The present application relates to the field of blockchain technology, and relates to a negotiable blockchain transaction method, device, device, and storage medium.

Background technique

The blockchain is essentially a distributed database. The entire data storage process is initiated by the application in the form of a transaction. On the blockchain, after being signed and endorsed by all parties, the transaction is accepted and the result of the transaction is written back to the blockchain. Once the transaction is written Blockchain is irrevocable.

However, the actual business environment has huge complexity. If a transaction involves an illegal transaction, once the transaction occurs and takes effect, it may cause irreparable losses; or it may result in a transaction error caused by the originator of the transaction. Transactions that should not have occurred are also serious losses.

In addition, in actual commercial business scenarios, it often involves the two parties of the transaction needing to negotiate multiple times. When the transaction initiator initiates a transaction, the transaction receiver considers that the amount of the transaction is unreasonable. At this time, the receiver can only Rejecting this transaction, and then negotiating with the transaction initiator through other methods, such as offline, and then re-initiating a new transaction by the transaction initiator, this process is inefficient and inconvenient.

Summary of the Invention

The technical problem to be solved in this application is to overcome the problem that the transactions on the blockchain cannot be changed or revoked in the prior art. A negotiable blockchain transaction method, device, device and storage medium are proposed. Transaction buffer, used to buffer all unconfirmed transaction messages.

This application solves the above technical problems through the following technical solutions:

A negotiable blockchain transaction method. A temporary ledger block and a formal ledger block with a mapping relationship are established on the blockchain. The transaction includes the following steps:

Receive a transaction request initiated by the transfer of funds in the transaction to the blockchain;

Verify the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current official ledger balance, and the signature included in the received request. If the verification is passed, write all the content contained in the request to the transaction Request the corresponding temporary ledger block;

Receiving a feedback request initiated by the blockchain in the opposite direction of the request, if the feedback request is a transaction modification request, repeating the previous step; if the feedback request is a transaction end request, further identifying the type of the transaction end request;

If the transaction end request is a consent transaction request, write the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender to the The temporary ledger block has a mapping relationship in the formal ledger block;

If the transaction end request is a transaction rejection request, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.

This application also discloses an electronic device. The electronic device stores a negotiable blockchain transaction system. The negotiable blockchain transaction system includes:

The request receiving module is used to receive a transaction request initiated by the blockchain in the transfer of funds out of the transaction, and a feedback request initiated by the blockchain opposite to the originating request;

A verification module for verifying the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current formal ledger balance, and the signature included in the received request, and after all the verifications are passed, all The content is written into the temporary ledger block corresponding to the transaction request;

A feedback request identification module, configured to identify the type of the feedback request, and jump to the verification module when the feedback request is a transaction modification request, and further identify the end of the transaction when the feedback request is a transaction end request The type of request

A formal ledger modification module is configured to: when the transaction end request is a consent transaction request, the formal ledger balance included in the consent transaction request and the formal request included in the last request initiated by the counterparty of the consent request sender The ledger balance is written into a formal ledger block having a mapping relationship with the temporary ledger block;

The transaction termination module is configured to: when the transaction end request is a transaction refusal request, in the temporary ledger block, add the temporary ledger balance and formal ledger balance of both parties to the transaction to the transaction amount included in the latest request, respectively.

This application also discloses a computer device including a memory and a processor. The memory stores a negotiable blockchain transaction system that can be executed by the processor, and the system is implemented when the system is executed by the processor. The following steps:

The present application also discloses a computer-readable storage medium. The computer-readable storage medium stores computer program instructions, and the computer program instructions can be executed by at least one processor to enable the at least one processor to execute. The following steps:

The positive progress effect of this application lies in:

1. This application breaks the deadlock that cannot be negotiated online in the traditional blockchain transaction model;

2. This application divides the ledger into a temporary ledger and a formal ledger, so that the negotiation process will not affect the formal ledger.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a flowchart of Embodiment 1 of a negotiable blockchain transaction method;

FIG. 2 shows a flowchart of a second embodiment of a negotiable blockchain transaction method;

3 shows a schematic diagram of a program module of a first embodiment of a negotiable blockchain transaction system in an electronic device of the present application;

4 shows a schematic diagram of a program module of a second embodiment of a negotiable blockchain transaction system in an electronic device of the present application;

FIG. 5 shows a schematic diagram of a hardware architecture of an embodiment of a computer device of the present application.

detailed description

The following further describes the application by way of examples, but the application is not limited to the scope of the examples.

First, this application proposes a negotiable blockchain transaction method.

This method requires the establishment of a temporary ledger block and a formal ledger block with a mapping relationship on the blockchain. That is, two sets of ledgers are established on the blockchain with a mapping relationship between the two sets of ledgers (between the two sets of ledgers). The mapping relationship can be regarded as two states of a ledger, and they have the same AccountId (account ID), that is, the mapping relationship is determined by AccountId). All transaction records before confirmation are only recorded in the temporary ledger block. Only the transaction that is finally confirmed will be recorded in both the temporary ledger block and the formal ledger block.

In the first embodiment, as shown in FIG. 1, the negotiable blockchain transaction includes the following steps:

Step 01: Receive a transaction request initiated by the transfer of funds in the transaction to the blockchain.

The fund transfer party is from the perspective of the ledger, and refers to the party whose funds are reduced.

The content of the transaction request includes a ledger ID, a current transaction ID, a transaction requester ID, a transaction counterparty ID, a transaction amount, a current temporary ledger balance of the transaction requester, a current formal ledger balance of the transaction requester, and the current formal ledger Zero-knowledge proof of the balance, zero-knowledge proof of the current temporary ledger balance, and the signature of the requester of the transaction.

The ledger ID is used to distinguish the creator of the ledger. For example, WeChat's ledger is recorded by the blockchain created by Tencent. Alipay's ledger is recorded by the blockchain created by Alibaba. Since anyone can create a blockchain ledger, In order to distinguish ledgers, each ledger is assigned an ID for unique identification, which is the ledger ID.

The current transaction ID, transaction requester ID, and transaction counterparty ID are IDs used to uniquely distinguish the transaction, the transaction requester, and the transaction counterparty, respectively.

The current formal ledger balance of the transaction requester refers to the real balance of the transaction requester recorded in the formal ledger block; the current temporary ledger balance of the transaction requester refers to the transaction requester (specifically in this step: The official account balance (real balance) of the fund transfer party that initiated the transaction request minus all its pending transactions (because the transaction requester is allowed to initiate multiple transaction requests at the same time, and these transaction requests are (Before confirmation, all are in the state of confirmation) The difference after the sum of the amounts.

For example, suppose the transaction requester initiated two pending transactions, specifically to deliver two transactions totaling 100 yuan to its counterparty. Since neither transaction has been confirmed by the counterparty of the transaction, the transaction The claimant's account book also has the 100 yuan, that is, the 100 yuan has not been deducted from its real balance, but the 100 yuan has been deducted from its temporary account book balance. Are inconsistent.

The zero-knowledge proof refers to a method in which the demonstrator does not disclose any information when proving his identity, and the verifier cannot obtain any private information of the demonstrator, but can effectively prove the identity of the other party. Take ZCASH (the name of an electronic currency) digital currency in the blockchain as an example. The digital currency uses zero-knowledge proof and is completely anonymous during the entire transaction process. During the ZCASH transaction, A transfers to B and creates a UTXO (Unspent Transaction Output). The original will be sent to a void list, but this list records the previous serial number or code, which proves the previous UTXO Failure. In this process, B cannot see the information before A, but the transaction does occur. Zero-knowledge proofs are used to ensure that there is no “double spending” on the transfer side.

In the blockchain, the signing used uses asymmetric encryption technology and digital digest technology to ensure the integrity of the data during transmission and the authenticity of the sender's identity cannot be counterfeited. Asymmetric encryption technology will generate a public key and a private key. The public key and the private key are a pair. The private key is kept in the owner's hands. It needs to be kept secret from outsiders. Other information recipients are public. If the private key is used to encrypt the data, only the corresponding public key can be decrypted. Conversely, the data encrypted by the public key can only be decrypted by the corresponding private key. A digital digest uses a hash function to transform information of any length into fixed-length information. The hash function is a one-way generation system, and the input value is generated irreversibly by the generated hash value.

The transaction amount described here and the current temporary ledger balance of the transaction requester and the current formal ledger balance of the transaction requester are encrypted.

Step 02: Verify the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current formal ledger balance, and the signature included in the received request. If the verification is passed, write all the content contained in the request To the temporary ledger block corresponding to the transaction request.

The verification means that the current temporary ledger balance and the current official ledger balance are both greater than zero, and that the transaction request is indeed initiated by the transaction requester in the transaction (ie, signature verification).

The counterparty of the requesting party that sent the request uses the public key to decrypt the current temporary ledger balance, current formal ledger balance, and transaction amount contained in the request. Only the content encrypted with the private key corresponding to the public key can be decrypted by the public key. In this way, the identity verification of the requesting party (that is, the transaction requesting party) that sends the request is implemented. Once the decryption fails, the signature verification fails.

After the decryption is successful, the zero-knowledge proof of the current temporary ledger balance and the zero-knowledge proof of the current formal ledger balance are further verified to determine whether the balances of both ledgers are greater than zero.

Step 03: Receive a feedback request initiated by the blockchain in the opposite direction of the request, and determine the type of the feedback request. If the feedback request is a transaction modification request, step 02 is performed; if the feedback request is a transaction end request, Then go to step 04. The content of the transaction modification request includes the current transaction ID, the transaction requester ID, the transaction counterparty ID, the new transaction amount, the current temporary ledger balance of the feedback requesting party, the formal ledger balance of the feedback requesting party, and the current temporary ledger balance Zero-knowledge proof of, the zero-knowledge proof of the current formal ledger balance, and the signature of the requester of feedback.

The transaction end request includes a transaction approval request and a transaction rejection request.

When the counterparty of the transaction receives the transaction request sent by the counterparty, it needs to respond to the request. If the amount needs to be modified, it directly sends a transaction modification request. If it agrees with the transaction or rejects the transaction, it sends a transaction end request. The transaction modification request here is equivalent to a new transaction, and the counterparty of the request is required to provide feedback on the transaction modification request.

A transaction can be modified for several rounds, unlimited times, and a transaction can only be formally concluded when a transaction end request is received.

Regardless of whether the feedback request is the transfer of funds or the transfer of funds in the transaction, the formal ledger balance needs to be included in the request, so that once the transaction is completed, the formal ledger balance will be written into the formal ledger block.

The counterparty here is relative to the originator of the request. For the transaction request, because the transaction request is initiated by the transferee, then the counterparty is the transferee; for the transaction modification request, The modification of the transaction can be made back and forth multiple times, so this counterparty depends on who initiated the transaction modification request. If the originator of the transaction modification request is the fund transfer-in party, then the counterparty is the fund transfer-out party. The initiator is the transferer of funds, and the counterparty is the transferer of funds.

Step 04: Determine whether the transaction end request agrees with the transaction request or rejects the transaction request. If the transaction request is agreed, step 05 is performed, and if the transaction request is rejected, step 06 is performed.

The content of the consent transaction request includes the current transaction ID, the originating requester ID, the requesting counterparty ID, the consent instruction, the consent requester's temporary ledger balance after consent, the consent requestor's formal ledger balance, and the zero of the formal ledger balance. Proof of knowledge; the content of the rejected transaction request includes the current transaction ID, the requesting party ID, the requesting counterparty ID, the rejection instruction, and the temporary account balance of the rejecting requester after rejection.

Therefore, the specific type of the request is identified by identifying whether the transaction end request includes an consent instruction or a rejection instruction.

Step 05: Write the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender to the temporary ledger block that has a mapping relationship with the temporary ledger block. In the official ledger block.

The bookkeeping action in the formal ledger block is triggered by a request to agree to a transaction. As long as one party in the transaction sends a request to agree to the transaction, it means that it has agreed to the transaction amount in the request sent by the other party.

In the temporary ledger, each time a party sends a request, the temporary ledger balance and the official ledger balance in the temporary ledger will be modified. Therefore, after triggering the bookkeeping action in the formal ledger block, you only need to directly transfer the transaction The respective formal ledger balances included in the request initiated by the two parties can be written into the formal ledger block.

Step 06: In the temporary ledger block, the temporary ledger balance and official ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.

If the transaction request is rejected, it means that the two parties did not reach an agreement on the transaction, and the transaction is cancelled, that is, the account balance needs to be restored to the state before the transaction. The account balance here involves the temporary account balance and the official account balance. Two, the formal ledger balance mentioned here refers to the formal ledger balance recorded on the temporary ledger block, but the formal ledger balance on the actual formal ledger block has not changed in any way.

In the second embodiment, based on the first embodiment, as shown in FIG. 2, the negotiable blockchain transaction method includes the following steps:

Steps 01 to 04 are the same as those in the first embodiment, and details are not described herein again.

Step 051: Reconfirm the transaction pointed to by the agreed transaction request according to a preset reconfirmation strategy. If the reconfirmation is passed, go to step 05, otherwise go to step 06.

The reconfirmation strategy may be any one of a third party confirmation, a counterparty confirmation of the transaction request, and a delayed automatic confirmation.

In one embodiment, the re-confirmation strategy adopts third-party confirmation, and the third party may be a regulatory agency, for example. At this time, the transaction request in step 01 also includes a third-party ID and contains Additional information for all content in this transaction request, said additional information is only accessible to third parties. The additional information can be encrypted by ECDH, and only the third party has the corresponding decryption key.

The steps of the third party confirmation are as follows:

Step 0511: Receive an approved transaction request sent by a third party.

The content of the approved transaction request includes a current transaction ID, a transaction requester ID, a transaction counterparty ID, a signature of a third party, and a consent instruction or a rejection instruction.

Step 0512: Determine whether the approved transaction includes a consent instruction or a rejection instruction. If a consent instruction is included, step 05 is performed, and if a rejection instruction is included, step 06 is performed.

In another embodiment, the reconfirmation strategy uses the counterparty confirmation of the transaction request, and the confirmation steps are the same as in the previous embodiment, and only the confirming party is different.

In yet another embodiment, the third party confirmation adopts a delayed automatic confirmation.

The step of delaying automatic confirmation includes:

It is determined whether a request for canceling a transaction sent by any of the two parties to the transaction is received within a preset time; if a request for canceling a transaction is not received, step 05 is performed; if a request for canceling a transaction is received, step 06 is performed.

Steps 05 to 06 are the same as those in the first embodiment, and details are not described herein again.

Secondly, this application proposes an electronic device. The electronic device stores a negotiable blockchain transaction system 20, and the system 20 can be divided into one or more program modules.

For example, FIG. 3 shows a schematic diagram of a program module of the first embodiment of the negotiable blockchain transaction system 20. In this embodiment, the system 20 can be divided into a request receiving module 201, a verification module 202, and a feedback The request identification module 203, the formal ledger modification module 204, and the transaction termination module 205. Among them, the program module referred to in the present application refers to a series of computer program instruction segments capable of performing specific functions. The following description will specifically introduce the specific functions of the program modules 201-205.

The request receiving module 201 is configured to receive a transaction request initiated by a block of funds in a transaction and a feedback request initiated by a block chain opposite to the originating request.

The verification module 202 is configured to verify the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current formal ledger balance, and the signature included in the received request, and after the verification is passed, the request includes All the contents of are written into the temporary ledger block corresponding to the transaction request.

The feedback request identification module 203 is configured to identify the type of the feedback request, and jump to the verification module when the feedback request is a transaction modification request, and further identify the feedback request when the feedback request is a transaction end request. The type of transaction end request.

The formal ledger modification module 204 is configured to include the formal ledger balance included in the consent transaction request and the last request initiated by the counterparty of the consent request sender when the transaction end request is a consent transaction request. The formal ledger balance is written into a formal ledger block having a mapping relationship with the temporary ledger block.

The transaction termination module 205 is configured to add, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction in the temporary ledger block, together with the transactions included in the latest request. Amount.

As another example, FIG. 4 shows a schematic diagram of a program module of the second embodiment of the negotiable blockchain transaction system 20. In this embodiment, the negotiable blockchain transaction system 20 can also be divided into requests The receiving module 201, the verification module 202, the feedback request identification module 203, the formal ledger modification module 204, the transaction termination module 205, and the reconfirmation module 206.

The program modules 201-205 are the same as those in the first embodiment, and will not be repeated here.

The reconfirmation module 206 is configured to reconfirm the transaction pointed to by the agreed transaction request according to a preset reconfirmation strategy when the transaction end request is an agreed transaction request, and if the reconfirmation is passed, skip again Go to the official ledger modification module.

Again, this application also proposes a computer device.

FIG. 5 is a schematic diagram of a hardware architecture of a computer device according to an embodiment of the present application. In this embodiment, the computer device 2 is a device capable of automatically performing numerical calculation and / or information processing according to an instruction set or stored in advance. For example, it can be a smart phone, a tablet computer, a notebook computer, a desktop computer, a rack server, a blade server, a tower server, or a rack server (including an independent server or a server cluster composed of multiple servers). As shown in the figure, the computer device 2 includes at least, but is not limited to, a memory 21, a processor 22, a network interface 23, and a negotiable blockchain transaction system 20 that can communicate with each other through a system bus. among them:

The memory 21 includes at least one type of computer-readable storage medium, and the readable storage medium includes a flash memory, a hard disk, a multimedia card, a card-type memory (for example, SD or DX memory, etc.), a random access memory (RAM), Static random access memory (SRAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), programmable read-only memory (PROM), magnetic memory, magnetic disks, optical disks, etc. In some embodiments, the memory 21 may be an internal storage unit of the computer device 2, such as a hard disk or a memory of the computer device 2. In other embodiments, the memory 21 may also be an external storage device of the computer device 2, such as a plug-in hard disk, a smart memory card (SMC), and a secure digital device. (Secure Digital, SD) card, Flash card, etc. Of course, the memory 21 may also include both an internal storage unit of the computer device 2 and an external storage device thereof. In this embodiment, the memory 21 is generally used to store an operating system and various application software installed on the computer device 2, such as program codes of the negotiable blockchain transaction system 20. In addition, the memory 21 may also be used to temporarily store various types of data that have been output or are to be output.

In some embodiments, the processor 22 may be a central processing unit (CPU), a controller, a microcontroller, a microprocessor, or another data processing chip. The processor 22 is generally used to control the overall operation of the computer device 2, for example, to perform control and processing related to data interaction or communication with the computer device 2. In this embodiment, the processor 22 is configured to run program code or process data stored in the memory 21, for example, to run the negotiable blockchain transaction system 20 and the like.

The network interface 23 may include a wireless network interface or a wired network interface. The network interface 23 is generally used to establish a communication connection between the computer device 2 and other computer devices. For example, the network interface 23 is configured to connect the computer device 2 and an external terminal through a network, and establish a data transmission channel and a communication connection between the computer device 2 and the external terminal. The network may be an intranet, the Internet, a Global System for Mobile Communication (GSM), a Wideband Code Division Multiple Access (WCDMA), a 4G network, 5G Wireless, wired or other networks such as Internet, Bluetooth, Wi-Fi.

It should be noted that FIG. 5 only shows the computer device 2 with components 21-23, but it should be understood that it is not required to implement all the illustrated components, and more or fewer components may be implemented instead.

In this embodiment, the negotiable blockchain transaction system 20 stored in the memory 21 may be executed by one or more processors (processor 22 in this embodiment) to complete the negotiable area. The operation of the blockchain transaction method.

In addition, the present application provides a computer-readable storage medium. The computer-readable storage medium is a non-volatile readable storage medium that stores therein computer program instructions that can be executed by at least one processor. To achieve the above-mentioned negotiable blockchain transaction method or operation of an electronic device.

Although the specific implementation of the present application is described above, those skilled in the art should understand that this is only an example, and the protection scope of the present application is defined by the appended claims. Those skilled in the art can make various changes or modifications to these embodiments without departing from the principle and essence of this application, but these changes and modifications fall within the protection scope of this application.

Claims

A negotiable blockchain transaction method, which establishes a temporary ledger block and a formal ledger block with a mapping relationship on the blockchain, wherein the transaction includes the following steps:

Receive a transaction request initiated by the transfer of funds in the transaction to the blockchain;

Verify the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current official ledger balance, and the signature included in the received request. If the verification is passed, write all the content contained in the request to the transaction Request the corresponding temporary ledger block;

Receiving a feedback request initiated by the blockchain in the opposite direction of the request, if the feedback request is a transaction modification request, repeating the previous step; if the feedback request is a transaction end request, further identifying the type of the transaction end request;

If the transaction end request is a consent transaction request, write the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender to the The temporary ledger block has a mapping relationship in the formal ledger block;

If the transaction end request is a transaction rejection request, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.
The negotiable blockchain transaction method according to claim 1, wherein the current temporary ledger balance refers to the official account balance of the requesting party who initiated the request minus all of the requesting party's pending confirmation status The difference between the sum of the transaction amounts.
The negotiable blockchain transaction method according to claim 1, wherein the verification passes:

The counterparty of the requesting party that sent the request successfully decrypted the current temporary ledger balance, current formal ledger balance, and transaction amount contained in the request using the public key; and,

Both the current temporary ledger balance and the current official ledger balance are greater than zero.
The negotiable blockchain transaction method according to claim 1, characterized in that, if the transaction end request is a consent transaction request, the transaction directed by the consent transaction request is first performed according to a preset reconfirmation policy Reconfirmation, if the reconfirmation is passed, then the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the The temporary ledger block has a mapping relationship in the formal ledger block.
The negotiable blockchain transaction method according to claim 1, wherein the reconfirmation strategy is a third party confirmation or a counterparty confirmation of the transaction request, and the reconfirmation step includes:

Receiving an approved transaction request sent by a third party or a counterparty of the transaction request;

If the approved transaction includes a consent instruction, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the The temporary ledger block has a formal ledger block with a mapping relationship;

If the approved transaction includes a refusal instruction, the temporary ledger balance and the formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request in the temporary ledger block.
The negotiable blockchain transaction method according to claim 1, wherein the re-confirmation strategy is delayed automatic confirmation, and the re-confirmation step comprises:

Determine whether a request to cancel a transaction sent by any of the two parties to the transaction is received within a preset time;

If no request to cancel the transaction is received, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the temporary account. The ledger block has a mapping relationship in the formal ledger block;

If a request to cancel a transaction is received, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.
An electronic device is characterized in that a negotiable blockchain transaction system is stored on the electronic device, and the negotiable blockchain transaction system includes:

The request receiving module is used to receive a transaction request initiated by the blockchain in the transfer of funds out of the transaction, and a feedback request initiated by the blockchain opposite to the originating request;

A verification module for verifying the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current formal ledger balance, and the signature included in the received request, and after all the verifications are passed, all The content is written into the temporary ledger block corresponding to the transaction request;

A feedback request identification module, configured to identify the type of the feedback request, and jump to the verification module when the feedback request is a transaction modification request, and further identify the end of the transaction when the feedback request is a transaction end request The type of request

A formal ledger modification module is configured to: when the transaction end request is a consent transaction request, the formal ledger balance included in the consent transaction request and the formal request included in the last request initiated by the counterparty of the consent request sender The ledger balance is written into a formal ledger block having a mapping relationship with the temporary ledger block;

The transaction termination module is configured to: when the transaction end request is a transaction refusal request, in the temporary ledger block, add the temporary ledger balance and formal ledger balance of both parties to the transaction to the transaction amount included in the latest request, respectively.
The electronic device according to claim 7, wherein the negotiable blockchain transaction system further comprises:

A reconfirmation module is configured to reconfirm the transaction pointed to by the agreed transaction request according to a preset reconfirmation policy when the transaction end request is an agreed transaction request, and if the reconfirmation is passed, then jump to Modification of official ledger.
A computer device includes a memory and a processor, wherein the memory stores a negotiable blockchain transaction system that can be executed by the processor, and the system is implemented as follows when executed by the processor: step:

Receive a transaction request initiated by the transfer of funds in the transaction to the blockchain;

Verify the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current official ledger balance, and the signature included in the received request. If the verification is passed, write all the content contained in the request to the transaction Request the corresponding temporary ledger block;

Receiving a feedback request initiated by the blockchain in the opposite direction of the request, if the feedback request is a transaction modification request, repeating the previous step; if the feedback request is a transaction end request, further identifying the type of the transaction end request;

If the transaction end request is a consent transaction request, write the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender to the The temporary ledger block has a mapping relationship in the formal ledger block;

If the transaction end request is a transaction rejection request, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.
The computer device according to claim 9, wherein the current temporary ledger balance is the balance of the official account of the requesting party who initiated the request minus the sum of all the transaction amounts of the requesting party in the pending status. Difference.
The computer device according to claim 9, wherein the verification passes:

The counterparty of the requesting party that sent the request successfully decrypted the current temporary ledger balance, current formal ledger balance, and transaction amount contained in the request using the public key; and,

Both the current temporary ledger balance and the current official ledger balance are greater than zero.
The computer device according to claim 9, characterized in that, if the transaction end request is a consent transaction request, the transaction pointed to by the consent transaction request is reconfirmed according to a preset reconfirmation policy, and if reconfirmed To pass, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written in a mapping with the temporary ledger block Relationship in the formal ledger block.
The computer device according to claim 9, wherein the reconfirmation strategy is a third party confirmation or a counterparty confirmation of the transaction request, and the reconfirmation step comprises:

Receiving an approved transaction request sent by a third party or a counterparty of the transaction request;

If the approved transaction includes a consent instruction, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the The temporary ledger block has a formal ledger block with a mapping relationship;

If the approved transaction includes a refusal instruction, the temporary ledger balance and the formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request in the temporary ledger block.
The computer device according to claim 9, wherein the reconfirmation strategy is delayed automatic confirmation, and the reconfirmation step comprises:

Determine whether a request to cancel a transaction sent by any of the two parties to the transaction is received within a preset time;

If no request to cancel the transaction is received, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the temporary account. The ledger block has a mapping relationship in the formal ledger block;

If a request to cancel a transaction is received, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.
A computer-readable storage medium, characterized in that computer program instructions are stored in the computer-readable storage medium, and the computer program instructions are executable by at least one processor, so that the at least one processor executes as follows step:

Receive a transaction request initiated by the transfer of funds in the transaction to the blockchain;

Verify the zero-knowledge certificate of the current temporary ledger balance, the zero-knowledge certificate of the current official ledger balance, and the signature included in the received request. If the verification is passed, write all the content contained in the request to the transaction Request the corresponding temporary ledger block;

Receiving a feedback request initiated by the blockchain in the opposite direction of the request, if the feedback request is a transaction modification request, repeating the previous step; if the feedback request is a transaction end request, further identifying the type of the transaction end request;

If the transaction end request is a consent transaction request, write the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender to the The temporary ledger block has a mapping relationship in the formal ledger block;

If the transaction end request is a transaction rejection request, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.
The computer-readable storage medium according to claim 15, wherein the current temporary ledger balance refers to the official account balance of the requesting party who initiated the request minus all the transaction amounts of the requesting party in a pending status The difference after the sum.
The computer-readable storage medium according to claim 15, wherein the verification passes:

The counterparty of the requesting party that sent the request successfully decrypted the current temporary ledger balance, current formal ledger balance, and transaction amount contained in the request using the public key; and,

Both the current temporary ledger balance and the current official ledger balance are greater than zero.
The computer-readable storage medium according to claim 15, wherein if the transaction end request is a consent transaction request, first re-confirm the transaction pointed to by the consent transaction request according to a preset reconfirmation policy, If the reconfirmation is passed, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the temporary ledger area. A block in a formal ledger block with a mapping relationship.
The computer-readable storage medium according to claim 15, wherein the reconfirmation strategy is a third party confirmation or a counterparty confirmation of the transaction request, and the reconfirmation step includes:

Receiving an approved transaction request sent by a third party or a counterparty of the transaction request;

If the approved transaction includes a consent instruction, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the The temporary ledger block has a formal ledger block with a mapping relationship;

If the approved transaction includes a refusal instruction, the temporary ledger balance and the formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request in the temporary ledger block.
The computer-readable storage medium according to claim 15, wherein the reconfirmation strategy is delayed automatic confirmation, and the reconfirmation step comprises:

Determine whether a request to cancel a transaction sent by any of the two parties to the transaction is received within a preset time;

If no request to cancel the transaction is received, the formal ledger balance included in the consent transaction request and the formal ledger balance included in the last request initiated by the counterparty of the consent request sender are written into the temporary account. The ledger block has a mapping relationship in the formal ledger block;

If a request to cancel a transaction is received, in the temporary ledger block, the temporary ledger balance and formal ledger balance of both parties to the transaction are added to the transaction amount included in the latest request, respectively.