CN110505065B - A method, device and storage medium for adding trusted timestamp - Google Patents

Abstract

The embodiments of the present application provide a method, device and storage medium for adding a trusted timestamp, which relate to the technical field of blockchain. Wherein, the method includes: obtaining block data of the current latest block on the blockchain; obtaining a trusted time, and adding a trusted timestamp to the block data according to the trusted time, so as to obtain a trusted timestamp. block data; construct a timestamp transaction request according to the block data with a trusted timestamp; send the timestamp transaction request to a node in the blockchain, so that the node can trade according to the timestamp Request to add the trusted timestamped block data to the blockchain. The embodiment of the present application improves the performance of the blockchain and facilitates the management of the blockchain by asynchronously adding a trusted timestamp to the block data of the current latest block of the blockchain.

Description

A method, device and storage medium for adding trusted timestamp

technical field

The present application relates to the field of blockchain technology, and in particular to a method, device and storage medium for adding trusted timestamps.

Background technique

A blockchain is a decentralized database formed by combining blocks in a chain. Specifically, the information generated within a period of time (including the data on deposit) is packaged to generate a block, a trusted timestamp is added to the block, and then connected with the previous block. In this way, the end-to-end connection forms a block. blockchain. Among them, the block header of each block, except the genesis block, includes the hash value of the previous block, the block body of each block includes at least one transaction, and the transaction includes the generated The information includes, for example, evidence-based data. Since the blockchain adds a trusted timestamp when generating blocks, the time when the information stored in the blockchain is generated is credible, thus giving the blockchain a trusted time.

In the prior art, the method of adding a trusted timestamp to a blockchain is as follows: a consensus node of the blockchain network obtains a trusted timestamp when generating a block. This method of adding trusted timestamps requires the blockchain itself to obtain trusted timestamps, that is, the consensus nodes of the blockchain need to obtain trusted timestamps when generating blocks. Trusted time, which invades the blockchain, needs to modify the code of the consensus node so that the consensus node can support obtaining trusted timestamps, thus reducing the performance of the blockchain.

SUMMARY OF THE INVENTION

The embodiments of the present application provide a method, device and storage medium for adding a trusted timestamp, which can improve the performance of the blockchain.

The embodiment of the present application provides a method for adding a trusted timestamp, including:

Get the block data of the current latest block on the blockchain;

Obtaining a trusted time, and adding a trusted timestamp to the block data according to the trusted time to obtain block data with a trusted timestamp;

constructing a timestamp transaction request according to the block data with the trusted timestamp;

The timestamp transaction request is sent to the node in the blockchain, so that the node adds the block data with a trusted timestamp to the blockchain according to the timestamp transaction request.

The embodiment of the present application also provides a method for adding a trusted timestamp, which is applied to a first node, where the first node is any node in the blockchain, including:

Receive a timestamp transaction request, where the timestamp transaction request carries block data with a trusted timestamp;

When the first node is a target node that can generate a block, generate a block, and the block includes block data with a trusted timestamp;

Broadcast the verification request of the block to a second node in the blockchain, where the second node is a node other than the first node in the blockchain;

receiving a verification result returned by the second node based on the verification request;

Based on the verification result returned by the second node, the block is added to the blockchain.

The embodiment of the present application also provides a trusted timestamp adding device, including:

The block data acquisition unit is used to acquire the block data of the current latest block on the blockchain;

a timestamp adding unit, configured to obtain a trusted time, and add a trusted timestamp to the block data according to the trusted time to obtain block data with a trusted timestamp;

a request construction unit, configured to construct a timestamp transaction request according to the block data with a trusted timestamp;

A request sending unit, configured to send the time stamp transaction request to the node in the blockchain, so that the node adds the block data with a trusted time stamp to all the nodes according to the time stamp transaction request in the blockchain described above.

Further, the request building unit includes:

a template obtaining unit, configured to obtain a preset transaction template, where the preset transaction template includes a transaction content field;

a filling unit, configured to perform data filling on the transaction content field according to the block data with a trusted timestamp;

The timestamp transaction construction unit is used to construct a timestamp transaction according to the filled preset transaction template;

A request generating unit, configured to generate a timestamp transaction request according to the timestamp transaction.

Further, the device for adding trusted time stamps further includes:

a time obtaining unit, used to obtain the first generation time of the latest block recorded last time in the blockchain and the second generation time of the current latest block;

A time recording unit for recording the second generation time if the difference between the second generation time and the first generation time reaches a preset time interval, and triggers the block data acquisition unit for acquiring the area The block data of the current latest block on the blockchain.

Further, the time stamp transaction request includes a time stamp transaction, and the time stamp transaction is constructed according to the block data with a trusted time stamp, and the trusted time stamp adding device further includes:

a target block obtaining unit, used for obtaining the blocks generated within the preset time interval as target blocks;

A block detection unit, configured to detect whether the target block includes transactions other than the timestamp transaction; if the target block includes transactions other than the timestamp transaction, trigger the block The data acquisition unit is used to acquire the block data of the current latest block on the blockchain.

Further, the device for adding trusted time stamps further includes:

The height obtaining unit is used to obtain the last recorded block height and the current block height in the blockchain;

The height recording unit is used to record the current block height when the difference between the current block height and the previously recorded block height reaches a preset height difference, and trigger the block data acquisition unit to use It is used to obtain the block data of the current latest block on the blockchain.

The embodiment of the present application also provides a trusted timestamp adding device, which is applied to a first node, where the first node is any node in the blockchain, including:

a request receiving unit, configured to receive a timestamp transaction request, where the timestamp transaction request carries block data with a trusted timestamp;

a block generating unit, configured to generate a block when the first node is a target node that can generate a block, and the block includes block data with a trusted timestamp;

a broadcasting unit, configured to broadcast the verification request of the block to a second node in the blockchain, where the second node is a node other than the first node in the blockchain;

a verification result receiving unit, configured to receive the verification result returned by the second node based on the verification request;

A block adding unit, configured to add the block to the blockchain based on the verification result returned by the second node.

Further, the device for adding trusted time stamps further includes:

an instruction generation unit, configured to generate a sending instruction according to the timestamp transaction request when the first node is not a target node that can generate a block;

an instruction sending unit, configured to send the sending instruction to a target node, where the sending instruction is used to instruct: the target node to generate a block and add the block to the blockchain based on a consensus mechanism.

Embodiments of the present application further provide a computer-readable storage medium, where a computer program is stored in the computer-readable storage medium, and when the computer program is executed by a processor, any of the foregoing methods for adding a trusted timestamp is implemented.

The embodiment of the present application obtains the block data of the current latest block on the blockchain; obtains the trusted time, and adds a trusted timestamp to the block data according to the trusted time, so as to obtain block data with a trusted timestamp, Construct a timestamp transaction request according to the block data with a trusted timestamp, and send the timestamp transaction request to a node in the blockchain, so that the node will send the block with a trusted timestamp according to the timestamp transaction request. Block data is added to the blockchain. In this way, a trusted timestamp is asynchronously added to the current latest block of the blockchain, and the trusted timestamp is added to the blockchain to give the blockchain a trusted time, without the need for the blockchain itself to acquire Trusted timestamp, that is, the solution in this application does not intrude on the blockchain, and does not need to modify the consensus node of the blockchain. The embodiment of the present application improves the performance of the blockchain by asynchronously adding a trusted timestamp to the latest block of the blockchain, facilitates the management of the blockchain, and does not require consensus nodes in the blockchain to generate blocks The trusted timestamp is obtained from time to time, which improves the flexibility of the blockchain; in addition, the solution for adding a trusted timestamp in the embodiment of the present application can assign a trusted timestamp to any blockchain, and has wide applicability.

Description of drawings

In order to illustrate the technical solutions in the embodiments of the present application more clearly, the following briefly introduces the drawings that are used in the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present application. For those skilled in the art, other drawings can also be obtained from these drawings without creative effort.

FIG. 1a is a schematic diagram of a system for adding a trusted timestamp to a blockchain provided by an embodiment of the present application;

1b is a schematic flowchart of a method for adding a trusted timestamp provided by an embodiment of the present application;

1c is a schematic diagram of a block structure provided by an embodiment of the present application;

2a is a schematic flowchart of a method for adding a trusted timestamp provided by an embodiment of the present application;

