CN118740851A - Blockchain data processing method, device, electronic device and storage medium - Google Patents

Abstract

The embodiments of the present application disclose a blockchain data processing method, device, electronic device and storage medium. The method extracts the target transaction identifier of the target transaction from the target block, accesses the cache service storing the first data pair, and obtains the second transaction data associated with the target transaction from the cache service according to the target transaction identifier. By introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier even when the second transaction data does not need to be uploaded to the chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers. On this basis, the target transaction data can be obtained according to the first transaction data and the second transaction data, thereby improving the integrity of the transaction data in the local database on the basis of improving the security of the transaction data. The method can be widely used in technical fields such as blockchain, cloud technology, and payment.

Description

Blockchain data processing method, device, electronic device and storage medium

Technical Field

The present application relates to the field of blockchain technology, and in particular to a blockchain data processing method, device, electronic device and storage medium.

Background Art

With the development of blockchain technology, blockchain-based applications are becoming more and more widespread. In the application process of blockchain, transactions will generate some key transaction data, which will generally be uploaded to the blockchain and then stored on the blockchain to achieve the effect that the transaction data cannot be tampered with and can be traced.

In related technologies, transaction data on the chain is usually synchronized to the local database. However, this method can only synchronize some key transaction data from the blockchain network, resulting in incomplete transaction data synchronized from the local database. If all transaction data is stored on the blockchain, although the integrity of the transaction data synchronized from the blockchain can be improved, it will reduce the security of some transaction data that needs to be kept confidential. It can be seen that how to simultaneously improve the integrity and security of transaction data in the local database is a problem that needs to be solved urgently.

Summary of the invention

The following is a summary of the subject matter described in detail in this application. This summary is not intended to limit the scope of the claims.

The embodiments of the present application provide a blockchain data processing method, device, electronic device and storage medium, which can simultaneously improve the integrity and security of transaction data in a local database.

On the one hand, an embodiment of the present application provides a blockchain data processing method, including:

When the target block is approved by the blockchain network consensus, receiving the target block sent by the blockchain network, wherein the target block includes at least one target transaction;

Extracting a target transaction identifier of the target transaction and first transaction data associated with the target transaction from the target block;

Accessing a cache service storing a first data pair, and obtaining second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier, wherein the first data pair is constructed based on the transaction identifier and the transaction data, and the transaction identifier in the first data pair is returned by the blockchain network after receiving the asynchronously sent transaction request;

Target transaction data is obtained according to the first transaction data and the second transaction data, and the target transaction data is stored in a target database.

On the other hand, the embodiment of the present application also provides a blockchain data processing method, including:

Asynchronously sending a transaction request for a target transaction to a blockchain network, and receiving a target transaction identifier of the target transaction returned by the blockchain network;

Acquire second transaction data associated with the target transaction, and construct a first data pair according to the target transaction identifier and the second transaction data;

The first data pair is stored in the cache service so that when the target block corresponding to the target transaction is passed by the blockchain network consensus, the detection service extracts the target transaction identifier and the first transaction data associated with the target transaction from the target block, accesses the cache service, obtains the second transaction data from the first data pair of the cache service according to the target transaction identifier, obtains the target transaction data according to the first transaction data and the second transaction data, and stores the target transaction data in the target database.

On the other hand, the embodiment of the present application also provides a blockchain data processing device, including:

A block receiving module, configured to receive the target block sent by the blockchain network when the target block is approved by the blockchain network consensus, wherein the target block includes at least one target transaction;

A block processing module, configured to extract a target transaction identifier of the target transaction and first transaction data associated with the target transaction from the target block;

an access module, configured to access a cache service storing a first data pair, and obtain second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier, wherein the first data pair is constructed based on the transaction identifier and the transaction data, and the transaction identifier in the first data pair is generated by the blockchain network after receiving an asynchronously sent transaction request;

The storage module is used to obtain target transaction data according to the first transaction data and the second transaction data, and store the target transaction data in a target database.

Furthermore, the block receiving module is specifically used for:

Generate a block subscription request according to a preset block number interval, and send the block subscription request to the blockchain network;

Whenever a target block within the block number interval is approved by the blockchain network consensus, the target block sent by the blockchain network in response to the block subscription request is received.

Furthermore, the storage module is also used for:

generating storage result information of the target transaction data, wherein the storage result information is used to indicate whether the target transaction data has been successfully stored in the target database or has not been successfully stored in the target database;

A second data pair is constructed based on the target transaction identifier and the storage result information, and the second data pair is stored in the cache service.

Furthermore, the storage module is also used for:

When the target transaction data has been successfully stored in the target database, determine the block number of the target block and the transaction sequence number of the current target transaction in the target block, and record the block number and the transaction sequence number;

After restarting, the block number and the transaction sequence number are loaded, and the next target transaction is determined according to the block number and the transaction sequence number.

Furthermore, the storage module is also used for:

If the transaction type of the target transaction is a chain configuration type, extracting server attribute information of the target server from the target block, and a server transaction certificate assigned to the target server by the blockchain network, wherein the target server is a server configured for the target transaction;

The server attribute information and the server transaction certificate are stored in the target database.

Furthermore, the storage module is specifically used for:

Extracting a target transaction certificate used to sign the target transaction from the target block;

Matching the target transaction certificate with the server transaction certificate, and acquiring the server attribute information corresponding to the target transaction from the target database according to the matching result;

The first transaction data, the second transaction data, the server attribute information and the target transaction certificate are combined into target transaction data.

Furthermore, the access module is specifically used to:

Extracting a target transaction certificate used when signing the target transaction from the target block;

Obtaining the server transaction certificate loaded at startup, and comparing the server transaction certificate loaded at startup with the target transaction certificate;

When the comparison result is that the server transaction certificate loaded at startup is consistent with the target transaction certificate, a cache service storing the first data pair is accessed.

Furthermore, the storage module is also used for:

When the comparison result shows that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, taking the first transaction data as the target transaction data, and storing the target transaction data in the target database;

Alternatively, when the comparison result is that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, the cache service is accessed, and the encrypted transaction data corresponding to the target transaction identifier is obtained from the cache service according to the first data pair, and the pre-stored decryption information is obtained. The encrypted transaction data is decrypted according to the decryption information to obtain the second transaction data corresponding to the target transaction identifier, and the target transaction data is obtained according to the first transaction data and the second transaction data, and the target transaction data is stored in the target database, wherein the decryption information is generated by the target server that constructs the first data pair.

Furthermore, the data pair building module is specifically used for:

Encrypting the second transaction data to obtain encrypted transaction data, and sending decryption information corresponding to the encrypted transaction data to the detection service;

A first data pair is constructed according to the target transaction identifier and the encrypted transaction data.

On the other hand, the embodiment of the present application also provides a blockchain data processing device, including:

A request module, used to asynchronously send a transaction request of a target transaction to a blockchain network, and receive a target transaction identifier of the target transaction returned by the blockchain network;

a data pair construction module, configured to obtain second transaction data associated with the target transaction, and construct a first data pair according to the target transaction identifier and the second transaction data;

A cache module is used to store the first data pair in a cache service so that when the target block corresponding to the target transaction is passed by the blockchain network consensus, the detection service extracts the target transaction identifier and the first transaction data associated with the target transaction from the target block, accesses the cache service, obtains the second transaction data from the first data pair of the cache service according to the target transaction identifier, obtains the target transaction data according to the first transaction data and the second transaction data, and stores the target transaction data in a target database.

Furthermore, the blockchain data processing device also includes a message sending module, which is used to:

Acquire the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, and generate a first notification message indicating a transaction result of the target transaction according to the storage result information;

The first notification message is sent to the account that initiates the target transaction.

Furthermore, the message sending module is specifically used for:

Based on a preset time interval, continuously obtaining the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier;

When the storage result information is obtained, a first notification message indicating the transaction result of the target transaction is generated according to the storage result information; or, when the duration of requesting the storage result information exceeds a preset duration threshold, a second notification message indicating a timeout is generated, and the second notification message is sent to the account that initiated the target transaction.

On the other hand, an embodiment of the present application further provides an electronic device, comprising a memory and a processor, wherein the memory stores a computer program, and the processor implements the above-mentioned blockchain data processing method when executing the computer program.

On the other hand, an embodiment of the present application further provides a computer-readable storage medium, wherein the storage medium stores a computer program, and the computer program is executed by a processor to implement the above-mentioned blockchain data processing method.

On the other hand, the embodiment of the present application further provides a computer program product, which includes a computer program, and the computer program is stored in a computer-readable storage medium. The processor of the computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the computer device executes the above-mentioned blockchain data processing method.

The embodiments of the present application include at least the following beneficial effects: when the target block is approved by the blockchain network consensus, the target block sent by the blockchain network is received, and the first transaction data associated with the target transaction is extracted from the target block. In a scenario where multiple different servers participate in the blockchain business system, different servers can synchronously obtain the transaction data of other servers in the blockchain, thereby realizing cross-server sharing of transaction data, and by extracting the target transaction identifier of the target transaction from the target block, accessing the cache service storing the first data pair, and obtaining the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. Since the first The data pair is constructed based on the transaction identifier and the transaction data. Therefore, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be on-chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers. On this basis, the target transaction data can be obtained according to the first transaction data and the second transaction data, and the target transaction data can be stored in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data that is not in the blockchain, thereby improving the integrity of the transaction data in the local database while improving the security of the transaction data.

Other features and advantages of the present application will be set forth in the following description, and in part will become apparent from the description, or may be understood by practicing the present application.

BRIEF DESCRIPTION OF THE DRAWINGS

The accompanying drawings are used to provide further understanding of the technical solution of the present application and constitute a part of the specification. Together with the embodiments of the present application, they are used to explain the technical solution of the present application and do not constitute a limitation on the technical solution of the present application.

FIG1 is a schematic diagram of an optional blockchain data processing architecture provided in an embodiment of the present application;

FIG2 is a schematic diagram of an optional implementation environment provided in an embodiment of the present application;

FIG3 is a schematic diagram of an optional internal architecture of a server provided in an embodiment of the present application;

FIG4 is a schematic diagram of an optional flow chart of a blockchain data processing method provided in an embodiment of the present application;

FIG5 is a schematic diagram of an optional process for determining second transaction data corresponding to a target transaction identifier according to an embodiment of the present application;

6 is a schematic diagram of the interaction process between the backend service and the cache service based on the second data pair provided in an embodiment of the present application;

FIG7 is a schematic diagram of an optional processing flow when the target database is unavailable provided in an embodiment of the present application;

FIG8 is a schematic diagram of an optional data interaction when multiple target servers share a cache service according to an embodiment of the present application;

FIG9 is a schematic diagram of an optional detailed processing flow of the detection service provided in an embodiment of the present application;

FIG10 is another optional flowchart of the blockchain data processing method provided in an embodiment of the present application;

FIG11 is a schematic diagram of an optional detailed processing flow of a backend service provided in an embodiment of the present application;

FIG12 is a schematic diagram of an optional interaction process between the detection service and the backend service provided in an embodiment of the present application;

FIG13 is a schematic diagram of an optional overall interaction flow of the blockchain data processing method provided in an embodiment of the present application;

FIG14 is another optional overall interaction flow diagram of the blockchain data processing method provided in an embodiment of the present application;

FIG15 is a schematic diagram of an optional structure of a first blockchain data processing device provided in an embodiment of the present application;

FIG16 is a schematic diagram of an optional structure of a second blockchain data processing device provided in an embodiment of the present application;

FIG17 is a partial structural block diagram of a terminal provided in an embodiment of the present application;

FIG18 is a partial structural block diagram of the server provided in an embodiment of the present application.

DETAILED DESCRIPTION

In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

It should be noted that in each specific embodiment of the present application, when it comes to the need to perform relevant processing based on data related to the characteristics of the target object such as target object attribute information or attribute information set, the permission or consent of the target object will be obtained first, and the collection, use and processing of these data will comply with the relevant laws, regulations and standards of the relevant countries and regions. Among them, the target object can be a user. In addition, when the embodiment of the present application needs to obtain the target object attribute information, the separate permission or separate consent of the target object will be obtained by means of a pop-up window or jumping to a confirmation page, and after the separate permission or separate consent of the target object is clearly obtained, the necessary target object-related data for enabling the normal operation of the embodiment of the present application will be obtained.

To facilitate understanding of the technical solutions provided in the embodiments of the present application, some key terms used in the embodiments of the present application are explained here:

Blockchain is a new application model of computer technologies such as distributed data storage, peer-to-peer transmission, consensus mechanism, and encryption algorithm. Blockchain is essentially a decentralized database, a string of data blocks generated by cryptographic methods. Each data block contains a batch of network transaction information, which is used to verify the validity of its information (anti-counterfeiting) and generate the next block. Blockchain can include the underlying blockchain platform, platform product service layer, and application service layer. The underlying blockchain platform can include processing modules such as user management, basic services, smart contracts, and operation detection. Among them, the user management module is responsible for the identity information management of all blockchain participants, including maintaining the generation of public and private keys (account management), key management, and the maintenance of the corresponding relationship between the user's real identity and the blockchain address (authority management), and, under authorization, supervises and audits the transactions of certain real identities and provides risk control rule configuration (risk control audit); the basic service module is deployed on all blockchain node devices to verify the validity of business requests and record the valid requests to the storage after consensus is reached. For a new business request, the basic service first adapts the interface to parse and authenticate (interface adaptation), and then encrypts the business information through the consensus algorithm (consensus management). The smart contract module is responsible for the registration and issuance of contracts, contract triggering and contract execution. Developers can define the contract logic in a programming language and publish it to the blockchain (contract registration). According to the logic of the contract terms, the key or other event trigger execution is called to complete the contract logic. At the same time, it also provides the function of contract upgrade and cancellation. The operation detection module is mainly responsible for the deployment, configuration modification, contract setting, cloud adaptation and real-time status visualization output of the product during the product release process, such as alarm, network status detection, node equipment health status detection, etc. The platform product service layer provides the basic capabilities and implementation framework of typical applications. Developers can complete the blockchain implementation of business logic based on these basic capabilities and superimpose business characteristics. The application service layer provides application services based on blockchain solutions for business participants to use.

