WO2021103998A1 - 一种跨链交易签名方法及装置 - Google Patents

一种跨链交易签名方法及装置 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)
French (fr)
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/zh

Links

Images

Classifications

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

一种跨链交易签名方法及装置,涉及金融科技领域,具体涉及区块链领域,其中,方法包括:第一跨链组件将上链请求发送至第二跨链组件,第二跨链组件根据上链请求和区块链的状态信息生成待签名交易,并将待签名交易和区块链的签名算法发送至第一跨链组件,第一跨链组件根据签名算法,使用用户私钥对待签名交易进行签名,将生成的已签名交易发送至第二跨链组件,第二跨链组件将已签名交易发送至区块链中。用以解决现有技术中客户端的复杂度较高的问题。

Description

一种跨链交易签名方法及装置
相关申请的交叉引用
本申请要求在2019年11月25日提交中国专利局、申请号为201911165887.9、申请名称为“一种跨链交易签名方法及装置”的中国专利申请的优先权,其全部内容通过引用结合在本申请中。
技术领域
本发明实施例涉及金融科技(Fintech)领域,尤其涉及区块链领域中的一种跨链交易签名方法及装置。
背景技术
随着计算机技术的发展,越来越多的技术应用在金融领域,传统金融业正在逐步向金融科技(Fintech)转变,但由于金融行业的安全性、实时性要求,也对技术提出的更高的要求。
目前存在着各种各样类型的区块链。在某些业务场景下,客户端需要同时对不同类型的区块链进行操作,向不同类型的区块链发送交易,但不同类型的区块链的签名算法不同,如一个客户端同时对应以太坊区块链和比特币区块链,当客户端需要将交易发送至以太坊区块链时,则根据以太坊区块链的签名算法对交易进行签名后发送,当客户端需要将交易发送至比特币区块链时,则根据比特币区块链的签名算法对交易进行签名后发送。
现有技术中,客户端本地需要配置对应不同类型区块链的签名算法,且在发送交易之前需要判断目标区块链的签名算法并根据该签名算法进行签名。该方式对客户端的要求较高,增加客户端的复杂度。
发明内容
本发明实施例提供一种跨链交易签名方法及装置,用以解决现有技术中客户端的复杂度较高的问题。
第一方面,本发明实施例提供的一种跨链交易签名方法,包括:
第一跨链组件将上链请求发送至第二跨链组件;所述第一跨链组件与客户端对应,所述第二跨链组件与区块链对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
所述第一跨链组件接收所述第二跨链组件发送的待签名交易和所述区块链的签名算法;所述待签名交易是所述第二跨链组件根据所述上链请求和所述区块链的状态信息生成的;
所述第一跨链组件根据所述签名算法,使用用户私钥对所述待签名交易签名,将生成的已签名交易发送至所述第二跨链组件,以使所述第二跨链组件将所述已签名交易发送至所述区块链中。
可选的,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用 户私钥。
可选的,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
可选的,所述待上链数据中包括所述待上链数据对应的目标区块链的标识和交易内容;
所述第一跨链组件将上链请求发送至第二跨链组件,包括:
所述第一跨链组件根据所述交易内容生成所述上链请求;
所述第一跨链组件将所述上链请求发送至所述目标区块链对应的第二跨链组件。
上述技术方案中,部署与客户端对应的第一跨链组件以及与区块链对应第二跨链组件,第一跨链组件用于接收客户端发送的待上链数据并生成上链请求,第二跨链组件用于接收第一跨链组件发送的上链请求并根据区块链的状态信息生成用于上链的但尚未签名的交易,并将区块链的签名算法一起发送至第一跨链组件以使得第一跨链组件根据签名算法采用用户私钥对尚未签名的交易进行签名。也就是说,第一跨链组件用于根据用户私钥进行签名,第二跨链组件用于提供给第一跨链组件相应的签名算法,通过第一跨链组件和第二跨链组件之间的交互,实现客户端只要将待上链数据提交至第一跨链组件即可,无需客户端根据不同类型区块链的签名算法对交易进行签名,减少了客户端的复杂性。进一步的,客户端与第一跨链组件对应,客户端在向第一跨链组件提交待上链数据时,待上链数据为固定格式,客户端也无需根据不同类型区块链的需要将待上链数据转换成不同格式,进一步减少客户端的复杂性。
第二方面,本发明实施例提供的一种跨链交易签名方法,包括:
第二跨链组件接收第一跨链组件发送的上链请求;所述第二跨链组件与区块链对应,所述第一跨链组件与客户端对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
所述第二跨链组件根据所述上链请求和所述区块链的状态信息生成待签名交易,并将所述待签名交易和所述区块链的签名算法发送至所述第一跨链组件;
所述第二跨链组件接收所述第一跨链组件发送的已签名交易;所述已签名交易是所述第一跨链组件使用用户私钥对所述待签名交易签名后生成的;
所述第二跨链组件将所述已签名交易发送至所述区块链中。
可选的,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用户私钥。
可选的,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
可选的,所述第二跨链组件根据所述上链请求和所述区块链的状态信息 生成待签名交易之前,还包括:
所述第二跨链组件向所述区块链发送同步请求;
所述第二跨链组件接收所述区块链反馈的所述状态信息;所述状态信息是所述区块链根据所述区块链的最新状态生成的。
上述技术方案中,部署与客户端对应的第一跨链组件以及与区块链对应第二跨链组件,第一跨链组件用于接收客户端发送的待上链数据生成上链请求,第二跨链组件用于接收第一跨链组件发送的上链请求并根据区块链的状态信息生成用于上链的但尚未签名的交易,并将区块链的签名算法一起发送至第一跨链组件以使得第一跨链组件根据签名算法采用用户私钥对尚未签名的交易进行签名。也就是说,第一跨链组件用于根据用户私钥进行签名,第二跨链组件用于提供给第一跨链组件相应的签名算法,通过第一跨链组件和第二跨链组件之间的交互,实现客户端只要将待上链数据提交至第一跨链组件即可,无需客户端根据不同类型的区块链的签名算法对交易进行签名,减少了客户端的复杂性。进一步的,客户端与第一跨链组件对应,客户端在向第一跨链组件提交待上链数据时,待上链数据为固定格式,客户端也无需根据不同类型的区块链的需要将待上链数据转换成不同格式,进一步减少客户端的复杂性。
第三方面,本发明实施例还提供了一种跨链交易签名装置,包括:
第一跨链组件,所述第一跨链组件包括收发单元、处理单元;
所述收发单元用于将上链请求发送至第二跨链组件;所述第一跨链组件与客户端对应,所述第二跨链组件与区块链对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
所述收发单元还用于接收所述第二跨链组件发送的待签名交易和所述区块链的签名算法;所述待签名交易是所述第二跨链组件根据所述上链请求和所述区块链的状态信息生成的;
所述处理单元用于根据所述签名算法,使用用户私钥对所述待签名交易签名,控制所述收发单元将生成的已签名交易发送至所述第二跨链组件,以使所述第二跨链组件将所述已签名交易发送至所述区块链中。
可选的,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用户私钥。
可选的,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
可选的,所述待上链数据中包括所述待上链数据对应的目标区块链的标识和交易内容;
所述收发单元具体用于:
根据所述交易内容生成所述上链请求,将所述上链请求发送至所述目标区块链对应的第二跨链组件。
第四方面,本发明实施例还提供了一种跨链交易签名装置,包括:
第二跨链组件,所述第二跨链组件包括收发单元、处理单元;
所述收发单元用于接收第一跨链组件发送的上链请求;所述第二跨链组件与区块链对应,所述第一跨链组件与客户端对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
所述处理单元用于根据所述上链请求和所述区块链的状态信息生成待签名交易,并控制所述收发单元将所述待签名交易和所述区块链的签名算法发送至所述第一跨链组件;
所述收发单元还用于接收所述第一跨链组件发送的已签名交易;所述已签名交易是所述第一跨链组件使用用户私钥对所述待签名交易签名后生成的;
所述收发单元还用于将所述已签名交易发送至所述区块链中。
可选的,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用户私钥。
可选的,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
可选的,所述收发单元还用于:
在所述处理单元根据所述上链请求和所述区块链的状态信息生成待签名交易之前,向所述区块链发送同步请求;
接收所述区块链反馈的所述状态信息;所述状态信息是所述区块链根据所述区块链的最新状态生成的。
第五方面,本发明实施例还提供了一种计算设备,包括:
处理器、存储器、通信接口;其中,处理器、存储器与通信接口之间通过总线连接;
所述处理器,用于读取所述存储器中的程序,上述第一方面或第一方面中任一种可能的跨链交易签名方法,或执行上述第二方面或第二方面中任一种可能的跨链交易签名方法。
所述存储器,用于存储一个或多个可执行程序,可以存储所述处理器在执行操作时所使用的数据。
第六方面,本发明实施例还提供了一种非暂态计算机可读存储介质,非暂态计算机可读存储介质中存储计算机指令,当其在计算机上运行时,使得计算机上述第一方面或第一方面中任一种可能的跨链交易签名方法,或执行上述第二方面或第二方面中任一种可能的跨链交易签名方法。
第七方面,本发明实施例还提供一种包含指令的计算机程序产品,所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行上述第一方面或第一方面中任一种可能的跨链交易签名方法,或执行上述第二方面或第二方面中任一种可能的跨链交易签名方法。
附图说明
为了更清楚地说明本发明实施例中的技术方案,下面将对实施例描述中所需要使用的附图作简要介绍,显而易见地,下面描述中的附图仅仅是本发明的一些实施例,对于本领域的普通技术人员来讲,在不付出创造性劳动的前提下,还可以根据这些附图获得其他的附图。
图1(a)为本发明实施例提供的一种***架构的示意图;
图1(b)为本发明实施例提供的另一种***架构的示意图;
图2为本发明实施例提供的一种跨链交易签名方法的流程示意图;
图3为本发明实施例提供的另一种跨链交易签名方法的流程示意图;
图4为本发明实施例提供的一种跨链交易签名装置的结构示意图;
图5为本发明实施例提供的另一种跨链交易签名装置的结构示意图;
图6为本申请提供的一种计算设备的结构示意图。
具体实施方式
为了使本发明的目的、技术方案和优点更加清楚,下面将结合附图对本发明作进一步地详细描述,显然,所描述的实施例仅仅是本发明一部分实施例,而不是全部的实施例。基于本发明中的实施例,本领域普通技术人员在没有做出创造性劳动前提下所获得的所有其它实施例,都属于本发明保护的范围。
图1示例性的示出了本发明实施例提供跨链交易签名方法所适用的***架构,该***架构可以包括第一区块链、第二区块链、跨链组件和客户端。
第一区块链与第二区块链为不同类型的区块链,二者所采用的签名算法不同,如第一区块链为以太坊区块链、第二区块链为比特币区块链,第一区块链采用以太坊区块链的签名算法,第二区块链采用比特币区块链的签名算法。
跨链组件用于连接客户端和第一区块链,以及用于连接客户端和第二区块链。跨链组件中配置有用户私钥和各区块链的签名算法,用于根据区块链的签名算法采用用户私钥对客户端的待上链交易进行签名后执行上链操作。举例来说,如图1(a)中,若第一区块链为以太坊区块链,则跨链组件可以根据以太坊区块链的签名算法采用用户私钥对客户端的待上链交易进行签名后将签名后的交易发送至以太坊区块链中。
进一步的,跨链组件中可以包括第一跨链组件和第二跨链组件,其中,第一跨链组件与客户端对应,第一跨链组件可以是安装在客户端中的组件,也可以是独立于客户端以外的组件,第一跨链组件中可以安装有SDK(Software Development Kit,软件开发工具包)用于为客户端提供统一的接口;第二跨链组件与区块链对应,且每个区块链对应至少一个第二跨链组件,如图1(b)中,第一区块链对应有一个第二跨链组件,第二区块链对应有一个第二跨链组件。
第一跨链组件本地配置有用户私钥,第二跨链组件本地配置有区块链的签名算法,通过第一跨链组件与第二跨链组件之间的数据交互可以实现根据 区块链的签名算法采用用户私钥对客户端的待上链交易进行签名后执行上链操作。举例来说,如图1(b)中,若第一区块链为以太坊区块链,则以太坊区块链对应的第二跨链组件本地配置有以太坊区块链的签名算法,第一跨链组件根据该第二跨链组件本地配置的以太坊区块链的签名算法采用用户私钥对客户端的待上链交易进行签名后发送至该第二跨链组件,进而该第二跨链组件将签名后的待上链交易发送至以太坊区块链中。
图1(a)、图1(b)所示的***架构中,虽然只示出了两个区块链,但是本方案还适用于多个区块链,该多个区块链对应至少两种类型。而且,一个区块链可以对应至少一个第二跨链组件,该至少一个第二跨链组件中的任一个第二跨链组件的本地都配置有与该区块链相对应的签名算法。
基于上述描述,图2示例性的示出了本发明实施例提供的一种跨链交易签名方法的流程,该流程可以由第一跨链组件和第二跨链组件交互执行。
如图2所示,该流程具体包括:
步骤201,第一跨链组件将上链请求发送至第二跨链组件。
上链请求是第一跨链组件根据客户端的待上链数据确定的。第一跨链组件向客户端提供一个统一的接口,用于接收客户端发送的待上链数据,待上链数据中可以包括交易路径和交易内容,交易路径包括待上链数据对应的目标区块链的标识和目标区块链上待调用的目标合约的标识;交易内容包括交易方法、交易参数,其中,交易方法指的是待调用的目标合约中的合约方法;交易参数指的是输入至合约方法中的参数。
一种实现方式中,第一跨链组件接收客户端发送的待上链数据,并根据待上链数据中的交易内容生成上链请求,以及根据待上链数据中的交易路径确定目标区块链对应的第二跨链组件,将生成的上链请求发送至目标区块链对应的第二跨链组件。换个角度来说,客户端调用第一跨链组件提供的统一接口发送待上链数据,将待上链数据中的交易方法、交易参数、交易路径传入至第一跨链组件的统一接口中,第一跨链组件根据交易方法、交易参数构造预发送请求包(相当于上链请求),并根据交易路径将该预发送请求包发送至交易路径对应的第二跨链组件。其中,预发送请求包可以是Json格式。
步骤202,第二跨链组件根据上链请求和区块链的状态信息生成待签名交易。
区块链的状态信息可以理解成区块链根据最新的状态数据生成的信息,区块链的状态信息中可以包括区块链的最新区块头信息。第二跨链组件不断与区块链中节点保持同步,以从区块链中同步区块链的状态信息,具体的,第二跨链组件向区块链发送同步请求,区块链接收到同步请求后,根据最新的状态数据如最新区块的区块头信息,生成状态信息,并将该状态信息发送至第二跨链组件,相应的,第二跨链组件接收区块链反馈的状态信息。
本发明实施例中,待签名交易即尚未签名的交易,也即生成的待签名交易中的签名字段为空。待签名交易可以是二进制格式。
步骤203,第二跨链组件将待签名交易和区块链的签名算法发送至第一跨链组件。
签名算法是配置在第二跨链组件本地的区块链的签名算法,也可以说,第二跨链组件本地可以配置有区块链的签名算法,在第二跨链组件生成待签名交易后,会将生成的待签名交易和本地配置的区块链的签名算法一起发送至第一跨链组件。
举例来说,区块链为BCOS,BCOS所采用的签名算法是ECDSA(Elliptic Curve Digital Signature Algorithm,椭圆曲线数字签名算法)算法,则与BCOS对应的第二跨链组件本地配置有ECDSA算法,当该第二跨链组件接收到第一跨链组件发送的上链请求之后,将生成的待签名交易和ECDSA算法一起发送至第一跨链组件。
步骤204,第一跨链组件根据签名算法,使用用户私钥对待签名交易签名。
用户私钥是配置在第一跨链组件本地的客户端的用户私钥,第一跨链组件在接收到待签名交易和区块链的签名算法之后,会根据区块链的签名算法使用本地配置的用户私钥对待签名交易签名,生成已签名交易。
步骤205,第一跨链组件将生成的已签名交易发送至第二跨链组件。
步骤206,第二跨链组件将已签名交易发送至区块链中。
需要说明的是,一个客户端可以对应多个区块链,也即一个客户端可能会向不同的区块链发送交易,如图2中,客户端可以向第一区块链发送第一交易,也可以向第二区块链发送第二交易,客户端在向不同区块链发送交易时,采用的签名算法不同,本发明实施例将区块链的签名算法配置在对应的第二跨链组件中,当第一跨链组件将上链请求发送至目标区块链的第二跨链组件时,目标区块链的第二跨链组件会根据上链请求和状态信息生成待签名交易,以及将本地配置的目标区块链的签名算法和待签名交易反馈至第一跨链组件,第一跨链组件根据目标区块链的签名算法使用用户私钥对待签名交易进行签名,从而生成的已签名交易是符合目标区块链的签名算法的交易。
下面结合场景对本发明实施例做具体说明,客户端对应两个区块链,分别是区块链A和区块链B,区块链A上部署有存证合约a,区块链B上部署有存证合约b。客户端可以调用存证合约a的存证方法的接口在区块链A中存储证据,或调用存证合约b的存证方法的接口在区块链B中存储证据。但由于区块链A和区块链B的区块链类型不同,则需要针对不同类型的区块链采用与区块链相对应的签名算法对需要上链的交易进行签名后才能发送至链上。本发明实施例中,首先会在第一跨链组件中配置用户私钥,以及在第二跨链组件中配置与第二跨链组件对应区块链的签名算法,假设区块链A对应第二跨链组件1,在第二跨链组件1中配置区块链A的签名算法,且第二跨链组件1不断从区块链A中的节点同步状态信息;区块链B对应第二跨链组件2,在第二跨链组件2中配置区块链B的签名算法,且第二跨链组件2不断从区块链B中的节点同步状态信息。
如客户端需要将证据存储至区块链A中,则客户端、第一跨链组件、第二跨链组件1、区块链A之间的交互流程可以如图3所示。
步骤301,客户端发送待上链数据至第一跨链组件;
客户端调用统一接口,传入接口参数如下:
交易路径:区块链A/存证合约a
交易方法:存证方法
交易参数:证据信息
步骤302,第一跨链组件根据交易方法和交易参数构造上链请求;
上链请求可以是Json格式,也可以是其他格式。
步骤303,第一跨链组件根据交易路径将上链请求发送至第二跨链组件1;
步骤304,第二跨链组件1根据区块链A的当前块高和上链请求,生成待签名交易。
待签名交易是第二跨链组件1根据当前块高和上链请求生成的适用于区块链A的待签名交易,此处,待签名交易即尚未签名的交易,也即生成的待签名交易中的签名字段为空。待签名交易可以是二进制格式。
步骤305,第二跨链组件1将待签名交易和区块链A的签名算法发送至第一跨链组件;
步骤306,第一跨链组件根据区块链A的签名算法采用用户秘钥对待签名交易进行签名;
相当于在待签名交易的签名字段中加入根据区块链A的签名算法采用用户秘钥生成的签名,从而确定出已签名交易。
步骤307,第一跨链组件将已签名交易发送至第二跨链组件1;
步骤308,第二跨链组件1将已签名交易发送至区块链A。
如果客户端将证据存储至区块链B中,则客户端、第一跨链组件、第二跨链组件2、区块链B之间的交互流程与上述步骤301至步骤308类似,不再赘述。
本发明实施例中,部署与客户端对应的第一跨链组件以及与区块链对应第二跨链组件,第一跨链组件用于接收客户端发送的待上链数据生成上链请求,第二跨链组件用于接收第一跨链组件发送的上链请求并根据区块链的状态信息生成用于上链的但尚未签名的交易,并将区块链的签名算法一起发送至第一跨链组件以使得第一跨链组件根据签名算法采用用户私钥对尚未签名的交易进行签名。也就是说,第一跨链组件用于根据用户私钥进行签名,第二跨链组件用于提供给第一跨链组件相应的签名算法,通过第一跨链组件和第二跨链组件之间的交互,实现客户端只要将待上链数据提交至第一跨链组件即可,无需客户端根据不同类型的区块链的签名算法对交易进行签名,减少了客户端的复杂性。进一步的,客户端与第一跨链组件对应,客户端在向第一跨链组件提交待上链数据时,待上链数据为固定格式,客户端也无需根据不同类型的区块链的需要将待上链数据转换成不同格式,进一步减少客户端的复杂性。
基于同一发明构思,图4示例性的示出了本发明实施例提供的一种跨链交易签名装置的结构,该装置可以执行基于跨链交易签名方法的流程。
所述装置包括:
第一跨链组件,所述第一跨链组件包括收发单元401、处理单元402;
所述收发单元401用于将上链请求发送至第二跨链组件;所述第一跨链 组件与客户端对应,所述第二跨链组件与区块链对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
所述收发单元401还用于接收所述第二跨链组件发送的待签名交易和所述区块链的签名算法;所述待签名交易是所述第二跨链组件根据所述上链请求和所述区块链的状态信息生成的;
所述处理单元402用于根据所述签名算法,使用用户私钥对所述待签名交易签名,控制所述收发单元401将生成的已签名交易发送至所述第二跨链组件,以使所述第二跨链组件将所述已签名交易发送至所述区块链中。
可选的,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;
所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用户私钥。
可选的,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
可选的,所述待上链数据中包括所述待上链数据对应的目标区块链的标识和交易内容;
所述收发单元401具体用于:
根据所述交易内容生成所述上链请求,将所述上链请求发送至所述目标区块链对应的第二跨链组件。
基于同一发明构思,图5示例性的示出了本发明实施例提供的一种跨链交易签名装置的结构,该装置可以执行基于跨链交易签名方法的流程。
所述装置包括:
第二跨链组件,所述第二跨链组件包括收发单元501、处理单元502;
所述收发单元501用于接收第一跨链组件发送的上链请求;所述第二跨链组件与区块链对应,所述第一跨链组件与客户端对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
所述处理单元502用于根据所述上链请求和所述区块链的状态信息生成待签名交易,并控制所述收发单元501将所述待签名交易和所述区块链的签名算法发送至所述第一跨链组件;
所述收发单元501还用于接收所述第一跨链组件发送的已签名交易;所述已签名交易是所述第一跨链组件使用用户私钥对所述待签名交易签名后生成的;
所述收发单元501还用于将所述已签名交易发送至所述区块链中。
可选的,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;
所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用户私钥。
可选的,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
可选的,所述收发单元501还用于:
在所述处理单元502根据所述上链请求和所述区块链的状态信息生成待签名交易之前,向所述区块链发送同步请求;
接收所述区块链反馈的所述状态信息;所述状态信息是所述区块链根据所述区块链的最新状态生成的。
基于相同的构思,本申请还提供一种计算设备,如图6所示,该计算设备包括至少一个处理器620,用于实现图2相关实施例中的跨链交易签名方法,或图3相关实施例中的跨链交易签名方法。
计算设备600还可以包括至少一个存储器630,用于存储程序指令和/或数据。存储器630和处理器620耦合。本申请实施例中的耦合是装置、单元或模块之间的间接耦合或通信连接,可以是电性,机械或其它的形式,用于装置、单元或模块之间的信息交互。处理器620可能和存储器630协同操作。处理器620可能执行存储器630中存储的程序指令。所述至少一个存储器中的至少一个可以包括于处理器中。
在实现过程中,上述方法的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。结合本申请实施例所公开的方法的步骤可以直接体现为硬件处理器执行完成,或者用处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。为避免重复,这里不再详细描述。
应注意,本申请实施例中的处理器可以是一种集成电路芯片,具有信号的处理能力。在实现过程中,上述方法实施例的各步骤可以通过处理器中的硬件的集成逻辑电路或者软件形式的指令完成。上述的处理器可以是通用处理器、数字信号处理电路(digital signal processor,DSP)、专用集成芯片(application specific integrated circuit,ASIC)、现场可编程门阵列(field programmable gate array,FPGA)或者其他可编程逻辑器件、分立门或者晶体管逻辑器件、分立硬件组件。可以实现或者执行本申请实施例中的公开的各方法、步骤及逻辑框图。通用处理器可以是微处理器或者该处理器也可以是任何常规的处理器等。结合本申请实施例所公开的方法的步骤可以直接体现为硬件译码处理器执行完成,或者用译码处理器中的硬件及软件模块组合执行完成。软件模块可以位于随机存储器,闪存、只读存储器,可编程只读存储器或者电可擦写可编程存储器、寄存器等本领域成熟的存储介质中。该存储介质位于存储器,处理器读取存储器中的信息,结合其硬件完成上述方法的步骤。
可以理解,本申请实施例中的存储器可以是易失性存储器或非易失性存储器,或可包括易失性和非易失性存储器两者。其中,非易失性存储器可以是只读存储器(read-only memory,ROM)、可编程只读存储器(programmable ROM,PROM)、可擦除可编程只读存储器(erasable PROM,EPROM)、电可擦除可编程只读存储器(electrically EPROM,EEPROM)或闪存。易失性存储器可以是随机存取存储器(random access memory,RAM),其用作外部 高速缓存。通过示例性但不是限制性说明,许多形式的RAM可用,例如静态随机存取存储器(static RAM,SRAM)、动态随机存取存储器(dynamic RAM,DRAM)、同步动态随机存取存储器(synchronous DRAM,SDRAM)、双倍数据速率同步动态随机存取存储器(double data rate SDRAM,DDR SDRAM)、增强型同步动态随机存取存储器(enhanced SDRAM,ESDRAM)、同步连接动态随机存取存储器(synchlink DRAM,SLDRAM)和直接内存总线随机存取存储器(direct rambus RAM,DR RAM)。应注意,本文描述的***和方法的存储器旨在包括但不限于这些和任意其它适合类型的存储器。
计算设备600还可以包括通信接口610,用于通过传输介质和其它设备进行通信,从而用于计算设备600中的装置可以和其它设备进行通信。在本申请实施例中,通信接口可以是收发器、电路、总线、模块或其它类型的通信接口。在本申请实施例中,通信接口为收发器时,收发器可以包括独立的接收器、独立的发射器;也可以集成收发功能的收发器、或者是接口电路。
计算设备600还可以包括通信线路640。其中,通信接口610、处理器620以及存储器630可以通过通信线路640相互连接;通信线路640可以是外设部件互连标准(peripheral component interconnect,简称PCI)总线或扩展工业标准结构(extended industry standard architecture,简称EISA)总线等。所述通信线路640可以分为地址总线、数据总线、控制总线等。为便于表示,图6中仅用一条粗线表示,但并不表示仅有一根总线或一种类型的总线。
基于同一发明构思,本发明实施例还提供了一种非暂态计算机可读存储介质,非暂态计算机可读存储介质中存储计算机指令,当其在计算机上运行时,使得计算机执行图2相关实施例中的跨链交易签名方法,或执行图3相关实施例中的跨链交易签名方法。
基于同一发明构思,本申请实施例提供一种计算机程序产品,所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行图2相关实施例中的跨链交易签名方法,或执行图3相关实施例中的跨链交易签名方法。
本发明是参照根据本发明实施例的方法、设备(***)、和计算机程序产品的流程图和/或方框图来描述的。应理解可由计算机程序指令实现流程图和/或方框图中的每一流程和/或方框、以及流程图和/或方框图中的流程和/或方框的结合。可提供这些计算机程序指令到通用计算机、专用计算机、嵌入式处理机或其他可编程跨链交易签名设备的处理器以产生一个机器,使得通过计算机或其他可编程跨链交易签名设备的处理器执行的指令产生用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的装置。
这些计算机程序指令也可存储在能引导计算机或其他可编程跨链交易签名设备以特定方式工作的计算机可读存储器中,使得存储在该计算机可读存储器中的指令产生包括指令装置的制造品,该指令装置实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能。
这些计算机程序指令也可装载到计算机或其他可编程跨链交易签名设备上,使得在计算机或其他可编程设备上执行一系列操作步骤以产生计算机实现的处理,从而在计算机或其他可编程设备上执行的指令提供用于实现在流程图一个流程或多个流程和/或方框图一个方框或多个方框中指定的功能的步骤。
尽管已描述了本发明的优选实施例,但本领域内的技术人员一旦得知了基本创造性概念,则可对这些实施例作出另外的变更和修改。所以,所附权利要求意欲解释为包括优选实施例以及落入本发明范围的所有变更和修改。
显然,本领域的技术人员可以对本发明进行各种改动和变型而不脱离本发明的精神和范围。这样,倘若本发明的这些修改和变型属于本发明权利要求及其等同技术的范围之内,则本发明也意图包含这些改动和变型在内。

