WO2021220062A1

WO2021220062A1 - Blockchain transaction

Info

Publication number: WO2021220062A1
Application number: PCT/IB2021/000334
Authority: WO
Inventors: 鲁泽增; 魏玮; 王林青; 陈春伟
Original assignee: 支付宝实验室(新加坡)有限公司
Priority date: 2020-04-29
Filing date: 2021-04-23
Publication date: 2021-11-04
Also published as: CN111552991A

Abstract

Provided are a blockchain transaction method and apparatus, comprising: a service system sends a constructed target service transaction to a node device of a blockchain by means of a bridging end, the target service transaction comprising a first digital signature generated by the service system, using a first private key, for detailed data of the target service transaction, so that when the node device performs transaction verification, at least the first digital signature is verified on the basis of a first public key corresponding to the first private key, and after the verification is passed, the target service transaction is executed and an execution result of the target service transaction and a second digital signature generated by the node device in the blockchain, using a second private key, for the execution result are stored in a blockchain database locally stored by the node device.

Description

Blockchain transaction

Technical field

One or more implementations of this specification relate to the field of blockchain technology, and in particular to a blockchain transaction method and device.

Background technique

Blockchain technology, also known as distributed ledger technology, is an emerging technology in which several computing devices participate in "bookkeeping" and jointly maintain a complete distributed database. Because the blockchain technology has the characteristics of decentralization, openness and transparency, each computing device can participate in database records, and the rapid data synchronization between computing devices, the blockchain technology has been widely used in many fields. To apply.

With the development of blockchain technology, more and more business systems have put forward the need to connect to the blockchain network. However, directly connecting the business system server with the blockchain network will bring data security risks, especially when When the blockchain network is a public blockchain network, it not only has higher hardware requirements for the business system server, but also has a greater risk of privacy breaches for the business system server.

Summary of the invention

In view of this, one or more implementations of this specification provide a blockchain transaction method, device, and computer equipment.

According to the first aspect of one or more implementation manners of this specification, an application to a business system is proposed; the business system is connected to a node device of the blockchain through a bridge terminal; the method includes: the target that the business system will construct The business transaction is sent to the node device of the blockchain through the bridge terminal, wherein the target business transaction includes a first digital signature generated by the business system using a first private key for the detailed data of the target business transaction , So that when the node device performs transaction verification, it verifies the first digital signature based at least on the first public key corresponding to the first private key, and executes the target business transaction after the verification is passed, And storing the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result in the blockchain database stored locally by the node device; Obtain the execution result of the target business transaction and the second digital signature from the node device through the bridge terminal; verify the second digital signature based on the second public key corresponding to the second private key, and After the verification of the second digital signature is passed, further business processing logic related to the transaction detail data is executed based on the execution result.

According to the second aspect of one or more implementations of this specification, a blockchain transaction method is proposed, which is applied to the node equipment of the blockchain; the business system is connected to the node equipment of the blockchain through the bridge terminal; The method includes: a node device connected to the bridge terminal obtains a target business transaction constructed by the business system through the bridge terminal, wherein the target business transaction includes the business system using a first private key as the target A first digital signature generated by the detailed data of the business transaction; transaction verification is performed on the target business transaction, the transaction verification at least including performing the first digital signature on the first public key corresponding to the first private key Verification; after the verification is passed, execute the target business transaction, and the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using a second private key for the execution result Stored in the blockchain database locally stored in the node device; sending the execution result and the second digital signature to the business system through the bridge end, so that the business system is based on the second private The second public key corresponding to the key verifies the second digital signature, and after the second digital signature is verified, executes further business processing logic related to the transaction detail data based on the execution result.

According to the third aspect of one or more embodiments of this specification, a blockchain transaction device is proposed, which is applied to a business system; the business system is connected to a node device of the blockchain through a bridge terminal; the device includes : A sending unit, which sends the constructed target business transaction to the node device of the blockchain through the bridge end, wherein the target business transaction includes the use of the first private key by the business system for the target business transaction The first digital signature generated by the detailed data, so that when the node device performs transaction verification, the first digital signature is verified at least based on the first public key corresponding to the first private key, and after the verification is passed Execute the target business transaction, and store the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result to the node device Locally stored blockchain database; obtain the execution result of the target business transaction and the second digital signature from the node device through the bridge terminal; verify based on the second public key corresponding to the second private key The second digital signature, and after the verification of the second digital signature is passed, execute further business processing logic related to the transaction detail data based on the execution result.

According to the fourth aspect of one or more implementations of this specification, a blockchain transaction device is proposed, which is applied to the node equipment of the blockchain; the business system is connected to the node equipment of the blockchain through the bridge terminal; The device includes: an acquiring unit, and a node device connected to the bridge terminal acquires a target business transaction constructed by the business system through the bridge terminal, wherein the target business transaction includes the business system using a first private key for The first digital signature generated by the detailed data of the target business transaction; a verification unit, which performs transaction verification on the target business transaction, the transaction verification at least including a transaction verification based on a first public key corresponding to the first private key The first digital signature is verified; the execution unit executes the target business transaction; the storage unit uses the execution result of the target business transaction and the node device in the blockchain using a second private key as the execution result The generated second digital signature is stored in the blockchain database locally stored in the node device; the sending unit sends the execution result and the second digital signature to the business system through the bridge end, so that the The business system verifies the second digital signature based on the second public key corresponding to the second private key, and after passing the verification of the second digital signature, executes the related transaction detail data based on the execution result The further business processing logic.

According to a fifth aspect of one or more implementation manners of this specification, a computer device is proposed, including: a memory and a processor; the memory stores a computer program that can be run by the processor; When the computer program is described, the blockchain transaction method executed by the business system is executed.

According to the sixth aspect of one or more implementation manners of this specification, a computer device is proposed, including: a memory and a processor; the memory stores a computer program that can be run by the processor; When the computer program is described, the blockchain transaction method executed by the node device connected to the bridge terminal is executed.

The blockchain transaction methods, devices, and computer equipment provided by the various implementations of this specification set up a bridge terminal between the business system and the blockchain node equipment, and the bridge terminal is responsible for forwarding the transaction and transaction constructed by the business system to the blockchain network. Forward the transaction execution result on the blockchain to the business system. In order to prevent the bridging end from doing evil, the transaction constructed by the above-mentioned business system includes the first digital signature made by the business system, and the blockchain node device connected to the bridging end includes the node of the blockchain in the block in which the above-mentioned transaction is recorded. The second digital signature made by the device, through the digital signature verification technology, effectively reduces the data security risk caused by the evildoing of the bridge end, and improves the data security of the business system.

Description of the drawings