Cloud technology is a general term for network technology, information technology, integration technology, management platform technology, application technology, etc. based on the cloud computing business model. It can form a resource pool, which can be used on demand and is flexible and convenient. Cloud computing technology will become an important support. The backend services of the technical network system require a large amount of computing and storage resources, such as video websites, picture websites and more portal websites. With the rapid development and application of the Internet industry, in the future, each item may have its own identification mark, which needs to be transmitted to the backend system for logical processing. Data of different levels will be processed separately. All kinds of industry data need strong system backing support, which can only be achieved through cloud computing.

Referring to Figure 1, Figure 1 is a schematic diagram of an optional blockchain data processing architecture provided in an embodiment of the present application. In a blockchain-based business system involving multiple parties, it includes a first business server and a second business server. The first business server and the second business server can be servers deployed in two different regions. The first business server and the second business server both run their own back-end services and local databases. The first business server corresponds to a first blockchain node in the blockchain network, the second business server corresponds to a first blockchain node in the blockchain network, and the second business server corresponds to a second blockchain node in the blockchain network. Accordingly, the first blockchain node and the second blockchain node are blockchain nodes in two different regions respectively.

Based on the architecture shown in Figure 1, terminal A initiates a transaction request to the backend service of the first business server, provides transaction information to the first business server, and the backend service of the first business server extracts key transaction information and uploads it to the chain;

The backend service sends the transaction request to the first blockchain node in a synchronous manner through the SDK (Software Development Kit) client. The synchronous method means that the SDK client will always wait for the execution result of the transaction synchronously.

After the first blockchain node and the second blockchain node reach a consensus on the execution of the transaction, the SDK client will synchronously obtain the execution result of the transaction and the transaction data returned after the transaction is executed, and store the transaction data in the local database.

Similarly, terminal B also initiates a request to the backend service of the second business server in a similar manner, and finally the second business server stores the transaction data in the local database of the second business server through the SDK client.

In the above architecture, the first business server and the second business server can only synchronize the transaction data of terminal A and terminal B respectively, and cannot realize cross-server data sharing. In addition, only some key transaction data can be synchronized from the blockchain network, resulting in incomplete transaction data synchronized from the local database. If all transaction data are stored on the blockchain, although the integrity of the transaction data synchronized from the blockchain can be improved, it will reduce the security of some transaction data that needs to be kept confidential.

Based on this, the embodiments of the present application provide a blockchain data processing method, device, electronic device and storage medium, which can simultaneously improve the integrity and security of transaction data in the local database.

The method provided in the embodiments of the present application can be applied to different technical fields, including but not limited to blockchain, cloud technology, payment and other technical fields.

Referring to FIG. 2 , FIG. 2 is a schematic diagram of an optional implementation environment provided in an embodiment of the present application, wherein the implementation environment includes a terminal 201 and a server 202 , wherein the terminal 201 and the server 202 are connected via a communication network.

Server 202 can be an independent physical server, or a server cluster or distributed system composed of multiple physical servers, or a cloud server that provides basic cloud computing services such as cloud services, cloud databases, cloud computing, cloud functions, cloud storage, network services, cloud communications, middleware services, domain name services, security services, CDN (Content Delivery Network), and big data and artificial intelligence platforms. In addition, server 202 can also be a node server in a blockchain network.

The terminal 201 may be a smart phone, a tablet computer, a laptop computer, a desktop computer, a smart speaker, a smart watch, a vehicle-mounted terminal, etc., but is not limited thereto. The terminal 201 and the server 202 may be directly or indirectly connected via wired or wireless communication, which is not limited in the present embodiment.

In a possible implementation, referring to FIG3 , FIG3 is a schematic diagram of an optional internal architecture of a server provided in an embodiment of the present application, wherein the server may be deployed with a backend service, a cache service, a detection service, and a target database, wherein the terminal may send a transaction request to the backend service, and the backend service may construct a target transaction and then asynchronously send a transaction request for the target transaction to the blockchain network, receive a target transaction identifier of the target transaction returned by the blockchain network, obtain second transaction data associated with the target transaction, construct a first data pair based on the target transaction identifier and the second transaction data, and store the first data pair in the cache service; when the target block corresponding to the target transaction is passed by the consensus of the blockchain network, the detection service receives the target block sent by the blockchain network, extracts the target transaction identifier of the target transaction and the first transaction data associated with the target transaction from the target block; accesses the cache service storing the first data pair, obtains the second transaction data associated with the target transaction from the first data pair of the cache service based on the target transaction identifier, obtains the target transaction data based on the first transaction data and the second transaction data, and stores the target transaction data in the target database.

When the target block is passed by the consensus of the blockchain network, the target block sent by the blockchain network is received, and the first transaction data associated with the target transaction is extracted from the target block. In the scenario where multiple different servers participate in the blockchain business system, different servers can synchronously obtain the transaction data of other servers in the blockchain, thereby realizing cross-server sharing of transaction data. In addition, by extracting the target transaction identifier of the target transaction from the target block, accessing the cache service storing the first data pair, and obtaining the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier, since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier even when the second transaction data does not need to be uploaded to the chain, thereby improving the security of transaction data in the scenario of cross-server sharing of transaction data. On this basis, the target transaction data can be obtained according to the first transaction data and the second transaction data, and the target transaction data can be stored in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data not in the blockchain, thereby improving the integrity of the transaction data in the local database on the basis of improving the security of the transaction data.

It can be understood that the back-end service, cache service, detection service and database shown in Figure 3 are all integrated into the same server. In addition, at least one of the back-end service, cache service, detection service and database can also be deployed in a discrete manner, which is not limited to the embodiments of the present application.

Based on the implementation environment shown in Figures 2 and 3, refer to Figure 4, which is an optional flow chart of the blockchain data processing method provided in an embodiment of the present application. At least a part of the process of the blockchain data processing method can be executed by the server, or by the terminal, or by the terminal and the server in cooperation. The blockchain data processing method includes but is not limited to the following steps 401 to 404.

Step 401: When the target block is approved by the blockchain network consensus, the target block sent by the blockchain network is received.

Among them, the target block is generated after the blockchain network receives the target transaction and packages the target transaction. The target block includes at least one target transaction, that is, the target block can be packaged by one or more target transactions. After the blockchain network generates the target block, the blockchain nodes in the blockchain network will reach a consensus on the target block. When the target block is passed by the blockchain network consensus, it indicates that the blockchain network recognizes the target transaction, and the target block will be stored on the blockchain, that is, the target block is "on-chained". After the target block is passed by the blockchain network consensus, the blockchain network will send the target block to the detection service, that is, the detection service will receive the target block sent by the blockchain network, where the sending action of the blockchain network can be for each new target block, that is, whenever a target block is passed by the blockchain network consensus, the blockchain network will send the target block to the detection service. In the scenario of the alliance chain, the target blocks generated by different blockchain nodes will be added to the blockchain. In other words, in addition to receiving the target block corresponding to its own server, the detection service can also receive the target blocks corresponding to other servers. Therefore, different servers can synchronously obtain the transaction data of other servers in the blockchain, thereby realizing cross-server sharing of transaction data.

In one possible implementation, when the target block is approved by the blockchain network consensus, the target block sent by the blockchain network is received. Specifically, a block subscription request can be generated according to a preset block number interval, and the block subscription request can be sent to the blockchain network. Whenever the target block within the block number interval is approved by the blockchain network consensus, the target block sent by the blockchain network in response to the block subscription request is received.

Among them, the block subscription request is used to subscribe to new block events from the blockchain network. The new block event is used to send the target block to the target object whenever a new target block is passed by consensus. The block number interval is used to indicate the detection range of the detection service, that is, the block numbers of the target blocks received by the detection service are all within the block number interval.

For example, the block number interval can be expressed as [startBlockNumber, endBlockNumber], where startBlockNumber represents the starting block number of the interval, and endBlockNumber represents the ending block number of the interval. In addition, endBlockNumber can be set to a negative value to instruct the detection service to continue detecting new target blocks.

By sending a block subscription request to the blockchain network, an automatic detection connection can be established between the detection service and the blockchain network, so that whenever a target block within the block number interval is approved by the blockchain network consensus, the detection service can automatically and continuously receive the new target block to avoid missing the target block. At the same time, the detection service does not need to frequently request the blockchain network to obtain new target blocks, which can improve the interaction efficiency between the detection service and the blockchain network.

Step 402: extracting a target transaction identifier of a target transaction and first transaction data associated with the target transaction from the target block.

Among them, the target transaction identifier is used to uniquely identify the target transaction, and the first transaction data is the transaction data stored on the blockchain. The first transaction data is the on-chain transaction data, which at least includes the data generated after the target transaction is executed. For example, taking account registration as an example, the first transaction data may include the information provided by the back-end service in the transaction request, such as account identifier, name, public key, etc. On this basis, the first transaction data may also include the on-chain address. The on-chain address is assigned to the corresponding account by the blockchain network after the target block is passed by consensus, that is, the on-chain address is the data generated after the target transaction is executed.

In one possible implementation, when the target block includes multiple target transactions, the detection service can traverse the multiple target transactions in the target block, parse each target transaction, and then extract the target transaction identifier of the target transaction and the first transaction data associated with the target transaction, so as not to miss any target transaction.

Step 403: access the cache service storing the first data pair, and obtain the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier.

Among them, the cache service is another service besides the detection service, which is mainly used to store the first data pair. In a possible implementation, the cache service can be implemented based on Redis (Remote Dictionary Server). The cache service based on Redis has the advantages of high throughput, high stability, etc.

In a possible implementation, the first data pair is constructed based on the transaction identifier and the transaction data, that is, the first data pair is used to store the association relationship between the transaction identifier and the transaction data, and the first data pair can be a key-value pair. Correspondingly, the key of the key-value pair can be constructed based on the transaction identifier, and the value of the key-value pair can be constructed based on the transaction data. Since the transaction data is managed by the backend service, the first data pair can be constructed by the backend service and stored in the cache service.

Among them, the transaction identifier in the first data pair is returned by the blockchain network after receiving the asynchronously sent transaction request. The transaction request is a request for initiating a target transaction. The transaction request can be sent asynchronously by the back-end service to the blockchain network. After receiving the transaction request, the blockchain network generates a target transaction identifier corresponding to the target transaction and returns it to the back-end service as a reply message of the transaction request. Therefore, the back-end service can obtain the target transaction identifier corresponding to the target transaction. In addition, since the detection service has established a connection with the blockchain network, after the back-end service sends the transaction request to the blockchain network, it does not need to wait for the transaction request to be packaged into the target block and the target block to be passed by consensus. It only needs to receive the target transaction identifier returned immediately by the blockchain network. In other words, the back-end service can send the transaction request to the blockchain network based on an asynchronous method. Compared with sending the transaction request to the blockchain network in a synchronous manner (i.e., waiting for the execution result of the transaction request after sending the transaction request to the blockchain network before performing subsequent actions), it can significantly improve the interaction efficiency between the back-end service and the blockchain network. Moreover, under this architecture, the back-end service does not need to receive the transaction result of the target transaction after the subsequent target block is passed by consensus, which is conducive to reducing the resource occupation of the back-end service.

In one possible implementation, the number of first data pairs can be multiple, and different first data pairs correspond to different transaction identifiers. Since the storage space of the cache service is limited, a corresponding effective time can be configured for each first data pair. When the time for which the first data pair is stored in the cache service reaches the effective time, the cache service can delete the first data pair to release the storage space of the cache service and prevent the cache service data from expanding. In addition, when the occupancy ratio of the storage space of the cache service reaches a preset ratio threshold, the first data pairs can be sorted according to the storage time from early to late or from late to early, and the first data pairs sorted before or after the preset ranking threshold can be deleted to release the storage space of the cache service and prevent the cache service data from expanding.

Among them, the second transaction data is transaction data that is not on the chain, and is generally stored locally, such as some transaction data that needs to be kept confidential (address, number of logins, etc.). After the detection service parses the target transaction identifier from the target block, it can match the target transaction identifier with the transaction identifier in each first data pair, and then determine the second transaction data corresponding to the target transaction identifier. For example, referring to Figure 5, Figure 5 is an optional flow chart for determining the second transaction data corresponding to the target transaction identifier provided in an embodiment of the present application. Assuming that three first data pairs are stored in the cache service, namely [TxId1, AAA], [TxId2, BBB] and [TxId3, CCC], when the target transaction identifier is TxId2, it can be determined that the corresponding second transaction data is BBB.

In a possible implementation, when the backend service constructs the key of the key-value pair based on the transaction identifier, prefix information may be added on the basis of the transaction identifier. The prefix information is used to construct the transaction identifier and different types of data into a data pair, and different prefix information may form different keys in the key-value pair with the transaction identifier. For example, when constructing the first data pair, "txid/req" may be added before the target transaction identifier TxId1. In this case, the first data pair may be [txid/req/TxId1, AAA], so that the first data pair used to obtain the second transaction data can be distinguished from other data pairs.

Since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be uploaded to the chain, thereby improving the security of the transaction data in the scenario of sharing transaction data across servers.

Step 404: Obtain target transaction data according to the first transaction data and the second transaction data, and store the target transaction data in a target database.

