CN114387104A - Cross-block-chain data pushing method and device - Google Patents

Cross-block-chain data pushing method and device Download PDF

Info

Publication number
CN114387104A
CN114387104A CN202210036205.XA CN202210036205A CN114387104A CN 114387104 A CN114387104 A CN 114387104A CN 202210036205 A CN202210036205 A CN 202210036205A CN 114387104 A CN114387104 A CN 114387104A
Authority
CN
China
Prior art keywords
transaction
data
blockchain
identifier
intelligent contract
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Pending
Application number
CN202210036205.XA
Other languages
Chinese (zh)
Inventor
赵文强
李艳鹏
陆旭明
陈辰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Alipay Hangzhou Information Technology Co Ltd
Ant Blockchain Technology Shanghai Co Ltd
Original Assignee
Alipay Hangzhou Information Technology Co Ltd
Ant Blockchain Technology Shanghai Co Ltd
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Alipay Hangzhou Information Technology Co Ltd, Ant Blockchain Technology Shanghai Co Ltd filed Critical Alipay Hangzhou Information Technology Co Ltd
Priority to CN202210036205.XA priority Critical patent/CN114387104A/en
Publication of CN114387104A publication Critical patent/CN114387104A/en
Pending legal-status Critical Current

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
    • G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/602—Providing cryptographic facilities or services
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06F—ELECTRIC DIGITAL DATA PROCESSING
    • G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
    • G06F21/60—Protecting data
    • G06F21/62—Protecting access to data via a platform, e.g. using keys or access control rules
    • G06F21/6218—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database
    • G06F21/6227—Protecting access to data via a platform, e.g. using keys or access control rules to a system of files or objects, e.g. local or distributed file system or database where protection concerns the structure of data, e.g. records, types, queries