Claims (11)

  1. 一种跨链交易签名方法,其特征在于,包括:
    第一跨链组件将上链请求发送至第二跨链组件;所述第一跨链组件与客户端对应,所述第二跨链组件与区块链对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
    所述第一跨链组件接收所述第二跨链组件发送的待签名交易和所述区块链的签名算法;所述待签名交易是所述第二跨链组件根据所述上链请求和所述区块链的状态信息生成的;
    所述第一跨链组件根据所述签名算法,使用用户私钥对所述待签名交易签名,将生成的已签名交易发送至所述第二跨链组件,以使所述第二跨链组件将所述已签名交易发送至所述区块链中。
  2. 如权利要求1所述的方法,其特征在于,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用户私钥。
  3. 如权利要求1所述的方法,其特征在于,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
  4. 如权利要求1至3任一项所述的方法,其特征在于,所述待上链数据中包括所述待上链数据对应的目标区块链的标识和交易内容;
    所述第一跨链组件将上链请求发送至第二跨链组件,包括:
    所述第一跨链组件根据所述交易内容生成所述上链请求;
    所述第一跨链组件将所述上链请求发送至所述目标区块链对应的第二跨链组件。
  5. 一种跨链交易签名方法,其特征在于,包括:
    第二跨链组件接收第一跨链组件发送的上链请求;所述第二跨链组件与区块链对应,所述第一跨链组件与客户端对应;所述上链请求是所述第一跨链组件根据所述客户端的待上链数据确定的;
    所述第二跨链组件根据所述上链请求和所述区块链的状态信息生成待签名交易,并将所述待签名交易和所述区块链的签名算法发送至所述第一跨链组件;
    所述第二跨链组件接收所述第一跨链组件发送的已签名交易;所述已签名交易是所述第一跨链组件使用用户私钥对所述待签名交易签名后生成的;
    所述第二跨链组件将所述已签名交易发送至所述区块链中。
  6. 如权利要求5所述的方法,其特征在于,所述签名算法是配置在所述第二跨链组件本地的所述区块链的签名算法;所述用户私钥是配置在所述第一跨链组件本地的所述客户端的用户私钥。
  7. 如权利要求5所述的方法,其特征在于,所述区块链有多个类型,不同类型的区块链的签名算法不同;对于每个区块链,与所述区块链对应的第 二跨链组件的本地配置有所述区块链的签名算法;每个区块链对应的第二跨链组件至少有一个。
  8. 如权利要求5至7任一项所述的方法,其特征在于,所述第二跨链组件根据所述上链请求和所述区块链的状态信息生成待签名交易之前,还包括:
    所述第二跨链组件向所述区块链发送同步请求;
    所述第二跨链组件接收所述区块链反馈的所述状态信息;所述状态信息是所述区块链根据所述区块链的最新状态生成的。
  9. 一种计算设备,其特征在于,包括处理器、存储器、通信接口,其中处理器、存储器与通信接口之间通过总线连接;
    所述处理器,用于读取所述存储器中的程序,执行权利要求1至4任一所述方法,或执行权利要求5至8任一所述方法;
    所述存储器,用于存储一个或多个可执行程序,以及存储所述处理器在执行操作时所使用的数据。
  10. 一种非暂态计算机可读存储介质,其特征在于,所述非暂态计算机可读存储介质存储计算机指令,所述计算机指令用于使所述计算机执行权利要求1至4任一所述方法,或执行权利要求5至8任一所述方法。
  11. 一种计算机程序产品,其特征在于,所述计算机程序产品包括存储在非暂态计算机可读存储介质上的计算程序,所述计算机程序包括程序指令,当所述程序指令被计算机执行时,使所述计算机执行权利要求1至4任一所述方法,或执行权利要求5至8任一所述方法。
