# US 2019/0173667 A1 · Block generation method, device and blockchain network

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2019/0173667 A1
- Document ID: US20190173667A1
- Status: Published application
- Kind: A1
- Application number: 16/314,635
- Filed: 2016-12-23
- Published: 2019-06-06
- Earliest claimed: 2016-12-23
- Assignees: Cloudminds (Shenzhen) Robotics Systems Co., Ltd.
- Applicants: Cloudminds (Shenzhen) Robotics Systems Co., Ltd.
- Inventors: Jian WANG; Hui XIE
- Web page: https://patentgrep.com/patent/US20190173667A1

## CPC

- G06F 21/31: User authentication
- H04L 9/0637: {Modes of operation, e.g. cipher block chaining [CBC], electronic codebook [ECB] or Galois/counter mode [GCM]}
- G06F 21/64: Protecting data integrity, e.g. using checksums, certificates or signatures
- H04L 9/0643: {Hash functions, e.g. MD5, SHA, HMAC or f9 MAC}
- H04L 9/0861: {Generation of secret information including derivation or calculation of cryptographic keys or passwords}
- H04L 9/0863: {involving passwords or one-time passwords (network architectures or network communication protocols for using one-time keys in a packet data network H04L63/067)}
- H04L 9/14: using a plurality of keys or algorithms
- H04L 9/32: including means for verifying the identity or authority of a user of the system {or for message authentication, e.g. authorization, entity authentication, data integrity or data verification, non-repudiation, key authentication or verification of credentials}
- H04L 9/3236: {using cryptographic hash functions}
- H04L 9/3239: {involving non-keyed hash functions, e.g. modification detection codes [MDCs], MD5, SHA or RIPEMD}
- H04L 9/3247: {involving digital signatures}
- H04L 63/062: {for key distribution, e.g. centrally by trusted party (cryptographic mechanisms or cryptographic arrangements for key distribution involving a central third party H04L9/0819)}
- H04L 63/08: {for authentication of entities (cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32)}
- H04L 63/083: {using passwords (cryptographic mechanisms or cryptographic arrangements for entity authentication using a predetermined code H04L9/3226)}
- H04L 67/1097: for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]
- H04L 9/50: {using hash chains, e.g. blockchains or hash trees}
- G06F: ELECTRIC DIGITAL DATA PROCESSING (computer systems based on specific computational models G06N)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

A block generation method, a device and a blockchain network are used for improving the safety of a blockchain. The method comprises: signing a block generated by a block generation device according to private key information of the block generation device to obtain a signed block; and issuing the signed block to other node devices through a first node device in the blockchain network.

## Claims

### Claim 1

A block generation method, wherein the method is applied to a block generation device, private key information is built in the block generation device, and the method comprises:
signing a block generated by the block generation device according to the private key information to obtain a signed block; and
issuing the signed block to other node devices through a first node device in a blockchain network.

### Claim 2 (depends on 1)

The method according to claim 1, wherein the block generation device comprises a hash processor unit, before signing the block generated by the block generation device according to the private key, the method comprises:
performing hash calculation according to a specific hash algorithm built in the hash processor unit to obtain the block.

### Claim 3 (depends on 2)

The method according to claim 2, wherein, before performing the hash calculation according to the specific hash algorithm built in the first processing unit to obtain the block, the method further comprises:
obtaining transaction data through the first node device, wherein the block includes the transaction data.

### Claim 4 (depends on 1)

The method according to claim 1, wherein the block generation device comprises a key processor unit, and signing the block generated by the block generation device according to the private key comprises:
signing the block according to the private key information in the key processor unit to obtain the signed block.

### Claim 5 (depends on 1)

The method according to claim 1, wherein the method further comprises:
obtaining, through the first node device, a signed block issued by a second node device in the blockchain network;
performing signature verification on the signed block issued by the second node device according to public key information;
performing proof-of-work verification on the obtained signed block after the signification verification succeeds; and
determining whether to add the signed block to a blockchain according to a result of the proof-of-work verification.

### Claim 6 (depends on 1)

The method according to claim 1, wherein before signing the block generated by the block generation device according to the private key information, the method comprises:
determining, through the first node device, a number of blocks between a block last generated by the block generation device and a latest block in the current blockchain; and
determining that the number of the blocks is not less than a preset threshold m, wherein m is a positive integer greater than or equal to 1 and less than n, and n is a number of node devices in the blockchain network.

### Claim 7