2b is a schematic diagram of adding a trusted timestamp provided by an embodiment of the present application;

3 is another schematic flowchart of a method for adding a trusted timestamp provided by an embodiment of the present application;

4 is a schematic block diagram of an apparatus for adding a trusted timestamp provided by an embodiment of the present application;

Fig. 5 is another schematic block diagram of a trusted timestamp adding device provided by an embodiment of the present application;

Fig. 6 is another schematic block diagram of a trusted timestamp adding device provided by an embodiment of the present application;

FIG. 7 is a schematic structural diagram of a computer device provided by an embodiment of the present application.

Detailed ways

The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, but not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by those skilled in the art without creative work fall within the protection scope of the present application.

Before explaining the embodiments of the present invention in detail, some terms involved in the embodiments of the present invention are explained first.

Blockchain: Blockchain technology is born out of Bitcoin technology and is the underlying technology of Bitcoin, which is a decentralized distributed ledger database. The blockchain itself is a series of data blocks (that is, blocks) that are associated with cryptographic algorithms, and each data block contains information for valid confirmation of multiple blockchain network transactions. Based on this, it is impossible to cheat by tampering with the data on the block, and it can ensure that the data on any block is open and transparent, ensuring the security of the data.

Blockchain can be divided into public chain, private chain, alliance chain. Among them, the alliance chain is between the public chain and the private chain. Several organizations cooperate to maintain a blockchain. The use of the blockchain must be managed with permission, and relevant information will be protected, such as financial organizations. To sum up, the blockchain is a distributed database system participated by nodes, or it can also be called a distributed public ledger based on a P2P (peer-to-peer) network. Since a trusted timestamp is added to the blockchain, so , The characteristics of the blockchain are that it cannot be changed or forged.

Nodes of the blockchain: The devices that participate in building the blockchain. A node can be a single computer device participating in the construction of the blockchain, or a cluster of computer devices such as a server cluster. The node stores relevant block data, for example, the block data may include data such as transactions. Among them, the nodes include consensus nodes, and consensus nodes refer to nodes that can generate blocks (have the ability to generate blocks), and nodes that can agree on transactions that occur within a certain period of time based on a consensus mechanism, such as Newly generated blocks are subject to consensus to achieve consensus. At the same time, it should be noted that only one consensus node in the blockchain network can generate blocks at the same time.

The multiple nodes of the blockchain and the interconnected relationships between the multiple nodes constitute the blockchain network. Therefore, a node in a blockchain network has the same meaning as a node in the blockchain.

Embodiments of the present application provide a method, apparatus, computer device, and storage medium for adding a trusted timestamp.

An embodiment of the present application provides a trusted timestamp adding system, including the trusted timestamp adding device provided by any of the embodiments of the present application. The trusted time stamp adding device may be integrated in network equipment such as a server. For example, the trusted timestamp addition system includes a server and a blockchain network. Among them, the server and the blockchain network are connected through a network. The network includes network entities such as routers and gateways. In each blockchain network, there are multiple nodes of the blockchain (also called network nodes or node devices), each node is connected peer-to-peer, and each node stores the full amount of the blockchain data.

Configure a node in the blockchain network in the server, obtain the configured node, and the server establishes a connection with the obtained section through the interface provided by the blockchain network. In this way, the server establishes a connection with the blockchain network.

Among them, the server implementation of the trusted timestamp adding system: obtains the block data of the current latest block on the blockchain; obtains the trusted time, and adds a trusted timestamp to the block data according to the trusted time, and obtains a reliable timestamp. block data with trusted timestamps; construct timestamp transaction requests based on block data with trusted timestamps; send timestamp transaction requests to nodes in the blockchain, so that nodes will have trusted time based on timestamp transaction requests The stamped block data is added to the blockchain. Among them, the node is any node in the blockchain.

Any node in the blockchain network realizes: receives a timestamp transaction request, and the timestamp transaction request carries block data with a trusted timestamp; when the node is the target node (target consensus node) that can generate blocks When the block is generated, a block is generated and added to the blockchain based on the consensus mechanism; when the node is not the target node that can generate a block, a sending instruction is generated according to the timestamp transaction request; the sending instruction is sent to the target node , the sending instruction is used to instruct: the target node generates a block and adds the block to the blockchain based on a consensus mechanism.

Block data with trusted timestamps can include trusted timestamps and block data, or only trusted timestamps.

It should be noted that the server of the trusted timestamp adding system may be one server or multiple servers, such as a server cluster.

For example, referring to Figure 1a, a trusted time stamping system includes an intermediate server, a time stamping server, and a blockchain network. That is, the servers in the trusted timestamp adding system include two: an intermediate server and a timestamp server. The intermediate server and the timestamp server are connected to each other, eg via an interface. Among them, the blockchain network includes multiple consensus nodes, and the multiple consensus nodes are equal, such as including n consensus nodes. The full data of the blockchain is stored in each consensus node. In one embodiment, the trusted time stamp adding system further includes a national time service center.

A certain consensus node in the blockchain network is configured in the intermediate server, the configured consensus node is obtained, and the intermediate server establishes a connection with the obtained consensus node through the interface provided by the blockchain network.

It should be noted that the consensus node configured in the intermediate server can be any consensus node in the blockchain network, or a specified consensus node, such as a consensus node specified according to preset rules, such as , specify a consensus node that is closest to the network of the intermediate server, and configure the consensus node that is closest to the network in the intermediate server.

After the intermediate server establishes a connection with the blockchain network, the intermediate server obtains the block data of the current latest block of the blockchain, and sends the block data to the timestamp server. After the timestamp server receives the block data, it adds a trusted timestamp to the block data. Specifically, the time stamp server goes to the national time service center to obtain the trusted time, and signs the obtained trusted time and block data together to obtain block data with a trusted time stamp, and signs the obtained trusted time with the block data, etc. The time stamped block data is returned to the intermediate server. The intermediate server receives the block data with a trusted timestamp returned by the timestamp server, constructs a timestamp transaction request based on the block data with a trusted timestamp, and sends the timestamp transaction request to the blockchain network. A consensus node, which is a pre-configured consensus node, which can be any consensus node in the blockchain network.

The content implemented by the consensus node of the blockchain network is consistent with the nodes in the blockchain network above, and will not be repeated here.

1b is a schematic flowchart of a method for adding a trusted timestamp provided by an embodiment of the present application. The method is applied to a server. The specific process of the method for adding a trusted timestamp may be as follows:

101. Obtain block data of the current latest block on the blockchain.

Among them, each block in the blockchain includes a block header and a block body, as shown in Figure 1c. The block body includes at least one transaction. In general, the block body includes multiple transactions, and the transaction includes certificate data and so on. As shown in Figure 1c, 8 transactions are included. The block header includes the hash value, version, timestamp of the previous block (used to save the local time when the block was generated), difficulty, random number, Merkel follow, block height and other information. It should be noted that Figure 1c only exemplifies part of the information, and the block header also includes other information, such as the number of transactions in the block header. It should be noted that to obtain the block data of the latest block on the blockchain, the block data can be the data of the block header and block body of the latest block, or the block header of the latest block. The data can also be the block hash value of the current latest block, etc., or other combinations of the data exemplified here. It should be noted that the block data of the current latest block can uniquely represent a block. The block hash value refers to a hash value obtained by performing a hash operation on the information in the block header, and the hash value can uniquely represent a block. The current latest block refers to the most recently generated block on the blockchain. After a block is generated, the hash value of the block can be calculated.

Specifically, for example, the server sends an acquisition request to a certain node of the blockchain, and the acquisition request is used to request to acquire the block data of the current latest block of the blockchain, such as the block hash value; the node of the blockchain After receiving the acquisition request, the calculated block data of the current latest block is returned to the server. Alternatively, some conditions can also be set to trigger the server to send the acquisition request, for example, after a certain time period is set, the server is triggered to send the acquisition request.

In one embodiment, if the server includes a plurality of servers, such as an intermediate server and a timestamp server, wherein the intermediate server and the timestamp server are connected to each other. Step 101 includes: obtaining block data of the latest current block on the blockchain from an intermediate server. Understandably, the intermediate server obtains the block data of the current latest block on the blockchain, and the timestamp server obtains the block data of the current latest block on the blockchain from the intermediate server.

102. Obtain a trusted time, and add a trusted timestamp to the block data according to the trusted time, to obtain block data with a trusted timestamp.