In a possible implementation manner, the target transaction data is obtained according to the first transaction data and the second transaction data. Specifically, the first transaction data and the second transaction data may be combined to obtain the target transaction data.

The target database may be a local database of the server. It is understandable that the local database of the server may be a database deployed in the server or a database that establishes a communication connection with the server.

The detection service obtains the target transaction data based on the first transaction data and the second transaction data, and stores the target transaction data in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data that is not in the blockchain, thereby improving the integrity of the transaction data in the local database.

It can be seen that the detection service receives the target block sent by the blockchain network when the target block is passed by the blockchain network consensus, and extracts the first transaction data associated with the target transaction from the target block. In the scenario where multiple different servers participate in the blockchain business system, different servers can synchronously obtain the transaction data of other servers in the blockchain, thereby realizing cross-server sharing of transaction data, and by extracting the target transaction identifier of the target transaction from the target block, accessing the cache service storing the first data pair, and obtaining the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. Since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier when the second transaction data does not need to be on-chained, thereby improving the security of transaction data in the scenario of cross-server sharing of transaction data. On this basis, the target transaction data can be obtained according to the first transaction data and the second transaction data, and the target transaction data can be stored in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data that is not in the blockchain, thereby improving the integrity of the transaction data in the local database on the basis of improving the security of the transaction data.

In a possible implementation, the detection service may further generate storage result information of the target transaction data, construct a second data pair based on the target transaction identifier and the storage result information, and store the second data pair in the cache service.

Among them, the storage result information is used to indicate that the target transaction data has been successfully stored in the target database or has not been successfully stored in the target database. The second data pair is constructed by the detection service based on the target transaction identifier and the storage result information. Similar to the structure of the first data pair, the second data pair can also be in the form of a key-value pair, with the target transaction identifier as the key of the key-value pair and the storage result information as the value of the key-value pair. Referring to the previous explanation, since the second data pair is also constructed based on the target transaction identifier, when constructing the key of the key-value pair based on the target transaction identifier, prefix information can also be added on the basis of the target transaction identifier. For example, when constructing the second data pair, "txid/resp" can be added before the target transaction identifier TxId1. At this time, the second data pair can be [txid/resp/TxId1, AAA], so that the second data pair can be distinguished from the first data pair.

In a possible implementation, the storage result information may include the storage result of the target transaction data and the target transaction data. In addition, the storage result information may also only include the storage result of the target transaction data.

For example, referring to FIG6, FIG6 is a schematic diagram of the interaction process between the backend service and the cache service provided by the embodiment of the present application based on the second data pair. Taking the target transaction as an example of account registration, if the target transaction data is not successfully stored in the target database, the storage result information can be {"error information": write failure; "account information": "null"}, at this time, "error information" is not null, "account information" (i.e., target transaction data) is null, indicating that the target transaction data is not successfully stored in the target database; if the target transaction data is successfully stored in the target database, the storage result information can be {"error information": null; "account information": "XXX"}, at this time, "error information" is null, "account information" is not null, indicating that the target transaction data is successfully stored in the target database. Then, "txid/resp/TxId1" can be used as the key of the key-value pair, and the detection service successfully stores the target transaction data in the target database as an example, then the second data pair can be [txid/resp/TxId1, {"error information": null; "account information": "XXX"}]. Next, the backend service can construct the key "txid/resp/TxId1" of the key-value pair based on the target transaction identifier returned by the blockchain network, and match the value of the key-value pair {"error message": empty; "account information": "XXX"} from the cache service.

The detection service constructs a second data pair based on the target transaction identifier and the storage result information, and stores the second data pair in the cache service, so that the backend service can obtain the storage result of the transaction data from the cache service, so that the backend service can perform subsequent processing, such as sending a notification message corresponding to the storage result. In addition, due to the introduction of the cache service, there is no need for synchronous communication between the detection service and the backend service, which improves the interaction efficiency between the detection service and the backend service.

In one possible implementation, the detection service can also determine the block number of the target block and the transaction sequence number of the current target transaction in the target block when the target transaction data has been successfully stored in the target database, record the block number and the transaction sequence number, load the block number and the transaction sequence number after restarting, and determine the next target transaction based on the block number and the transaction sequence number.

The block number is the number of the target block in the blockchain, and the transaction number is used to indicate the position order of the target transaction in the target block. For example, if the transaction number is 2, the target transaction is the second transaction in the target block. In the process of storing the target transaction data in the target database, the target database may be unavailable, resulting in the failure to successfully store the target transaction data in the target database. At this time, since the transaction data has been stored on the blockchain, there will be inconsistencies between the on-chain data and the local data. In an embodiment of the present application, when the target transaction data has been successfully stored in the target database, the block number of the target block and the transaction sequence number of the current target transaction in the target block are determined. For the next target transaction, if the target database crashes when the target transaction data corresponding to the next target transaction is stored in the target database, the detection service will not record the block number and transaction sequence number corresponding to the next target transaction. At this time, the detection service still records the block number and transaction sequence number corresponding to the previous target transaction. Therefore, the detection service can be restarted based on a preset frequency. After restarting, if the target database recovers normally, the detection service can load the block number and transaction sequence number corresponding to the previous target transaction, and retry processing from the block number and transaction sequence number corresponding to the previous target transaction until the target transaction data is successfully stored in the target database and the records of the block number and transaction sequence number are updated.

It can be seen that the above method can improve the consistency between the transaction data stored on the blockchain and the transaction data stored in the target database, and improve the reliability of the transaction data. In addition, by recording the block number and transaction sequence number, the detection service does not need to reprocess from the first target transaction of the first block, reducing redundant useless operations and significantly improving the efficiency of transaction data processing. In addition, the detection service restarts regularly and continuously tries to process from the block number and transaction sequence number corresponding to the previous target transaction. This process does not require manual intervention and can also effectively improve the efficiency of transaction data processing.

For example, referring to FIG. 7 , FIG. 7 is a schematic diagram of an optional processing flow when the target database provided in an embodiment of the present application is unavailable. Assuming that the block number of the current target block is 0, the target block includes two target transactions with transaction numbers 0 and 1, respectively. When the detection service receives the target block, it first processes the target transaction with transaction number 0, and stores the target transaction data corresponding to the target transaction with transaction number 0 in the target database. At this time, the detection service records the block number 0 and the transaction number 0; then processes the target transaction with transaction number 1. At this time, the target database crashes, and the detection service fails to successfully store the target transaction data corresponding to the target transaction with transaction number 0 in the target database. Therefore, the block number 0 and the transaction number 0 are not updated, but based on the prediction It restarts at the set frequency. After the target database returns to normal, it starts processing from the next target transaction with block number 0 and transaction sequence number 0, that is, it starts processing from the target transaction with block number 0 and transaction sequence number 1. After storing the target transaction data corresponding to the target transaction with transaction sequence number 1 in the target database, the detection service updates the originally recorded "block number 0 and transaction sequence number 0" to "block number 0 and transaction sequence number 1", and so on. If the target database also crashes when processing the next target transaction (for example, the target transaction with block number 1 and transaction sequence number 0), the target transaction data corresponding to the target transaction with block number 1 and transaction sequence number 0 can be successfully stored in the target database in the same way, thereby maintaining the consistency between the on-chain transaction data and the local transaction data.

In one possible implementation, if the transaction type of the target transaction is a chain configuration type, the detection service can extract the server attribute information of the target server and the server transaction certificate assigned to the target server by the blockchain network from the target block, and store the server attribute information and the server transaction certificate in the target database.

Among them, in the scenario of alliance chain, there will be multiple different business providers participating in the blockchain business system. Each business provider corresponds to a target server. The target server is the server configured for the target transaction. The target transaction configures the target server, that is, the blockchain node corresponding to the target server is added to the blockchain network. After the blockchain node corresponding to the target server is added to the blockchain network, a server transaction certificate and a server private key will be assigned to the target server. In addition, the blockchain node corresponding to the target server will package the server attribute information and the server transaction certificate into a target block, which will be stored in the blockchain after the consensus is passed.

Among them, the server attribute information is used to indicate the attributes of the server, such as UNI, APPID (application identification), etc. By extracting the server attribute information of the target server from the target block, and the server transaction certificate assigned to the target server by the blockchain network, and storing the server attribute information and the server transaction certificate in the target database, in the scenario where multiple different business providers participate in the blockchain business system, as long as a new target server joins, other servers can obtain the server attribute information and server transaction certificate of the newly joined target server, thereby achieving the sharing effect of server attribute information and server transaction certificate.

The server attribute information and the server transaction certificate may be stored in other data tables other than the data table corresponding to the target transaction data.

For example, the blockchain node corresponding to the target server of business provider G joins the blockchain network, and a server transaction certificate Cert-G and a server private key key-G are assigned to the target server. Subsequently, the server transaction certificate Cert-G and the UNI-G and APPI D-G of the target server are packaged into a target block of the chain configuration type. After the target block is passed by consensus, the detection service corresponding to the target server of business provider G receives the target block and stores UNI-G, APPI D-G and Cert-G in the target database. Similarly, after the blockchain node corresponding to the target server of business provider B joins the blockchain network, the detection service corresponding to the target server of business provider B can also extract UNI-B, APPI D-B and Cert-B from the corresponding target block and store them in the target database. At this time, the target database in the target server of business provider G stores its own business party data "UNI-G, APPI D-G and Cert-G", as well as the business party data "UNI-B, APPI D-B and Cert-B" of business provider B. Similarly, for the target server of business provider B, processing starts from the first target block in the blockchain, and the business party data "UNI-G, APPI D-G and Cert-G" of business provider G and its own business party data "UNI-B, APPI D-B and Cert-B" can also be stored in the target database. It can be seen that the business party data is shared between the target server of business provider G and the target server of business provider B.

When multiple different business providers participate in the blockchain business system, in one possible implementation, when obtaining the target transaction data based on the first transaction data and the second transaction data, the target transaction certificate used to sign the target transaction can be extracted from the target block, the target transaction certificate can be matched with the server transaction certificate, and the server attribute information corresponding to the target transaction can be obtained from the target database based on the matching result, and the first transaction data, the second transaction data, the server attribute information and the target transaction certificate can be merged into the target transaction data.

Among them, when initiating a transaction request for a target transaction, the backend service of the target server will use its own target transaction certificate to sign the transaction request and attach the target transaction certificate, so that the target transaction certificate can be extracted from the subsequent target block.

In addition, since the target database stores multiple different server attribute information and corresponding server transaction certificates, the server attribute information corresponding to the target transaction certificate can be determined based on the matching result between the target transaction certificate and the server transaction certificate, and the first transaction data, the second transaction data, the server attribute information and the target transaction certificate can be merged into the target transaction data. Therefore, the types of target transaction data can be expanded and the integrity of the target transaction data can be improved.

For example, if the first transaction data is "account identification, name, public key, on-chain address", the second transaction data is "address, number of logins", the server attribute information is "UNI-G, APPI D-G", and the target transaction certificate is "Cert-G", then the target transaction data is "account identification, name, public key, on-chain address, address, number of logins, UN I-G, APPI D-G, Cert-G".

When multiple different business providers participate in the blockchain business system, in one possible implementation, accessing the cache service storing the first data pair can specifically include extracting a target transaction certificate used to sign the target transaction from the target block, obtaining a server transaction certificate loaded at startup, and comparing the server transaction certificate loaded at startup with the target transaction certificate. When the comparison result is that the server transaction certificate loaded at startup is consistent with the target transaction certificate, accessing the cache service storing the first data pair.

Among them, when the detection service is started, the server transaction certificate of the target server where the detection service is located will be loaded. The server transaction certificate is the certificate assigned to the target server by the blockchain network after the blockchain node corresponding to the target server joins the blockchain network. Since the server transaction certificate is unique, that is, the server transaction certificates of different target servers are different, therefore, by comparing whether the server transaction certificate is consistent with the target transaction certificate, it can be determined whether the target transaction is initiated locally or remotely. When the target transaction certificate is consistent with the server transaction certificate, it indicates that the target transaction is initiated locally. When the target transaction certificate is inconsistent with the server transaction certificate, it indicates that the target transaction is initiated remotely.

In one possible implementation, in order to further improve the security of transaction data, the cache service can be deployed in each target server respectively. Accordingly, the cache service can only store the second transaction data corresponding to the current target server, that is, the local second transaction data. When the target transaction certificate is consistent with the server transaction certificate, it indicates that the target transaction is initiated locally. Therefore, the cache service can be accessed to successfully obtain the corresponding second transaction data; when the target transaction certificate is inconsistent with the server transaction certificate, it indicates that the target transaction is initiated remotely. Therefore, the corresponding second transaction data will not exist in the cache service. At this time, the detection service may not access the cache service, that is, when the comparison result is that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, the first transaction data can be directly used as the target transaction data, and the target transaction data can be stored in the target database, thereby reducing redundant interactions between the detection service and the cache service.

For example, following the previous example, the target database of the target server of the service provider G stores "UNI-G, APPI D-G and Cert-G" and "UNI-B, APPI D-B and Cert-B". If the target transaction certificate extracted by the detection service from the target block is "Cert-G", that is, the target transaction certificate is consistent with the server transaction certificate, it indicates that the target transaction is initiated by the back-end service of the target server of the service provider G, so that the cache service can be accessed to obtain the second transaction data, otherwise the cache service will not be accessed.

In addition, the cache service can also be shared by multiple target servers. In this case, when the back-end service stores the first data pair in the cache service, it can encrypt the second transaction data in the first data pair to obtain encrypted transaction data. At the same time, the back-end service in the target server that constructs the first data pair generates decryption information corresponding to the encrypted transaction data, and sends the decryption information corresponding to the encrypted transaction data to the detection service of each target server (including the target server where it is located). Therefore, when the comparison result is that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, the detection service can access the cache service, obtain the encrypted transaction data corresponding to the target transaction identifier from the cache service according to the first data pair, obtain the pre-stored decryption information, decrypt the encrypted transaction data according to the decryption information, obtain the second transaction data corresponding to the target transaction identifier, obtain the target transaction data based on the first transaction data and the second transaction data, and store the target transaction data in the target database.