FIG. 1 is a schematic diagram of implementing blockchain transactions through a system including a business system, a bridge terminal, and a blockchain network provided by an exemplary embodiment;

FIG. 2 is a schematic flowchart of a blockchain transaction method provided by an exemplary embodiment;

Fig. 3 is a schematic diagram of a blockchain transaction device applied to a business system according to an exemplary embodiment;

FIG. 4 is a schematic diagram of a blockchain transaction device applied to a device side of a blockchain node according to an exemplary embodiment;

Fig. 5 is a hardware structure diagram for running the implementation of the blockchain transaction device provided in this specification.

Detailed ways

Here, exemplary embodiments will be described in detail, and examples thereof are shown in the accompanying drawings. When the following description refers to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all the embodiments consistent with one or more embodiments in this specification. On the contrary, they are merely examples of devices and methods consistent with some aspects of one or more embodiments of this specification as detailed in the appended claims.

It should be noted that in other embodiments, the steps of the corresponding method are not necessarily executed in the order shown and described in this specification. In some other embodiments, the method may include more or fewer steps than described in this specification. In addition, a single step described in this specification may be decomposed into multiple steps for description in other embodiments; and multiple steps described in this specification may also be combined into a single step in other embodiments. describe.

As the application business supported by the blockchain matures, more and more business systems need to be connected to the blockchain network to send transfer transactions, deposit certificate transactions, or smart contract call transactions to the blockchain, and obtain the above The execution result of the transaction on the blockchain. If the business system is directly connected to the node equipment of the blockchain network, in addition to the business logic, complex logic such as network communication, certificate exchange, key security and privacy protection needs to be deployed in the business system for the security of the business system. The cost of direct access to the blockchain is higher.

In view of the above problems, one or more implementations of this specification provide a blockchain transaction method for the business system to publish transactions to the blockchain network and receive the execution results of the transaction; the above-mentioned business system communicates with each other through a bridge The node device connection of the blockchain.

The business system described in one or more implementations of this specification may include one or more business system servers deployed with business processing logic, and may also include other functions such as connection with the business system server, responsible for network communication, or key calculation. Hardware modules (such as HSM hardware security modules) or stand-alone devices.

The bridge terminal received in one or more embodiments of this specification is an independent device that connects the business system with any node device of the blockchain, or is a hardware module set inside the business system, so that the business system can pass through the The hardware module is connected to the node device of the blockchain, and may also be a hardware module installed inside the node device of the blockchain, which is not limited here.

Specifically, the above-mentioned business system may set its trusted blockchain node device, and require the bridge terminal to communicate with the above-mentioned trusted blockchain node device to perform business transaction execution.

The blockchain or blockchain network described in one or more embodiments of this specification can specifically refer to a P2P network system with a distributed data storage structure reached by each node device through a consensus mechanism. Ledger data is distributed in time-connected "blocks". The next block can contain the data summary of the previous block and is based on the specific consensus mechanism (such as POW, POS, DPOS or PBFT, etc.) ) To achieve full backup of all or part of the node data.

Those skilled in the art are well aware that because the blockchain network system operates under the corresponding consensus mechanism, the data that has been included in the blockchain database is difficult to be tampered with by any node. For example, a blockchain using Pow consensus requires at least full Only 51% of the network's computing power can tamper with existing data. Therefore, the blockchain system has the characteristics of ensuring data security and preventing attack and tampering that other centralized database systems cannot match.

For the real data generated in the physical world, it can be constructed into a standard transaction format supported by the blockchain, and then published and broadcasted to the node devices of the blockchain. The received transaction is processed by consensus, and after a consensus is reached, the node device as the accounting node in the block chain will package the transaction into the block and carry out persistent storage in the block chain.

No matter which consensus algorithm the blockchain uses, the accounting node can package the received transaction to generate the latest block, and send the generated latest block or the block header of the latest block to other node devices for consensus verification . If other node equipment receives the latest block or the block header of the latest block, it is verified that there is no problem, and the latest block can be appended to the end of the original blockchain to complete the accounting process of the blockchain. When other nodes verify the new block or block header sent by the accounting node, they can also execute the transactions contained in the block.

For most blockchain models, Merkle trees are usually used; or, based on the data structure of Merkle trees, to store and maintain data. Take Ethereum as an example. Ethereum uses MPT tree (a variant of Merkle tree) as a form of data organization to organize and manage important data such as account status and transaction information.

Ethereum has designed three MPT trees for the data that needs to be stored and maintained in the blockchain, namely the MPT state tree, the MPT transaction tree and the MPT receipt tree. Among them, in addition to the above three MPT trees, there is actually a Storage tree constructed based on the storage content of the contract account.

MPT state tree is an MPT tree organized by the account state data of all accounts in the blockchain; MPT transaction tree is an MPT tree organized by transaction data in the blockchain; MPT receipt tree , Is the MPT tree organized by the receipt of each transaction generated after the transactions in the block are executed. The hash values of the root nodes of the MPT state tree, MPT transaction tree, and MPT receipt tree shown above will all be added to the block header of the corresponding block eventually.

Among them, the MPT transaction tree and MPT receipt tree correspond to blocks, that is, each block has its own MPT transaction tree and MPT receipt tree. The MPT state tree is a global MPT tree, which does not correspond to a specific block, but covers the account state data of all accounts in the blockchain.

The organized MPT transaction tree, MPT receipt tree, and MPT state tree will eventually be stored in a Key-Value database (for example, LevelDB) that uses a multi-level data storage structure. The execution method of the transaction can be specifically set according to the type and content of the transaction. For example, when the transaction is a transfer transaction, after receiving a new block sent by the accounting node, the node device of the blockchain can store it in the locally stored blockchain user account status database based on the transfer value included in the transfer transaction , The amount corresponding to the transfer value is transferred from the sender account of the transfer transaction, and the recipient user adds and transfers to the corresponding amount, and the execution result of the transaction will be saved in the local state of the node device in the form of a transaction log In the receipt tree (MPT) of the database.

When the transaction is a business data certificate transaction, the node device of the blockchain can save the new block containing the business data certificate transaction in the locally maintained blockchain ledger after receiving the new block sent by the accounting node. In the database (block block), and the execution result of the transaction will be stored in the receipt tree (MPT) of the local state database of the node device in the form of a transaction log;

When the transaction is a smart contract call transaction, the node device of the blockchain can execute the smart contract logic of the transaction call on the local virtual machine after receiving the new block sent by the accounting node, except for the execution result of the transaction In addition to being stored in the receipt tree (MPT) of the local state database of the node device in the form of a transaction log, the execution result of the smart contract logic can also be stored in the blockchain state data storage space corresponding to the smart contract.