After the server obtains the block data of the current latest block, it obtains the trusted time from the National Time Service Center. After the server receives the trusted time returned by the National Time Service Center, the server adds a trusted time stamp to the block data according to the trusted time. The server signs the acquired block data, trusted time, etc. with the private key stored in the server, and finally obtains block data with a trusted timestamp. Understandably, the server functions as a timestamp server. The time stamp server conforms to the "RFC3161 standard", and has been inspected by the Ministry of Public Security and the State Secret Service, and is safe and reliable; the private key of the time stamp server exists in the time stamp server password card and cannot be exported and cannot be obtained by anyone; therefore, the time stamp server Credible proof of time can be provided.

Since the block data of the current latest block is obtained, the block data can uniquely represent the current block. Therefore, after adding a trusted timestamp to the block data, it is the current latest block chain obtained. Add a trusted timestamp to the block and the block before the current latest block of the acquired blockchain to prove that the current latest block in the acquired blockchain and the current latest block of the acquired blockchain All transactions in blocks prior to the block that existed before the trusted time corresponding to this trusted timestamp.

103. Construct a timestamp transaction request according to the block data with the trusted timestamp.

A timestamp transaction request is generated according to the block data with a trusted timestamp, and the timestamp transaction request includes the block data with a trusted timestamp.

In one embodiment, step 103 includes: constructing a timestamp transaction according to the block data with a trusted timestamp, and generating a timestamp transaction request according to the timestamp transaction. Among them, the timestamp transaction refers to that the transaction includes block data with a trusted timestamp. Essentially, a timestamp transaction is also a transaction, except that the transaction includes block data with a trusted timestamp.

Specifically, the steps of constructing timestamp transactions according to the block data with trusted timestamps include:

(1) Obtain a preset transaction template, where the preset transaction template includes transaction content.

The preset transaction template may be a transaction template pre-set by the operation and maintenance personnel, or a transaction template provided to the server after being pre-established by other devices, or a transaction template generated by the server itself, and so on. The preset transaction template may be temporarily generated or acquired by the server when the transaction is constructed; it may also be pre-set or pre-generated or pre-acquired and stored in the server, and the saved preset transaction template is acquired when the transaction is constructed.

A preset transaction template can also be understood as a preset transaction format or a preset transaction data structure, etc. The fields in the preset transaction template can also be understood as parameters, and each parameter includes parameter name, parameter type, parameter value and other information. It should be reminded that some fields in the preset transaction template may also include next-level fields. For example, when defining a data structure for some fields, it is defined that the field includes multiple fields of the next level, and the fields of the next level also include fields of the next level. If some fields are stored in an array, multiple data in the array correspond to the next-level fields of the field.

The fields in the preset transaction template include transaction version number, additional data (type is json), input array, output array, lock time (default value is 0), base58|hex return format and other fields. Among them, for example, the base58|hex return format field, the type is string, the default is that the base58|hex return format field is not filled, if not filled, the base58|hex return format field value = base58, this field does not participate sign.

Among them, the input array field of each transaction includes one or more inputs, eg, for timestamp transactions, there is an input in the input array field. Each input includes fields such as input serial number, reference source output information, and unlock script. For example, the input sequence number field, the type is uint32, and the value is a positive integer starting from 0, such as 0, the input sequence number only guarantees uniqueness, and does not need to guarantee continuity. For example, the application source output information field, the type is json, the application source output information refers to the information of the reference transaction, that is, the output information of the previous transaction. This field also includes two fields at the next level: hash and index, where hash refers to the hash value of the referenced transaction, and index refers to the index of the referenced transaction. It should be noted that since timestamp transactions do not refer to transactions, hash and index are fixed values for special processing; non-timestamp transactions, that is, transactions other than timestamp transactions, such as deposit transactions, need to refer to actual information . For example, to unlock the script field, the type can be string or base58, and the value of this field is calculated by using the base58 function, such as the value calculated by base58 (script type + script version + signature).

Among them, the output array field of each transaction includes one or more outputs, for example, for timestamp transactions, there is one output in the output array field. Each output includes fields such as output serial number, account address, asset ID, amount, transaction content, and lock script. For example, the output sequence number field is of type uint32, and the value is a positive integer starting from 0, such as 0. The output sequence number field only needs to ensure uniqueness, not continuity. For example, the arrival address field, the type is string or base58, and the value is 1KzBWDAcf66fyZ1qGb2r6YZp3CfuRgfdDr. For example, the amount field, the type is uint64, the value is 100. For example, the transaction content field is of type string or base58. For timestamp transactions, the value of the transaction content field is the serialized block data and data type with a trusted timestamp.

(2) Filling the transaction content field in the preset transaction template with data according to the block data with a trusted timestamp.

The transaction content field is a field information included in an output in the output array. Arbitrary data can be filled in the transaction content field, where filling can be understood as assigning a value to the field. In the timestamp transaction, the data filled in the transaction content field includes: the type of the filled data and the specific content of the filled data. For example, the type of the filling data is a trusted timestamp, and the specific content of the filling data is the block data with a trusted timestamp. Serialize the type of the padding data and the specific content of the padding data to get the serialized value. If the value of the data type of the serialized trusted timestamp is represented by 5, the value of the data type of the trusted timestamp can also be represented by other numbers, letters or symbols. The value is djREFASDGJs483K. Then, after the transaction content field is filled with data and serialized, it is: 5djREFASDGJs483K. It should be reminded that the value of the data type of the timestamp here and the value of the block data with a trusted timestamp are not real values. Restrictions on the value of the block data and the value of the trusted timestamp data type.

(3) Construct a timestamp transaction according to the filled preset transaction template.

In the filled preset transaction template, the fields of the transaction content have been assigned values.

It should be noted that the reference source output information refers to the information of the reference transaction, that is, the output information of the previous transaction. Since the timestamp transaction does not have a previous transaction, that is, the timestamp transaction does not refer to the output information of the previous transaction, therefore, the timestamp transaction does not actually refer to the source output information, so the hash and index in the reference source output information are set. is a fixed value. Among them, hash="000000000000.....000" (64 zeros), index="-1". In addition, the values of the arrival address, amount and other fields in the output array of the timestamp transaction are also set to fixed values.

Build a transaction based on the filled preset transaction template, including the following three situations:

1. In the obtained preset transaction template, in addition to the fields of transaction content, other fields, such as the hash and index values in the reference source output information, the account address in the output array, the amount of money and other fields have been processed. Setting (ie data filling), such as setting to a fixed value or a temporarily calculated value. It is understandable that, in the acquired preset transaction template, except for the transaction content field, other fields already have corresponding values. Then, after the transaction content is filled with data, all fields in the filled preset transaction template already have corresponding values. In this way, the preset transaction template with all fields filled with data constitutes a transaction. The constructed transaction will be used as a timestamp transaction.

Second, in the acquired preset transaction template, all fields are not filled with data, which can be understood as the values of all fields are empty. After the transaction content field is filled with data, only the transaction content field in the filled preset transaction template is filled with data. In this way, the step of "constructing a timestamp transaction according to the filled preset transaction template" also includes: filling other fields except the transaction content field with data, and filling all fields with data in the preset transaction template. as a transaction. The constructed transaction will be used as a timestamp transaction.

Third, in the acquired preset transaction template, some fields are filled with data, which can be understood as the value of some fields is empty, and the value of some fields is not empty. After the transaction content fields are filled with data, there are still some fields whose values are not filled with data. The step of "constructing a transaction according to the pre-filled preset transaction template" further includes: filling the fields without data filling with data, and using the preset transaction template after all fields have been filled with data as a transaction. The constructed transaction will be used as a timestamp transaction.

Understandably, step 103 includes: acquiring a preset transaction template, where the preset transaction template includes transaction content; filling the transaction content field in the preset transaction template with data according to block data with a trusted timestamp; The filled preset transaction template builds a timestamp transaction; generates a timestamp transaction request according to the timestamp transaction.

In this way, the timestamp transaction request includes a timestamp transaction, and the timestamp transaction includes block data with a trusted timestamp.