Furthermore, the decryption information corresponding to the encrypted transaction data in different first data pairs is different, that is, the backend service will update the corresponding decryption information when constructing different first data pairs. At the same time, the backend service can select one or more other target servers to send decryption information. Only the detection service of the target server that receives the decryption information can successfully decrypt the second transaction data. The backend service that can receive the decryption information can be determined according to actual needs, and the embodiments of this application do not limit it.

In one possible implementation, the second transaction data in the first data pair can be encrypted using a commonly used encryption algorithm, such as a symmetric encryption algorithm, an asymmetric encryption algorithm, a hash algorithm, etc. Correspondingly, the decryption information can be a decryption key, which is not limited in the embodiments of the present application.

For example, referring to Figure 8, Figure 8 is an optional data interaction diagram when multiple target servers share a cache service provided in an embodiment of the present application. The target server of business provider G and the target server of business provider B share a cache service. The back-end service in the target server of business provider B encrypts the second transaction data when constructing the first data pair, and then stores it in the cache service, and sends the corresponding decryption information to the detection service of each target server. For the detection service in the target server of business provider B, after obtaining the encrypted first data pair from the cache service based on the target transaction identifier, the encrypted transaction data is decrypted based on the decryption information sent by the back-end service in the target server of business provider B, and then the second transaction data and the first transaction data obtained by decryption and restoration are stored in the target database in the target server of business provider B; similarly, for the detection service in the target server of business provider G, after obtaining the encrypted first data pair from the cache service based on the target transaction identifier, the encrypted transaction data is decrypted based on the decryption information sent by the back-end service in the target server of business provider B, and then the second transaction data and the first transaction data obtained by decryption and restoration are stored in the target database in the target server of business provider G.

By having multiple target servers share one cache service, the internal architecture of each target server can be simplified, and the first data pairs in the cache service are all encrypted. In the scenario where multiple target servers share one cache service, the security of transaction data can be effectively improved.

The following describes a detailed processing flow of the detection service in an embodiment of the present application, with reference to FIG. 9 , which is a schematic diagram of an optional detailed processing flow of the detection service provided in an embodiment of the present application, and may specifically include the following steps 901 to 907 .

Step 901: The detection service sends a block subscription request to the blockchain network. When the target block is approved by the blockchain network consensus, the detection service receives the target block sent by the blockchain network.

Among them, the block subscription request is used to subscribe to new block events from the blockchain network. The new block event is used to send the target block to the target object whenever a new target block is passed by consensus. The block number interval is used to indicate the detection range of the detection service, that is, the block numbers of the target blocks received by the detection service are all within the block number interval. By sending a block subscription request to the blockchain network, an automatic detection connection can be established between the detection service and the blockchain network, so that whenever a target block within the block number interval is passed by the blockchain network consensus, the detection service can automatically and continuously receive the new target block to avoid missing the target block. At the same time, the detection service does not need to frequently request the blockchain network to obtain new target blocks, which can improve the interaction efficiency between the detection service and the blockchain network.

Step 902: When the target transaction in the target block is a transaction of the chain configuration type, the detection service extracts the server attribute information of the target server and the server transaction certificate assigned to the target server by the blockchain network from the target block, and stores the server attribute information and the server transaction certificate in the target database;

Among them, the target transaction in the target block can be of multiple types. Therefore, after receiving the target block, the detection service will first determine the type of the target transaction in the target block. The detection service will perform different actions for different target transaction types. When the target transaction in the target block is a chain configuration type transaction, it indicates that the target block is used to adjust the blockchain configuration, for example, it can be a new blockchain node in the blockchain network. The server attribute information and server transaction certificate of the newly added blockchain node will be packaged into a block for consensus. Therefore, the detection service can extract the server attribute information and server transaction certificate of the target server from the target block. By extracting the server attribute information of the target server from the target block, as well as the server transaction certificate assigned to the target server by the blockchain network, and storing the server attribute information and server transaction certificate in the target database, in the scenario where multiple different business providers participate in the blockchain business system, as long as a new target server joins, other servers can obtain the server attribute information and server transaction certificate of the newly added target server, thereby achieving the sharing effect of server attribute information and server transaction certificate.

Step 903: When the target transaction in the target block is not a transaction of the chain configuration type, the detection service extracts the target transaction identifier of the target transaction and the first transaction data associated with the target transaction from the target block;

Among them, when the target transaction in the target block is not a transaction of the chain configuration type, it indicates that the target block is generated after the blockchain network receives the transaction request sent asynchronously by the backend service and packages the target transaction. The target transaction can be account registration, payment, etc. The target transaction identifier is generated by the blockchain network after receiving the transaction request, and is used to uniquely identify the target transaction. The first transaction data is the transaction data stored on the blockchain. The first transaction data is the on-chain transaction data, which at least includes the data generated after the target transaction is executed. Specifically, the first transaction data may include the transaction data that needs to be stored in the blockchain based on the transaction request, and the transaction data additionally generated by the blockchain network after the target transaction is executed. For example, taking the account registration request as an example, the transaction request carries the name, public key, address, and other attributes. The backend service can generate an account identifier based on the transaction request, and extract the transaction data that needs to be stored in the blockchain from the transaction request. In this example, it is the name and public key. At this time, the transaction data that needs to be stored in the blockchain is the account identifier, name, and public key. After the target transaction is executed, the blockchain network will assign an on-chain address to the account. At this time, the additional transaction data generated after the target transaction is executed is the on-chain address. Therefore, the first transaction data can include the account ID, name, public key and on-chain address.

When the target block includes multiple target transactions, the detection service can traverse the multiple target transactions in the target block, parse each target transaction, and then extract the target transaction identifier of the target transaction and the first transaction data associated with the target transaction, so as not to miss any target transaction.

Step 904: the detection service extracts the target transaction certificate used to sign the target transaction from the target block, obtains the server transaction certificate loaded at startup, and when the server transaction certificate loaded at startup is consistent with the target transaction certificate, accesses the cache service storing the first data pair, and obtains the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier;

Among them, when the back-end service initiates a transaction request for the target transaction, it will use its own target transaction certificate to sign the transaction request and attach the target transaction certificate. When the detection service is started, it will load the server transaction certificate of the target server where the detection service is located. The server transaction certificate is the certificate assigned to the target server by the blockchain network after the blockchain node corresponding to the target server joins the blockchain network. Since the server transaction certificate is unique, that is, the server transaction certificates of different target servers are different, therefore, by comparing whether the server transaction certificate is consistent with the target transaction certificate, it can be determined whether the target transaction is initiated locally or remotely.

When the target transaction certificate is consistent with the server transaction certificate, it indicates that the target transaction is initiated locally. Referring again to the example shown in Figure 5, the detection service can access the cache service that stores the first data pair, and obtain the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. Since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be uploaded to the chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers.

Step 905: The detection service combines the first transaction data, the second transaction data, the server attribute information and the target transaction certificate into target transaction data, and stores the target transaction data in the target database;

Among them, by obtaining the target transaction data according to the first transaction data and the second transaction data, the target transaction data is stored in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data not in the blockchain, thereby improving the integrity of the transaction data in the local database on the basis of improving the security of the transaction data. On this basis, further introducing server attribute information and target transaction certificates as target transaction data can expand the types of target transaction data and improve the integrity of the target transaction data.

Step 906: The detection service generates storage result information of the target transaction data, constructs a second data pair based on the target transaction identifier and the storage result information, stores the second data pair in the cache service, determines the block number of the target block and the transaction sequence number of the current target transaction in the target block, and records the block number and the transaction sequence number;

Here, referring again to the example described in FIG. 6 , the second data pair is stored in the cache service so that the backend service obtains the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, generates a first notification message indicating the transaction result of the target transaction according to the storage result information, and sends the first notification message to the account that initiated the target transaction. The backend service can specifically obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier based on a preset time interval, and when the storage result information is obtained, generates a first notification message indicating the transaction result of the target transaction according to the storage result information, thereby achieving the effect of conveniently notifying the account that initiated the target transaction and improving the efficiency of human-computer interaction.

Step 907: When the next target transaction data is not successfully stored in the target database, the detection service restarts based on the preset frequency. After restarting, the recorded block number and transaction sequence number are loaded, and the next target transaction is determined based on the block number and transaction sequence number until the transaction data in all target blocks in the blockchain network are stored.

Among them, referring to the example shown in Figure 7 again, when the detection service stores the target transaction data in the target database, it will determine whether the target transaction data can be successfully stored in the target database. If the current target transaction data is successfully stored in the target database, the block number and transaction sequence number corresponding to the current target transaction data will be recorded, and then the next target transaction data will be processed. When the next target transaction data is not successfully stored in the target database, after the detection service is restarted, it does not know which target transaction is processed. At this time, the block number and transaction sequence number recorded previously can be reloaded to determine the next target transaction. There is no need to reprocess from the first target transaction of the first block, which reduces redundant useless operations, significantly improves the processing efficiency of transaction data, and can improve the consistency between the transaction data stored on the blockchain and the transaction data stored in the target database. In addition, the detection service restarts regularly and continuously tries to process from the block number and transaction sequence number corresponding to the previous target transaction. This process does not require manual intervention and can also effectively improve the processing efficiency of transaction data.

In the above steps 901 to 907, by introducing a cache service, even when the second transaction data does not need to be put on the chain, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier, thereby improving the security of transaction data in the scenario of cross-server sharing of transaction data. On this basis, the target transaction data can be obtained according to the first transaction data, the second transaction data, the server attribute information and the target transaction certificate, and the target transaction data is stored in the target database, so that relatively complete transaction data can be stored in the target database. In addition, by recording the block number of the target block and the transaction sequence number of the current target transaction in the target block when the target transaction data has been successfully stored in the target database, the breakpoint resumption of transaction data processing can be achieved, and the consistency of transaction data on and off the chain can be improved. Therefore, interoperability, integrity, security and consistency when storing transaction data can be achieved at the same time.

In addition, referring to Figure 10, Figure 10 is another optional flow chart of the blockchain data processing method provided in an embodiment of the present application. At least a part of the process of the blockchain data processing method can be executed by the server, or by the terminal, or by the terminal and the server in cooperation. The blockchain data processing method includes but is not limited to the following steps 1001 to 1003.

Step 1001: asynchronously send a transaction request for a target transaction to the blockchain network, and receive a target transaction identifier of the target transaction returned by the blockchain network.

In a possible implementation, the backend service can receive a transaction request from a terminal, and then generate a transaction request for the target transaction based on the transaction request from the terminal. For example, taking account registration as an example, the terminal can apply to the backend service to register an on-chain account, and provide the backend service with information such as name and address. The backend service can generate a unique account ID for the terminal. At this time, the data that needs to be stored in the blockchain is the name, account ID, public key, etc., and the data that is not stored in the blockchain is the address. Then the backend service will use the SDK client to construct the metadata of the target transaction based on the name, account ID, public key, etc., and after signing with the private key of the target server, generate a transaction request for the target transaction and send it to the blockchain network.

Among them, the backend service sends the transaction request of the target transaction to the blockchain network in an asynchronous manner, which means that the SDK client will not wait for the execution result of the target transaction, but will immediately proceed to the next step after receiving the target transaction identifier returned by the blockchain network. Compared with sending transaction requests to the blockchain network in a synchronous manner (i.e., waiting for the execution result of the transaction request after sending the transaction request to the blockchain network before taking subsequent actions), it can significantly improve the interaction efficiency between the backend service and the blockchain network. Moreover, under this architecture, the backend service does not need to receive the transaction result of the target transaction after the subsequent target block is passed by consensus, which is conducive to reducing the resource usage of the backend service.

Step 1002: Acquire second transaction data associated with the target transaction, and construct a first data pair according to the target transaction identifier and the second transaction data;

Among them, after receiving the target transaction identifier returned by the blockchain network, the backend service can construct a first data pair based on the target transaction identifier and the data sent by the terminal that is not stored in the blockchain (i.e., the second transaction data). The first data pair is used to store the association relationship between the transaction identifier and the transaction data. The first data pair can be a key-value pair. Correspondingly, the key of the key-value pair can be constructed based on the transaction identifier, and the value of the key-value pair can be constructed based on the transaction data. Since the transaction data is managed by the backend service, the first data pair can be constructed by the backend service and stored in the cache service.

Step 1003: The first data pair is stored in the cache service so that when the target block corresponding to the target transaction is approved by the blockchain network consensus, the detection service extracts the target transaction identifier and the first transaction data associated with the target transaction from the target block, accesses the cache service, obtains the second transaction data from the first data pair of the cache service according to the target transaction identifier, obtains the target transaction data according to the first transaction data and the second transaction data, and stores the target transaction data in the target database.

Among them, the back-end service stores the first data pair in the cache service, so that when the target block is passed by the blockchain network consensus, the detection service can receive the target block sent by the blockchain network, and extract the first transaction data associated with the target transaction from the target block. In the scenario where multiple different servers participate in the blockchain business system, different servers can synchronously obtain the transaction data of other servers in the blockchain, thereby realizing cross-server sharing of transaction data, and by extracting the target transaction identifier of the target transaction from the target block, accessing the cache service storing the first data pair, and obtaining the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. Since the first The data pair is constructed based on the transaction identifier and the transaction data. Therefore, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be on-chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers. On this basis, the target transaction data can be obtained according to the first transaction data and the second transaction data, and the target transaction data can be stored in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data that is not in the blockchain, thereby improving the integrity of the transaction data in the local database while improving the security of the transaction data.