PCT/CN2020/127566 2019-11-25 2020-11-09 一种跨链交易签名方法及装置 WO2021103998A1 (zh)

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 (zh) 2021-06-03

Family

ID=70112676

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2020/127566 WO2021103998A1 (zh) 2019-11-25 2020-11-09 一种跨链交易签名方法及装置

Country Status (2)

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

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 众安信息技术服务有限公司 在区块链中进行通信的方法和装置
CN110008686B (zh) * 2018-11-16 2020-12-04 创新先进技术有限公司 跨区块链的数据处理方法、装置、客户端、区块链***
CN111614656B (zh) * 2018-11-16 2021-12-24 创新先进技术有限公司 跨链数据的可信管理方法及装置、电子设备
CN109903041A (zh) * 2018-11-30 2019-06-18 阿里巴巴集团控股有限公司 用于区块链交易的区块上链的方法及***
WO2019101235A2 (en) * 2019-03-04 2019-05-31 Alibaba Group Holding Limited Methods and devices for testing signature verification for blockchain system
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
CN111008827A (zh) 2020-04-14
CN111008827B (zh) 2023-07-21

Similar Documents

Publication Publication Date Title
WO2021103998A1 (zh) 一种跨链交易签名方法及装置
WO2021068728A1 (zh) 一种区块的状态树的生成和链上数据验证的方法及装置
WO2021109735A1 (zh) 一种基于跨链网络的资源处理方法及装置
WO2021036702A1 (zh) 一种基于区块链***的共识方法及装置
CN111080449B (zh) 区块链的跨链交易方法、管理节点、区块链网络
WO2019072280A3 (en) Executing multi-party transactions using smart contracts
CN104253856A (zh) 可缩放Web实时通信媒体引擎以及相关的方法、***
WO2020248982A1 (zh) 一种区块链中交易处理的方法及装置
CN113556339B (zh) 支持异构可信执行环境tee算力节点交互的隐私计算方法
CN111144883A (zh) 一种区块链网络的处理性能分析方法及装置
US20220337429A1 (en) Interactive aggregate signature method, and device and storage medium
WO2020248981A1 (zh) 一种基于区块链的物联网iot设备间通信的方法及装置
WO2024001035A1 (zh) 基于区块链中继通信网络***的消息传输方法及装置
US20220224648A1 (en) Method for balancing cross-domain broadcast network load of blockchain, computer device, and non-transitory computer-readable storage medium
WO2020173126A1 (zh) 基于区块链的会话数据处理方法、装置、设备及介质
EP3972199B1 (en) Open interface management method, electronic device, and storage medium
CN111901384B (zh) 处理报文的***、方法、电子设备以及可读存储介质
JP2023507224A (ja) 通信方法及び関連製品
CN116382675A (zh) 一种接口配置与调用方法、装置、***及介质
CN113905094B (zh) 工业互联网集成方法、装置及***
WO2015169053A1 (zh) 一种报文数据处理方法、装置及***
WO2022095179A1 (zh) 数据处理***、方法、电子设备及存储介质
WO2017032212A1 (zh) 一种数据流处理方法和装置
CN112184452A (zh) 基于区块链的多方频谱交易平台、交易方法及存储介质
CN111783147A (zh) 信用数据交换方法、装置、***以及存储介质

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