This embodiment further defines how to construct timestamp transaction requests from block data with trusted timestamps. First, a preset transaction template is obtained, and the preset transaction template includes a special field: the transaction content field. Any content can be filled in the transaction content field. Therefore, the transaction content field in the preset transaction template is filled according to the block data with a trusted timestamp. Then, a timestamp transaction is constructed according to the preset transaction template filled with the transaction content field, and finally, a timestamp transaction request is generated according to the timestamp transaction. Since the block data with trusted timestamp is filled into the transaction content field of the preset transaction template, the constructed timestamp transaction has nothing special to the nodes of the blockchain, and is only regarded as a common transaction, the nodes of the blockchain process the timestamp transaction as a normal transaction.

In an embodiment, if the server includes multiple servers, such as an intermediate server and a timestamp server, step 103 includes: constructing a timestamp transaction request according to the block data with a trusted timestamp through the intermediate server. Understandably, the block data with a trusted timestamp is sent to the intermediate server, so that the intermediate server constructs the timestamp transaction request. Specifically, the above steps (1), (2), (3) and the step of generating a timestamp transaction request according to the timestamp transaction are completed on the intermediate server.

104. Send the timestamp transaction request to the node in the blockchain, so that the node adds the block data with a trusted timestamp to the blockchain according to the timestamp transaction request middle.

The server can send timestamp transaction requests to any consensus node in the blockchain, or to a designated consensus node. Among them, the consensus node for sending the timestamp transaction request needs to be configured in the server in advance. Wherein, after receiving the timestamp transaction request, the consensus node in the blockchain adds the block data with a trusted timestamp carried in the timestamp transaction request to the blockchain.

In the embodiment of the present application, the block data of the current latest block on the blockchain is obtained; the trusted time is obtained, and a trusted timestamp is added to the block data according to the trusted time, so as to obtain a trusted timestamp block data; construct a timestamp transaction request according to the block data with trusted timestamp; send the timestamp transaction request to the node in the blockchain, so that the node can make the timestamp according to the timestamp A transaction request adds the trusted timestamped block data to the blockchain. In this way, the server asynchronously adds a trusted timestamp to the block data of the current latest block of the blockchain, giving the blockchain a trusted time, and does not require the blockchain itself to obtain a trusted timestamp, that is, the implementation of this application. The solution in the example is non-intrusive to the blockchain, and can give the blockchain a credible time without modifying the blockchain itself. The embodiment of the present application improves the performance of the blockchain by asynchronously adding a trusted timestamp to the block data of the latest block of the blockchain, so that the blockchain itself does not need to pay attention to the trusted timestamp, and no block Nodes in the chain obtain trusted timestamps when generating blocks, which facilitates the management of the blockchain and improves the performance and flexibility of the blockchain. On the other hand, after adding block data with trusted timestamps to the blockchain, it is convenient for nodes accessing the blockchain to obtain block data with trusted timestamps, and it is convenient to perform trusted timestamps. shared. Moreover, the solution for adding a trusted timestamp in the embodiment of the present application can add a trusted timestamp to any blockchain, that is, assign a trusted time to any blockchain, and has wide applicability.

2a is another schematic flowchart of a method for adding a trusted timestamp provided by an embodiment of the present application, which is applied to a server. The specific process of the method for adding a trusted timestamp includes:

201. Obtain the first generation time of the latest block recorded last time in the blockchain.

The first generation time of the latest block recorded last time can be understood as the latest block obtained when the trusted timestamp was added to the blockchain last time, the generation time of the latest block. When the latest block is generated, the generation time of the latest block is recorded. Obtain the generation time of the latest block recorded last time as the first generation time.

It should be noted that if a trusted timestamp is added to the blockchain for the first time, there is no first generation time of the latest block recorded last time, then step 202 is executed to obtain the generation time of the current latest block, and Record the generation time of the current latest block as the first generation time, and perform the step of "obtaining the block data of the latest block on the blockchain" to directly add a trusted timestamp to the blockchain.

202. Obtain the second generation time of the current latest block. That is, the generation time of the current latest block is obtained as the second generation time. Wherein, both the first generation time and the second generation time are obtained from the server.

203. Determine whether the difference between the second generation time and the first generation time reaches a preset time interval.

The preset time interval is preset, for example, the granularity is in seconds, such as 5 seconds, and can also be set to other granularities. Determine whether the difference between the second generation time and the first generation time reaches a preset time interval. If the preset time interval is reached, step 204 is executed; if the preset time interval is not reached, the step of "obtaining the second generation time of the current latest block" is executed.

204. Record the second generation time.

205. Obtain block data of the latest block on the blockchain.

206. Obtain a trusted time, and add a trusted timestamp to the block data according to the trusted time, to obtain block data with a trusted timestamp.

207. Construct a timestamp transaction request according to the block data with the trusted timestamp.

208. Send the timestamp transaction request to the node in the blockchain, so that the node adds the block data with a trusted timestamp to the blockchain according to the timestamp transaction request middle.

For steps 205-208 in this embodiment, please refer to the description of steps 101-104 in the above-mentioned embodiment, and details are not repeated here.

This embodiment further defines that a trusted timestamp is added to the block data of the current latest block of the blockchain according to a preset time interval, that is, every preset time interval, the block data of the current latest block of the blockchain is added. A trusted timestamp is added once, and a timestamp transaction request is constructed according to the block data with the trusted timestamp, and the block data with the trusted timestamp is added to the blockchain according to the timestamp transaction request. In this way, it is not necessary to add a trusted timestamp to the block data of the current latest block of the blockchain in real time, which reduces the interaction with the server, saves the cost of adding a trusted timestamp, and also reduces the storage area with trusted timestamps. Storage overhead and storage cost of block data.

In one embodiment, if constructing a timestamp transaction request according to the block data with a trusted timestamp, the method includes: constructing a timestamp transaction according to the block data with a trusted timestamp, and constructing a timestamp transaction according to the block data with a trusted timestamp. A timestamp transaction request is generated, or it can also be understood that a timestamp transaction is carried in the timestamp transaction request, and the timestamp transaction is constructed according to the block data with a trusted timestamp. After the generation time, before acquiring the block data of the current latest block on the blockchain, the method further includes:

A. Obtain blocks generated within a preset time interval as target blocks.

In the blockchain, if the number of transactions that have not been added to the blockchain reaches a preset number, or the transaction that has not been added to the blockchain has existed for a predetermined time, it will trigger the generation of a new block. Therefore, during the preset time interval, it is possible that multiple blocks are generated, or only one block is generated.

When each block in the blockchain is generated, the block generation time will be written in the block header. As shown in Figure 1c, the "time stamp" in the block header stores the time when the block was generated. The block generated by the blockchain within a preset time interval can be obtained as the target block according to the time when the block was generated. It is also possible to obtain the blocks generated by the blockchain within a preset time interval according to the height of the block, such as obtaining the height of the blockchain when the last acquisition time was obtained, and the height of the blockchain when the preset time interval was reached. Blocks generated by the blockchain at preset time intervals.

B. Check whether the target block includes transactions other than timestamp transactions.

Among them, transactions other than timestamp transactions include transactions in which evidence data is stored. A transaction that stores data on deposit can also be referred to as a deposit transaction. In this way, it can be understood that the transaction in this embodiment of the present application includes at least a time stamp transaction and a certificate deposit transaction.

The number of target blocks is detected. If there are multiple target blocks, it is determined that the target block includes transactions other than timestamp transactions, that is, it is determined that the target block includes certificate transactions. Understandably, only one time stamp transaction will be generated within the preset time interval. If the time stamp transaction exists for the preset time, and no deposit transaction is generated within the preset time interval, in this case , only the timestamp transaction is included in the generated block, and the deposit transaction is not included. Then only one target block is generated within the preset time interval, and the target block only includes the timestamp transaction. If there are multiple target blocks, assuming that one of the target blocks only includes timestamp transactions, other blocks must include certificate transactions, that is, the target block must include transactions other than timestamp transactions.

If there is one target block, it includes the following two situations: 1. The one target block includes timestamp transactions and certificate transactions. 2. Only timestamp transactions are included in the target block. If there is one target block, the number of transactions in the target block can be obtained, and based on the number of transactions, it can be judged whether the target block includes transactions other than timestamp transactions. If a target block only includes timestamp transactions, then the transaction quantity of the target block is fixed, and the fixed transaction quantity value is used as the preset quantity. After obtaining the transaction quantity of the target block, determine whether the transaction quantity value of the target block is the preset quantity. If it is the preset quantity, it is determined that the target block does not include transactions other than timestamp transactions, that is, the target block is determined. Only timestamp transactions are included in the block; if the number of transactions in the target block is not the preset number, it is determined that the target block includes transactions other than timestamp transactions, that is, the target block includes certificate transactions. It should be noted that there are other ways to determine whether transactions other than timestamp transactions are included in the target block.