It should be noted that each time the blockchain generates a newest block, after the transaction in the latest block is executed, the relevant account of the executed transaction in the blockchain (can be an external account or a contract account) The status of the account will usually change accordingly. For example, when a "transfer transaction" in a block is executed, the balances of the transferor account and transferee account related to the "transfer transaction" (that is, the field value of the Balance field of these accounts) are usually also Will change accordingly.

After the transaction of the node device in the latest block generated by the blockchain is completed, because the account status in the current blockchain has changed, the node device needs to use the current account status data of all accounts in the blockchain to Construct the MPT state tree to maintain the latest state of all accounts in the blockchain.

That is, whenever a newest block is generated in the blockchain, and the transaction in the latest block is executed, the account status in the blockchain changes, and the node device needs to be based on all accounts in the blockchain With the latest account status data, rebuild an MPT status tree. In other words, each block in the blockchain has a corresponding MPT state tree; the MPT state tree maintains that after the transactions in the block are executed, all accounts in the blockchain are up to date The status of the account.

Blockchain is generally divided into three types: Public Blockchain, Private Blockchain and Consortium Blockchain. In addition, there can also be a combination of the above types, such as private chain + consortium chain, consortium chain + public chain, and so on.

Among them, the most decentralized one is the public chain. The public chain is represented by Bitcoin and Ethereum. Participants who join the public chain (also called nodes in the blockchain) can read the data records on the chain, participate in transactions, and compete for the accounting rights of new blocks, etc. . Moreover, each node can freely join or exit the network, and perform related operations.

The private chain is the opposite. The write permission of the network is controlled by an organization or institution, and the data read permission is regulated by the organization. In simple terms, a private chain can be a weakly centralized system with strict restrictions on nodes and a small number of nodes. This type of blockchain is more suitable for internal use by specific institutions.

Consortium chain is a block chain between public chain and private chain, which can realize "partial decentralization". Each node in the alliance chain usually has a corresponding entity or organization; nodes are authorized to join the network and form a stakeholder alliance to jointly maintain the operation of the blockchain.

It can be expected that the implementation provided in this specification can be implemented in any suitable type of blockchain network.

As shown in Figure 2, the blockchain transaction method provided by one or more implementations provided in this specification includes:

Step 202: The business system sends the constructed target business transaction to the node device of the blockchain through the bridge end, where the target business transaction includes the business system using the first private key as the target The first digital signature generated by the detailed data of the business transaction.

The business system may construct a target business transaction based on business needs, the target business transaction may include detailed data related to business processing, and a first digital signature generated by the business system using the first private key held by the business system for the detailed data. Specifically, the first digital signature may be made for derived data such as the original text of the detailed data or the hash digest of the detailed data.

In order to further improve the key security, the above-mentioned first private key is stored in the hardware security module HSM carried by the business system. The hardware security module HSM is a computer hardware device used to protect and manage the keys used by the business system, and at the same time provide related key calculation operations (such as digital signature operations). For example, the business system can use instructions that include the above detailed data. Invoke the HSM to execute the key calculation service of generating the first digital signature on the above-mentioned detailed data based on the stored first private key, and directly obtain the above-mentioned first digital signature from the HSM. Further, the business system may encapsulate the above-mentioned detailed data and the first digital signature into a target business transaction according to the transaction format, and then send the target business transaction to the bridge end.

Step 204: The bridge terminal forwards the target service transaction to the node device connected to the bridge terminal.

In this embodiment, the above-mentioned bridge terminal can be connected to one or more node devices in the above-mentioned blockchain network, and forward the above-mentioned target business transaction to one or more node devices; the node device that obtains the above-mentioned target business transaction You can continue to broadcast and forward the above-mentioned target business transactions in the blockchain network.

Step 206: When the node device (including the node device connected to the bridge terminal) in the blockchain performs transaction verification, at least perform the first digital signature on the first public key corresponding to the first private key. Verify, and after the verification is passed, execute the target business transaction.

One or more node devices corresponding to the above-mentioned bridge terminal, or node devices in the blockchain, may store the first public key corresponding to the first private key held by the business system. In the implementation, the business system can apply for joining the above-mentioned blockchain network, or when the above-mentioned business system connected with the bridge terminal and the above-mentioned one or more node devices are initialized and connected, the first private held by the above-mentioned business system The first public key corresponding to the key is forwarded through the above-mentioned bridging terminal or directly communicated with the above-mentioned one or more node devices through the service system, and the above-mentioned first public key is transmitted to the above-mentioned one or more node devices, or the Node equipment in the blockchain. This specification does not limit the specific way for the node device of the blockchain to obtain the above-mentioned first public key.

Moreover, in order to further ensure the security of the business system, the business system may also periodically update the aforementioned first private key-first public key pair, and transmit the updated first public key to the node device of the blockchain.

Step 208, the node device connected to the bridge terminal stores the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result to the bridge terminal The blockchain database stored locally on the connected node device.

In one embodiment, the second digital signature is the second private key held by the node device of the blockchain, and is the status database stored in the block header of the target block that contains the target business transaction. The digital signature generated by the certification root.

After receiving the target block after consensus verification, the node device of the blockchain can execute the transaction included in the target block, and store the execution result of the transaction, that is, the state data after the transaction is executed, in the blockchain state database. The authentication root described in this embodiment is derived from the state data corresponding to all transactions in the target block, or derived from the execution result data of all transactions, and can be the execution result of any transaction in the target block The value of the data for authentication verification, which can be stored in the block header of the target block.

For example, Ethereum has designed three MPT trees for the data that needs to be stored and maintained in the blockchain, namely the MPT state tree, the MPT transaction tree and the MPT receipt tree. Among them, in addition to the above three MPT trees, there is actually a Storage tree constructed based on the storage content of the contract account.

MPT state tree is an MPT tree organized by the account state data of all accounts in the blockchain; MPT transaction tree is an MPT tree organized by transaction data in the blockchain; MPT receipt tree , Is an MPT tree organized into transaction log receipts (receipts) corresponding to each transaction generated after the transactions in the block are executed, and the transaction log receipts contain the execution results of the transaction. The hash values of the root nodes of the MPT state tree, MPT transaction tree, and MPT receipt tree shown above will all be added to the block header of the corresponding block eventually. At this time, the state database described in the foregoing embodiment is a Merkel tree (MPT state tree or MPT state tree) constructed based on the state data corresponding to the transaction stored in the target block; the authentication root is the The root hash of the Merkel tree (MPT state tree or MPT state tree).

