WO2021103998A1 - Procédé de signature de transactions de chaînes de blocs croisées et dispositif - Google Patents

Procédé de signature de transactions de chaînes de blocs croisées et dispositif Download PDF

Info

Publication number
WO2021103998A1
WO2021103998A1 PCT/CN2020/127566 CN2020127566W WO2021103998A1 WO 2021103998 A1 WO2021103998 A1 WO 2021103998A1 CN 2020127566 W CN2020127566 W CN 2020127566W WO 2021103998 A1 WO2021103998 A1 WO 2021103998A1
Authority
WO
WIPO (PCT)
Prior art keywords
cross
blockchain
chain component
chain
transaction
Prior art date
Application number
PCT/CN2020/127566
Other languages
English (en)
Chinese (zh)
Inventor
石翔
莫楠
李辉忠
张开翔
范瑞彬
Original Assignee
深圳前海微众银行股份有限公司
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 深圳前海微众银行股份有限公司 filed Critical 深圳前海微众银行股份有限公司
Publication of WO2021103998A1 publication Critical patent/WO2021103998A1/fr

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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/08—Payment architectures
    • G06Q20/085—Payment architectures involving remote charge determination or related payment systems
    • 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
    • G06Q20/00—Payment architectures, schemes or protocols
    • G06Q20/38—Payment protocols; Details thereof
    • G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
    • G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management