If the target block includes transactions other than timestamp transactions, perform the step of "obtaining the block data of the current latest block in the blockchain". If the target block includes transactions other than time stamp transactions, that is, the target block includes certificate transactions, then add a trusted timestamp to the blockchain again, that is, add trusted time stamps to the certificate transactions in the target block. time, it is necessary. If the target block does not include transactions other than timestamp transactions, execute the step of "obtaining the first generation time of the latest block last recorded in the blockchain".

If the target block does not include transactions other than timestamp transactions, perform the step of obtaining the first generation time of the latest block recorded last time in the blockchain. Understandably, if the target block does not include transactions other than timestamp transactions, the step of obtaining the block data of the current latest block on the blockchain is not performed, and adding trusted timestamps to the blockchain is suspended. To avoid the situation where only one block is generated within a preset time interval, and the block only includes timestamp transactions, that is, to avoid adding trusted time to blocks that only include timestamp transactions, or it can also be understood as avoiding The resulting multiple consecutive blocks only include the case of timestamped transactions.

As shown in FIG. 2b , it is a schematic diagram of adding a trusted timestamp provided by an embodiment of the present application. In the embodiment of the present application, the transaction includes two types: time stamp transaction and certificate deposit transaction. In Figure 2b, the server includes multiple: an intermediate server and a timestamp server. The intermediate server obtains the block data of the current latest block of the blockchain, such as the block hash value, and the intermediate server sends the obtained block data to The timestamp server obtains the trusted time of the National Time Service Center, and signs the block data and the trusted time together to generate block data with a trusted timestamp. The intermediate server receives the block data with a trusted timestamp returned by the timestamp server, and constructs a transaction including the trusted timestamp as a timestamp transaction, generates a timestamp transaction request according to the timestamp transaction, and uses the timestamp Transaction requests are sent to nodes in the blockchain network. Nodes of the blockchain network add timestamp transactions included in timestamp transaction requests to the blockchain. Wherein, after the first generation time and the second generation time in the blockchain reach a preset time interval, a trusted timestamp is then added to the block data of the current latest block of the blockchain. In a preset time interval, the target block includes multiple, such as six in FIG. 2b (the second to seventh in FIG. 2b). Within a preset time interval, a block including timestamp transactions is generated, such as a block with a white background, in this block, in addition to including timestamp transactions (transactions with a white background), it also includes certificate transactions (transactions with a dark gray background), i.e. in Figure 2b, the timestamp transaction and other depository transactions together generate a block, which is added to the blockchain. It should be noted that, in some embodiments, the timestamp transaction can independently generate a block and add it to the blockchain.

This embodiment further defines that if the target blocks generated within the preset time interval include transactions other than timestamp transactions, the block data of the latest block in the blockchain is obtained, which is the blockchain Add a trusted timestamp to the latest block of the blockchain; if the target block generated within the preset time interval does not include transactions other than timestamp transactions, add trusted time to the latest block of the blockchain. stamp. This embodiment further precludes adding trusted time to blocks that only include timestamped transactions, reduces interaction with the server, saves the cost of adding trusted timestamps, and also reduces storing timestamped transactions and transactions with trusted timestamps The storage overhead and storage cost of the block data.

The embodiment of the present application also provides a method for adding a trusted timestamp, which is applied to the server side. The difference between this embodiment and the embodiment in FIG. 1b is that: before acquiring the block data of the current latest block on the blockchain , adding a step: obtaining the timing time, and detecting whether the timing time reaches the preset time interval, if the preset time interval reaches the preset time interval, execute the step of obtaining the block data of the current latest block on the blockchain and the following steps; If the preset time interval is not reached, continue to perform the step of detecting whether the timing time reaches the preset time interval. The step of acquiring the block data of the current latest block on the blockchain and the subsequent steps are consistent with the embodiment in FIG. 1b . For details, please refer to the description corresponding to the embodiment in FIG. 1b .

Among them, detecting whether the timing time reaches the preset time interval can be realized in various ways. For example, setting a timer, obtaining the timing time is the time of obtaining the timer, the timer starts counting from zero, when the preset time interval is reached, it is determined that the timing time reaches the preset time interval, and the timer is reset. zero. For example, the first time on the local machine is obtained, and the timer is started from the first time. If it is detected that the preset time interval has elapsed from the first time, it is determined that the detected time has reached the preset time interval. Understandably, if the preset time interval is set to one minute, it is understood that the step of "obtaining the block data of the current latest block on the blockchain" is executed every one minute.

In this embodiment, before acquiring the block data of the current latest block on the blockchain, steps A and B described above may also be performed. It is not repeated here.

In this embodiment, whether the preset time interval is reached is determined according to the timing time, and if the preset time interval is reached, the step of "obtaining the block data of the current latest block on the blockchain" is performed. That is, this embodiment further defines whether to determine whether the preset time interval has been reached according to the timing time, adding a trusted timestamp to the block data of the current latest block of the blockchain according to the preset time interval, and according to the trusted timestamp. The block data constructs a timestamp transaction request, and the block data with a trusted timestamp is added to the blockchain according to the timestamp transaction request. In this way, it is not necessary to add a trusted timestamp to the block data of the latest block of the blockchain in real time, which reduces the interaction with the server, saves the cost of adding a trusted timestamp, and reduces the storage of block data with a trusted timestamp. storage overhead and storage cost.

The embodiment of the present application also provides a method for adding a trusted timestamp, which is applied to the server side. The difference between this embodiment and the embodiment in FIG. 1b is that: before acquiring the block data of the current latest block on the blockchain , adding steps a-d. The differences between this embodiment and the embodiment in FIG. 1b will be described in detail below. In addition, the step of acquiring the block data of the current latest block on the blockchain and the subsequent steps are consistent with the embodiment in FIG. 1b . For details, please refer to the description corresponding to the embodiment in FIG. 1b .

a, Get the block height last recorded in the blockchain.

Understandably, when a trusted timestamp is added to the block data of the latest block of the blockchain last time, the block height of the blockchain is obtained and recorded.

b, Get the current block height.

c. Determine whether the difference between the current block height and the last recorded block height reaches a preset height difference.

The preset height difference is set in advance, and the preset height difference is a positive integer greater than 1, for example, the preset height difference is 2, 5, and so on. The preset height difference is a positive integer greater than 1, indicating that the number of blocks greater than 1 has been generated between the time when the current block height of the blockchain was obtained and the time when the previous block height was obtained. The block must include transactions other than timestamp transactions. If the difference between the current block height and the previous block height reaches the preset height difference, execute step d; if the difference between the current block height and the last block height does not reach the preset height difference, execute step b to obtain the current block height. block height.

d, record the current block height. And perform the steps of obtaining the block data of the current latest block on the blockchain and the following steps.

This embodiment further defines that a trusted timestamp is added to the block data of the latest block of the blockchain according to the preset height difference, that is, every preset height difference (every preset number of blocks) is a block Add a trusted timestamp to the block data of the latest block of the chain to obtain block data with a trusted timestamp, and construct a timestamp transaction request. According to the timestamp transaction request, the block data with a trusted timestamp is added to the blockchain. In this way, it is not necessary to add a trusted timestamp to the block data of the latest block of the blockchain in real time, which reduces the interaction with the server, saves the cost of adding a trusted timestamp, and also reduces the storage area with trusted timestamps. Storage overhead and storage cost of block data.

FIG. 3 is another schematic flowchart of a method for adding a trusted timestamp provided by an embodiment of the present application, where the method is applied to a first node, and the first node is any node in the blockchain. It should be noted that the nodes in the embodiments of this application refer to consensus nodes. The specific process of this method includes:

301. Receive a timestamp transaction request, where the timestamp transaction request carries block data with a trusted timestamp.

The first consensus node in the blockchain network receives a timestamp transaction request sent by the server, and the timestamp transaction request carries the timestamp transaction. It should be noted that the first consensus node is the consensus node configured in the server.

302. Detect whether the first node is a target node.