Landscapes

  • Engineering & Computer Science (AREA)
  • Theoretical Computer Science (AREA)
  • Physics & Mathematics (AREA)
  • Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Finance (AREA)
  • General Engineering & Computer Science (AREA)
  • Software Systems (AREA)
  • Computer Security & Cryptography (AREA)
  • Computer Hardware Design (AREA)
  • Bioethics (AREA)
  • General Health & Medical Sciences (AREA)
  • Accounting & Taxation (AREA)
  • Health & Medical Sciences (AREA)
  • Economics (AREA)
  • General Business, Economics & Management (AREA)
  • Technology Law (AREA)
  • Strategic Management (AREA)
  • Marketing (AREA)
  • Development Economics (AREA)
  • Databases & Information Systems (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

The embodiment of the specification provides a data pushing method and device of a cross-block chain. The method is executed by a data pushing device crossing block chains, wherein the data pushing device is respectively connected with a first block chain and a second block chain, and the method comprises the following steps: receiving a data push request, wherein the data push request comprises a transaction identifier of a first transaction in the first blockchain; acquiring the first transaction from the first blockchain, wherein the first transaction comprises first data; and sending a second transaction to the second blockchain, wherein the second transaction comprises second data acquired based on the first data.

Description

Cross-block-chain data pushing method and device
Technical Field
One or more embodiments of the present disclosure relate to the field of blockchains, and in particular, to a method and an apparatus for pushing data across blockchains.
Background
The Blockchain (Blockchain) is a novel application mode of computer technologies such as distributed data storage, point-to-point transmission, a consensus mechanism, an encryption algorithm and the like. Because the blockchain has the characteristics of decentralization, information non-tampering, autonomy and the like, the blockchain is also paid more and more attention and is applied by people.
In some service scenarios, data stored in a certain blockchain needs to be pushed to other blockchains.
Disclosure of Invention
One or more embodiments of the present specification provide a method and an apparatus for pushing data across a block chain.
In a first aspect, a method for pushing data across a blockchain is provided, where the method is performed by a data pushing apparatus, and the data pushing apparatus is connected to a first blockchain and a second blockchain, respectively. The method comprises the following steps: receiving a data push request, wherein the data push request comprises a transaction identifier of a first transaction in the first blockchain; acquiring the first transaction from the first blockchain, wherein the first transaction comprises first data; and sending a second transaction to the second blockchain, wherein the second transaction comprises second data acquired based on the first data.
In one possible embodiment, the second data is the first data.
In one possible embodiment, the first data is a ciphertext generated by encrypting the second data with a first key. The method further comprises the following steps: and decrypting the first data by using a second key corresponding to the first key to obtain the second data.
In one possible embodiment, the method further comprises: generating a digital signature corresponding to the second data in a trusted execution environment; generating the second transaction, wherein the digital signature is also included in the second transaction.
In one possible embodiment, the second transaction is used to invoke a first smart contract in the second blockchain, causing the first smart contract to verify the second data in accordance with the digital signature.
In one possible implementation, the first intelligent contract is further configured to invoke a second intelligent contract in the second blockchain to pass the second data to the second intelligent contract if the second data is validated.
In one possible embodiment, the method further comprises: receiving block headers for the respective blocks it generates from the first chain of blocks; receiving a merkle tree path corresponding to the first transaction from the first blockchain; and performing simple payment verification on the first transaction according to the merkle tree path and each block head.
In one possible embodiment, the method further comprises: and verifying each block header.
In one possible embodiment, the obtaining the first transaction from the first blockchain includes: and sending a third transaction to the first blockchain, wherein the third transaction comprises a transaction identifier of the first transaction, and the third transaction is used for calling a third intelligent contract in the first blockchain, so that the third intelligent contract returns to the first transaction according to the transaction identifier of the first transaction.
In a possible implementation manner, the third transaction further includes a chain identifier of the second blockchain, and the third smart contract is further configured to record, according to the transaction identifier and the chain identifier, push information for indicating that the second data has been pushed to the second blockchain.
In a second aspect, a data pushing apparatus across block chains is provided, and the data pushing apparatus is connected to a first block chain and a second block chain respectively. The device comprises: a receiving unit configured to receive a data push request, where the data push request includes a transaction identifier of a first transaction in the first blockchain; the query unit is configured to acquire the first transaction from the first blockchain, and the first transaction comprises first data; a sending unit configured to send a second transaction to the second blockchain, wherein the second transaction includes second data acquired based on the first data.
In one possible embodiment, the second data is the first data.
In one possible embodiment, the first data is a ciphertext generated by encrypting the second data with a first key; the device further comprises: and the decryption processing unit is configured to decrypt the first data by using a second key corresponding to the first key to obtain the second data.
In a possible embodiment, the apparatus further comprises: the signature processing unit is configured to generate a digital signature corresponding to the second data in a trusted execution environment; a transaction generation unit configured to generate the second transaction, wherein the digital signature is further included in the second transaction.
In one possible embodiment, the second transaction is used to invoke a first smart contract in the second blockchain, causing the first smart contract to verify the second data in accordance with the digital signature.
In one possible implementation, the first intelligent contract is further configured to invoke a second intelligent contract in the second blockchain to pass the second data to the second intelligent contract if the second data is validated.
In a possible implementation, the receiving unit is further configured to receive, from the first block chain, a block header of each block it generates; and receiving a merkle tree path corresponding to the first transaction from the first blockchain. The device further comprises: and the verification unit is configured to perform simple payment verification on the first transaction according to the merkle tree path and each block head.
In a possible implementation manner, the verification unit is further configured to verify each of the block headers.
In a possible implementation manner, the query unit is specifically configured to send a third transaction to the first blockchain, where the third transaction includes the transaction identifier, and the third transaction is used to invoke a third intelligent contract in the first blockchain, so that the third intelligent contract returns to the first transaction according to the transaction identifier.
In a possible implementation manner, the third transaction further includes a chain identifier of the second blockchain, and the third smart contract is further configured to record, according to the transaction identifier and the chain identifier, push information for indicating that the second data has been pushed to the second blockchain.
In a third aspect, there is provided a computer readable storage medium having stored thereon a computer program/instructions which, when executed in a computing device, implement the method of any one of the first aspects.
By the method and the device provided in one or more embodiments of the present specification, a data push device across a blockchain receives and responds to a data push request from an application program, so as to query a corresponding transaction from a first blockchain, and push data to a second blockchain based on data contained in the transaction. An intelligent contract for supporting data pushing does not need to be deployed in the blockchain serving as the data sending party, corresponding authority configuration is not needed to be performed on the application program in the blockchain serving as the sending party, and data pushing across the blockchain according to the expectation of the application program can be achieved more conveniently and rapidly.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present disclosure, the drawings used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present disclosure, and it is obvious for those skilled in the art that other drawings can be obtained according to the drawings without creative efforts.
Fig. 1 is a schematic diagram of an application scenario of the technical solution provided in the embodiment of the present specification;
fig. 2 is a flowchart of a data pushing method across block chains provided in an embodiment of the present specification;
fig. 3 is a flowchart of another data pushing method across block chains provided in an embodiment of the present specification;
fig. 4 is a schematic diagram of a data pushing apparatus across a block chain provided in an embodiment of the present specification.
Detailed Description
Various non-limiting embodiments provided by the present specification are described in detail below with reference to the attached figures.
Fig. 1 is a schematic diagram of an application scenario of the technical solution provided in the embodiment of the present specification. As shown in fig. 1, for a transaction TX _1 stored in the first block chain, its Data field may contain corresponding traffic Data; other applications may desire to push the traffic data in transaction TX _1 to the second blockchain, e.g., to store the traffic data to the second blockchain, or to pass the traffic data to an intelligent Contract _1 deployed into the second blockchain via transaction TX _ 2.
In one possible implementation, a corresponding intelligent contract may be deployed in a first blockchain as a data sender, and an application may implement pushing data stored in the first blockchain to a second blockchain as a data receiver by calling the intelligent contract. However, in this embodiment, an intelligent contract for supporting data push needs to be written additionally and deployed into the first blockchain, and the access right of the application program to the intelligent contract needs to be configured in the first blockchain.
The embodiment of the specification provides a method and a device for data pushing across block chains, an intelligent contract for supporting data pushing does not need to be deployed in a block chain serving as a data sending party, corresponding authority configuration does not need to be performed on an application program in the block chain, and data pushing across the block chains according to expectation of the application program can be achieved more conveniently and rapidly.
Fig. 2 is a flowchart of a data pushing method across a block chain provided in an embodiment of the present specification. The method can be executed by a data pushing device crossing block chains, and the device is respectively connected with a plurality of block chains as independent middleware, for example, is connected with a first block chain as a data sending party and is connected with a second block chain as a data receiving party. The data pushing means across the blockchain may be implemented as any device, platform or cluster of devices with computing/processing capabilities. In addition, in terms of a hardware environment, the data pushing device crossing the block chain can comprise a trusted execution environment and an untrusted execution environment corresponding to the trusted execution environment; in other words, a software program used by a data push across a blockchain may include a trusted processing unit running in a trusted execution environment and an untrusted processing unit running in an untrusted execution environment. For each method step described below, the method step may be performed in either a trusted execution environment or an untrusted execution environment unless specifically stated to be required to be performed in a trusted execution environment; in other words, for each method step that is not specifically stated as being required in a viable execution environment, it may be executed by either the untrusted processing unit or the trusted processing unit. As shown in fig. 2, the method may include at least the following steps 201 to 205.
First, in step 201, a data push request is received, the data push request including a transaction identification of a first transaction in a first blockchain.
The data pushing device receives a data pushing request from a corresponding application program, where the application program may be deployed in a terminal device, may also be deployed in a data pushing device across block chains, and may also be deployed in a block chain node of a certain block chain connected to the data pushing device. The transaction identification of the first transaction may include, but is not limited to, a hash value of the first transaction. If the first block chain as the data sender is not predetermined in the data pushing device, the data pushing request may further include a chain identifier of the first block chain; similarly, if the second blockchain as the data receiver is not predetermined in the data pushing apparatus, the data pushing request may further include a chain identifier of the second blockchain.
Next, in step 203, a first transaction is obtained from the first blockchain, the first transaction including first data.
The data push device may determine the first blockchain as the data sender in advance, or determine the first blockchain as the data sender based on a chain identifier of the first blockchain in the data push request, and then obtain the first transaction from the first blockchain according to the transaction identifier of the first transaction. In one example, the data pushing device may send a query request to the first blockchain, the query request including a transaction identifier of the first transaction, so that the first blockchain returns the first transaction based on the transaction identifier. In another example, the data push device may send a third transaction to the first blockchain, the third transaction including a transaction identifier of the first transaction, the third transaction being used to invoke a third intelligent contract in the first blockchain, such that when the first blockchain executes the third intelligent contract based on the third transaction, the third intelligent contract may query the first transaction in the first blockchain according to the transaction identifier of the first transaction and return the queried first transaction to the data push device.
In a more specific example, the aforementioned third transaction may further include a chain identifier of a second block chain as a data receiver, and when the first block chain executes a third intelligent contract based on the third transaction, the third intelligent contract may further record push information according to the transaction identifier of the first transaction and the chain identifier of the second block chain, where the push information is used to indicate that corresponding data has been pushed to the second block chain, for example, to indicate that first data in the first transaction or second data obtained based on the first data has been pushed to the second block chain. In this manner, the application program can learn about the data that it has pushed to the second blockchain by initiating a query transaction to the first blockchain to invoke the third intelligent contract.
In order to enable the data push device to perform simple payment verification on the first transaction from the first blockchain, the data push device may also receive the blockheaders of the respective blocks it generates from the first blockchain. In other words, referring to fig. 3, the method may further include step 301 of receiving the block header of each block generated by the first block chain. The data pushing device can periodically receive the block headers of the blocks generated in the current period from the first block chain; or after each new block is generated in the first block chain, the data pushing device obtains the block header of the block from the first block chain.
On the basis of the foregoing step 301, the method may further include a step 303 of verifying each block header. The verifying each block header means verifying whether information in each block header satisfies a specific condition, for example, verifying whether block heights in each block header are continuous. Correspondingly, the data pushing device may allow the data pushing device to continue to perform the step 203 on the basis of the step 201 specifically when each block header received by the data pushing device passes the verification.
In order to enable the data pushing device to perform simple payment verification on the first transaction from the first blockchain, when the first blockchain returns the first transaction to the data pushing device, a merkle tree path corresponding to the first transaction may also be returned to the data pushing device. In other words, referring to fig. 3, the method may further include receiving 305 a merkle tree path corresponding to the first transaction from the first blockchain.
Correspondingly, on the basis of the foregoing steps 301 to 305, the method may further include step 307, performing simple payment verification on the first transaction according to the merkle tree path and the block headers corresponding to the first transaction. For example, a merkle root corresponding to a block to which the first transaction belongs can be calculated according to the first transaction and the corresponding merkle tree path thereof, and if the merkle root is the same as the merkle root in any block head, the first transaction is verified through simple payment. In the case that the first transaction passes the simple payment verification, the subsequent steps may be continued, otherwise the subsequent steps may not be performed.
The first Data may be, for example, a field value of a Data field in the first transaction. When the first transaction passes the simple payment verification and the first data is clear text which is not encrypted, the first data is the second data which needs to be pushed to the second block chain. When the first transaction is verified through the simple payment and the first data is a ciphertext generated by encrypting the second data with the first key, the method may further include: 3091, decrypting the first data by using a second key corresponding to the first key to obtain second data; step 3093, a digital signature corresponding to the second data is generated in the trusted execution environment.
To implement pushing the second data to the second blockchain, the method may further include step 3095, generating a second transaction, where the second transaction includes at least the second data and optionally a digital signature corresponding to the second data.
Next, at step 205, a second transaction is sent to the second blockchain.
When the second transaction includes the second data but not its corresponding digital signature, the second transaction may be used to enable storage of the second data to the second blockchain, or the second transaction may also be used to invoke a second smart contract in the second blockchain to transfer the second data to the second smart contract.
When the second transaction includes the second data and its corresponding digital signature, the second transaction may be used to invoke the first smart contract in the second blockchain, so that the first smart contract verifies the second data in the second transaction according to the digital signature. Correspondingly, in the case that the second data is verified, the first intelligent contract can also continue to call the second intelligent contract in the second block chain to transfer the second data in the second transaction to the second intelligent contract.
It should be noted that, when the second transaction directly or indirectly calls the second intelligent contract in the second block chain in the foregoing manner, the second transaction sent by the Data pushing device may also include a contract address of the second intelligent contract, for example, the Data field of the second transaction includes the contract address of the second intelligent contract. The contract address of the second intelligent contract is, for example, a data push request received from the data push device, and the second intelligent contract is directionally pushed to the second intelligent contract in the second block chain according to the desire of the application program, wherein the second data stored in the first block chain is plaintext or encrypted.
Based on the same concept as the foregoing method embodiment, in this specification embodiment, a data pushing apparatus across block chains is further provided, where the apparatus is connected to a first block chain as a data sending side and a second block chain as a data receiving side, respectively. As shown in fig. 4, the apparatus may include at least: the data push device is respectively connected with the first block chain and the second block chain, and the device comprises: a receiving unit 401 configured to receive a data push request, where the data push request includes a transaction identifier of a first transaction in the first blockchain; a querying unit 402, configured to obtain the first transaction from the first blockchain, where the first transaction includes first data; a sending unit 403, configured to send a second transaction to the second blockchain, where the second transaction includes second data obtained based on the first data.
In one possible embodiment, the second data is the first data.
In one possible embodiment, the first data is a ciphertext generated by encrypting the second data with a first key. The device further comprises: a decryption processing unit 404 configured to decrypt the first data by using a second key corresponding to the first key to obtain the second data.
In a possible embodiment, the apparatus further comprises: a signature processing unit 405 configured to generate a digital signature corresponding to the second data in a trusted execution environment; a transaction generating unit 406 configured to generate the second transaction, wherein the digital signature is further included in the second transaction.
In one possible embodiment, the second transaction is used to invoke a first smart contract in the second blockchain, causing the first smart contract to verify the second data in accordance with the digital signature.
In one possible implementation, the first intelligent contract is further configured to invoke a second intelligent contract in the second blockchain to pass the second data to the second intelligent contract if the second data is validated.
In a possible implementation, the receiving unit 401 is further configured to receive, from the first block chain, a block header of each block it generates; and receiving a merkle tree path corresponding to the first transaction from the first blockchain. The device further comprises: a verification unit 407 configured to perform a simple payment verification on the first transaction according to the merkle tree path and each of the block headers.
In a possible implementation manner, the verification unit 407 is further configured to verify each of the block headers.
In a possible implementation manner, the querying unit 402 is specifically configured to send a third transaction to the first blockchain, where the third transaction includes the transaction identifier, and the third transaction is used to invoke a third intelligent contract in the first blockchain, so that the third intelligent contract returns to the first transaction according to the transaction identifier.
In a possible implementation manner, the third transaction further includes a chain identifier of the second blockchain, and the third smart contract is further configured to record, according to the transaction identifier and the chain identifier, push information for indicating that the second data has been pushed to the second blockchain.
Those skilled in the art will recognize that in one or more of the examples described above, the functions described in this specification can be implemented in hardware, software, firmware, or any combination thereof. When implemented in software, a computer program corresponding to these functions may be stored in a computer-readable medium or transmitted as one or more instructions/codes on the computer-readable medium, so that when the computer program corresponding to these functions is executed by a computer, the method described in any one of the embodiments of the present specification is implemented by the computer.
Also provided in an embodiment of the present specification is a computer-readable storage medium, on which a computer program/instruction is stored, when the computer program/instruction is executed in a computing device, the computing device executes a data push method across a blockchain provided in any one of embodiments of the present specification.
The embodiments in the present description are described in a progressive manner, and the same and similar parts in the embodiments are referred to each other, and each embodiment focuses on the differences from the other embodiments. In particular, as for the apparatus embodiment, since it is substantially similar to the method embodiment, the description is relatively simple, and for the relevant points, reference may be made to the partial description of the method embodiment.
The foregoing description has been directed to specific embodiments of this disclosure. Other embodiments are within the scope of the following claims. In some cases, the actions or steps recited in the claims may be performed in a different order than in the embodiments and still achieve desirable results. In addition, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In some embodiments, multitasking and parallel processing may also be possible or may be advantageous.
The above-mentioned embodiments, objects, technical solutions and advantages of the present invention are further described in detail, it should be understood that the above-mentioned embodiments are only exemplary embodiments of the present invention, and are not intended to limit the scope of the present invention, and any modifications, equivalent substitutions, improvements and the like made on the basis of the technical solutions of the present invention should be included in the scope of the present invention.

Claims (19)

1. A method of data push across blockchains, the method being performed by a data push device connected to a first blockchain and a second blockchain, respectively, the method comprising:
receiving a data push request, wherein the data push request comprises a transaction identifier of a first transaction in the first blockchain;
acquiring the first transaction from the first blockchain, wherein the first transaction comprises first data;
and sending a second transaction to the second blockchain, wherein the second transaction comprises second data acquired based on the first data.
2. The method of claim 1, wherein the second data is the first data; alternatively, the first and second electrodes may be,
the first data is a ciphertext generated by encrypting the second data with a first key; the method further comprises the following steps: and decrypting the first data by using a second key corresponding to the first key to obtain the second data.
3. The method of claim 1, wherein the method further comprises:
generating a digital signature corresponding to the second data in a trusted execution environment;
generating the second transaction, wherein the digital signature is also included in the second transaction.
4. The method of claim 3, wherein the second transaction is used to invoke a first smart contract in the second blockchain, causing the first smart contract to verify the second data in accordance with the digital signature.
5. The method of claim 4, wherein the first intelligent contract is further configured to invoke a second intelligent contract in the second blockchain to pass the second data to the second intelligent contract if the second data is validated.
6. The method of any of claims 1-5, further comprising:
receiving block headers for the respective blocks it generates from the first chain of blocks;
receiving a merkle tree path corresponding to the first transaction from the first blockchain;
and performing simple payment verification on the first transaction according to the merkle tree path and each block head.
7. The method of claim 6, further comprising: and verifying each block header.
8. The method of any of claims 1-5, wherein the obtaining the first transaction from the first blockchain comprises: and sending a third transaction to the first blockchain, wherein the third transaction comprises the transaction identifier, and the third transaction is used for calling a third intelligent contract in the first blockchain, so that the third intelligent contract returns to the first transaction according to the transaction identifier.
9. The method of claim 8, wherein the third transaction further comprises a chain identifier of the second blockchain, and the third smart contract is further configured to record push information indicating that the second data has been pushed to the second blockchain according to the transaction identifier and the chain identifier.
10. A data pushing apparatus across blockchains, the data pushing apparatus being connected to a first blockchain and a second blockchain, respectively, the apparatus comprising:
a receiving unit configured to receive a data push request, where the data push request includes a transaction identifier of a first transaction in the first blockchain;
the query unit is configured to acquire the first transaction from the first blockchain, and the first transaction comprises first data;
a sending unit configured to send a second transaction to the second blockchain, wherein the second transaction includes second data acquired based on the first data.
11. The apparatus of claim 10, wherein the second data is the first data; alternatively, the first and second electrodes may be,
the first data is a ciphertext generated by encrypting the second data with a first key; the device further comprises: and the decryption processing unit is configured to decrypt the first data by using a second key corresponding to the first key to obtain the second data.
12. The apparatus of claim 10, the apparatus further comprising:
the signature processing unit is configured to generate a digital signature corresponding to the second data in a trusted execution environment;
a transaction generation unit configured to generate the second transaction, wherein the digital signature is further included in the second transaction.
13. The apparatus of claim 12, wherein the second transaction is to invoke a first smart contract in the second blockchain, causing the first smart contract to verify the second data in accordance with the digital signature.
14. The apparatus of claim 13, wherein the first intelligent contract is further configured to invoke a second intelligent contract in the second blockchain to pass the second data to the second intelligent contract if the second data is validated.
15. The apparatus according to any of claims 10-14, wherein the receiving unit is further configured to receive, from the first chain of blocks, block headers of respective blocks it generates; and receiving a merkle tree path corresponding to the first transaction from the first blockchain;
the device further comprises: and the verification unit is configured to perform simple payment verification on the first transaction according to the merkle tree path and each block head.
16. The apparatus of claim 15, wherein the verification unit is further configured to verify each of the block headers.
17. The apparatus according to any of claims 10-14, wherein the query unit is specifically configured to send a third transaction to the first blockchain, the third transaction including the transaction identifier, the third transaction being configured to invoke a third intelligent contract in the first blockchain, so that the third intelligent contract returns to the first transaction according to the transaction identifier.
18. The apparatus of claim 17, wherein the third transaction further comprises a chain identifier of the second blockchain, and the third smart contract is further configured to record push information indicating that the second data has been pushed to the second blockchain according to the transaction identifier and the chain identifier.
19. A computer-readable storage medium having stored thereon a computer program which, when executed in a computing device, performs the method of any of claims 1-9.
CN202210036205.XA 2022-01-13 2022-01-13 Cross-block-chain data pushing method and device Pending CN114387104A (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202210036205.XA CN114387104A (en) 2022-01-13 2022-01-13 Cross-block-chain data pushing method and device

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202210036205.XA CN114387104A (en) 2022-01-13 2022-01-13 Cross-block-chain data pushing method and device

Publications (1)

Publication Number Publication Date
CN114387104A true CN114387104A (en) 2022-04-22

Family

ID=81201940

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202210036205.XA Pending CN114387104A (en) 2022-01-13 2022-01-13 Cross-block-chain data pushing method and device

Country Status (1)

Country Link
CN (1) CN114387104A (en)

Similar Documents

Publication Publication Date Title
CN107483419B (en) Method, device and system for authenticating access terminal by server, server and computer readable storage medium
CN111047450A (en) Method and device for calculating down-link privacy of on-link data
CN112637836B (en) Data processing method and device, electronic equipment and storage medium
EP3779792B1 (en) Two-dimensional code generation method, data processing method, apparatus, and server
US11546348B2 (en) Data service system
CN110543510B (en) Bill data processing method, device, storage medium and computer equipment
CN110781140B (en) Method, device, computer equipment and storage medium for signing data in blockchain
CN111131416A (en) Business service providing method and device, storage medium and electronic device
CN104836784A (en) Information processing method, client, and server
CN112383522B (en) Function parameter data transmission encryption method, system, device and readable storage medium
CN111639108A (en) Data query method and device, electronic equipment and computer readable storage medium
CN114142995B (en) Key security distribution method and device for block chain relay communication network
CN111314309B (en) Data transmission method and device, electronic equipment and computer readable storage medium
CN114553590A (en) Data transmission method and related equipment
CN115664655A (en) TEE credibility authentication method, device, equipment and medium
CN111414640A (en) Key access control method and device
CN101980471A (en) Digital signature method, and method, device and system for verifying digital signature
CN116455572B (en) Data encryption method, device and equipment
CN110266478B (en) Information processing method and electronic equipment
CN114172923B (en) Data transmission method, communication system and communication device
CN114387104A (en) Cross-block-chain data pushing method and device
CN114143038A (en) Key secure distribution method and device for block chain relay communication network
CN112862488A (en) Data signature method and device, electronic equipment and computer readable storage medium
CN111414588B (en) Authorization key generation method, authorization key generation device and authorization server
CN113486375B (en) Storage method and device of equipment information, storage medium and electronic device

Legal Events

Date Code Title Description
PB01 Publication
PB01 Publication
SE01 Entry into force of request for substantive examination
SE01 Entry into force of request for substantive examination