Of course, this embodiment does not limit the above-mentioned blockchain to the Ethereum architecture. Those skilled in the art can at least design specific derivative rules for the execution result of the target business transaction or the state data after the execution of the target business transaction. , And include the authentication root in the block header of the target block to realize the verification of the target business transaction based on the authentication root.

This embodiment does not limit the role of the node device that generates the digital signature for the authentication root in the block header of the target block, nor does it limit the storage location for generating the digital signature for the authentication root in the block header of the target block.

In one embodiment, the above-mentioned second digital signature is generated by the accounting node device of the blockchain using a second private key held by it, and the second digital signature is stored in the blockchain. The block header of the target block.

After receiving the above target business transaction, the accounting node of the blockchain uses the second private key held by the accounting node when packaging the above target business transaction into the target block, which is the block header of the target block. The authentication root generates a second digital signature, and the second digital signature is also included in the block header of the target block. The accounting node broadcasts the target block containing the second digital signature to the node device in the blockchain network for consensus verification. The election method of the above-mentioned blockchain's accounting nodes, the collection method of the transactions included in the new block, and the specific method of consensus verification of the new block are also different based on the difference of the blockchain consensus mechanism, and will not be discussed here. limited.

When the above-mentioned target block passes the consensus verification of the node device in the blockchain network (including the verification of the first digital signature described in the above-mentioned embodiment), the node device in the blockchain can execute the above-mentioned target block chain. And store the target block containing the second digital signature made by the above-mentioned accounting node in the blockchain database stored locally in the node device.

In another embodiment, the above-mentioned second digital signature is generated by the node device connected to the bridge terminal using a second private key held by it, and the second digital signature is stored in a local storage of the node device connected to the bridge terminal. The block header of the target block.

In this embodiment, after receiving the above-mentioned target business transaction, the accounting node of the blockchain can package the above-mentioned target business transaction into a target block, and then broadcast the target block to the node device in the blockchain network For consensus verification. The election method of the above-mentioned blockchain's accounting nodes, the collection method of the transactions included in the new block, and the specific method of consensus verification of the new block are also different based on the difference of the blockchain consensus mechanism, and will not be discussed here. limited.

The above-mentioned one or more node devices connected to the bridge terminal, after receiving the target block including the above-mentioned target business transaction, can execute each transaction included in the above-mentioned target block, and store it in the blockchain state database locally Store the execution results of each of the above transactions and update the state data corresponding to each transaction; when one or more node devices connected to the bridge end store the above target blocks locally, they can use their own second private The key generates a second digital signature for the authentication root in the block header of the target block, and saves the second digital signature in the block header of the target block stored locally in the node device.

It is worth noting that the second digital signature made by the node device connected to the bridge terminal in this embodiment to the authentication root in the block header of the target block based on the second private key it holds is only In order to prevent the bridging end from doing evil and to facilitate the business system to verify the execution results of the target business transaction, the node device connected to the bridging end saves it in the block header of the target block stored locally. Others in the blockchain The node device receives the target block broadcast by the accounting node that does not include the second digital signature.

In another embodiment, after the node device connected to the bridge terminal executes the above-mentioned target service transaction, the second private key held by the node device can be used to generate a second digital signature for the execution result of the above-mentioned target service transaction.

Take the account-type blockchain based on the Ethereum architecture as an example. When the target business transaction is a transfer transaction, the node device of the blockchain can receive the target block sent by the accounting node according to the transfer transaction. Transfer value, in the locally stored blockchain state database, transfer the amount corresponding to the transfer value from the sender account of the transfer transaction, and add and transfer to the corresponding amount on the receiving user, and the execution result of the transaction It will be stored in the receipt tree (receipt MPT) of the local state database of the node device in the form of a transaction log.

When the target business transaction is a business data deposit transaction, the node device of the blockchain can save the execution result of the transaction on the node device in the form of a transaction log after receiving the target block sent by the accounting node. In the receipt tree (MPT) of the locally maintained blockchain state database.

When the target business transaction is a smart contract call transaction, the node device of the blockchain can execute the smart contract logic of the transaction call on the local virtual machine after receiving the target block sent by the accounting node, except for the transaction The execution results of the smart contract are stored in the receipt tree (receipt MPT) of the local state database of the node device in the form of transaction logs, and the execution results of the smart contract logic can also be stored in the account storage space (storage MPT) corresponding to the smart contract. )middle.

By executing the foregoing target business transaction, the execution result of the foregoing target business transaction is stored in the blockchain state database stored locally in the node device. In this embodiment, in order to prevent the bridging end from doing evil when notifying the business system of the execution result of the target business transaction, one or more node devices connected to the bridging end can verify the target business transaction and include the target business. When the target block of the transaction is executed, the target business transaction is executed, and a second digital signature is generated for the execution result of the target business transaction using the held second private key.

Specifically, the node device connected to the bridge terminal may perform a digital signature operation on the plaintext of the execution result of the target business transaction to obtain the second digital signature; or, for some target business transactions, the execution result may occupy a large amount of At this time, the node device may also perform a digital signature operation on the verification data of the execution result, for example, the hash digest of the execution result, to obtain the second digital signature.

Similarly, the second digital signature made by the node device connected to the bridge terminal based on the second private key held by it to the execution result of the target business transaction described in this embodiment is only to prevent the bridge terminal from doing evil. In order to facilitate the business system to verify the execution results of the target business transaction, the node device connected to the bridge terminal is stored in its locally stored blockchain database. Other node devices in the blockchain are not connected to the above-mentioned business system. There is no need to digitally sign the execution result of the above-mentioned target business transaction, and there is no need to store the above-mentioned digital signature in its locally stored blockchain database.

In this embodiment, the specific storage location of the second digital signature in the local blockchain database of the node device connected to the bridge terminal is not limited. In order to facilitate the bridge end or business system to verify that the target business transaction is indeed included in the target block, the node device can notify the bridge end or business system that the target business transaction is blocked by sending the entire target block to the bridge end. In order to further facilitate the notification and reduce the information interaction steps between the node device and the bridge terminal, the node device may combine the execution result and the second digital signature, or the verification data of the execution result (such as the hash digest of the execution result) and The second digital signature is stored in the target block, for example, in the block header of the target block. The execution result and the second digital signature are obtained by directly pulling the target block from the node device through the bridge terminal.

Or, in order to facilitate the node device connected to the bridge terminal to query the execution result and the second digital signature generated for the execution result, the second digital signature can be stored in the state database by the node device corresponding to the execution result, for example, The second digital signature and execution result are correspondingly stored in the receipt tree corresponding to the target block, or the second digital signature and execution result are correspondingly stored in the account storage space of the smart contract called by the target business transaction, and so on.