Among them, the target node refers to the target consensus node, and the target consensus node is the node that can currently generate blocks. After receiving the timestamp transaction request sent by the server, the first consensus node in the blockchain network obtains the target consensus node information stored in the first consensus node, and the target consensus node information includes the IP and other information of the target consensus node. Obtain the IP of the first consensus node; determine whether the IP of the first consensus node is the same as the IP of the target consensus node; if they are the same, determine that the first consensus node is the target consensus node; if not, determine the first consensus node A consensus node is not the target consensus node.

It should be noted that the target consensus node will be pre-selected in this blockchain network, and the information of the target consensus node will be stored in other consensus nodes. Once the target consensus node is selected, if it is detected that the block generated by the target consensus node has not been verified by other consensus nodes in the blockchain network, the target consensus node needs to be replaced. Specifically, a consensus node is selected from other consensus nodes according to the algorithm, the consensus node is used as the target consensus node, and the information of the target consensus node is sent to other consensus nodes, so that the other consensus nodes can save it Information of the target consensus node.

If the first consensus node is the target consensus node, step 303 is performed; if the first consensus node is not the target consensus node, step 307 is performed.

303. Generate a block, where the block includes block data with a trusted timestamp.

If it is determined that the first consensus node is the target consensus node, and if it is detected that the target consensus node satisfies the conditions for generating the block (such as whether the time for generating the block is reached), a block including block data with a trusted timestamp is generated.

304. Broadcast the verification request of the block to a second node in the blockchain, where the second node is a node other than the first node in the blockchain.

The second node refers to the second consensus node, and broadcasts the verification request of the block to the second consensus node in the blockchain, so that the second consensus node has received the block message. After receiving the message of the block, the second consensus node verifies the block.

305. Receive a verification result returned by the second node based on the verification request.

The second consensus node will broadcast the verification result, so that the second consensus node will receive the broadcast verification result. Wherein, the verification results include verification pass results and verification failure results.

306. Add the block to the blockchain based on the verification result returned by the second node.

Wherein, adding the block to the blockchain based on the verification results returned by the second node includes: if there are verification results returned by the second consensus node that reach a first preset number of pass results , adding the block to the blockchain. Wherein, the first preset number is related to the total number of consensus nodes in the blockchain network, (the first preset number+1)/total number of consensus nodes=preset ratio. The preset ratio is a value greater than 1/2, for example, the preset ratio=2/3. The first preset number + 1 refers to the first preset number of second consensus nodes and target consensus nodes. If the verification result sent by the second consensus node reaching the first preset number is received, it means that the newly generated block completes the consensus, and the block is added to the blockchain.

307. Generate a sending instruction according to the timestamp transaction request.

That is, if the first consensus node is not the target consensus node, a sending instruction is generated according to the timestamp transaction request.

308. Send the sending instruction to the target node, where the sending instruction is used to instruct the target node to generate a block and add the block to the blockchain based on a consensus mechanism.

After the target consensus node receives the sending instruction (including the timestamp transaction request), it detects whether the conditions for generating blocks are met (such as whether the time for generating blocks is reached). The first consensus node and the second consensus node in the blockchain broadcast the verification request of the block, wherein the second consensus node here is a node other than the first consensus node and the target consensus node in the blockchain; the first consensus node The consensus node will get a verification result based on the verification request, and at the same time receive the verification results returned by the second consensus node and the target consensus node based on the verification request; if the second preset number of verification results are detected, the block will be added to all in the blockchain described above. Wherein, the second preset number is related to the total number of consensus nodes in the blockchain network, (the second preset number)/total number of consensus nodes=preset ratio. If it is detected that the verification result reaches the second preset number, it means that the newly generated block completes the consensus, and the newly generated block is added to the blockchain.

In this embodiment, the target consensus node in the blockchain network is pre-selected, and after the target consensus node is selected, the target consensus node generally does not change (the block generated by the target consensus node will not be re-selected until the verification is passed). target consensus node). The current block is generated through the fixed target consensus node without requiring all consensus nodes to compete for the right to generate the current block, which improves the efficiency of generating blocks and reduces the resource consumption for competing for the right to generate the current block. On the other hand, the first consensus node that receives the timestamp transaction request sent by the server does not need to broadcast the timestamp transaction request to other consensus nodes, but only needs to send it to the target consensus node, and the target consensus node generates a block , which reduces bandwidth, saves network resources, and storage resources for each consensus node to store the transaction.

According to the method described in the above embodiment, this embodiment will be further described from the perspective of a trusted time stamp adding device. The trusted time stamp adding device can be specifically implemented as an independent entity, or can be implemented by being integrated in a server. .

As shown in FIG. 4 , the apparatus for adding trusted timestamp includes a unit corresponding to executing the method for adding trusted timestamp in FIG. 1 b. The apparatus may include a block data acquiring unit 401 , a time stamp adding unit 402 , a request constructing unit 403 , and a request sending unit 404 .

The block data acquisition unit 401 is configured to acquire block data of the latest current block on the blockchain.

The timestamp adding unit 402 is configured to obtain a trusted time, and add a trusted timestamp to the block data according to the trusted time to obtain block data with a trusted timestamp.

The request constructing unit 403 is configured to construct a timestamp transaction request according to the block data with a trusted timestamp.

A request sending unit 404 is configured to generate a submission instruction according to the time stamp transaction, and send the submission instruction to a second server, where the submission instruction is used to instruct the second server to add the time stamp transaction to the in the blockchain.

In an embodiment, the request constructing unit 403 specifically includes: a transaction constructing unit and a request generating unit. Among them, the transaction construction unit is used to construct a timestamp transaction according to the block data with a trusted timestamp. The request generation unit is used to generate a timestamp transaction request according to the timestamp transaction. The transaction construction unit includes: a template acquisition unit, a filling unit, and a timestamp transaction construction unit. The template obtaining unit is used for obtaining a preset transaction template, and the preset transaction template includes a transaction content field. A filling unit, configured to perform data filling in the transaction content field in the preset transaction template according to the trusted timestamp. The timestamp transaction construction unit is used to construct a timestamp transaction according to the filled preset transaction template.

FIG. 5 is another schematic block diagram of an apparatus for adding a trusted time stamp provided by an embodiment of the present application, where the apparatus includes a unit corresponding to executing the method for adding a trusted time stamp in the embodiment of FIG. 2a. The apparatus includes a time acquisition unit 501 , a time judgment unit 502 , a time recording unit 503 , a block data acquisition unit 504 , a time stamp addition unit 505 , a request construction unit 506 , and a request transmission unit 507 . The difference between this apparatus embodiment and the apparatus embodiment shown in FIG. 4 is that a time acquisition unit 501 , a time judgment unit 502 , and a time recording unit 503 are added. The block data acquiring unit 504, the time stamp adding unit 505, the request constructing unit 506, and the request sending unit 507 in this embodiment are the same as the block data acquiring unit 401, the time stamp adding unit 402, and the request constructing unit in the above embodiment 403 and the request sending unit 404 are in a one-to-one correspondence. For details, reference may be made to the description in the embodiment of FIG. 4 , which will not be repeated here. The differences between the apparatus embodiment and the apparatus embodiment shown in FIG. 4 will be described below.

The time obtaining unit 501 is configured to obtain the first generation time of the latest block recorded last time in the blockchain. The time acquisition unit 501 is also used for the second generation time of the current latest block.

The time judgment unit 502 is used for whether the difference between the second generation time and the first generation time reaches a preset time interval.

The time recording unit 503 is configured to record the second generation time if the difference between the second generation time and the first generation time reaches a preset time interval. Next, the block data acquisition unit 504 is triggered; if the difference between the second generation time and the first generation time does not reach the preset time interval, the time acquisition unit 501 is triggered to acquire the second generation time of the current latest block.

In one embodiment, if a timestamp transaction is carried in the timestamp transaction request, and the timestamp transaction is constructed according to the block data with the trusted timestamp, the trusted timestamp adding device further includes a target. Block acquisition unit, block detection unit. in,

The target block acquiring unit is used for acquiring the blocks generated within the preset time interval as the target blocks.

The block detection unit is used to detect whether transactions other than timestamp transactions are included in the target block.

If the target block does not include transactions other than timestamp transactions, the time acquisition unit 501 is triggered to obtain the first generation time of the latest block recorded last time in the blockchain; if the target block includes transactions other than timestamp transactions Transactions other than timestamp transactions trigger the block data acquisition unit 504 .