A block generation method, wherein the method is applied to a block generation device, and the method comprises:
obtaining, through a second node device, a signed block issued by a first node device in a blockchain network;
performing signature verification on the signed block according to public key information;
performing proof-of-work verification on the signed block after the signature verification succeeds; and
determining whether to add the signed block to a blockchain according to a result of the proof-of-work verification.

### Claim at position 8

8-11. (canceled)

### Claim 12

A block generation device, wherein the block generation device comprising:
at least one processor unit, a communication interface, a memory and a communication bus; the at least one processor unit, the communication interface, and the memory communicate with each other through the communication bus;
the memory is configured to store program codes;
the at least one processor unit is configured to run the program codes to implement the following operations:
signing a block generated by the block generation device according to private key information built in the block generation device to obtain a signed block; and
issuing the signed block to other node devices through a first node device in the blockchain network.

### Claim 13 (depends on 12)

The block generation device according to claim 12, wherein the at least one processor unit comprises a main processor unit and a hash processor unit; and
the main processor unit is configured to perform hash calculation according to a specific hash algorithm built in the hash processor unit to obtain the block.

### Claim 14 (depends on 13)

The block generation device according to claim 13, wherein the at least one processor unit is also used for obtaining transaction data through the first node device, wherein the block includes the transaction data.

### Claim 15 (depends on 12)

The block generation device according to claim 12, wherein the at least one processor unit comprises a main processor unit and a key processor unit; and
the main processor unit is configured to sign the block according to the private key information in the key processor unit to obtain the signed block.

### Claim 16

A block generation device, wherein the block generation device comprising:
at least one processor unit, a communication interface, a memory and a communication bus; the at least one processor unit, the communication interface, and the memory communicate with each other through the communication bus;
the memory is configured to store program codes;
the at least one processor unit is configured to run the program codes to implement the following operations:
obtaining, through a second node device, a signed block issued by a first node device in a blockchain network;
performing signature verification on the signed block according to public key information;
performing proof-of-work verification on the signed block after the signature verification succeeds; and
determining whether to add the signed block to a blockchain according to a result of the proof-of-work verification.

### Claim at position 14

17-19. (canceled)

### Claim 20

A non-transitory computer readable storage medium applied to a block generation device, private key information is built in the block generation device, wherein the non-transitory computer readable medium is used for storing a computer program, and the computer program comprises instructions for performing the following method:
signing a block generated by the block generation device according to the private key information to obtain a signed block; and
issuing the signed block to other node devices through a first node device in a blockchain network.

### Claim 21 (depends on 20)

The non-transitory computer readable storage medium according to claim 20, wherein the block generation device comprises a hash processor unit, before signing the block generated by the block generation device according to the private key, the method comprises:
performing hash calculation according to a specific hash algorithm built in the hash processor unit to obtain the block.

### Claim 22 (depends on 21)

The non-transitory computer readable storage medium according to claim 21, wherein, before performing the hash calculation according to the specific hash algorithm built in the first processing unit to obtain the block, the method further comprises:
obtaining transaction data through the first node device, wherein the block includes the transaction data.

### Claim 23 (depends on 20)

The non-transitory computer readable storage medium according to claim 20, wherein the block generation device comprises a key processor unit, and signing the block generated by the block generation device according to the private key comprises:
signing the block according to the private key information in the key processor unit to obtain the signed block.

### Claim 24 (depends on 20)

The non-transitory computer readable storage medium according to claim 20, wherein the method further comprises:
obtaining, through the first node device, a signed block issued by a second node device in the blockchain network;
performing signature verification on the signed block issued by the second node device according to public key information;
performing proof-of-work verification on the obtained signed block after the signification verification succeeds; and
determining whether to add the signed block to a blockchain according to a result of the proof-of-work verification.

### Claim 25 (depends on 20)

The non-transitory computer readable storage medium according to claim 20, wherein, before signing the block generated by the block generation device according to the private key information, the method comprises:
determining, through the first node device, a number of blocks between a block last generated by the block generation device and a latest block in the current blockchain; and
determining that the number of the blocks is not less than a preset threshold m, wherein m is a positive integer greater than or equal to 1 and less than n, and n is a number of node devices in the blockchain network.

### Claim 26

A non-transitory computer readable storage medium, wherein the non-transitory computer readable medium is used for storing a computer program, and the computer program comprises instructions for performing the following method:
obtaining, through a second node device, a signed block issued by a first node device in a blockchain network;
performing signature verification on the signed block according to public key information;
performing proof-of-work verification on the signed block after the signature verification succeeds; and
determining whether to add the signed block to a blockchain according to a result of the proof-of-work verification.