Step 210: The bridge terminal forwards the execution result of the target service transaction and the second digital signature sent by the node device connected to the bridge terminal to the service system.

The node device connected to the bridge terminal can obtain the above-mentioned execution result and the second digital signature from its locally stored blockchain database, and then send the above-mentioned execution result and the second digital signature to the bridge terminal, so that the bridge terminal can The above execution result and the second digital signature are forwarded to the business system.

In one embodiment, when the second digital signature is generated by the accounting node of the blockchain for the authentication root of the state database stored in the block header of the target block of the target business transaction, or when the second The digital signature is generated by the node device connected to the bridge terminal for the above authentication root, and the business system verifies that the second digital signature is the accounting node device or the node device connected to the bridge terminal is included in the above block header. If the authentication root is generated, it is also necessary to verify the authentication correspondence between the execution result of the target business transaction and the authentication root contained in the block header, that is, verify whether the execution result is indeed included in the block corresponding to the target block The chain state database.

At this time, the node device connected to the bridge terminal also needs to send state data corresponding to the target block to the bridge terminal. The state data may include a default constructed based on the state data corresponding to the transaction stored in the target block. Kerr tree (such as MPT state tree or MPT receipt tree), the Merkel tree contains the execution result of the above target business transaction, so that the bridge end forwards the above state data to the business system, and the business system is based on the execution result that contains the above execution result. Whether the state data can be derived to obtain the above authentication root, if it can be obtained, it is proved that the execution result of the target business transaction is indeed included in the blockchain state database corresponding to the target block.

It is worth noting that the above-mentioned business system may locally store the public key corresponding to the node device in the blockchain or the node device connected with the bridge terminal to facilitate the verification of the above-mentioned second digital signature.

In yet another embodiment, the second digital signature is made by the node device connected to the bridge terminal using the second private key to write the original text of the execution result, and the node device connected to the bridge terminal can compare the execution result with the result of the execution. The second digital signature is stored in the block header of the target block stored locally. The bridge terminal can monitor the node device connected to it regularly to obtain the target block stored by the node device. Alternatively, the node device, after storing the execution result and the second digital signature in the target block, sends a notification to the bridge end that the target business transaction is included. The notification may include the block height of the target block and the retrieval identifier of the target business transaction, so that the bridge terminal can pull the target block from the node device and check that the target business transaction is included based on the retrieval identifier. In the target block.

In another embodiment, the above-mentioned second digital signature is made by a node device connected to the bridge terminal using the second private key to a hash digest of the execution result, the hash of the execution result The digest and the second digital signature are stored in the block header of the target block stored locally in the node device. After storing the hash value of the execution result and the second digital signature in the block header of the target block, the node device may send a notification that the target business transaction is included to the bridge end, and the notification may include the block of the target block Height and the retrieval identifier of the target business transaction (for example, the TXID or transaction serial number of the target business transaction), so that the bridge terminal can pull the target block from the node device and send it to the node device based on the retrieval identifier. Inquire about the execution result of the target business transaction; based on the search identifier, the node device queries the execution result corresponding to the target business transaction in its locally maintained blockchain state database, and returns the execution result to the bridge end, So that the bridging end forwards the execution result to the business system.

In another embodiment, the above-mentioned second digital signature is made by a node device connected to the bridge terminal using the second private key on the original text of the execution result or the hash digest of the execution result , And the second digital signature and the execution result are correspondingly saved in the blockchain state database stored locally in the node device. The node device can directly obtain the original text of the execution result and the second digital signature from its locally stored blockchain state database, and forward the original text of the execution result and the second digital signature from the bridge end to business system.

Step 212: The service system verifies the second digital signature based on the second public key corresponding to the second private key, and after the verification of the second digital signature is passed, executes the transaction based on the execution result. Describe the further business processing logic related to the transaction detail data.

The above-mentioned business system can maintain its trusted blockchain node equipment (such as the above-mentioned accounting node) or the public key list of the node equipment connected to the bridge terminal locally, and receive the execution result and forwarded by the above-mentioned bridge terminal. After the second digital signature, the business system can obtain the second public key corresponding to the second private key held by the node device from the public key list, and verify the second digital signature based on the second public key .

When the above-mentioned second digital signature is generated based on the authentication root included in the block header of the target block, in addition to verifying the above-mentioned second digital signature, the business system also needs to be based on the state database data of the blockchain forwarded by the bridge end For example, the Merkel tree (MPT receipt tree or MPT state tree) constructed by the target block based on the state data corresponding to the transaction stored in the target block, or the account space of the smart contract called by the target business exchange The stored state data tree is used to verify the authentication correspondence between the authentication root and the execution result. The business system can perform Merkel tree root generation calculations on the values of the execution results of all transactions in the target block containing the target business transaction to verify the calculated root of the Merkel tree and the authentication in the block header. Whether the roots are consistent; when the two root values are consistent, it means that the execution result can be authenticated by the authentication root, and the execution result is included in the blockchain state database that can generate the authentication root.

When the second digital signature is made by the node device connected to the bridge terminal using the second private key to at least the hash digest of the execution result, in addition to verifying the second digital signature, the business system also needs to verify the Whether the hash digest of the execution result matches the execution result.

After the verification of the second digital signature is passed, or the authentication correspondence between the execution result and the authentication root is verified, or the hash digest of the execution result is consistent with the original text of the execution result, the execution and The business processing logic related to the transaction detail data.

In one embodiment, the transaction detail data includes blockchain transfer data, and the target business transaction is a transfer transaction. After the above transfer transaction is included in the target block of the blockchain, the node device can transfer from the sender account of the transfer transaction in the locally stored blockchain user account status database according to the transfer value included in the transfer transaction. The amount corresponding to the transfer value is output, and the recipient user adds and transfers to the corresponding amount. The user account balance value and transfer value of the above blockchain correspond to the virtual currency (Token) circulating on the blockchain. The virtual currency can only be used as a currency symbol corresponding to the actual assets under the chain to circulate assets on the chain. Proof of the process.

After the above-mentioned transfer transaction is successfully executed on the blockchain, the business system needs to perform the remittance operation related to the above-mentioned blockchain transfer data outside the chain, for example, the above-mentioned business system initiates the actual bank remittance operation to its user, or notify The sender related to the aforementioned transfer transaction performs the remittance operation, or informs the recipient related to the aforementioned transfer transaction to check whether the remittance is received, and so on.

When the execution result of the above transfer transaction shows that the transfer has failed, the business system needs to perform the refund operation related to the above blockchain transfer data outside the chain, for example, the above business system initiates the actual bank account refund operation to its user, or Notify the sender related to the above transfer transaction to perform the refund operation, or notify the receiver related to the above transfer transaction to check whether the refund is received, and so on.