Definitions

  • the embodiment of the present invention relates to the field of financial technology (Fintech), and in particular to a method and device for signing a cross-chain transaction in the field of blockchain.
  • Fetech financial technology
  • the client needs to operate on different types of blockchains at the same time and send transactions to different types of blockchains, but the signature algorithms of different types of blockchains are different.
  • a client corresponds to the ether at the same time.
  • Blockchain and Bitcoin Blockchain When the client needs to send a transaction to the Ethereum blockchain, the transaction is signed and sent according to the signature algorithm of the Ethereum blockchain.
  • the client When it comes to the Bitcoin blockchain, the transaction is sent after it is signed according to the signature algorithm of the Bitcoin blockchain.
  • the client needs to locally configure signature algorithms corresponding to different types of blockchains, and before sending a transaction, it needs to determine the signature algorithm of the target blockchain and sign according to the signature algorithm.
  • This method has higher requirements on the client and increases the complexity of the client.
  • the embodiments of the present invention provide a cross-chain transaction signature method and device to solve the problem of high complexity of the client in the prior art.
  • a method for signing a cross-chain transaction includes:
  • the first cross-chain component sends an upload request to the second cross-chain component; the first cross-chain component corresponds to the client, and the second cross-chain component corresponds to the blockchain; the upload request is the The first cross-chain component is determined according to the client's data to be uploaded to the chain;
  • the first cross-chain component receives the transaction to be signed sent by the second cross-chain component and the signature algorithm of the blockchain; the transaction to be signed is the second cross-chain component according to the on-chain request and Generated by the state information of the blockchain;
  • the first cross-chain component signs the transaction to be signed using the user’s private key according to the signature algorithm, and sends the generated signed transaction to the second cross-chain component, so that the second cross-chain component Send the signed transaction to the blockchain.
  • the signature algorithm is a signature algorithm of the blockchain configured locally in the second cross-chain component; the user private key is configured locally in the client of the first cross-chain component User private key.
  • the blockchain has multiple types, and different types of blockchains have different signature algorithms; for each blockchain, the local configuration of the second cross-chain component corresponding to the blockchain is different.
  • the data to be uploaded includes the identifier and transaction content of the target blockchain corresponding to the data to be uploaded;
  • the first cross-chain component sending an on-chain request to the second cross-chain component includes:
  • the first cross-chain component generates the chain request according to the transaction content
  • the first cross-chain component sends the upload request to the second cross-chain component corresponding to the target blockchain.
  • a first cross-chain component corresponding to the client and a second cross-chain component corresponding to the blockchain are deployed.
  • the first cross-chain component is used to receive the data to be uploaded from the client and generate an upload request.
  • the second cross-chain component is used to receive the on-chain request sent by the first cross-chain component and generate a transaction for on-chain but not yet signed according to the state information of the blockchain, and send the signature algorithm of the blockchain to the first A cross-chain component so that the first cross-chain component uses the user's private key to sign the transaction that has not been signed according to the signature algorithm.
  • the first cross-chain component is used to sign according to the user’s private key
  • the second cross-chain component is used to provide the corresponding signature algorithm for the first cross-chain component.
  • the interaction between the client can realize that the client only needs to submit the data to be uploaded to the first cross-chain component, without the client signing the transaction according to the signature algorithm of different types of blockchains, which reduces the complexity of the client.
  • the client corresponds to the first cross-chain component.
  • the data to be uploaded is in a fixed format, and the client does not need to update the data according to the needs of different types of blockchains.
  • the data to be on the chain is converted into different formats, further reducing the complexity of the client.
  • a method for signing a cross-chain transaction includes:
  • the second cross-chain component receives the upload request sent by the first cross-chain component; the second cross-chain component corresponds to the blockchain, and the first cross-chain component corresponds to the client; the upload request is the The first cross-chain component is determined according to the client's data to be uploaded to the chain;
  • the second cross-chain component generates a transaction to be signed according to the on-chain request and the state information of the blockchain, and sends the transaction to be signed and the signature algorithm of the blockchain to the first cross-chain Chain component
  • the second cross-chain component receives the signed transaction sent by the first cross-chain component; the signed transaction is generated after the first cross-chain component signs the transaction to be signed using the user's private key;
  • the second cross-chain component sends the signed transaction to the blockchain.
  • the signature algorithm is a signature algorithm of the blockchain configured locally in the second cross-chain component; the user private key is configured locally in the client of the first cross-chain component User private key.
  • the blockchain has multiple types, and different types of blockchains have different signature algorithms; for each blockchain, the local configuration of the second cross-chain component corresponding to the blockchain is different.
  • the method further includes:
  • the second cross-chain component sends a synchronization request to the blockchain
  • the second cross-chain component receives the state information fed back by the blockchain; the state information is generated by the blockchain according to the latest state of the blockchain.
  • a first cross-chain component corresponding to the client and a second cross-chain component corresponding to the blockchain are deployed.
  • the first cross-chain component is used to receive the data to be uploaded from the client to generate an upload request.
  • the second cross-chain component is used to receive the on-chain request sent by the first cross-chain component and generate a transaction that has not yet been signed for on-chain according to the state information of the blockchain, and send the signature algorithm of the blockchain to the first
  • the cross-chain component is such that the first cross-chain component uses the user's private key to sign the transaction that has not been signed according to the signature algorithm.
  • the first cross-chain component is used to sign according to the user’s private key
  • the second cross-chain component is used to provide the corresponding signature algorithm for the first cross-chain component.
  • the interaction between the client only needs to submit the data to be uploaded to the first cross-chain component, and the client does not need to sign the transaction according to the signature algorithm of different types of blockchains, which reduces the complexity of the client.
  • the client corresponds to the first cross-chain component.
  • the client submits the data to be uploaded to the first cross-chain component
  • the data to be uploaded is in a fixed format, and the client does not need to meet the needs of different types of blockchains. Convert the data to be uploaded into different formats to further reduce the complexity of the client.
  • an embodiment of the present invention also provides a cross-chain transaction signing device, including:
  • a first cross-chain component where the first cross-chain component includes a transceiver unit and a processing unit;
  • the transceiving unit is used to send an upload request to a second cross-chain component; the first cross-chain component corresponds to the client, and the second cross-chain component corresponds to the blockchain; the upload request is all The first cross-chain component is determined according to the data to be uploaded on the client by the client;
  • the transceiving unit is also configured to receive the transaction to be signed and the signature algorithm of the blockchain sent by the second cross-chain component; the transaction to be signed is the second cross-chain component according to the on-chain request and Generated by the state information of the blockchain;
  • the processing unit is configured to use the user private key to sign the transaction to be signed according to the signature algorithm, and control the transceiver unit to send the generated signed transaction to the second cross-chain component, so that the first The second cross-chain component sends the signed transaction to the blockchain.
  • the signature algorithm is a signature algorithm of the blockchain configured locally in the second cross-chain component; the user private key is configured locally in the client of the first cross-chain component User private key.
  • the blockchain has multiple types, and different types of blockchains have different signature algorithms; for each blockchain, the local configuration of the second cross-chain component corresponding to the blockchain is different.
  • the data to be uploaded includes the identifier and transaction content of the target blockchain corresponding to the data to be uploaded;
  • the transceiver unit is specifically configured to:
  • the on-chain request is generated according to the transaction content, and the on-chain request is sent to the second cross-chain component corresponding to the target blockchain.
  • an embodiment of the present invention also provides a cross-chain transaction signing device, including:
  • a second cross-chain component where the second cross-chain component includes a transceiver unit and a processing unit;
  • the transceiving unit is configured to receive an on-chain request sent by a first cross-chain component; the second cross-chain component corresponds to the blockchain, and the first cross-chain component corresponds to a client; the on-chain request is The first cross-chain component is determined according to the data to be uploaded on the client by the client;
  • the processing unit is used to generate a transaction to be signed according to the on-chain request and the state information of the blockchain, and to control the transceiver unit to send the transaction to be signed and the signature algorithm of the blockchain to the The first cross-chain component;
  • the transceiver unit is also configured to receive a signed transaction sent by the first cross-chain component; the signed transaction is generated after the first cross-chain component signs the transaction to be signed using the user's private key;
  • the transceiver unit is also used to send the signed transaction to the blockchain.
  • the signature algorithm is a signature algorithm of the blockchain configured locally in the second cross-chain component; the user private key is configured locally in the client of the first cross-chain component User private key.
  • the blockchain has multiple types, and different types of blockchains have different signature algorithms; for each blockchain, the local configuration of the second cross-chain component corresponding to the blockchain is different.
  • the transceiver unit is further configured to:
  • the processing unit Before the processing unit generates a transaction to be signed according to the on-chain request and the state information of the blockchain, sending a synchronization request to the blockchain;
  • the state information is generated by the block chain according to the latest state of the block chain.
  • an embodiment of the present invention also provides a computing device, including:
  • processor, memory, and communication interface among them, the processor, memory and communication interface are connected by a bus;
  • the processor is configured to read the program in the memory, any one of the possible cross-chain transaction signing methods in the first aspect or the first aspect, or execute any one of the second aspect or the second aspect above Possible cross-chain transaction signature methods.
  • the memory is used to store one or more executable programs, and can store data used by the processor when performing operations.
  • the embodiments of the present invention also provide a non-transitory computer-readable storage medium.
  • the non-transitory computer-readable storage medium stores computer instructions, which when running on a computer, cause the computer to or Any one of the possible cross-chain transaction signature methods in the first aspect, or any one of the possible cross-chain transaction signature methods in the second aspect or the second aspect described above.
  • an embodiment of the present invention also provides a computer program product containing instructions.
  • the computer program product includes a calculation program stored on a non-transitory computer-readable storage medium.
  • the computer program includes program instructions. When the program instructions are executed by a computer, the computer executes any possible cross-chain transaction signing method in the first aspect or the first aspect, or executes any possible cross-chain transaction signature method in the second or second aspect. Chain transaction signature method.
  • Figure 1 (a) is a schematic diagram of a system architecture provided by an embodiment of the present invention.
  • Figure 1(b) is a schematic diagram of another system architecture provided by an embodiment of the present invention.
  • FIG. 2 is a schematic flowchart of a method for signing a cross-chain transaction according to an embodiment of the present invention
  • FIG. 3 is a schematic flowchart of another method for signing a cross-chain transaction according to an embodiment of the present invention.
  • FIG. 4 is a schematic structural diagram of a cross-chain transaction signature device provided by an embodiment of the present invention.
  • FIG. 5 is a schematic structural diagram of another cross-chain transaction signature device provided by an embodiment of the present invention.
  • FIG. 6 is a schematic structural diagram of a computing device provided by this application.
  • FIG. 1 exemplarily shows a system architecture applicable to a method for signing a cross-chain transaction provided by an embodiment of the present invention.
  • the system architecture may include a first blockchain, a second blockchain, a cross-chain component, and a client.
  • the first block chain and the second block chain are different types of block chains, and the signature algorithms used by the two are different.
  • the first block chain is the Ethereum block chain
  • the second block chain is the Bitcoin area.
  • Blockchain the first blockchain uses the signature algorithm of the Ethereum blockchain
  • the second blockchain uses the signature algorithm of the Bitcoin blockchain.
  • the cross-chain component is used to connect the client to the first blockchain, and to connect the client to the second blockchain.
  • the cross-chain component is configured with the user's private key and the signature algorithm of each block chain, which is used to perform the chain operation after signing the client's transaction to be chained by using the user's private key according to the block chain's signature algorithm.
  • the cross-chain component can use the user's private key to pair the client's pending transaction on the chain according to the signature algorithm of the Ethereum blockchain. After signing, send the signed transaction to the Ethereum blockchain.
  • the cross-chain component may include a first cross-chain component and a second cross-chain component, where the first cross-chain component corresponds to the client, and the first cross-chain component may be a component installed in the client, or it may It is a component independent of the client.
  • SDK Software Development Kit
  • each blockchain corresponds to at least one second cross-chain component, as shown in Figure 1(b), the first blockchain corresponds to a second cross-chain component, and the second blockchain corresponds to a second cross-chain component .
  • the first cross-chain component is locally configured with the user's private key
  • the second cross-chain component is locally configured with the signature algorithm of the blockchain.
  • the data interaction between the first cross-chain component and the second cross-chain component can be realized according to the blockchain
  • the first blockchain is the Ethereum blockchain
  • the second cross-chain component corresponding to the Ethereum blockchain is locally configured with the signature algorithm of the Ethereum blockchain.
  • the first cross-chain component uses the user’s private key to sign the client’s pending transaction on the chain according to the signature algorithm of the Ethereum blockchain locally configured by the second cross-chain component, and then sends it to the second cross-chain component, and then the second cross-chain component.
  • the cross-chain component sends the signed transaction to be chained to the Ethereum blockchain.
  • one blockchain may correspond to at least one second cross-chain component, and any second cross-chain component of the at least one second cross-chain component is locally configured with a signature algorithm corresponding to the blockchain.
  • FIG. 2 exemplarily shows the flow of a method for signing a cross-chain transaction provided by an embodiment of the present invention, and the flow can be executed interactively by the first cross-chain component and the second cross-chain component.
  • the process specifically includes:
  • Step 201 The first cross-chain component sends an upload request to the second cross-chain component.
  • the chain request is determined by the first cross-chain component based on the client's data to be chained.
  • the first cross-chain component provides the client with a unified interface for receiving the data to be uploaded to the client.
  • the data to be uploaded can include the transaction path and transaction content, and the transaction path includes the target area corresponding to the data to be uploaded.
  • the transaction content includes the transaction method and transaction parameters, where the transaction method refers to the contract method in the target contract to be called; the transaction parameter refers to the input To the parameters in the contract method.
  • the first cross-chain component receives the data to be uploaded from the client, generates an upload request based on the transaction content in the data to be uploaded, and determines the target block according to the transaction path in the data to be uploaded
  • the second cross-chain component corresponding to the chain sends the generated on-chain request to the second cross-chain component corresponding to the target blockchain.
  • the client calls the unified interface provided by the first cross-chain component to send the data to be uploaded to the chain, and transfers the transaction method, transaction parameters, and transaction path in the data to be uploaded to the unified interface of the first cross-chain component .
  • the first cross-chain component constructs a pre-sending request packet (equivalent to an on-chain request) according to the transaction method and transaction parameters, and sends the pre-sending request packet to the second cross-chain component corresponding to the transaction path according to the transaction path.
  • the pre-send request packet may be in Json format.
  • Step 202 The second cross-chain component generates a transaction to be signed according to the on-chain request and the state information of the blockchain.
  • the state information of the block chain can be understood as the information generated by the block chain based on the latest state data, and the state information of the block chain can include the latest block header information of the block chain.
  • the second cross-chain component is constantly synchronized with the nodes in the blockchain to synchronize the state information of the blockchain from the blockchain. Specifically, the second cross-chain component sends a synchronization request to the blockchain, and the block link receives After the synchronization request, the state information is generated according to the latest state data such as the block header information of the latest block, and the state information is sent to the second cross-chain component, and correspondingly, the second cross-chain component receives the state feedback from the blockchain information.
  • the transaction to be signed is a transaction that has not been signed, that is, the signature field in the generated transaction to be signed is empty.
  • the transaction to be signed can be in a binary format.
  • Step 203 The second cross-chain component sends the transaction to be signed and the signature algorithm of the blockchain to the first cross-chain component.
  • the signature algorithm is the signature algorithm of the blockchain that is configured locally in the second cross-chain component. It can also be said that the second cross-chain component can be configured with the signature algorithm of the blockchain locally. After the second cross-chain component generates the transaction to be signed , The generated transaction to be signed and the signature algorithm of the locally configured blockchain will be sent to the first cross-chain component.
  • the blockchain is BCOS
  • the signature algorithm used by BCOS is the ECDSA (Elliptic Curve Digital Signature Algorithm) algorithm
  • the second cross-chain component corresponding to BCOS is locally configured with the ECDSA algorithm.
  • the second cross-chain component receives the on-chain request sent by the first cross-chain component, it sends the generated transaction to be signed together with the ECDSA algorithm to the first cross-chain component.
  • step 204 the first cross-chain component uses the user's private key to sign the signed transaction according to the signature algorithm.
  • the user private key is the user private key configured on the local client side of the first cross-chain component. After the first cross-chain component receives the transaction to be signed and the signature algorithm of the blockchain, it will use the local configuration according to the signature algorithm of the blockchain. The user's private key to sign the transaction to be signed to generate the signed transaction.
  • Step 205 The first cross-chain component sends the generated signed transaction to the second cross-chain component.
  • Step 206 The second cross-chain component sends the signed transaction to the blockchain.
  • a client can correspond to multiple blockchains, that is, a client may send transactions to different blockchains, as shown in Figure 2, the client can send the first transaction to the first blockchain , The second transaction can also be sent to the second blockchain.
  • the client uses different signature algorithms when sending transactions to different blockchains.
  • the signature algorithm of the blockchain is configured in the corresponding second blockchain.
  • the chain component when the first cross-chain component sends an on-chain request to the second cross-chain component of the target blockchain, the second cross-chain component of the target blockchain will generate a transaction to be signed based on the on-chain request and status information , And feed back the locally configured signature algorithm of the target blockchain and the transaction to be signed to the first cross-chain component.
  • the first cross-chain component uses the user’s private key to sign the transaction to be signed according to the signature algorithm of the target blockchain to generate
  • the signed transaction is a transaction that conforms to the signature algorithm of the target blockchain.
  • the client corresponds to two blockchains, namely, blockchain A and blockchain B.
  • Blockchain A is deployed with certificate deposit contract a
  • blockchain B is deployed There is a certificate of deposit contract b.
  • the client can call the deposit certificate method interface of the deposit certificate contract a to store the evidence in the blockchain A, or call the deposit certificate method interface of the deposit contract b to store the evidence in the blockchain B.
  • the blockchain types of blockchain A and blockchain B are different, it is necessary to use the signature algorithm corresponding to the blockchain for different types of blockchains to sign the transactions that need to be connected to the chain before they can be sent to the chain. on.
  • the user private key is first configured in the first cross-chain component, and the signature algorithm of the blockchain corresponding to the second cross-chain component is configured in the second cross-chain component.
  • blockchain A corresponds to the first cross-chain component.
  • the second cross-chain component 1 the signature algorithm of blockchain A is configured in the second cross-chain component 1, and the second cross-chain component 1 continuously synchronizes state information from the nodes in the blockchain A;
  • the blockchain B corresponds to the second In the cross-chain component 2
  • the signature algorithm of the blockchain B is configured in the second cross-chain component 2 continuously synchronizes state information from the nodes in the blockchain B.
  • the interaction process between the client, the first cross-chain component, the second cross-chain component 1, and the blockchain A can be as shown in FIG. 3.
  • Step 301 The client sends the data to be uploaded to the first cross-chain component
  • the client calls the unified interface, and the incoming interface parameters are as follows:
  • Step 302 The first cross-chain component constructs an on-chain request according to the transaction method and transaction parameters;
  • the chain request can be in Json format or other formats.
  • Step 303 The first cross-chain component sends an on-chain request to the second cross-chain component 1 according to the transaction path;
  • step 304 the second cross-chain component 1 generates a transaction to be signed according to the current block height of the blockchain A and the chain request.
  • the transaction to be signed is a transaction to be signed for blockchain A generated by the second cross-chain component 1 according to the current block height and on-chain request.
  • the transaction to be signed is a transaction that has not yet been signed, that is, the generated transaction to be signed
  • the signature field in is empty.
  • the transaction to be signed can be in a binary format.
  • Step 305 The second cross-chain component 1 sends the transaction to be signed and the signature algorithm of blockchain A to the first cross-chain component;
  • Step 306 The first cross-chain component uses the user secret key to sign the transaction to be signed according to the signature algorithm of Blockchain A;
  • Step 307 The first cross-chain component sends the signed transaction to the second cross-chain component 1;
  • step 308 the second cross-chain component 1 sends the signed transaction to the blockchain A.
  • the interaction process between the client, the first cross-chain component, the second cross-chain component 2, and the blockchain B is similar to the above steps 301 to 308, no longer Go into details.
  • a first cross-chain component corresponding to the client and a second cross-chain component corresponding to the blockchain are deployed.
  • the first cross-chain component is used to receive the data to be uploaded from the client to generate an upload request.
  • the second cross-chain component is used to receive the on-chain request sent by the first cross-chain component and generate a transaction for on-chain but not yet signed according to the state information of the blockchain, and send the signature algorithm of the blockchain to the first A cross-chain component so that the first cross-chain component uses the user's private key to sign the transaction that has not been signed according to the signature algorithm.
  • the first cross-chain component is used to sign according to the user’s private key
  • the second cross-chain component is used to provide the corresponding signature algorithm for the first cross-chain component.
  • the interaction between the client only needs to submit the data to be uploaded to the first cross-chain component, and the client does not need to sign the transaction according to the signature algorithm of different types of blockchains, which reduces the complexity of the client.
  • the client corresponds to the first cross-chain component.
  • the client submits the data to be uploaded to the first cross-chain component
  • the data to be uploaded is in a fixed format, and the client does not need to meet the needs of different types of blockchains. Convert the data to be uploaded into different formats to further reduce the complexity of the client.
  • FIG. 4 exemplarily shows the structure of a cross-chain transaction signature device provided by an embodiment of the present invention, which can execute a process based on a cross-chain transaction signature method.
  • the device includes:
  • a first cross-chain component where the first cross-chain component includes a transceiver unit 401 and a processing unit 402;
  • the transceiving unit 401 is configured to send an upload request to a second cross-chain component; the first cross-chain component corresponds to the client, and the second cross-chain component corresponds to the blockchain; the upload request is The first cross-chain component is determined according to the data to be uploaded on the client by the client;
  • the transceiving unit 401 is also configured to receive the transaction to be signed and the signature algorithm of the blockchain sent by the second cross-chain component; the transaction to be signed is the second cross-chain component according to the on-chain request And the state information of the blockchain;
  • the processing unit 402 is configured to use the user private key to sign the transaction to be signed according to the signature algorithm, and control the transceiver unit 401 to send the generated signed transaction to the second cross-chain component, so that all The second cross-chain component sends the signed transaction to the blockchain.
  • the signature algorithm is a signature algorithm of the blockchain configured locally in the second cross-chain component
  • the user private key is the user private key of the client configured locally in the first cross-chain component.
  • the blockchain has multiple types, and different types of blockchains have different signature algorithms; for each blockchain, the local configuration of the second cross-chain component corresponding to the blockchain is different.
  • the data to be uploaded includes the identifier and transaction content of the target blockchain corresponding to the data to be uploaded;
  • the transceiver unit 401 is specifically configured to:
  • the on-chain request is generated according to the transaction content, and the on-chain request is sent to the second cross-chain component corresponding to the target blockchain.
  • FIG. 5 exemplarily shows the structure of a cross-chain transaction signature device provided by an embodiment of the present invention, which can execute a process based on a cross-chain transaction signature method.
  • the device includes:
  • a second cross-chain component where the second cross-chain component includes a transceiver unit 501 and a processing unit 502;
  • the transceiving unit 501 is configured to receive an on-chain request sent by a first cross-chain component; the second cross-chain component corresponds to the blockchain, and the first cross-chain component corresponds to the client; the on-chain request is The first cross-chain component is determined according to the data to be uploaded on the client by the client;
  • the processing unit 502 is configured to generate a transaction to be signed according to the on-chain request and the state information of the blockchain, and control the transceiver unit 501 to send the transaction to be signed and the signature algorithm of the blockchain To the first cross-chain component;
  • the transceiver unit 501 is also configured to receive a signed transaction sent by the first cross-chain component; the signed transaction is generated after the first cross-chain component signs the transaction to be signed using the user's private key;
  • the transceiver unit 501 is also used to send the signed transaction to the blockchain.
  • the signature algorithm is a signature algorithm of the blockchain configured locally in the second cross-chain component
  • the user private key is the user private key of the client configured locally in the first cross-chain component.
  • the blockchain has multiple types, and different types of blockchains have different signature algorithms; for each blockchain, the local configuration of the second cross-chain component corresponding to the blockchain is different.
  • the transceiving unit 501 is further configured to:
  • the processing unit 502 Before the processing unit 502 generates a transaction to be signed according to the on-chain request and the state information of the blockchain, sending a synchronization request to the blockchain;
  • the state information is generated by the block chain according to the latest state of the block chain.
  • the present application also provides a computing device.
  • the computing device includes at least one processor 620, configured to implement the cross-chain transaction signature method in the related embodiment of FIG. 2, or related to FIG. 3.
  • the cross-chain transaction signature method in the embodiment is not limited to the embodiment.
  • the computing device 600 may also include at least one memory 630 for storing program instructions and/or data.
  • the memory 630 and the processor 620 are coupled.
  • the coupling in the embodiments of the present application is an indirect coupling or communication connection between devices, units or modules, and may be in electrical, mechanical or other forms, and is used for information exchange between devices, units or modules.
  • the processor 620 may cooperate with the memory 630 to operate.
  • the processor 620 may execute program instructions stored in the memory 630. At least one of the at least one memory may be included in the processor.
  • each step of the above method can be completed by an integrated logic circuit of hardware in the processor or instructions in the form of software.
  • the steps of the method disclosed in combination with the embodiments of the present application may be directly embodied as being executed and completed by a hardware processor, or executed and completed by a combination of hardware and software modules in the processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware. To avoid repetition, it will not be described in detail here.
  • the processor in the embodiment of the present application may be an integrated circuit chip with signal processing capability.
  • the steps of the foregoing method embodiments can be completed by hardware integrated logic circuits in the processor or instructions in the form of software.
  • the above-mentioned processor may be a general-purpose processor, a digital signal processing circuit (digital signal processor, DSP), a dedicated integrated circuit (application specific integrated circuit, ASIC), a field programmable gate array (field programmable gate array, FPGA) or other Programming logic devices, discrete gates or transistor logic devices, discrete hardware components.
  • DSP digital signal processing circuit
  • ASIC application specific integrated circuit
  • FPGA field programmable gate array
  • Programming logic devices discrete gates or transistor logic devices, discrete hardware components.
  • the general-purpose processor may be a microprocessor or the processor may also be any conventional processor or the like.
  • the steps of the method disclosed in the embodiments of the present application may be directly embodied as being executed and completed by a hardware decoding processor, or executed and completed by a combination of hardware and software modules in the decoding processor.
  • the software module can be located in a mature storage medium in the field, such as random access memory, flash memory, read-only memory, programmable read-only memory, or electrically erasable programmable memory, registers.
  • the storage medium is located in the memory, and the processor reads the information in the memory and completes the steps of the above method in combination with its hardware.
  • the memory in the embodiments of the present application may be a volatile memory or a non-volatile memory, or may include both volatile and non-volatile memory.
  • the non-volatile memory may be read-only memory (ROM), programmable read-only memory (programmable ROM, PROM), erasable programmable read-only memory (erasable PROM, EPROM), and electrically available Erase programmable read-only memory (electrically EPROM, EEPROM) or flash memory.
  • Volatile memory can be random access memory (RAM), which is used as an external cache.
  • RAM random access memory
  • static random access memory static random access memory
  • dynamic RAM dynamic RAM
  • DRAM dynamic random access memory
  • synchronous dynamic random access memory synchronous DRAM, SDRAM
  • double data rate synchronous dynamic random access memory double data rate SDRAM, DDR SDRAM
  • enhanced synchronous dynamic random access memory enhanced SDRAM, ESDRAM
  • synchronous connection dynamic random access memory serial DRAM, SLDRAM
  • direct rambus RAM direct rambus RAM
  • the computing device 600 may further include a communication interface 610 for communicating with other devices through a transmission medium, so that the device used in the computing device 600 can communicate with other devices.
  • the communication interface may be a transceiver, circuit, bus, module, or other type of communication interface.
  • the transceiver when the communication interface is a transceiver, the transceiver may include an independent receiver and an independent transmitter; it may also be a transceiver with integrated transceiver functions, or an interface circuit.
  • the computing device 600 may also include a communication line 640.
  • the communication interface 610, the processor 620, and the memory 630 may be connected to each other through a communication line 640;
  • the communication line 640 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (extended industry standard architecture). , Referred to as EISA) bus and so on.
  • the communication line 640 can be divided into an address bus, a data bus, a control bus, and so on. For ease of representation, only one thick line is used in FIG. 6, but it does not mean that there is only one bus or one type of bus.
  • embodiments of the present invention also provide a non-transitory computer-readable storage medium.
  • the non-transitory computer-readable storage medium stores computer instructions. When it runs on a computer, the computer executes the related The cross-chain transaction signature method in the embodiment, or the cross-chain transaction signature method in the related embodiment of FIG. 3 is executed.
  • inventions of the present application provide a computer program product.
  • the computer program product includes a calculation program stored on a non-transitory computer-readable storage medium.
  • the computer program includes program instructions. When executed by a computer, the computer is caused to execute the cross-chain transaction signature method in the related embodiment of FIG. 2 or the cross-chain transaction signature method in the related embodiment of FIG.
  • These computer program instructions can also be stored in a computer-readable memory that can guide a computer or other programmable cross-chain transaction signature equipment to work in a specific manner, so that the instructions stored in the computer-readable memory produce a manufactured product that includes the instruction device,
  • the instruction device implements the functions specified in one process or multiple processes in the flowchart and/or one block or multiple blocks in the block diagram.
  • These computer program instructions can also be loaded on a computer or other programmable cross-chain transaction signature equipment, so that a series of operation steps are executed on the computer or other programmable equipment to produce computer-implemented processing, and then the computer or other programmable equipment
  • the executed instructions provide steps for implementing functions specified in a flow or multiple flows in the flowchart and/or a block or multiple blocks in the block diagram.