In an embodiment, a trusted timestamp adding device is also provided, the device includes a timing detection unit, a block data acquisition unit, a timestamp adding unit, a request constructing unit, and a request sending unit. The difference between this device embodiment and the device embodiment shown in FIG. 4 is that a timing detection unit is added, wherein the timing detection unit is used to acquire the timing time and detect whether the timing time reaches a preset time interval. Among them, the block data acquisition unit, the time stamp adding unit, the request construction unit, and the request sending unit in the device embodiment are the same as the block data acquisition unit 401 and the time stamp adding unit 402 in the device embodiment shown in FIG. 4 . , the request constructing unit 403 , and the request sending unit 404 are in a one-to-one correspondence. For details, please refer to the description in the embodiment of FIG. 4 , which will not be repeated here.

The embodiment of the present application also provides a trusted timestamp adding device, which is integrated in the server. The device includes a height obtaining unit, a height judging unit, a height recording unit, a block data obtaining unit, a time stamp adding unit, a request constructing unit, and a request sending unit. The difference between this apparatus embodiment and the apparatus embodiment shown in FIG. 4 is that an altitude acquisition unit, an altitude judgment unit, and an altitude recording unit are added. The block data acquisition unit, time stamp addition unit, request construction unit, and request transmission unit in this embodiment are the same as the block data acquisition unit 401, the time stamp addition unit 402, and the request construction unit in the embodiment shown in FIG. 4 above. 403 and the request sending unit 404 are in a one-to-one correspondence. For details, reference may be made to the description in the embodiment of FIG. 4 , which will not be repeated here. The differences between the apparatus embodiment and the apparatus embodiment shown in FIG. 4 will be described below.

The height obtaining unit is used to obtain the last recorded block height in the blockchain, and is also used to obtain the current block height of the blockchain.

The height judgment unit is used for judging whether the difference between the height of the current block and the height of the block recorded last time reaches a preset height difference.

The height recording unit is used to record the current block height and trigger the block data acquisition unit if the difference between the current block height and the last recorded block height reaches the preset height difference; The difference between the heights of the blocks does not reach the preset height difference, and the height obtaining unit is triggered to obtain the current block height of the blockchain.

During specific implementation, the above units may be implemented as independent entities, or may be combined arbitrarily to be implemented as the same or several entities. For the specific implementation process of the above device and each unit, as well as the beneficial effects achieved, reference may be made to the corresponding description in the foregoing method embodiments applied to the server side.

According to the method described in the above embodiment, this embodiment will be further described from the perspective of a trusted timestamp adding device. The trusted timestamp adding device can be specifically implemented as an independent entity, or can be integrated in a blockchain network. in the node to achieve.

The embodiment of the present application also provides another apparatus for adding a trusted timestamp. As shown in FIG. 6 , the apparatus includes a unit corresponding to executing the method for adding a trusted timestamp in the embodiment of FIG. 3 . The device includes a request receiving unit 601 , a node detecting unit 602 , a block generating unit 603 , a broadcasting unit 604 , a verification result receiving unit 605 , a block adding unit 606 , an instruction generating unit 607 , and an instruction sending unit 608 . in,

A request receiving unit 601, configured to receive a timestamp transaction request, where the timestamp transaction request carries block data with a trusted timestamp;

A node detection unit 602, configured to detect whether the first node is a target node.

A block generating unit 603, configured to generate a block when the first node is a target node that can generate a block, and the block includes block data with a trusted timestamp;

A broadcasting unit 604, configured to broadcast the verification request of the block to a second node in the blockchain, wherein the second node is a node other than the first node in the blockchain;

a verification result receiving unit 605, configured to receive the verification result returned by the second node based on the verification request;

A block adding unit 606, configured to add the block to the blockchain based on the verification result returned by the second node.

An instruction generating unit 607, configured to generate a sending instruction according to the timestamp transaction request when the first node is not a target node that can generate a block;

an instruction sending unit 608, configured to send the sending instruction to the target node, where the sending instruction is used to instruct: the target node to generate a block and add the block to the blockchain based on a consensus mechanism .

During specific implementation, the above units may be implemented as independent entities, or may be combined arbitrarily to be implemented as the same or several entities. For the specific implementation process of the above devices and units, as well as the beneficial effects achieved, reference may be made to the corresponding descriptions in the foregoing method embodiments applied to the nodes of the blockchain.

The embodiment of the present application also provides a computer device, as shown in FIG. 7 , which shows a schematic structural diagram of the computer device involved in the embodiment of the present application, specifically:

The computer device may include a processor 701 of one or more processing cores, a memory 702 of one or more computer-readable storage media, a radio frequency (RF) circuit 703 , a power supply 704 , an input unit 705 , and a display unit 706 and other parts. Those skilled in the art can understand that the computer device structure shown in the figures does not constitute a limitation on the computer device, and may include more or less components than the one shown, or combine some components, or arrange different components. in:

The processor 701 is the control center of the computer equipment, uses various interfaces and lines to connect various parts of the entire computer equipment, runs or executes the software programs and/or modules stored in the memory 702, and calls the software programs stored in the memory 702. Data, perform various functions of computer equipment and process data, so as to conduct overall monitoring of computer equipment. Optionally, the processor 701 may include one or more processing cores; preferably, the processor 701 may integrate an application processor and a modem processor, wherein the application processor mainly processes the operating system, user interface, and application programs, etc. , the modem processor mainly deals with wireless communication. It can be understood that, the above-mentioned modulation and demodulation processor may also not be integrated into the processor 701 .

The memory 702 can be used to store software programs and modules, and the processor 701 executes various functional applications and data processing by running the software programs and modules stored in the memory 702 . The memory 702 may mainly include a stored program area and a stored data area, wherein the stored program area may store an operating system, an application program (such as a sound playback function, an image playback function, etc.) required for at least one function, and the like; Data created by the use of computer equipment, etc. Additionally, memory 702 may include high-speed random access memory, and may also include non-volatile memory, such as at least one magnetic disk storage device, flash memory device, or other volatile solid state storage device. Accordingly, memory 702 may also include a memory controller to provide processor 701 access to memory 702 .

The RF circuit 703 can be used for signal reception and transmission in the process of sending and receiving information. In particular, after receiving the downlink information of the base station, it is processed by one or more processors 701; in addition, it sends the uplink data to the base station. Typically, the RF circuit 703 includes, but is not limited to, an antenna, at least one amplifier, a tuner, one or more oscillators, a Subscriber Identity Module (SIM) card, a transceiver, a coupler, a Low Noise Amplifier (LNA) , duplexer, etc. In addition, the RF circuit 703 can also communicate with the network and other devices through wireless communication. The wireless communication can use any communication standard or protocol, including but not limited to Global System for Mobile Communication (GSM, Global System of Mobile communication), General Packet Radio Service (GPRS, General Packet Radio Service), Code Division Multiple Access (CDMA, Code Division Multiple Access), Wideband Code Division Multiple Access (WCDMA, Wideband CodeDivision Multiple Access), Long Term Evolution (LTE, Long Term Evolution), email, Short Messaging Service (SMS, Short Messaging Service), etc.

The computer equipment also includes a power supply 704 (such as a battery) for supplying power to various components. Preferably, the power supply 704 can be logically connected to the processor 701 through a power management system, so that functions such as managing charging, discharging, and power consumption management are implemented through the power management system. . Power supply 704 may also include one or more DC or AC power sources, recharging systems, power failure detection circuits, power converters or inverters, power status indicators, and any other components.

The computer device may also include an input unit 705 that may be used to receive input numerical or character information and generate keyboard, mouse, joystick, optical, or trackball signal input related to user settings and function control. Specifically, in a specific embodiment, the input unit 705 may include a touch-sensitive surface as well as other input devices. A touch-sensitive surface, also known as a touch display or trackpad, collects the user's touch operations on or near it (such as the user's finger, stylus, etc., any suitable operation near the surface), and drive the corresponding connection device according to the preset program. Alternatively, the touch-sensitive surface may include two parts, a touch detection device and a touch controller. Among them, the touch detection device detects the user's touch orientation, detects the signal brought by the touch operation, and transmits the signal to the touch controller; the touch controller receives the touch information from the touch detection device, converts it into contact coordinates, and then sends it to the touch controller. To the processor 701, and can receive the command sent by the processor 701 and execute it. Additionally, touch-sensitive surfaces can be implemented using resistive, capacitive, infrared, and surface acoustic wave types. In addition to touch-sensitive surfaces, input unit 705 may also include other input devices. Specifically, other input devices may include, but are not limited to, one or more of physical keyboards, function keys (such as volume control keys, switch keys, etc.), trackballs, mice, joysticks, and the like.

