CONSENSUS VERIFICATION METHOD, APPARATUS, AND DEVICE

• US 20200136830A1
• Filed: 12/23/2019
• Published: 04/30/2020
• Est. Priority Date: 03/09/2018
• Status: Active Grant

• Current Assignee: Advanced New Technologies Company Limited (Ant Group Co., Ltd.)
• Original Assignee: Alibaba Group Holding Ltd.
• Inventors: Yang, Xinying
• Granted Patent: US 10,887,108 B2
• Time in Patent Office: Days
• CPC Class Codes: G06Q 20/065 using e-cash
• CPC Class Codes: G06Q 20/401 Transaction verification
• CPC Class Codes: G06Q 20/403 Solvency checks
• CPC Class Codes: G06Q 2220/00 Business processing using cryptography
• CPC Class Codes: H04L 2209/56 Financial cryptography, e.g. electronic payment or e-cash
• CPC Class Codes: H04L 67/1042 using topology management mechanisms
• CPC Class Codes: H04L 9/0618 Block ciphers, i.e. encrypting groups of characters of a plain text message using fixed encryption transformation
• CPC Class Codes: H04L 9/3239 involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD
• CPC Class Codes: H04L 9/50 using hash chains, e.g. blockchains or hash trees

Abstract

Implementations of the present specification disclose a consensus verification method, apparatus, and device. In the implementations of the present specification, for each piece of service data, if first consensus verification on the service data fails, a first node determines whether the service data satisfies a predetermined retry condition instead of directly considering the service data to be invalid. If the predetermined retry condition is satisfied, then the service data is stored as service data to be retried. The first node can perform the first consensus verification on the service data to be retried in response to determining that a predetermined retry execution condition is triggered.

Claims

1. A computer-implemented method, comprising:

receiving, by a first node of a blockchain, service data;

performing first consensus verification on the service data;

determining whether the first consensus verification on the service data succeeds; and

in response to determining that the first consensus verification on the service data succeeds;

adding the service data to a service queue to be validated, the service data being selectable by a second node from the service queue to be validated to generate a block; and

performing second consensus verification on the block; and

in response to determining that the first consensus verification on the service data fails;

determining whether the service data satisfies a predetermined retry condition;

storing the service data as service data to be retried in response to determining that the predetermined retry condition is satisfied; and

after storing the service data as service data to be retried;

determining whether a predetermined retry execution condition is triggered; and

performing the first consensus verification on the service data to be retried in response to determining that the predetermined retry execution condition is triggered.

2. The computer-implemented method of claim 1, wherein determining whether the service data satisfies the predetermined retry condition comprises:

determining, based on a reason why the first consensus verification on the service data fails, whether the service data satisfies the predetermined retry condition.

3. The computer-implemented method of claim 2, wherein the service data comprises service data of a transfer service.

4. The computer-implemented method of claim 3, wherein determining, based on the reason why the first consensus verification on the service data fails, whether the service data satisfies the predetermined retry condition comprises:

determining whether an asset balance of a transfer is insufficient; and

determining that the service data satisfies the predetermined retry condition in response to determining that the asset balance is insufficient.

5. The computer-implemented method of claim 1, wherein of each of the first node and the second node of the blockchain comprises a predetermined maximum capacity and/or the second node generates a period of each block.

6. The computer-implemented method of claim 5, wherein determining that the predetermined retry execution condition is triggered comprises:

determining whether a difference between the maximum capacity and a total data amount of service data selected by each second node from the service queue to be validated to generate a next block falls within a first specified value range; and

determining that the predetermined retry execution condition is triggered in response to determining that the difference falls within the first specified value range.

7. The computer-implemented method of claim 5, wherein determining that the predetermined retry execution condition is triggered comprises:

determining whether a time interval between a current moment and an end moment of a current period falls within a second specified value range; and

determining that the predetermined retry execution condition is triggered in response to determining that the time interval falls within the second specified value range.

8. The computer-implemented method of claim 1, wherein storing the service data as service data to be retried comprises:

adding the service data to a queue tail of a precreated service queue to be retried as the service data to be retried.

9. The computer-implemented method of claim 8, wherein performing the first consensus verification on the service data to be retried comprises:

sequentially selecting, in a front-to-back order, at least one piece of service data to be retried from the service queue to be retried; and

performing the first consensus verification on the selected service data to be retried.