Landscapes

  • Business, Economics & Management (AREA)
  • Accounting & Taxation (AREA)
  • Engineering & Computer Science (AREA)
  • Finance (AREA)
  • Strategic Management (AREA)
  • Physics & Mathematics (AREA)
  • General Business, Economics & Management (AREA)
  • General Physics & Mathematics (AREA)
  • Theoretical Computer Science (AREA)
  • Computer Security & Cryptography (AREA)
  • Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)

Abstract

La présente invention se rapporte au domaine des technologies financières et, en particulier, au domaine des chaînes de blocs. L'invention concerne un procédé de signature de transactions de chaînes de blocs croisées et un dispositif. Le procédé comprend les étapes suivantes : un premier ensemble de chaînes de blocs croisées envoie une requête de liaison montante à un second ensemble de chaînes de blocs croisées ; le second ensemble de chaînes de blocs croisées génère une transaction à signer en fonction de la requête de liaison montante et d'informations d'état d'une chaîne de blocs et envoie, au premier ensemble de chaînes de blocs croisées, la transaction et un algorithme de signature de la chaîne de blocs ; et le premier ensemble de chaînes de blocs croisées utilise une clé privée d'un utilisateur pour signer la transaction en fonction de l'algorithme de signature et envoie la transaction signée au second ensemble de chaînes de blocs croisées et le second ensemble de chaînes de blocs croisées envoie la transaction signée à la chaîne de blocs. L'invention peut résoudre le problème en l'état de la technique selon lequel des opérations effectuées par un client sont complexes.
PCT/CN2020/127566 2019-11-25 2020-11-09 Procédé de signature de transactions de chaînes de blocs croisées et dispositif WO2021103998A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201911165887.9 2019-11-25
CN201911165887.9A CN111008827B (zh) 2019-11-25 2019-11-25 一种跨链交易签名方法及装置