Referring to the previous explanation, since the cache service can also store a second data pair constructed by a transaction identifier and storage result information, the back-end service can also obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, generate a first notification message indicating the transaction result of the target transaction according to the storage result information, and send the first notification message to the account that initiated the target transaction.

For example, the second data pair may be [txid/resp/TxId1, {"error information": empty; "account information": "XXX"}], if the target transaction identifier returned by the blockchain network is TxI d1, the backend service may construct the key "txid/resp/TxId1" of the key-value pair based on the target transaction identifier, match the storage result information {"error information": empty; "account information": "XXX"} from the cache service, and then generate the first notification message according to the storage result information. In this example, the account identifier may be obtained from the account information, and the first notification message of successful registration may be generated based on the account identifier and returned to the terminal, for example, the generated first notification message may be "registration successful, account identifier is XX". If the storage result information {"error information": write failure; "account information": "empty"} is matched from the cache service, the generated first notification message may be "registration failed".

In one possible implementation, when the back-end service obtains the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, it can specifically continue to obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier based on a preset time interval, and when the storage result information is obtained, generate a first notification message indicating the transaction result of the target transaction according to the storage result information.

Among them, the preset time interval is used to indicate the frequency of the backend service accessing the cache service. The preset time interval can be set according to actual needs, for example, it can be 50 milliseconds, 60 milliseconds, etc., which is not limited in the embodiment of the present application. The backend service obtains the storage result information by continuously accessing the cache service, and there is no need for synchronous communication between the detection service and the backend service, thereby improving the interaction efficiency between the detection service and the backend service.

When the duration of requesting to store the result information exceeds a preset duration threshold, the backend service may generate a second notification message indicating a timeout, and send the second notification message to the account that initiated the target transaction.

Among them, the duration threshold can be set according to actual needs, for example, it can be 1 second, 1.1 seconds, etc., and the embodiments of the present application are not limited. Exemplarily, the second notification message can be "access timeout", "processing timeout", etc. When the duration of the request to store the result information exceeds the preset duration threshold, the back-end service can notify the account that initiated the target transaction through the second notification message to improve the efficiency of human-computer interaction. At the same time, the back-end service can stop accessing the cache service to obtain the storage result information corresponding to the target transaction identifier, and then process the next target transaction identifier to release the processing resources of the back-end service.

In one possible implementation, when multiple target servers share a cache service, when the back-end service constructs a first data pair based on the target transaction identifier and the second transaction data, it can specifically encrypt the second transaction data to obtain encrypted transaction data, send the decryption information corresponding to the encrypted transaction data to the detection service, and construct the first data pair based on the target transaction identifier and the encrypted transaction data.

After receiving the target transaction identifier of the target transaction returned by the blockchain network, the backend service can encrypt the second transaction data in the target transaction to obtain the encrypted transaction data, construct the first data pair according to the target transaction identifier and the encrypted transaction data, and store it in the cache service. In addition, the backend service sends the decryption information corresponding to the encrypted transaction data to the detection service of each target server (including the target server where the backend service is located), so that the detection service of each target server can use the decryption information to decrypt and restore the second transaction data after obtaining the encrypted transaction data from the cache service, thereby effectively improving the security of the transaction data.

The following describes the detailed processing flow of the backend service in an embodiment of the present application, with reference to FIG11 . FIG11 is a schematic diagram of an optional detailed processing flow of the backend service provided in an embodiment of the present application, which may specifically include the following steps 1101 to 1105 .

Step 1101: The backend service receives the transaction request sent by the terminal, generates a transaction request for the target transaction, and sends the transaction request for the target transaction to the blockchain network in an asynchronous manner;

Among them, the transaction request sent by the terminal can be an account registration request, a payment request, etc. Since the detection service has established a connection with the blockchain network, after the back-end service sends the transaction request to the blockchain network, it does not need to wait for the transaction request to be packaged into the target block and the target block to be passed by consensus. It only needs to receive the target transaction identifier returned immediately by the blockchain network. In other words, the back-end service can send a transaction request to the blockchain network based on an asynchronous method. Compared with sending a transaction request to the blockchain network in a synchronous manner (i.e., after sending a transaction request to the blockchain network, waiting for the execution result of the transaction request before performing subsequent actions), it can significantly improve the interaction efficiency between the back-end service and the blockchain network. Moreover, under this architecture, the back-end service does not need to receive the transaction result of the target transaction after the subsequent target block is passed by consensus, which is conducive to reducing the resource occupation of the back-end service.

Step 1102: The backend service receives the target transaction identifier of the target transaction returned by the blockchain network based on the transaction request, obtains the second transaction data that is not stored in the blockchain, constructs a first data pair according to the target transaction identifier and the second transaction data, and stores the first data pair in the cache service;

Among them, the second transaction data not stored in the blockchain can be stored in the backend service. For example, when the backend service receives the account registration request sent by the terminal, it can extract the second transaction data from the account registration request for caching. If the account registration request carries the name, public key, address, and other attributes, the second transaction data can be the address and other attributes. The backend service constructs a first data pair based on the target transaction identifier and the second transaction data, and stores the first data pair in the cache service. Since the backend service will use its own target transaction certificate to sign the transaction request when initiating the transaction request of the target transaction, and attach the target transaction certificate, the detection service can load the server transaction certificate of the target server where the detection service is located at startup, and determine whether the target transaction is initiated locally or remotely by comparing whether the server transaction certificate is consistent with the target transaction certificate. When the target transaction certificate is consistent with the server transaction certificate, it indicates that the target transaction is initiated locally. Referring again to the example shown in Figure 5, the detection service can access the cache service that stores the first data pair, and obtain the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. Since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be uploaded to the chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers.

Step 1103: the backend service continuously obtains storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier based on a preset time interval;

Among them, referring to Figure 6 again, after the backend service stores the first data pair in the cache service, the detection service will generate storage result information of the target transaction data after successfully storing the target transaction data in the target database, and construct a second data pair based on the target transaction identifier and the storage result information, and store the second data pair in the cache service. At this time, the backend service can obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier without directly communicating with the backend service.

Step 1104: when the backend service obtains the storage result information, it generates a first notification message indicating the transaction result of the target transaction according to the storage result information, and sends the first notification message to the terminal;

Specifically, the back-end service can continuously obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier based on a preset time interval; when the storage result information is obtained, a first notification message indicating the transaction result of the target transaction is generated according to the storage result information, thereby achieving the effect of conveniently notifying the account that initiated the target transaction and improving the efficiency of human-computer interaction.

Step 1105: When the duration of the backend service request to store the result information exceeds a preset duration threshold, a second notification message indicating a timeout is generated, and the second notification message is sent to the account that initiated the target transaction.

Among them, when the duration of the backend service requesting the storage result information exceeds the preset duration threshold, it indicates that the target transaction data may not be successfully stored, and the backend service can stop accessing the cache service to obtain the storage result information corresponding to the target transaction identifier, and then process the next target transaction identifier to release the processing resources of the backend service. In addition, since the terminal is informed of this situation through the second notification message, it can also perform operations such as retrying the transaction request to improve the reliability of the transaction.

In the above steps 1101 to 1105, by introducing a cache service, it is possible to obtain the second transaction data associated with the target transaction according to the target transaction identifier even when the second transaction data does not need to be uploaded to the chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers. On this basis, it is convenient for the detection service to obtain the target transaction data according to the first transaction data, the second transaction data, the server attribute information and the target transaction certificate, and store the target transaction data in the target database, so that relatively complete transaction data can be stored in the target database.

The following describes the interaction process between the detection service and the backend service in an embodiment of the present application, with reference to FIG12 . FIG12 is a schematic diagram of an optional interaction process between the detection service and the backend service provided in an embodiment of the present application, which may specifically include the following steps 1201 to 1209 .

Step 1201: The detection service sends a block subscription request to the blockchain network;

Among them, the block subscription request is used to subscribe to new block events from the blockchain network. The new block event is used to send the target block to the target object whenever a new target block is passed by consensus. The block number interval is used to indicate the detection range of the detection service, that is, the block numbers of the target blocks received by the detection service are all within the block number interval. By sending a block subscription request to the blockchain network, an automatic detection connection can be established between the detection service and the blockchain network, so that whenever a target block within the block number interval is passed by the blockchain network consensus, the detection service can automatically and continuously receive the new target block to avoid missing the target block. At the same time, the detection service does not need to frequently request the blockchain network to obtain new target blocks, which can improve the interaction efficiency between the detection service and the blockchain network.

Step 1202: When the target block of the chain configuration type is passed by the blockchain network consensus, the detection service receives the target block sent by the blockchain network, extracts the server attribute information of the target server and the server transaction certificate assigned by the blockchain network to the target server from the target block, and stores the server attribute information and the server transaction certificate in the target database;

Among them, since the detection service continuously subscribes to the target block from the blockchain network, the detection service can also receive the target block containing the chain configuration type. Of course, there can be multiple types of target transactions in the same target block. Therefore, in step 1202, it can also be that when the target block containing the target transaction of the chain configuration type is passed by the blockchain network consensus, the detection service will first determine the type of target transaction in the target block after receiving the target block. The detection service will perform different actions for different target transaction types. When the target transaction in the target block is a transaction of the chain configuration type, it indicates that the target block is used to adjust the blockchain configuration, for example, it can be to add a new blockchain node in the blockchain network. The server attribute information and server transaction certificate of the newly added blockchain node will be packaged into a block for consensus. Therefore, the detection service can extract the server attribute information and server transaction certificate of the target server from the target block. By extracting the server attribute information of the target server and the server transaction certificate assigned to the target server by the blockchain network from the target block, and storing the server attribute information and the server transaction certificate in the target database, in the scenario where multiple different business providers participate in the blockchain business system, as long as a new target server joins, other servers can obtain the server attribute information and server transaction certificate of the newly joined target server, thereby achieving the sharing effect of server attribute information and server transaction certificate.

Step 1203: The backend service generates a transaction request for the target transaction in response to the transaction request sent by the terminal, and sends the transaction request for the target transaction to the blockchain network in an asynchronous manner;

Among them, the transaction request sent by the terminal can be an account registration request, a payment request, etc. Since the detection service has established a connection with the blockchain network, after the back-end service sends the transaction request to the blockchain network, it does not need to wait for the transaction request to be packaged into the target block and the target block to be passed by consensus. It only needs to receive the target transaction identifier returned immediately by the blockchain network. In other words, the back-end service can send a transaction request to the blockchain network based on an asynchronous method. Compared with sending a transaction request to the blockchain network in a synchronous manner (i.e., after sending a transaction request to the blockchain network, waiting for the execution result of the transaction request before performing subsequent actions), it can significantly improve the interaction efficiency between the back-end service and the blockchain network. Moreover, under this architecture, the back-end service does not need to receive the transaction result of the target transaction after the subsequent target block is passed by consensus, which is conducive to reducing the resource occupation of the back-end service.

Step 1204: The backend service receives the target transaction identifier of the target transaction returned by the blockchain network based on the transaction request, obtains the second transaction data that is not stored in the blockchain, constructs a first data pair according to the target transaction identifier and the second transaction data, stores the first data pair in the cache service, and continuously obtains the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier based on a preset time interval;

Among them, the second transaction data not stored in the blockchain can be stored in the backend service. For example, when the backend service receives the account registration request sent by the terminal, it can extract the second transaction data from the account registration request for caching. If the account registration request carries the name, public key, address, and other attributes, the second transaction data can be the address and other attributes. The backend service constructs a first data pair based on the target transaction identifier and the second transaction data, and stores the first data pair in the cache service. Since the backend service will use its own target transaction certificate to sign the transaction request when initiating the transaction request of the target transaction, and attach the target transaction certificate, the detection service can load the server transaction certificate of the target server where the detection service is located at startup, and determine whether the target transaction is initiated locally or remotely by comparing whether the server transaction certificate is consistent with the target transaction certificate. When the target transaction certificate is consistent with the server transaction certificate, it indicates that the target transaction is initiated locally. Referring again to the example shown in Figure 5, the detection service can access the cache service that stores the first data pair, and obtain the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. Since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be uploaded to the chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers.

Referring to Figure 6 again, after the backend service stores the first data pair in the cache service, the detection service will generate storage result information of the target transaction data after successfully storing the target transaction data in the target database, construct a second data pair based on the target transaction identifier and the storage result information, and store the second data pair in the cache service. At this time, the backend service can obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier without directly communicating with the backend service.

Step 1205: When the target block corresponding to the target transaction is approved by the blockchain network consensus, the detection service receives the target block sent by the blockchain network, and the detection service extracts the target transaction identifier of the target transaction and the first transaction data associated with the target transaction from the target block;

Among them, in step 1205, the target transaction is not a transaction of the chain configuration type, indicating that the target block is generated after the blockchain network receives the transaction request sent asynchronously by the backend service and packages the target transaction. The target transaction can be account registration, payment, etc. The target transaction identifier is generated by the blockchain network after receiving the transaction request, and is used to uniquely identify the target transaction. The first transaction data is the transaction data stored on the blockchain. The first transaction data is the on-chain transaction data, which at least includes the data generated after the target transaction is executed. Specifically, the first transaction data may include the transaction data that needs to be stored in the blockchain based on the transaction request, and the transaction data additionally generated by the blockchain network after the target transaction is executed. For example, taking the account registration request as an example, the transaction request carries the name, public key, address, and other attributes. The backend service can generate an account identifier based on the transaction request, and extract the transaction data that needs to be stored in the blockchain from the transaction request. In this example, it is the name and public key. At this time, the transaction data that needs to be stored in the blockchain is the account identifier, name, and public key. After the target transaction is executed, the blockchain network will assign an on-chain address to the account. At this time, the additional transaction data generated after the target transaction is executed is the on-chain address. Therefore, the first transaction data can include the account ID, name, public key and on-chain address.