In the blockchain transaction method provided by one or more of the above embodiments, a bridge terminal is set between the business system and the node equipment of the blockchain network, and the bridge terminal is responsible for forwarding the transaction constructed by the business system to the blockchain network And forward the transaction execution result on the blockchain to the business server. In order to prevent the bridging end from doing evil, the transaction constructed by the above-mentioned business system includes the first digital signature made by the business system based on the business data, and the block chain node device connected to the bridging end contains the block in the block containing the above-mentioned transaction. The second digital signature made by the node device of the chain based on the transaction execution result converts the trust of the business system to the bridge terminal into the trust of the node device in the blockchain; the digital signature verification technology effectively reduces the evil caused by the bridge terminal Data security risks not only reduce the cost of business system access to the blockchain, but also improve the data security of the business system.

Corresponding to the above-mentioned process realization, the embodiment of this specification also provides a block chain transaction device 30 and 40. The devices 30 and 40 can be implemented by software, or can be implemented by hardware or a combination of software and hardware. Taking software implementation as an example, as a logical device, it is formed by reading the corresponding computer program instructions into the memory by the CPU (Central Process Unit, central processing unit) of the device where it is located. From the perspective of hardware, in addition to the CPU, memory, and storage shown in Figure 5, the device where the above-mentioned device is located usually also includes other hardware such as chips for wireless signal transmission and reception, and/or for implementing network communication functions. Other hardware such as boards.

As shown in Fig. 3, this specification also provides a block chain transaction device 30, which is applied to a business system; the business system is connected to a node device of the block chain through a bridge terminal; the device 30 includes:

The sending unit 302 sends the constructed target business transaction to the node device of the blockchain through the bridge end, where the target business transaction includes the business system using the first private key for the target business transaction The first digital signature generated by the detailed data; so that when the node device performs transaction verification, the first digital signature is verified at least based on the first public key corresponding to the first private key, and after the verification is passed Execute the target business transaction, and store the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result to the node device Locally stored blockchain database;

An obtaining unit 304, which obtains the execution result of the target business transaction and the second digital signature from the node device through the bridge terminal;

The verification unit 306 verifies the second digital signature based on the second public key corresponding to the second private key;

The execution unit 308 executes further business processing logic related to the transaction detail data based on the execution result.

In another embodiment, the second digital signature is: the second private key held by the node device of the blockchain is the state stored in the block header of the target block that contains the target business transaction The digital signature generated by the authentication root of the database.

In another embodiment, the state database is a Merkel tree constructed based on state data corresponding to the transaction stored in the target block; the authentication root is the root hash of the Merkel tree.

In another embodiment, the second digital signature is generated by the accounting node device of the blockchain using a second private key held by it, and the second digital signature is stored in the blockchain storage The block header of the target block.

In another embodiment, the second digital signature is generated by the node device using a second private key held by it, and the second digital signature is stored in the target block stored locally by the node device The block header.

In another embodiment, the second digital signature includes: a digital signature generated by the node device using a second private key held by the node device for the execution result of the target business transaction.

In another embodiment, the second digital signature and the execution result, or the second digital signature and the hash digest of the execution result, are stored locally in the node device connected to the bridge end The block header of the target block.

In another embodiment, the obtaining unit 304 is further configured to: pull the target block from the node device through the bridge end to obtain the execution result and the second digital signature; or , Pull the target block from the node device through the bridge terminal to obtain the hash digest of the execution result and the second digital signature; and through the bridge terminal based on the target business transaction The identification is retrieved, and the execution result of the target business transaction is obtained from the node device.

In another embodiment, the second digital signature and the execution result are stored in the state database of the blockchain stored locally in the node device connected to the bridge terminal.

As shown in Figure 4, this specification also provides a blockchain transaction device 40, which is applied to the node equipment of the blockchain; the business system is connected to the node equipment of the blockchain through a bridge end; the device 40 includes :

An acquiring unit 402, the node device connected to the bridge terminal acquires the target business transaction constructed by the business system through the bridge terminal, wherein the target business transaction includes the business system using the first private key as the target The first digital signature generated by the detailed data of the business transaction;

The verification unit 404 performs transaction verification on the target business transaction, where the transaction verification at least includes verifying the first digital signature based on a first public key corresponding to the first private key;

The execution unit 406 executes the target business transaction;

The storage unit 408 stores the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result to a block locally stored by the node device Chain database

The sending unit 410 sends the execution result and the second digital signature to the service system through the bridge terminal, so that the service system verifies the execution result based on the second public key corresponding to the second private key. A second digital signature, and after the verification of the second digital signature is passed, further business processing logic related to the transaction detail data is executed based on the execution result.

In another embodiment, the second digital signature includes: a second private key held by a node device of the blockchain, which is a state stored in a block header of a target block that contains the target business transaction The digital signature generated by the authentication root of the database.

In another embodiment, the second digital signature and the execution result, or the second digital signature and the hash digest of the execution result are stored in the target block stored locally by the node device The block header.

In another embodiment, the sending unit 410 is further configured to: send the target block to the bridge end, so that the business system obtains the target block included in the target block through the bridge end. The execution result and the second digital signature; or, send the target block to the bridge end, so that the business system obtains the hash of the execution result included in the target block through the bridge end The summary and the second digital signature; and based on the retrieval identification of the target business transaction sent by the bridge end, the execution result is sent to the bridge end, so that the business system obtains all information through the bridge end The results of the implementation.

For the implementation process of the functions and roles of each unit in the above-mentioned devices 30 and 40, please refer to the implementation process of the corresponding steps in the blockchain transaction method executed by the above-mentioned business system and the node device side of the blockchain. For related details, please refer to the method implementation. Part of the description of the method is sufficient, so I won't repeat it here.

The device implementations described above are merely illustrative. The units described as separate components may or may not be physically separate, and the components displayed as units may or may not be physical modules, that is, they may be located in One place, or it can be distributed to multiple network modules. Some or all of the units or modules can be selected according to actual needs to achieve the purpose of the solution in this specification. Those of ordinary skill in the art can understand and implement without creative work.

The devices, units, and modules described in the foregoing implementation manners may be specifically implemented by computer chips or entities, or implemented by products with certain functions. A typical implementation device is a computer. The specific form of the computer can be a personal computer, a laptop computer, a cellular phone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email receiving and sending device, and a game control A console, a tablet computer, a wearable device, or a combination of any of these devices.