The computer device may also include a display unit 706 that may be used to display information input by the user or information provided to the user and various graphical user interfaces of the computer device, which may consist of graphics, text, icons, video and any combination thereof. The display unit 706 may include a display panel. Optionally, the display panel may be configured in the form of a liquid crystal display (LCD, Liquid Crystal Display), an organic light-emitting diode (OLED, Organic Light-Emitting Diode). Further, the touch-sensitive surface may cover the display panel, and when the touch-sensitive surface detects a touch operation on or near it, it is transmitted to the processor 701 to determine the type of the touch event, and then the processor 701 displays the touch event according to the type of the touch event. The corresponding visual output is provided on the panel. Although in the figures, the touch-sensitive surface and the display panel are implemented as two separate components to implement input and input functions, in some embodiments, the touch-sensitive surface and the display panel may be integrated to implement the input and output functions.

Although not shown, the computer device may also include a camera, a Bluetooth module, etc., which will not be described herein again. Specifically, in this embodiment, the processor 701 in the computer device loads the executable files corresponding to the processes of one or more application programs into the memory 702 according to the following instructions, and the processor 701 executes them and stores them in the memory 702 . The application program in the memory 702, thereby realizing various functions, as follows:

Obtain the block data of the current latest block on the blockchain; obtain the trusted time, and add a trusted timestamp to the block data according to the trusted time to obtain block data with a trusted timestamp; The block data with a trusted timestamp constructs a timestamp transaction request; the timestamp transaction request is sent to a node in the blockchain, so that the node converts the timestamp transaction request according to the timestamp transaction request. Trusted timestamped block data is added to the blockchain.

The computer device can implement the steps in any of the embodiments of the method for adding trusted timestamps in a server provided by the embodiments of this application, or implement the trusted timestamps provided in the embodiments of this application and applied in blockchain nodes. The steps in any of the embodiments of the method for adding time stamps can therefore achieve the beneficial effects that can be achieved by any method for adding trusted time stamps provided by the embodiments of the present application and applied to the server or achieve the benefits provided by the embodiments of the present application. The beneficial effects that can be achieved by any method for adding trusted timestamps applied to blockchain nodes can be seen in the previous embodiments, which will not be repeated here.

Those of ordinary skill in the art can understand that all or part of the steps in the various methods of the above-mentioned embodiments can be completed by instructions, or by instructions that control relevant hardware, and the instructions can be stored in a computer-readable storage medium, and loaded and executed by the processor. To this end, an embodiment of the present invention provides a storage medium, in which a plurality of instructions are stored, and the instructions can be loaded by a processor to execute any of the methods for adding a trusted timestamp applied to a server provided by the embodiments of the present invention. The steps of an embodiment may be performed to perform the steps of the method for adding a trusted timestamp applied to a blockchain node provided by the embodiments of the present application.

Wherein, the storage medium may include: a read only memory (ROM, Read Only Memory), a random access memory (RAM, Random Access Memory), a magnetic disk or an optical disk, and the like.

Since the instructions stored in the storage medium can perform the steps in any of the method embodiments for adding a trusted timestamp provided by the embodiments of the present invention, any trusted timestamp provided by the embodiments of the present invention can be implemented The beneficial effects that can be achieved by the adding method can be found in the previous embodiments, and details are not repeated here.

A method, device, computer device, and storage medium for adding a trusted timestamp provided by the embodiments of the present application have been described above in detail. The principles and implementations of the present application are described with specific examples in this article. The above embodiments The description is only used to help understand the method of the present application and its core idea; meanwhile, for those skilled in the art, according to the idea of the present application, there will be changes in the specific embodiments and application scope. In summary, the above , the contents of this specification should not be construed as limiting the application.

Claims (10)

1. a credible time stamp adding method, is characterized in that, comprises: Obtain the block data of the current latest block on the blockchain, the latest block includes a newly generated block on the blockchain, and the block data includes the block header data and block data of the current latest block At least one of the volume data; Obtaining a trusted time, and adding a trusted timestamp to the block data according to the trusted time to obtain block data with a trusted timestamp; constructing a timestamp transaction request according to the block data with the trusted timestamp; The timestamp transaction request is sent to the node in the blockchain, so that the node adds the block data with a trusted timestamp to the blockchain according to the timestamp transaction request. 2. The method for adding trusted timestamps according to claim 1, wherein the constructing a timestamp transaction request according to the block data with the trusted timestamps comprises: obtaining a preset transaction template, where the preset transaction template includes a transaction content field; Filling the transaction content field with data according to the block data with the trusted timestamp; Build a timestamp transaction based on the filled preset transaction template; A timestamp transaction request is generated based on the timestamp transaction. 3. The method for adding trusted timestamps as claimed in claim 1, characterized in that, before said acquiring the block data of the current latest block on the blockchain, the method further comprises: Obtain the first generation time of the latest block last recorded in the blockchain, and the second generation time of the current latest block; When the difference between the second generation time and the first generation time reaches a preset time interval, the second generation time is recorded, and the step of obtaining the block data of the current latest block on the blockchain is performed. . 4. The method for adding a trusted time stamp according to claim 3, wherein the time stamp transaction request carries a time stamp transaction, and the time stamp transaction is based on the block data with a trusted time stamp. constructed, after the recording of the second generation time, further comprising: Obtain the block generated within the preset time interval as the target block; detecting whether the target block includes transactions other than the timestamp transaction; If the target block includes transactions other than the timestamp transaction, the step of obtaining the block data of the current latest block on the blockchain is performed. 5. The method for adding trusted timestamps as claimed in claim 1, wherein, before acquiring the block data of the current latest block on the blockchain, the method further comprises: Get the last recorded block height and current block height in the blockchain; When the difference between the current block height and the last recorded block height reaches a preset height difference, the current block height is recorded, and the block that obtains the latest current block on the blockchain is executed. data steps. 6. The method for adding trusted time stamps according to claim 1, wherein, Obtaining the block data of the current latest block on the blockchain, including: obtaining the block data of the current latest block on the blockchain from an intermediate server; The constructing a timestamp transaction request according to the block data with the trusted timestamp includes: The time stamp transaction request is constructed according to the block data with the trusted time stamp through the intermediate server. 7. A method for adding trusted timestamps, characterized in that it is applied to a first node, and the first node is any node in the blockchain, comprising: Receive a timestamp transaction request, where the timestamp transaction request carries block data with a trusted timestamp, and the block data includes at least one of block header data and block body data of the current latest block; When the first node is a target node that can generate a block, generate a block, and the block includes block data with a trusted timestamp; Broadcast the verification request of the block to a second node in the blockchain, where the second node is a node other than the first node in the blockchain; receiving a verification result returned by the second node based on the verification request; Based on the verification result returned by the second node, the block is added to the blockchain. 8. The method for adding trusted timestamps as claimed in claim 7, further comprising: When the first node is not a target node capable of generating blocks, generating a sending instruction according to the timestamp transaction request; Sending the sending instruction to the target node, where the sending instruction is used to instruct: the target node to generate a block and add the block to the blockchain based on a consensus mechanism. 9. A device for adding trusted time stamps, comprising: A block data acquisition unit, configured to acquire block data of the current latest block on the blockchain, where the latest block includes a newly generated block on the blockchain, and the block data includes the current latest block At least one of block header data and block body data of the block; a timestamp adding unit, configured to obtain a trusted time, and add a trusted timestamp to the block data according to the trusted time to obtain block data with a trusted timestamp; a request construction unit, configured to construct a timestamp transaction request according to the block data with a trusted timestamp; A request sending unit, configured to send the time stamp transaction request to the node in the blockchain, so that the node adds the block data with a trusted time stamp to all the nodes according to the time stamp transaction request in the blockchain described above. 10. A computer-readable storage medium, wherein the computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the computer program according to any one of claims 1-6 is implemented. The method for adding timestamps.

Images