When the target block includes multiple target transactions, the detection service can traverse the multiple target transactions in the target block, parse each target transaction, and then extract the target transaction identifier of the target transaction and the first transaction data associated with the target transaction, so as not to miss any target transaction.

Step 1206: the detection service extracts the target transaction certificate used to sign the target transaction from the target block, obtains the server transaction certificate loaded at startup, and when the server transaction certificate loaded at startup is consistent with the target transaction certificate, accesses the cache service storing the first data pair, and obtains the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier;

Among them, when the back-end service initiates a transaction request for the target transaction, it will use its own target transaction certificate to sign the transaction request and attach the target transaction certificate. When the detection service is started, it will load the server transaction certificate of the target server where the detection service is located. The server transaction certificate is the certificate assigned to the target server by the blockchain network after the blockchain node corresponding to the target server joins the blockchain network. Since the server transaction certificate is unique, that is, the server transaction certificates of different target servers are different, therefore, by comparing whether the server transaction certificate is consistent with the target transaction certificate, it can be determined whether the target transaction is initiated locally or remotely.

When the target transaction certificate is consistent with the server transaction certificate, it indicates that the target transaction is initiated locally. Referring again to the example shown in Figure 5, the detection service can access the cache service that stores the first data pair, and obtain the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. Since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be uploaded to the chain, thereby improving the security of transaction data in the scenario of sharing transaction data across servers.

Step 1207: The detection service combines the first transaction data, the second transaction data, the server attribute information and the target transaction certificate into target transaction data, and stores the target transaction data in the target database;

Among them, by obtaining the target transaction data according to the first transaction data and the second transaction data, the target transaction data is stored in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data not in the blockchain, thereby improving the integrity of the transaction data in the local database on the basis of improving the security of the transaction data. On this basis, further introducing server attribute information and target transaction certificates as target transaction data can expand the types of target transaction data and improve the integrity of the target transaction data.

Step 1208: When the target transaction data is not successfully stored in the target database, the detection service loads the block number and transaction sequence number corresponding to the previous target transaction, and tries to process again from the block number and transaction sequence number corresponding to the previous target transaction until the target transaction data is successfully stored in the target database, updates the record of the block number and transaction sequence number, generates storage result information of the target transaction data, constructs a second data pair based on the target transaction identifier and the storage result information, and stores the second data pair in the cache service;

Among them, similar to the principle of step 907, referring to the example shown in Figure 7 again, when the detection service stores the target transaction data in the target database, it will determine whether the target transaction data can be successfully stored in the target database. If the current target transaction data is successfully stored in the target database, the block number and transaction sequence number corresponding to the current target transaction data will be recorded, and then the next target transaction data will be processed. Therefore, if the current target transaction data is not successfully stored in the target database, after the detection service is restarted, it is not known which target transaction is processed at this time. At this time, the block number and transaction sequence number of the previous target transaction record can be reloaded to determine the current target transaction. There is no need to reprocess from the first target transaction of the first block, which reduces redundant useless operations, significantly improves the processing efficiency of transaction data, and can improve the consistency between the transaction data stored on the blockchain and the transaction data stored in the target database. In addition, the detection service restarts regularly and continuously tries to process from the block number and transaction sequence number corresponding to the previous target transaction. This process does not require manual intervention and can also effectively improve the processing efficiency of transaction data.

Here, referring again to the example described in FIG. 6 , the second data pair is stored in the cache service so that the backend service obtains the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, generates a first notification message indicating the transaction result of the target transaction according to the storage result information, and sends the first notification message to the account that initiated the target transaction. The backend service can specifically obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier based on a preset time interval, and when the storage result information is obtained, generates a first notification message indicating the transaction result of the target transaction according to the storage result information, thereby achieving the effect of conveniently notifying the account that initiated the target transaction and improving the efficiency of human-computer interaction.

Step 1209: the backend service obtains the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, generates a first notification message indicating the transaction result of the target transaction according to the storage result information, and sends the first notification message to the terminal.

Specifically, the back-end service can continuously obtain the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier based on a preset time interval; when the storage result information is obtained, a first notification message indicating the transaction result of the target transaction is generated according to the storage result information, thereby achieving the effect of conveniently notifying the account that initiated the target transaction and improving the efficiency of human-computer interaction.

In the above steps 1201 to 1209, by introducing a cache service, even when the second transaction data does not need to be put on the chain, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier, thereby improving the security of transaction data in the scenario of cross-server sharing of transaction data. On this basis, the target transaction data can be obtained according to the first transaction data, the second transaction data, the server attribute information and the target transaction certificate, and the target transaction data is stored in the target database, so that relatively complete transaction data can be stored in the target database. In addition, by recording the block number of the target block and the transaction sequence number of the current target transaction in the target block when the target transaction data has been successfully stored in the target database, the breakpoint resumption of transaction data processing can be achieved, and the consistency of transaction data on and off the chain can be improved. Therefore, interoperability, integrity, security and consistency when storing transaction data can be achieved at the same time.

The following uses account registration as an example to illustrate the principle of the blockchain data processing method provided in the embodiment of the present application.

Referring to FIG. 13 , FIG. 13 is a schematic diagram of an optional overall interaction flow of the blockchain data processing method provided in an embodiment of the present application. In this example, the target server of business provider B (corresponding to region B) and the target server of business provider G (corresponding to region G) are both deployed with backend services, detection services, target databases, and cache services. When the target servers of business provider B and business provider G are added to the network, all services will be started, and the detector starts detection with block 0 and transaction 0:

(1) Joining the blockchain network and allocating certificates: Assuming that the target server of service provider G joins the blockchain network, the blockchain network will allocate a certificate Cert-G and a private key Key-G (for subsequent signature initiation transactions) to the target server of service provider G, and at the same time upload Cert-G and the UNI-G and APPID-G of the target server of service provider G to the blockchain; similarly, when the target server of service provider B joins the blockchain network, it will also be allocated a certificate Cert-B, and the Cert-B, UNI-B, and APPID-B of the target server of service provider B will also be uploaded to the blockchain in a similar manner. After [UNI-G, APPID-G, Cert-G] is uploaded to the chain (that is, the corresponding target block is approved by consensus), the detection service in the target server of business provider G can obtain the corresponding target block through the new block event subscription of the blockchain network, and obtain [UNI-G, APPID-G, Cert-G] in the corresponding transaction and write it to the data table Table _cert of the local target database. Similarly, the detection service in the target server of business provider G can also write [UNI-B, APPID-B, Cert-B] to the data table Table _cert of the local target database. The detection service in the target server of business provider B starts when the target server of business provider B joins the network, and starts detection with (block 0 and transaction 0) as the mark. It can also detect the above transactions, so it will also insert [UNI-G, APPID-G, Cert-G] and [UNI-B, APPID-B, Cert-B] into the data table Table _cert of the local target database. So far, the data table Table _cert of the local target database of the target server of business provider B and the target server of business provider G both have complete business party information:

[UNI-G, APPID-G, Certificate G]

[UNI-B, APPID-B, Certificate B]

At the same time, as long as a new service provider's target server is added, the detection service in the target server of each service provider in the current network can detect this type of chain configuration transaction and update the service provider information to the data table Table _cert of the local target database.

(2) Terminal initiates request: Terminal UE1 initiates an account registration request to the backend service in the target server of service provider G, applying to register an on-chain account. The information provided includes (name, public key, address, other attributes, etc.). The backend service will first use a certain strategy to generate a unique account identifier, and then extract some key or important attributes such as name and public key from the information provided by terminal UE1, and upload the account identifier, name and public key to the chain.

(3) The backend service asynchronously initiates a transaction request: The backend service in the target server of the service provider G uses the certificate Cert-G stored locally on the target server of the service provider G and the private key Key-G assigned by the blockchain network, and uses the corresponding SDK client to construct the transaction metadata using the account ID, name, and public key, then signs it with the private key Key-G, and finally attaches the certificate Cert-G to generate a transaction request for the target transaction. The transaction request is sent asynchronously to the blockchain node corresponding to the service provider G. The asynchronous method means that the SDK client will not wait for the execution result of the target transaction, but will receive the target transaction identifier TxId returned by the blockchain node.

It can be understood that if the terminal UE2 initiates a request to the backend service in the target server of the service provider B, when constructing the transaction request, the certificate Cert-B stored locally in the target server of the service provider B and the private key Key-B assigned by the blockchain network are used.

(4) The backend service sets the key-value pair to the cache service and waits: After the backend service in the target server of the service provider G obtains the TxId from the SDK client, it constructs the information that is not on the chain into a JSON string as the context of this transaction request, as shown below:

Context＝{"address":"address","other":"other attributes"}

After that, insert it into the cache service with "txid/req/TxId" as the complete Key and Context as the Value. For example, you can use the Set interface provided by the cache service. To prevent the cache service data from expanding, the data validity period can be set to 1 hour or shorter, that is:

Set(txid/req/TxId,Context,1hour)

After that, the backend service will enter the waiting stage, waiting for the notification of the detection service; the backend service will continue to call the Get interface of the cache service with "txid/resp/TxId" as the completion key, obtain the corresponding Value, and obtain the return value Resp placed in the cache service by the detection service;

Resp＝Get(txid/resp/TxId)

The backend service will obtain the value of the corresponding key from the cache service at a certain time interval (for example, 50 milliseconds) until it is obtained or the set time threshold (for example, 1 second) is reached. If it is obtained, Resp will be further processed; if it times out, an error message will be directly sent to the terminal UE1.

(5) Consensus: The blockchain node corresponding to business provider G will package the target transaction, construct a new target block and execute the target transaction therein. Finally, after multiple nodes (the blockchain node corresponding to business provider G and the blockchain node corresponding to business provider B) reach a consensus on the target block, the target block will be written to the disk, that is, stored on the blockchain. That is, the blockchain node corresponding to business provider G and the blockchain node corresponding to business provider B can both obtain the new target block and notify their respective detection services.

(6) The detection service processes the target block and target transaction: Whenever a new target block is generated by a blockchain node, the detection service that subscribes to the new block event of the blockchain node will receive the target block. When the detection service receives the new target block, it will traverse each target transaction in the target block. First, it will obtain the certificate T from the target transaction, and then query the data table Table _cert of the target database based on the certificate T to obtain the business party information. For example, it will obtain:

[UNI-G, APPID-G, Certificate G]

It can then be determined which target server the terminal is communicating with, and the business party information of the corresponding target server can be obtained; at the same time, the certificate T is compared with the locally stored certificate. If they are consistent, it means that the transaction was initiated by this business party. If they are inconsistent, it means that it was initiated by other business parties.

Specifically, take step (3) where the terminal UE1 initiates a request to the backend service in the target server of the service provider G and initiates a target transaction as an example:

In one case, the backend service in the target server of business provider G will think that the target transaction is initiated locally, so it will parse the target block to obtain the transaction data on the chain, that is, (account ID, name, public key and address on the chain), and at the same time, use txid/req/TxId as the complete key to call the Get interface of the cache service to obtain the Value stored in the cache service by the backend service with the same key:

Context＝Get("txid/req/TxId")＝{"address":"address","others":"other attributes"}

Afterwards, the Context and the obtained [UNI-G, APPID-G] are combined with the transaction data on the chain to form the complete target transaction data and stored in the target database. The addition of [UNI-G, APPID-G] will help with subsequent data statistics from the server dimension.

The target transaction data can be expressed as:

Info-G = (account ID, name, public key, on-chain address, address, other attributes, UNI-G, APPID-G)

Among them, only when the target transaction data is written successfully without any errors in the middle, the detection service in the target server of the service provider G will update the current (block number BN, transaction number TN) to the target database to indicate which target transactions the current detection service has successfully processed; when due to an unexpected crash, such as database unavailability, the detection service will start detection from block number BN when it restarts, and start processing from the TNth target transaction of the target block BN. Therefore, it can ensure that the on-chain transaction data can be fully synchronized to the target database to avoid data loss.

Finally, the detection service in the target server of service provider G calls the Set interface of the cache service, uses "txid/resp/TxId" as the complete key, and writes the following storage status information Resp to the cache service to notify the backend service in the target server of service provider G:

Set("txid/resp/TxId"，Resp,1hour)

Resp＝{"error":"error information","user":"target transaction data"}

In another case, the detection service in the target server of business provider B will think that the target transaction is not initiated locally, so it will parse the transaction to obtain the on-chain data, namely (account ID, name, public key and on-chain address), and combine it with the [UNI-G, APPID-G] obtained from the target database to merge into the complete target transaction data and store it in the target database:

Info-B = (account ID, name, public key, on-chain address, UNI-G, APPID-G)

Although there is only partial information, it can already meet some statistical analysis needs of the target server of business provider B, such as obtaining the total number of accounts. At the same time, since the address and other attributes are not stored on the chain, the target server of business provider B cannot obtain these transaction data, thereby improving the security of transaction data. It is understandable that in this case, the detection service of the target server of business provider B does not need to interact with the cache service.

Similarly, when the target transaction data is written successfully, the detection service in the target server of business provider B will update the current (block number BN, transaction number TN) to the target database to indicate which target transactions the current detection service has successfully processed; when there is an unexpected crash, such as database unavailability, the detection service will start detection from block number BN when it restarts, and start processing from the TNth target transaction of the target block BN. Therefore, it can ensure that the on-chain transaction data can be fully synchronized to the target database to avoid data loss.