Corresponding to the foregoing method embodiments, the embodiments of this specification also provide a computer device. As shown in FIG. 5, the computer device includes a memory and a processor. Wherein, the memory stores a computer program that can be run by the processor; when the processor runs the stored computer program, it executes each step of the blockchain transaction method executed by the business system in the embodiment of this specification. For a detailed description of each step of the blockchain transaction method executed by the above business system, please refer to the previous content and will not be repeated.

Corresponding to the foregoing method embodiments, the embodiments of this specification also provide a computer device. As shown in FIG. 5, the computer device includes a memory and a processor. Wherein, the memory stores a computer program that can be run by the processor; when the processor runs the stored computer program, it executes each step of the blockchain transaction method executed by the node device of the blockchain in the embodiment of this specification. For a detailed description of each step of the blockchain transaction method executed by the node device of the above blockchain, please refer to the previous content, and will not be repeated.

The above descriptions are only the preferred embodiments of this specification and are not intended to limit this specification. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of this specification shall be included in this specification. Within the scope of protection.

In a typical configuration, the computing device includes one or more processors (CPUs), input/output interfaces, network interfaces, and memory.

The memory may include non-permanent memory in a computer-readable medium, random access memory (RAM) and/or non-volatile memory, such as read-only memory (ROM) or flash memory (flash RAM). Memory is an example of computer readable media.

Computer-readable media include permanent and non-permanent, removable and non-removable media, and information storage can be realized by any method or technology. Information can be computer-readable instructions, data structures, program modules, or other data.

Examples of computer storage media include, but are not limited to, phase change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technology, CD-ROM, digital versatile disc (DVD) or other optical storage, Magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices or any other non-transmission media can be used to store information that can be accessed by computing devices. According to the definition in this article, computer-readable media does not include transitory media, such as modulated data signals and carrier waves.

It should also be noted that the terms "include", "include" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, commodity or equipment including a series of elements includes not only those elements, but also Other elements that are not explicitly listed, or also include elements inherent to such processes, methods, commodities, or equipment. If there are no more restrictions, the element defined by the sentence "including a..." does not exclude the existence of other identical elements in the process, method, commodity, or equipment that includes the element.

Those skilled in the art should understand that the implementation of this specification can be provided as a method, a system or a computer program product. Therefore, the implementation manners in this specification may adopt the form of a complete hardware implementation, a complete software implementation, or a combination of software and hardware implementations. Moreover, the implementation of this specification may adopt the form of a computer program product implemented on one or more computer-usable storage media (including but not limited to disk storage, CD-ROM, optical storage, etc.) containing computer-usable program codes. .

Claims

A blockchain transaction method, applied to a business system; the business system is connected to a node device of the blockchain through a bridge terminal; the method includes:

The business system sends the constructed target business transaction to the node device of the blockchain through the bridge end, where the target business transaction includes the business system using the first private key to transfer the target business transaction The first digital signature generated by the detailed data, so that the node device

When performing transaction verification, verify the first digital signature based at least on the first public key corresponding to the first private key,

After the verification is passed, the target business transaction is executed, and the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result are stored in The blockchain database locally stored in the node device;

Obtaining the execution result of the target business transaction and the second digital signature from the node device through the bridge terminal;

The second digital signature is verified based on the second public key corresponding to the second private key, and after the verification of the second digital signature is passed, further steps related to the transaction detail data are executed based on the execution result. Business processing logic.
The method according to claim 1, wherein the second digital signature comprises: a second private key held by a node device of the blockchain is stored in a block header of a target block that contains the target business transaction The digital signature generated by the authentication root of the state database.
According to the method of claim 2,

The state database is a Merkel tree constructed based on state data corresponding to transactions stored in the target block;

The authentication root is the root hash of the Merkel tree.
The method according to claim 2 or 3,

The second digital signature is generated by the accounting node device of the blockchain using the second private key held by it,

The second digital signature is stored in the block header of the target block stored in the blockchain.
The method according to claim 2 or 3,

The second digital signature is generated by the node device using the second private key held by it,

The second digital signature is stored in the block header of the target block stored locally in the node device.
The method according to claim 1, wherein the second digital signature comprises: a digital signature generated by the node device using a second private key held by the node device for the execution result of the target business transaction.
According to the method of claim 6,

The second digital signature and the execution result are stored in the block header of the target block locally stored in the node device connected to the bridge end; or,

The second digital signature and the hash digest of the execution result are stored in the block header of the target block stored locally in the node device connected to the bridge end.
The method according to claim 7, wherein the obtaining the execution result of the target service transaction and the second digital signature from the node device through the bridge terminal comprises:

Pull the target block from the node device through the bridge terminal to obtain the execution result and the second digital signature, or the hash digest of the execution result and the second digital signature; and

Obtain the execution result of the target business transaction from the node device through the bridge terminal based on the retrieval identifier of the target business transaction.
According to the method of claim 6, the second digital signature and the execution result are stored in the state database of the blockchain stored locally in the node device connected to the bridge terminal.
According to the method of claim 1, the first private key is stored in a hardware security module HSM carried by the business system.
The method according to claim 1,

The target business transaction is a transfer transaction;

The transaction detail data is blockchain transfer data;

The execution of further business processing logic related to the transaction detail data includes:

Perform remittance operations related to the blockchain transfer data; or,

Perform a refund operation related to the blockchain transfer data.
A block chain transaction method is applied to the node equipment of the block chain; the business system is connected to the node equipment of the block chain through a bridge end; the method includes:

The node device connected to the bridge terminal obtains the target business transaction constructed by the business system through the bridge terminal, wherein the target business transaction includes the business system using the first private key to provide the details of the target business transaction The first digital signature generated by the data;

Performing transaction verification on the target business transaction, the transaction verification at least including verifying the first digital signature based on a first public key corresponding to the first private key;

After the verification is passed, the target business transaction is executed, and the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result are stored in The blockchain database locally stored in the node device;

Send the execution result and the second digital signature to the service system through the bridge end, so that the service system verifies the second digital signature based on the second public key corresponding to the second private key , And after passing the verification of the second digital signature, execute further business processing logic related to the transaction detail data based on the execution result.
The method according to claim 12, wherein the second digital signature comprises: using a second private key held by the node device of the blockchain, storing in the block header of the target block that contains the target business transaction The digital signature generated by the authentication root of the state database.
According to the method of claim 13,

The state database is a Merkel tree constructed based on state data corresponding to transactions stored in the target block;

The authentication root is the root hash of the Merkel tree.
The method according to claim 13 or 14,

The second digital signature is generated by the accounting node device of the blockchain using the second private key held by it,

The second digital signature is stored in the block header of the target block stored in the blockchain.
The method according to claim 13 or 14,

The second digital signature is generated by the node device using the second private key held by it,