Publications (1)

Publication Number Publication Date
WO2021103998A1 true WO2021103998A1 (fr) 2021-06-03

Family

ID=70112676

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/127566 WO2021103998A1 (fr) 2019-11-25 2020-11-09 Procédé de signature de transactions de chaînes de blocs croisées et dispositif

Country Status (2)

Country Link
CN (1) CN111008827B (fr)
WO (1) WO2021103998A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113781216A (zh) * 2021-08-27 2021-12-10 浙商银行股份有限公司 基于回调合约机制的异步跨链交易查询方法及设备

Families Citing this family (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN111008827B (zh) * 2019-11-25 2023-07-21 深圳前海微众银行股份有限公司 一种跨链交易签名方法及装置
CN112150148A (zh) * 2020-09-24 2020-12-29 普华云创科技(北京)有限公司 一种基于区块链技术的企业资产保护方法与系统
CN113691621B (zh) * 2021-08-24 2023-10-13 上海点融信息科技有限责任公司 一种区块链数据上链方法

Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108256864A (zh) * 2018-02-13 2018-07-06 中链科技有限公司 一种区块链之间的跨链联盟的建立及通信方法、系统
CN108876618A (zh) * 2018-06-15 2018-11-23 浙江华信区块链科技服务有限公司 一种交换区块链系统及相应的通用区块链互操作方法和网络
CN109460413A (zh) * 2018-11-19 2019-03-12 众安信息技术服务有限公司 用于跨区块链建立账户的方法及系统
US10417188B2 (en) * 2016-05-27 2019-09-17 Mastercard International Incorporated Method and system for transferring trust across block chain segments
CN110266655A (zh) * 2019-05-30 2019-09-20 中国工商银行股份有限公司 一种基于区块链的跨链互联方法、设备以及系统
CN111008827A (zh) * 2019-11-25 2020-04-14 深圳前海微众银行股份有限公司 一种跨链交易签名方法及装置

Family Cites Families (9)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN109428722A (zh) * 2017-08-30 2019-03-05 上海策赢网络科技有限公司 一种内容发布方法及装置
CN107909369A (zh) * 2017-10-13 2018-04-13 布比（北京）网络技术有限公司 基于跨链交易的共识方法、装置和存储介质
CN109104287A (zh) * 2018-07-27 2018-12-28 众安信息技术服务有限公司 在区块链中进行通信的方法和装置
CN112765595B (zh) * 2018-11-16 2024-05-10 创新先进技术有限公司 跨区块链的数据处理方法、装置、客户端、区块链系统
CN110035045B (zh) * 2018-11-16 2020-04-03 阿里巴巴集团控股有限公司 跨链数据的可信管理方法及装置、电子设备
CN109903041A (zh) * 2018-11-30 2019-06-18 阿里巴巴集团控股有限公司 用于区块链交易的区块上链的方法及系统
EP3590084B1 (fr) * 2019-03-04 2022-05-11 Advanced New Technologies Co., Ltd. Procédés et dispositifs de vérification de signature de test pour système de chaîne de blocs
CN110011793A (zh) * 2019-04-03 2019-07-12 上海中商网络股份有限公司 防伪溯源数据处理方法、装置、设备及介质
CN110149316B (zh) * 2019-04-22 2022-05-17 众安信息技术服务有限公司 一种区块链的发布方法及装置

Patent Citations (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10417188B2 (en) * 2016-05-27 2019-09-17 Mastercard International Incorporated Method and system for transferring trust across block chain segments
CN108256864A (zh) * 2018-02-13 2018-07-06 中链科技有限公司 一种区块链之间的跨链联盟的建立及通信方法、系统
CN108876618A (zh) * 2018-06-15 2018-11-23 浙江华信区块链科技服务有限公司 一种交换区块链系统及相应的通用区块链互操作方法和网络
CN109460413A (zh) * 2018-11-19 2019-03-12 众安信息技术服务有限公司 用于跨区块链建立账户的方法及系统
CN110266655A (zh) * 2019-05-30 2019-09-20 中国工商银行股份有限公司 一种基于区块链的跨链互联方法、设备以及系统
CN111008827A (zh) * 2019-11-25 2020-04-14 深圳前海微众银行股份有限公司 一种跨链交易签名方法及装置

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN113781216A (zh) * 2021-08-27 2021-12-10 浙商银行股份有限公司 基于回调合约机制的异步跨链交易查询方法及设备
CN113781216B (zh) * 2021-08-27 2024-05-28 浙商银行股份有限公司 基于回调合约机制的异步跨链交易查询方法及设备

Also Published As

Publication number Publication date
CN111008827B (zh) 2023-07-21
CN111008827A (zh) 2020-04-14

Similar Documents

Publication Publication Date Title
WO2021103998A1 (fr) Procédé de signature de transactions de chaînes de blocs croisées et dispositif
WO2021036702A1 (fr) Procédé et dispositif de consensus utilisant un système de chaîne de blocs
WO2021109735A1 (fr) Procédé de traitement de ressource basé sur un réseau inter-chaînes, et dispositif
CN104253856A (zh) 可缩放Web实时通信媒体引擎以及相关的方法、系统
WO2020248982A1 (fr) Procédé et dispositif de traitement de transaction dans une chaîne de blocs
CN113556339B (zh) 支持异构可信执行环境tee算力节点交互的隐私计算方法
WO2019129167A1 (fr) Procédé de traitement de paquet de données et carte réseau
CN109711192B (zh) 区块链系统节点间交易方法及系统
CN111144883A (zh) 一种区块链网络的处理性能分析方法及装置
WO2020248981A1 (fr) Procédé et dispositif basés sur une chaîne de blocs pour la communication entre des dispositifs ido
CN110969524B (zh) 基于区块链的资金业务处理方法、装置、设备及介质
WO2022078181A1 (fr) Procédé et appareil de preuve de transaction de chaîne de blocs
US20220224648A1 (en) Method for balancing cross-domain broadcast network load of blockchain, computer device, and non-transitory computer-readable storage medium
CN115174267B (zh) 一种tls协议协商方法、设备及介质
WO2020173126A1 (fr) Procédé et dispositif de traitement de données de session à base de chaîne de blocs, équipement et support
JP2022554202A (ja) 対話型集約署名方法、設備および記憶媒体
WO2022041902A1 (fr) Procédé et appareil de traitement de données
WO2023078161A1 (fr) Fonctionnement d'un modèle
WO2021003621A1 (fr) Procédé et dispositif pour renvoyer un état de transmission de liaison latérale
EP3972199B1 (fr) Procédé de gestion d'interface ouverte, dispositif électronique et support d'enregistrement
CN116232944B (zh) 用于传输层安全协议报文业务的方法、设备及介质
JP2023507224A (ja) 通信方法及び関連製品
CN113905094B (zh) 工业互联网集成方法、装置及系统
WO2015169053A1 (fr) Procédé, dispositif et système de traitement de données de paquet
WO2022095179A1 (fr) Système et procédé de traitement de données, dispositif électronique et support de mémoire

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 20893044

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 20893044

Country of ref document: EP

Kind code of ref document: A1