At this point, the target servers of business provider G and business provider B have complete transaction data, which can meet some complex queries or some data statistical analysis tasks; at the same time, with the help of detection services and technical means of (block number BN, transaction number TN) as markers, the consistency between on-chain transaction data and off-chain transaction data can be improved, and transaction data will not be lost.

(7) Backend service acquisition result: In step (4), the backend service in the target server of the service provider G will use the cache service to obtain the result of the detection service setting, that is, the Resp stored in the cache service in step (6):

Resp＝{"error":"error information","user":"target transaction data"}

If there is an error in error, the relevant error information is returned to the terminal UE1; otherwise, the account identifier is taken out from the user and returned to the terminal UE1, indicating that the account registration is successful, and the specific account identifier in the current business is what it is, to facilitate subsequent operations.

It can be seen that the blockchain data processing method provided in the embodiment of the present application has the following advantages:

By recording the block number and transaction sequence number, the detection service ensures that the recorded block number and transaction sequence number will be updated only after the target transaction on the chain is successfully processed and the target transaction data is stored in the target database. At the same time, each time the detection service is started, it will continue to check and process the target transaction starting from the recorded block number and transaction sequence number, ensuring that the transaction data on the chain can be reliably written to the target database, ensuring that the transaction data will not be lost, and that the transaction data on the chain is consistent with that off the chain.

By using the cache service as a transit medium, after obtaining the transaction data on the chain, the detection service can use the cache service to safely and reliably obtain the context of the backend service cache (that is, the transaction data that is not on the chain), and then construct the complete target transaction data. This can not only ensure that the local target transaction data is completely written to the target database, but also obtain at least part of the transaction data in the servers corresponding to other business parties, thereby realizing cross-server transaction data interoperability.

By using the transaction certificate as the matching basis, when a new target server joins the blockchain network, the transaction certificate is allocated and uploaded to the chain, so that the target servers of different business parties can obtain the server attribute information of the target servers of other business parties through the detection service and store it in the database. When the detection service processes the target transaction, it can identify the target transactions initiated by the target servers of different business parties and perform different processing accordingly, thereby achieving interoperability of cross-server transaction data and facilitating data statistical analysis based on server attribute information.

In addition, referring to Figure 14, Figure 14 is another optional overall interaction flow diagram of the blockchain data processing method provided in an embodiment of the present application. The difference from the example shown in Figure 13 is that the target server of business provider B (corresponding to region B) and the target server of business provider G (corresponding to region G) are both deployed with back-end services, detection services and target databases, and the cache service is deployed on another independent server, and the target server of business provider B and the target server of business provider G share the same cache service.

Under this architecture, when the backend service in the target server of business provider G sets a key-value pair to the cache service, the transaction data that is not on the chain (i.e., the aforementioned Context) will be encrypted and then stored in the cache service. At the same time, in this example, the transaction data that is not on the chain does not want to be shared with the target server of business provider B, so only the corresponding encrypted information is sent to the detection service in the target server of business provider G.

For the detection service in the target server of the business provider G, after extracting the Context from the cache service, the Context can be decrypted according to the decryption information, and then the original transaction data can be restored, and then the target transaction data can be obtained:

Info-G = (account ID, name, public key, on-chain address, address, other attributes, UNI-G, APPID-G)

For the detection service in the target server of business provider B, the Context is also extracted from the cache service. However, since the detection service in the target server of business provider G does not have the corresponding decryption information, the decryption fails and only the target transaction data is obtained:

Info-B = (account ID, name, public key, on-chain address, UNI-G, APPID-G)

It can be seen that this example can effectively simplify the network architecture. At the same time, by encrypting the Context, the network architecture can be simplified without affecting the security of transaction data.

In addition, under this architecture, when the detection service in the target server of the service provider G writes the storage status information Resp to the cache service, it can further add the server identifier G in the key, for example, using "G/txid/resp/TxId" as the complete key, so that when the backend service obtains the storage status information Resp from the cache service, it can identify the storage status information Resp of the current target server according to the server identifier.

In addition, if the transaction data that is not on the chain needs to be shared with the target server of business provider B, the corresponding encrypted information can be sent to the detection service in the target server of business provider G and the detection service in the target server of business provider B. The detection service in the target server of business provider B can also decrypt the Context according to the decryption information, and then restore the original transaction data.

It is to be understood that, although each step in the above-mentioned each flow chart is shown in turn according to the indication of the arrow, these steps are not necessarily performed in turn according to the order indicated by the arrow. Unless there is a clear explanation in the present embodiment, the execution of these steps does not have a strict order restriction, and these steps can be performed in other orders. Moreover, at least a portion of the steps in the above-mentioned flow chart can include a plurality of steps or a plurality of stages, and these steps or stages are not necessarily performed at the same time, but can be performed at different times, and the execution order of these steps or stages is not necessarily performed in turn, but can be performed in turn or alternately with at least a portion of the steps or stages in other steps or other steps.

On the other hand, referring to FIG. 15 , FIG. 15 is an optional schematic diagram of the structure of the first blockchain data processing device provided in an embodiment of the present application, and the first blockchain data processing device 1500 includes:

The block receiving module 1501 is used to receive the target block sent by the blockchain network when the target block is approved by the blockchain network consensus, wherein the target block includes at least one target transaction;

The block processing module 1502 is used to extract the target transaction identifier of the target transaction and the first transaction data associated with the target transaction from the target block;

An access module 1503 is used to access a cache service storing a first data pair, and obtain second transaction data associated with a target transaction from the first data pair of the cache service according to a target transaction identifier, wherein the first data pair is constructed based on the transaction identifier and the transaction data, and the transaction identifier in the first data pair is generated by the blockchain network after receiving an asynchronously sent transaction request;

The storage module 1504 is used to obtain target transaction data according to the first transaction data and the second transaction data, and store the target transaction data in a target database.

Furthermore, the block receiving module 1501 is specifically used for:

Generate a block subscription request according to the preset block number range, and send the block subscription request to the blockchain network;

Whenever the target block in the block number interval is approved by the blockchain network consensus, the target block sent by the blockchain network in response to the block subscription request is received.

Furthermore, the storage module 1504 is also used for:

Generate storage result information of the target transaction data, wherein the storage result information is used to indicate whether the target transaction data has been successfully stored in the target database or has not been successfully stored in the target database;

A second data pair is constructed based on the target transaction identifier and the storage result information, and the second data pair is stored in the cache service.

Furthermore, the storage module 1504 is also used for:

When the target transaction data has been successfully stored in the target database, determine the block number of the target block and the transaction sequence number of the current target transaction in the target block, and record the block number and transaction sequence number;

After restarting, the block number and transaction sequence number are loaded, and the next target transaction is determined based on the block number and transaction sequence number.

Furthermore, the storage module 1504 is also used for:

If the transaction type of the target transaction is a chain configuration type, extract the server attribute information of the target server from the target block, and the server transaction certificate assigned to the target server by the blockchain network, wherein the target server is the server configured for the target transaction;

The server attribute information and the server transaction certificate are stored in the target database.

Further, the storage module 1504 is specifically used for:

Extract the target transaction certificate used to sign the target transaction from the target block;

Match the target transaction certificate with the server transaction certificate, and obtain the server attribute information corresponding to the target transaction from the target database according to the matching result;

The first transaction data, the second transaction data, the server attribute information and the target transaction certificate are combined into the target transaction data.

Further, the access module 1503 is specifically used for:

Extracting the target transaction certificate used to sign the target transaction from the target block;

Obtain the server transaction certificate loaded at startup, and compare the server transaction certificate loaded at startup with the target transaction certificate;

When the comparison result is that the server transaction certificate loaded at startup is consistent with the target transaction certificate, a cache service storing the first data pair is accessed.

Further, the storage module 1503 is also used for:

When the comparison result is that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, the first transaction data is used as the target transaction data, and the target transaction data is stored in the target database;

Alternatively, when the comparison result is that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, the cache service is accessed, and the encrypted transaction data corresponding to the target transaction identifier is obtained from the cache service according to the first data pair, and the pre-stored decryption information is obtained. The encrypted transaction data is decrypted according to the decryption information to obtain the second transaction data corresponding to the target transaction identifier, and the target transaction data is obtained according to the first transaction data and the second transaction data, and the target transaction data is stored in the target database, wherein the decryption information is generated by the target server that constructs the first data pair.

The first blockchain data processing device 1500 and the blockchain data processing method shown in FIG4 are based on the same inventive concept. When the target block is passed by the blockchain network consensus, the target block sent by the blockchain network is received, and the first transaction data associated with the target transaction is extracted from the target block. In the scenario where multiple different servers participate in the blockchain business system, different servers can synchronously obtain the transaction data of other servers in the blockchain, thereby realizing cross-server sharing of transaction data, and by extracting the target transaction identifier of the target transaction from the target block, accessing the cache service storing the first data pair, and obtaining the second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier. According to the invention, since the first data pair is constructed based on the transaction identifier and the transaction data, by introducing the cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be uploaded to the chain, thereby improving the security of the transaction data in the scenario of sharing transaction data across servers. On this basis, the target transaction data can be obtained according to the first transaction data and the second transaction data, and the target transaction data can be stored in the target database, so that the target database can store both the first transaction data in the blockchain and the second transaction data that is not in the blockchain, thereby improving the integrity of the transaction data in the local database on the basis of improving the security of the transaction data.

On the other hand, referring to FIG. 16 , FIG. 16 is an optional schematic diagram of the mechanism of the second blockchain data processing device provided in an embodiment of the present application, and the second blockchain data processing device 1600 includes:

Request module 1601, used to asynchronously send a transaction request of a target transaction to the blockchain network, and receive a target transaction identifier of the target transaction returned by the blockchain network;

A data pair construction module 1602 is used to obtain second transaction data associated with a target transaction, and to construct a first data pair according to the target transaction identifier and the second transaction data;

The cache module 1603 is used to store the first data pair in the cache service so that when the target block corresponding to the target transaction is approved by the blockchain network consensus, the detection service extracts the target transaction identifier and the first transaction data associated with the target transaction from the target block, accesses the cache service, obtains the second transaction data from the first data pair of the cache service according to the target transaction identifier, obtains the target transaction data according to the first transaction data and the second transaction data, and stores the target transaction data in the target database.

Furthermore, the blockchain data processing device further includes a message sending module 1604, which is used to:

Acquire storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, and generate a first notification message indicating a transaction result of the target transaction according to the storage result information;

The first notification message is sent to the account that initiated the target transaction.

Further, the message sending module 1604 is specifically used for:

Based on a preset time interval, continuously obtaining storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier;

When the storage result information is obtained, a first notification message indicating the transaction result of the target transaction is generated according to the storage result information; or, when the duration of the request for storage result information exceeds a preset duration threshold, a second notification message indicating a timeout is generated and sent to the account that initiated the target transaction.

Further, the data pair construction module 1602 is specifically used for:

Encrypting the second transaction data to obtain encrypted transaction data, and sending decryption information corresponding to the encrypted transaction data to the detection service;

A first data pair is constructed according to the target transaction identifier and the encrypted transaction data.

The above-mentioned second blockchain data processing device 1600 and the blockchain data processing method shown in FIG10 are based on the same inventive concept. By storing the first data pair in the cache service, when the target block is passed by the blockchain network consensus, the detection service can receive the target block sent by the blockchain network, and extract the first transaction data associated with the target transaction from the target block. In the scenario where multiple different servers participate in the blockchain business system, different servers can synchronously obtain the transaction data of other servers in the blockchain, thereby realizing cross-server sharing of transaction data, and by extracting the target transaction identifier of the target transaction from the target block, accessing the cache service storing the first data pair, and obtaining the target transaction identifier from the first data pair of the cache service according to the target transaction identifier. The second transaction data associated with the target transaction is constructed based on the transaction identifier and the transaction data. Therefore, by introducing a cache service, the second transaction data associated with the target transaction can be obtained according to the target transaction identifier without the need for the second transaction data to be uploaded to the chain. This improves the security of transaction data in the scenario of sharing transaction data across servers. On this basis, the target transaction data can be obtained based on the first transaction data and the second transaction data, and the target transaction data can be stored in the target database. The target database can store both the first transaction data in the blockchain and the second transaction data that is not in the blockchain. This improves the integrity of the transaction data in the local database while improving the security of the transaction data.

The electronic device for executing the above-mentioned blockchain data processing method provided in the embodiment of the present application may be a terminal. Referring to FIG. 17, FIG. 17 is a partial structural block diagram of the terminal provided in the embodiment of the present application, and the terminal includes: a camera assembly 1710, a memory 1720, an input unit 1730, a display unit 1740, a sensor 1750, an audio circuit 1760, a wireless fidelity (WiFi) module 1770, a processor 1780, and a power supply 1790. It can be understood by those skilled in the art that the terminal structure shown in FIG. 17 does not constitute a limitation on the terminal, and may include more or fewer components than shown in the figure, or combine certain components, or arrange components differently.

The camera assembly 1710 can be used to capture images or videos. Optionally, the camera assembly 1710 includes a front camera and a rear camera. Typically, the front camera is disposed on the front panel of the terminal, and the rear camera is disposed on the back of the terminal. In some embodiments, there are at least two rear cameras, which are any one of a main camera, a depth of field camera, a wide-angle camera, and a telephoto camera, so as to realize the fusion of the main camera and the depth of field camera to realize the background blur function, the fusion of the main camera and the wide-angle camera to realize the panoramic shooting and the VR (Virtual Reality) shooting function or other fusion shooting functions.

The memory 1720 may be used to store software programs and modules. The processor 1780 executes various functional applications and data processing of the terminal by running the software programs and modules stored in the memory 1720 .