The second digital signature is stored in the block header of the target block stored locally in the node device.
The method according to claim 12, wherein the second digital signature comprises: a digital signature generated by the node device using a second private key held by the node device for the execution result of the target business transaction.
According to the method of claim 17,

The second digital signature and the execution result are stored in the block header of the target block stored locally by the node device, or,

The second digital signature and the hash digest of the execution result are stored in the block header of the target block stored locally in the node device.
The method according to claim 18, wherein the sending the execution result and the second digital signature to the service system through the bridge terminal comprises:

Send the target block to the bridge end, so that the business system obtains the execution result and the second digital signature included in the target block through the bridge end, or the execution result is The hash digest and the second digital signature; and

Based on the retrieval identifier of the target business transaction sent by the bridge terminal, send the execution result to the bridge terminal, so that the business system obtains the execution result through the bridge terminal.
According to the method of claim 17, the second digital signature and the execution result are stored in the state database of the blockchain stored locally in the node device connected to the bridge terminal.
According to the method of claim 12, the first private key is stored in a hardware security module HSM carried by the business system.
According to the method of claim 12,

The target business transaction is a transfer transaction;

The transaction detail data is blockchain transfer data;

The execution of further business processing logic related to the transaction detail data includes:

Perform remittance operations related to the blockchain transfer data; or,

Perform a refund operation related to the blockchain transfer data.
A block chain transaction device is applied to a business system; the business system is connected to a node device of the block chain through a bridge terminal; the device includes:

A sending unit, which sends the constructed target business transaction to the node device of the blockchain through the bridge end, where the target business transaction includes the details of the target business transaction using the first private key by the business system Data generated by the first digital signature so that the node device

When performing transaction verification, verify the first digital signature based at least on the first public key corresponding to the first private key,

After the verification is passed, the target business transaction is executed, and the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using the second private key for the execution result are stored in The blockchain database locally stored in the node device;

An obtaining unit, which obtains the execution result of the target business transaction and the second digital signature from the node device through the bridge terminal;

A verification unit that verifies the second digital signature based on a second public key corresponding to the second private key;

The execution unit executes further business processing logic related to the transaction detail data based on the execution result.
The apparatus according to claim 23, wherein the second digital signature is: the node device of the blockchain uses a second private key held by the node device, and is stored in the block header of the target block that contains the target business transaction. The digital signature generated by the authentication root of the state database.
The device according to claim 24,

The state database is a Merkel tree constructed based on state data corresponding to transactions stored in the target block;

The authentication root is the root hash of the Merkel tree.
The device according to claim 24 or 25,

The second digital signature is generated by the accounting node device of the blockchain using the second private key held by it,

The second digital signature is stored in the block header of the target block stored in the blockchain.
The device according to claim 24 or 25,

The second digital signature is generated by the node device using the second private key held by it,

The second digital signature is stored in the block header of the target block stored locally in the node device.
The apparatus according to claim 23, wherein the second digital signature comprises: a digital signature generated by the node device using a second private key held by the node device for the execution result of the target business transaction.
The device according to claim 28,

The second digital signature and the execution result are stored in the block header of the target block locally stored in the node device connected to the bridge end; or,

The second digital signature and the hash digest of the execution result are stored in the block header of the target block stored locally in the node device connected to the bridge end.
The device according to claim 29, the acquiring unit is further configured to:

Pull the target block from the node device through the bridge terminal to obtain the execution result and the second digital signature or the hash digest of the execution result and the second digital signature; and

Obtain the execution result of the target business transaction from the node device through the bridge terminal based on the retrieval identifier of the target business transaction.
The apparatus according to claim 28, wherein the second digital signature and the execution result are stored in the state database of the blockchain stored locally in the node device connected to the bridge terminal.
A block chain transaction device is applied to the node equipment of the block chain; the business system is connected with the node equipment of the block chain through a bridge end; the device includes:

An acquiring unit, where the node device connected to the bridge terminal acquires the target business transaction constructed by the business system through the bridge terminal, wherein the target business transaction includes the business system using the first private key for the target business The first digital signature generated by the transaction detail data;

A verification unit for performing transaction verification on the target business transaction, the transaction verification at least including verifying the first digital signature based on a first public key corresponding to the first private key;

An execution unit to execute the target business transaction;

A storage unit that stores the execution result of the target business transaction and the second digital signature generated by the node device in the blockchain using a second private key for the execution result to the blockchain locally stored by the node device database;

The sending unit sends the execution result and the second digital signature to the service system through the bridge terminal, so that the service system verifies the first based on the second public key corresponding to the second private key 2. A digital signature, and after the verification of the second digital signature is passed, further business processing logic related to the transaction detail data is executed based on the execution result.
The apparatus according to claim 32, wherein the second digital signature comprises: a second private key held by a node device of the blockchain, stored in a block header of a target block that contains the target business transaction The digital signature generated by the authentication root of the state database.
The device according to claim 33,

The state database is a Merkel tree constructed based on state data corresponding to transactions stored in the target block;

The authentication root is the root hash of the Merkel tree.
The device according to claim 33 or 34,

The second digital signature is generated by the accounting node device of the blockchain using the second private key held by it,

The second digital signature is stored in the block header of the target block stored in the blockchain.
The device according to claim 33 or 34,

The second digital signature is generated by the node device using the second private key held by it,

The second digital signature is stored in the block header of the target block stored locally in the node device.
The apparatus according to claim 32, wherein the second digital signature comprises: a digital signature generated by the node device using a second private key held by the node device for the execution result of the target business transaction.
The device according to claim 37,

The second digital signature and the execution result, the second digital signature and the hash digest of the execution result are stored in the block header of the target block stored locally in the node device; or,

The second digital signature and the hash digest of the execution result are stored in the block header of the target block stored locally in the node device.
The device according to claim 38, the sending unit is further configured to:

Send the target block to the bridge end, so that the business system obtains the execution result and the second digital signature included in the target block through the bridge end, or the hash of the execution result Greek digest and said second digital signature; and

Based on the retrieval identifier of the target business transaction sent by the bridge terminal, the execution result is sent to the bridge terminal, so that the business system obtains the execution result through the bridge terminal.
The apparatus according to claim 37, wherein the second digital signature and the execution result are stored in the state database of the blockchain stored locally in the node device connected to the bridge terminal.
A computer device including a memory and a processor;

A computer program that can be run by the processor is stored on the memory;

When the processor runs the computer program, the method according to any one of claims 1 to 11 is executed.
A computer device including a memory and a processor;

A computer program that can be run by the processor is stored on the memory;

When the processor runs the computer program, the method according to any one of claims 12 to 22 is executed.