10. The computer-implemented method of claim 1, wherein the performing the first consensus verification on the service data to be retried comprises:

performing the first consensus verification on the service data to be retried until the first consensus verification on the service data to be retried succeeds or until the number of times of performing the first consensus verification on the service data to be retried reaches a specified value.

11. The computer-implemented method of claim 1, wherein adding the service data to the service queue to be validated comprises adding the service data to a queue tail of the service queue to be validated.

12. The computer-implemented method of claim 11, wherein the second node selects service data from the service queue to be validated to generate a block by performing operations comprising:

sequentially selecting, by each second node, several pieces of service data in a front-to-back order from the service queue to be validated to generate the block; and

after the performing the first consensus verification on the service data to be retried, the method further comprises adding service data to be retried whose first consensus verification succeeds to a location that is before a specified location in the service queue to be validate.

13. A non-transitory, computer-readable medium storing one or more instructions executable by a computer system to perform operations comprising:

receiving, by a first node of a blockchain, service data;

performing first consensus verification on the service data;

determining whether the first consensus verification on the service data succeeds; and

in response to determining that the first consensus verification on the service data succeeds;

adding the service data to a service queue to be validated, the service data being selectable by a second node from the service queue to be validated to generate a block; and

performing second consensus verification on the block; and

in response to determining that the first consensus verification on the service data fails;

determining whether the service data satisfies a predetermined retry condition;

storing the service data as service data to be retried in response to determining that the predetermined retry condition is satisfied; and

after storing the service data as service data to be retried;

determining whether a predetermined retry execution condition is triggered; and

performing the first consensus verification on the service data to be retried in response to determining that the predetermined retry execution condition is triggered.

14. The computer-readable medium of claim 13, wherein determining whether the service data satisfies the predetermined retry condition comprises:

determining, based on a reason why the first consensus verification on the service data fails, whether the service data satisfies the predetermined retry condition.

15. The computer-readable medium of claim 14, wherein the service data comprises service data of a transfer service.

16. The computer-readable medium of claim 15, wherein determining, based on the reason why the first consensus verification on the service data fails, whether the service data satisfies the predetermined retry condition comprises:

determining whether an asset balance of a transfer is insufficient; and

determining that the service data satisfies the predetermined retry condition in response to determining that the asset balance is insufficient.

17. The computer-readable medium of claim 13, wherein of each of the first node and the second node of the blockchain comprises a predetermined maximum capacity and/or the second node generates a period of each block, and wherein determining that the predetermined retry execution condition is triggered comprises:

determining whether a difference between the maximum capacity and a total data amount of service data selected by each second node from the service queue to be validated to generate a next block falls within a first specified value range; and

determining that the predetermined retry execution condition is triggered in response to determining that the difference falls within the first specified value range.

18. A computer-implemented system, comprising:

one or more computers; and

one or more computer memory devices interoperably coupled with the one or more computers and having tangible, non-transitory, machine-readable media storing one or more instructions that, when executed by the one or more computers, perform one or more operations comprising;

receiving, by a first node of a blockchain, service data;

performing first consensus verification on the service data;

determining whether the first consensus verification on the service data succeeds; and

in response to determining that the first consensus verification on the service data succeeds;

adding the service data to a service queue to be validated, the service data being selectable by a second node from the service queue to be validated to generate a block; and

performing second consensus verification on the block; and

in response to determining that the first consensus verification on the service data fails;

determining whether the service data satisfies a predetermined retry condition;

storing the service data as service data to be retried in response to determining that the predetermined retry condition is satisfied; and

after storing the service data as service data to be retried;

determining whether a predetermined retry execution condition is triggered; and

performing the first consensus verification on the service data to be retried in response to determining that the predetermined retry execution condition is triggered.

19. The computer-implemented system of claim 18, wherein determining whether the service data satisfies the predetermined retry condition comprises:

determining, based on a reason why the first consensus verification on the service data fails, whether the service data satisfies the predetermined retry condition.

20. The computer-implemented system of claim 19, wherein the service data comprises service data of a transfer service, and wherein determining, based on the reason why the first consensus verification on the service data fails, whether the service data satisfies the predetermined retry condition comprises:

determining whether an asset balance of a transfer is insufficient; and

determining that the service data satisfies the predetermined retry condition in response to determining that the asset balance is insufficient.