The input unit 1730 may be used to receive input digital or character information and generate key signal input related to the terminal's settings and function control. Specifically, the input unit 1730 may include a touch panel 1731 and other input devices 1732 .

The display unit 1740 may be used to display input information or provided information and various menus of the terminal. The display unit 1740 may include a display panel 1741 .

The audio circuit 1760, the speaker 1761, and the microphone 1762 may provide an audio interface.

The power source 1790 may be alternating current, direct current, a disposable battery, or a rechargeable battery.

The number of sensors 1750 may be one or more, and the one or more sensors 1750 include but are not limited to: acceleration sensors, gyroscope sensors, pressure sensors, optical sensors, etc. Among them:

The acceleration sensor can detect the magnitude of acceleration on the three coordinate axes of the coordinate system established by the terminal. For example, the acceleration sensor can be used to detect the components of gravity acceleration on the three coordinate axes. The processor 1780 can control the display unit 1740 to display the user interface in a horizontal view or a vertical view according to the gravity acceleration signal collected by the acceleration sensor. The acceleration sensor can also be used for collecting game or user motion data.

The gyroscope sensor can detect the body direction and rotation angle of the terminal, and the gyroscope sensor can cooperate with the acceleration sensor to collect the user's 3D actions on the terminal. The processor 1780 can implement the following functions based on the data collected by the gyroscope sensor: motion sensing (such as changing the UI according to the user's tilt operation), image stabilization during shooting, game control, and inertial navigation.

The pressure sensor can be set in the side frame of the terminal and/or the lower layer of the display unit 1740. When the pressure sensor is set in the side frame of the terminal, the user's holding signal of the terminal can be detected, and the processor 1780 performs left and right hand recognition or shortcut operation according to the holding signal collected by the pressure sensor. When the pressure sensor is set in the lower layer of the display unit 1740, the processor 1780 controls the operability controls on the UI interface according to the user's pressure operation on the display unit 1740. The operability control includes at least one of a button control, a scroll bar control, an icon control, and a menu control.

The optical sensor is used to collect the ambient light intensity. In one embodiment, the processor 1780 can control the display brightness of the display unit 1740 according to the ambient light intensity collected by the optical sensor. Specifically, when the ambient light intensity is high, the display brightness of the display unit 1740 is increased; when the ambient light intensity is low, the display brightness of the display unit 1740 is decreased. In another embodiment, the processor 1780 can also dynamically adjust the shooting parameters of the camera assembly 1710 according to the ambient light intensity collected by the optical sensor.

In this embodiment, the processor 1780 included in the terminal can execute the blockchain data processing method of the previous embodiment.

The electronic device for executing the above-mentioned blockchain data processing method provided in the embodiment of the present application can also be a server. Referring to FIG. 18, FIG. 18 is a partial structural block diagram of the server provided in the embodiment of the present application. The server 1800 may have relatively large differences due to different configurations or performances, and may include one or more central processing units (CPU) 1822 (for example, one or more processors) and memory 1832, and one or more storage media 1830 (for example, one or more mass storage devices) storing application programs 1842 or data 1844. Among them, the memory 1832 and the storage medium 1830 can be short-term storage or permanent storage. The program stored in the storage medium 1830 may include one or more modules (not shown in the figure), and each module may include a series of instruction operations in the server 1800. Furthermore, the central processor 1822 can be configured to communicate with the storage medium 1830 and execute a series of instruction operations in the storage medium 1830 on the server 1800.

The server 1800 may also include one or more power supplies 1826, one or more wired or wireless network interfaces 1850, one or more input and output interfaces 1858, and/or, one or more operating systems 1841, such as Windows ServerTM, Mac OS XTM, UnixTM, LinuxTM, FreeBSDTM, etc.

The processor in server 1800 can be used to execute the blockchain data processing method.

An embodiment of the present application also provides a computer-readable storage medium, which is used to store program code, and the program code is used to execute the blockchain data processing method of each of the aforementioned embodiments.

The embodiment of the present application also provides a computer program product, which includes a computer program, and the computer program is stored in a computer-readable storage medium. The processor of the computer device reads the computer program from the computer-readable storage medium, and the processor executes the computer program, so that the computer device executes the above-mentioned blockchain data processing method.

The terms "first", "second", "third", "fourth", etc. (if any) in the specification of the present application and the above-mentioned drawings are used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence. It should be understood that the data used in this way can be interchanged where appropriate to describe the embodiments of the present application, for example, it can be implemented in an order other than those illustrated or described here. In addition, the terms "including" and "having" and any of their variations are intended to cover non-exclusive inclusions, for example, a process, method, system, product or device that includes a series of steps or units is not necessarily limited to those steps or units that are clearly listed, but may include other steps or units that are not clearly listed or inherent to these processes, methods, products or devices.

It should be understood that in the present application, "at least one (item)" means one or more, and "plurality" means two or more. "And/or" is used to describe the association relationship of associated objects, indicating that three relationships may exist. For example, "A and/or B" can mean: only A exists, only B exists, and A and B exist at the same time, where A and B can be singular or plural. The character "/" generally indicates that the objects associated before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, at least one of a, b or c can mean: a, b, c, "a and b", "a and c", "b and c", or "a and b and c", where a, b, c can be single or multiple.

It should be understood that in the description of the embodiments of the present application, the meaning of multiple (or multiple items) is more than two, greater than, less than, exceed, etc. are understood to not include the number, and above, below, within, etc. are understood to include the number.

In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. For example, the device embodiments described above are only schematic. For example, the division of units is only a logical function division. There may be other division methods in actual implementation, such as multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be an indirect coupling or communication connection through some interfaces, devices or units, which can be electrical, mechanical or other forms.

The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

If the integrated unit is implemented in the form of a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application is essentially or the part that contributes to the prior art or all or part of the technical solution can be embodied in the form of a software product, and the computer software product is stored in a storage medium, including a number of instructions to enable a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (Read-Only Memory, referred to as ROM), random access memory (Random Access Memory, referred to as RAM), disk or optical disk and other media that can store program codes.

It should also be understood that the various implementation methods provided in the embodiments of the present application can be combined arbitrarily to achieve different technical effects.

The above is a specific description of the preferred implementation of the present application, but the present application is not limited to the above implementation mode. Technical personnel familiar with the field can also make various equivalent modifications or substitutions under the shared conditions without violating the spirit of the present application. These equivalent modifications or substitutions are all included in the scope defined by the claims of the present application.

Claims (17)

1. A blockchain data processing method, comprising: When the target block is approved by the blockchain network consensus, receiving the target block sent by the blockchain network, wherein the target block includes at least one target transaction; Extracting a target transaction identifier of the target transaction and first transaction data associated with the target transaction from the target block; Accessing a cache service storing a first data pair, and obtaining second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier, wherein the first data pair is constructed based on the transaction identifier and the transaction data, and the transaction identifier in the first data pair is returned by the blockchain network after receiving the asynchronously sent transaction request; Target transaction data is obtained according to the first transaction data and the second transaction data, and the target transaction data is stored in a target database. 2. The blockchain data processing method according to claim 1, characterized in that when the target block is passed by the blockchain network consensus, receiving the target block sent by the blockchain network comprises: Generate a block subscription request according to a preset block number interval, and send the block subscription request to the blockchain network; Whenever a target block within the block number interval is approved by the blockchain network consensus, the target block sent by the blockchain network in response to the block subscription request is received. 3. The blockchain data processing method according to claim 1, characterized in that the blockchain data processing method further comprises: generating storage result information of the target transaction data, wherein the storage result information is used to indicate whether the target transaction data has been successfully stored in the target database or has not been successfully stored in the target database; A second data pair is constructed based on the target transaction identifier and the storage result information, and the second data pair is stored in the cache service. 4. The blockchain data processing method according to claim 1, characterized in that the blockchain data processing method further comprises: When the target transaction data has been successfully stored in the target database, determine the block number of the target block and the transaction sequence number of the current target transaction in the target block, and record the block number and the transaction sequence number; After restarting, the block number and the transaction sequence number are loaded, and the next target transaction is determined according to the block number and the transaction sequence number. 5. The blockchain data processing method according to any one of claims 1 to 4, characterized in that the blockchain data processing method further comprises: If the transaction type of the target transaction is a chain configuration type, extracting server attribute information of the target server from the target block, and a server transaction certificate assigned to the target server by the blockchain network, wherein the target server is a server configured for the target transaction; The server attribute information and the server transaction certificate are stored in the target database. 6. The blockchain data processing method according to claim 5, characterized in that obtaining target transaction data according to the first transaction data and the second transaction data comprises: Extracting a target transaction certificate used to sign the target transaction from the target block; Matching the target transaction certificate with the server transaction certificate, and acquiring the server attribute information corresponding to the target transaction from the target database according to the matching result; The first transaction data, the second transaction data, the server attribute information and the target transaction certificate are combined into target transaction data. 7. The blockchain data processing method according to claim 5, wherein accessing the cache service storing the first data pair comprises: Extracting a target transaction certificate used when signing the target transaction from the target block; Obtaining the server transaction certificate loaded at startup, and comparing the server transaction certificate loaded at startup with the target transaction certificate; When the comparison result is that the server transaction certificate loaded at startup is consistent with the target transaction certificate, a cache service storing the first data pair is accessed. 8. The blockchain data processing method according to claim 7, characterized in that the blockchain data processing method further comprises: When the comparison result shows that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, taking the first transaction data as the target transaction data, and storing the target transaction data in the target database; Alternatively, when the comparison result is that the server transaction certificate loaded at startup is inconsistent with the target transaction certificate, the cache service is accessed, and the encrypted transaction data corresponding to the target transaction identifier is obtained from the cache service according to the first data pair, and the pre-stored decryption information is obtained. The encrypted transaction data is decrypted according to the decryption information to obtain the second transaction data corresponding to the target transaction identifier, and the target transaction data is obtained according to the first transaction data and the second transaction data, and the target transaction data is stored in the target database, wherein the decryption information is generated by the target server that constructs the first data pair. 9. A blockchain data processing method, comprising: Asynchronously sending a transaction request for a target transaction to a blockchain network, and receiving a target transaction identifier of the target transaction returned by the blockchain network; Acquire second transaction data associated with the target transaction, and construct a first data pair according to the target transaction identifier and the second transaction data; The first data pair is stored in the cache service so that when the target block corresponding to the target transaction is passed by the blockchain network consensus, the detection service extracts the target transaction identifier and the first transaction data associated with the target transaction from the target block, accesses the cache service, obtains the second transaction data from the first data pair of the cache service according to the target transaction identifier, obtains the target transaction data according to the first transaction data and the second transaction data, and stores the target transaction data in the target database. 10. The blockchain data processing method according to claim 9, characterized in that the cache service also stores a second data pair constructed by a transaction identifier and storage result information, and the blockchain data processing method further comprises: Acquire the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, and generate a first notification message indicating a transaction result of the target transaction according to the storage result information; The first notification message is sent to the account that initiates the target transaction. 11. The blockchain data processing method according to claim 10, characterized in that the step of acquiring the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier, and generating a first notification message indicating the transaction result of the target transaction according to the storage result information comprises: Based on a preset time interval, continuously obtaining the storage result information corresponding to the target transaction from the second data pair of the cache service according to the target transaction identifier; When the storage result information is obtained, a first notification message indicating the transaction result of the target transaction is generated according to the storage result information; or, when the duration of requesting the storage result information exceeds a preset duration threshold, a second notification message indicating a timeout is generated, and the second notification message is sent to the account that initiated the target transaction. 12. The blockchain data processing method according to claim 9, wherein the step of constructing a first data pair according to the target transaction identifier and the second transaction data comprises: Encrypting the second transaction data to obtain encrypted transaction data, and sending decryption information corresponding to the encrypted transaction data to the detection service; A first data pair is constructed according to the target transaction identifier and the encrypted transaction data. 13. A blockchain data processing device, comprising: A block receiving module, configured to receive the target block sent by the blockchain network when the target block is approved by the blockchain network consensus, wherein the target block includes at least one target transaction; A block processing module, configured to extract a target transaction identifier of the target transaction and first transaction data associated with the target transaction from the target block; an access module, configured to access a cache service storing a first data pair, and obtain second transaction data associated with the target transaction from the first data pair of the cache service according to the target transaction identifier, wherein the first data pair is constructed based on the transaction identifier and the transaction data, and the transaction identifier in the first data pair is generated by the blockchain network after receiving an asynchronously sent transaction request; The storage module is used to obtain target transaction data according to the first transaction data and the second transaction data, and store the target transaction data in a target database. 14. A blockchain data processing device, comprising: A request module, used to asynchronously send a transaction request of a target transaction to a blockchain network, and receive a target transaction identifier of the target transaction returned by the blockchain network; a data pair construction module, configured to obtain second transaction data associated with the target transaction, and construct a first data pair according to the target transaction identifier and the second transaction data; A cache module is used to store the first data pair in a cache service so that when the target block corresponding to the target transaction is passed by the blockchain network consensus, the detection service extracts the target transaction identifier and the first transaction data associated with the target transaction from the target block, accesses the cache service, obtains the second transaction data from the first data pair of the cache service according to the target transaction identifier, obtains the target transaction data according to the first transaction data and the second transaction data, and stores the target transaction data in a target database. 15. An electronic device comprising a memory and a processor, wherein the memory stores a computer program, and wherein the processor implements the blockchain data processing method according to any one of claims 1 to 12 when executing the computer program. 16. A computer-readable storage medium storing a computer program, wherein the computer program, when executed by a processor, implements the blockchain data processing method according to any one of claims 1 to 12. 17. A computer program product, comprising a computer program, characterized in that when the computer program is executed by a processor, the blockchain data processing method according to any one of claims 1 to 12 is implemented.