CN111161062A - Cross-chain transaction method and device - Google Patents
Cross-chain transaction method and device Download PDFInfo
- Publication number
- CN111161062A CN111161062A CN201911236593.0A CN201911236593A CN111161062A CN 111161062 A CN111161062 A CN 111161062A CN 201911236593 A CN201911236593 A CN 201911236593A CN 111161062 A CN111161062 A CN 111161062A
- Authority
- CN
- China
- Prior art keywords
- transaction
- asset
- account
- signature
- contract
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- 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/3825—Use of electronic signatures
Abstract
The invention relates to the field of financial technology (Fintech), and discloses a method and a device for cross-chain transaction in the field of block chains, which are suitable for cross-chain transaction among transaction accounts of different groups, wherein each group is provided with an HTLC corresponding to the group; the method comprises the following steps: the first group receives a retrieval transaction of a first asset sent by a first client; the retrieval transaction of the first asset comprises information of a first signature, a second signature and a first transaction contract; the first group releases the first asset from the first HTLC upon verifying that the first account corresponding to the first signature, the second account corresponding to the second signature, and the third and fourth accounts in the first transaction contract are consistent. The technical scheme is used for solving the problem that in the prior art, once a trading party locks the assets into the HTLC of the trading party in the group, the assets can be retrieved again only after the HTLC is locked for a long time, so that the efficiency of cross-chain trading is improved.
Description
Technical Field
The embodiment of the invention relates to the field of financial technology (Fintech), in particular to a method and a device for cross-chain transaction in the field of block chains.
Background
With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changing to financial technology (Finteh), but due to the requirements of the financial industry on safety and real-time performance, higher requirements are also put forward on the technologies.
When the assets of the transaction initiator and the assets of the transaction responder belong to different groups, the assets of the transaction initiator and the assets of the transaction responder perform asset exchange to belong to cross-chain transaction. In order to ensure the security of cross-link transaction, both transaction parties lock their assets into their respective group HTLCs (Hashed time lock contracts), and during the locking period when any transaction party is locked into its group HTLCs, none of the transaction parties can extract assets from its group HTLCs, but any transaction party can extract assets from the other group HTLCs based on the ciphertext original text negotiated by both parties.
However, in this method, any party cancels the transaction temporarily, and both parties of the transaction need to wait until the locking duration of the HTLC of their own group to the asset exceeds the preset duration and unlock the asset before retrieving the asset, which causes that any party of the transaction cannot perform the next transaction as soon as possible based on the asset again, thereby reducing the efficiency of the cross-chain transaction.
Disclosure of Invention
The embodiment of the invention provides a method and a device for cross-link transaction, which are used for solving the problem that once a transaction party locks assets into an HTLC of a group of the transaction party in the prior art, the assets can be retrieved again only after the HTLC is locked for a long time, so that the efficiency of cross-link transaction is improved.
The method for cross-link transaction provided by the embodiment of the invention is suitable for cross-link transaction among transaction accounts of different groups, wherein each group is provided with a hash time lock HTLC corresponding to the group, and the HTLC is used for locking assets of the transaction accounts of the group in the group during the cross-link transaction; the method comprises the following steps:
the first group receives a retrieval transaction of a first asset sent by a first client; the retrieval transaction of the first asset comprises information of a first signature, a second signature and a first transaction contract; the first signature is obtained by the first client signing the information of the first transaction contract through a first account; the second signature is obtained by the second client signing the information of the first transaction contract through a second account; the second signature is generated after the second client confirms to cancel the first trading contract; the first transaction contract indicating that the first asset is locked into a first HTLC of the first group;
the first group releases the first asset from the first HTLC upon verifying that a first account corresponding to the first signature, a second account corresponding to the second signature, and a third account and a fourth account in the first transaction contract are consistent.
Optionally, the second signature is generated after the second client confirms to cancel the first transaction contract, and includes:
the second group receives a retrieval transaction of a second asset sent by the second client; the retrieval transaction of the second asset comprises information of a third signature, a fourth signature and a second transaction contract; the third signature is obtained by the first client signing the information of the second transaction contract through the first account; the fourth signature is obtained by the second client signing the information of the second transaction contract through the second account; the third signature is generated after the first client confirms to cancel the second trading contract; the fourth signature is generated by the second client after receiving the third signature sent by the first client; the second transaction contract indicates that the second asset is locked into a second HTLC of the second group; the second trading contract is generated based on the first trading contract;
the second group releases the second asset from the second HTLC upon verifying that the first account corresponding to the third signature, the second account corresponding to the fourth signature, and the third and fourth accounts in the second transaction contract are consistent;
and the second group sends a notice of releasing the second asset to the second client so that the second client generates the second signature after confirming to cancel the first transaction contract.
Optionally, before the first group receives the retrieval transaction of the first asset sent by the first client, the method further includes:
the first group receives asset locking transactions of the third account sent by a third client;
the first group generating the first transaction contract after locking a first asset in the asset lock transaction into the first HTLC, storing the first transaction contract in the first HTLC;
the first group sending the identification of the first trading contract to the third client, so that the third client sends the identification of the first trading contract to the fourth client; the identification of the first trading contract is for the fourth client to verify the locked state of the first asset in the first trading contract from the first HTLC.
Optionally, the information of the first transaction contract includes an identification of the first transaction contract and the first asset;
the first group verifying that a first account corresponding to the first signature, a second account corresponding to the second signature, and a third account and a fourth account in the first transaction contract are consistent, including:
the first group determines that the first account is consistent with the third account if the address of the first account is determined to be consistent with the address of the third account according to the first signature, the identification of the first transaction contract and the first asset;
and if the first group determines that the address of the second account is consistent with the address of the fourth account according to the second signature, the identifier of the first transaction contract and the first asset, determining that the second account is consistent with the fourth account.
Optionally, the method further includes:
the first group releases the first asset from the first HTLC if the first HTLC does not receive the retrieval transaction of the first asset from the third account and does not receive the retrieval transaction of the first asset from the fourth account within a preset time period that the first HTLC locks the first asset.
In the above technical solution, after the first group receives the first signature obtained by the first client signing the information of the first transaction contract through the first account, and receives the second signature obtained by the second client signing the information of the first transaction contract through the second account, if it is determined that the first account corresponding to the first signature and the second account corresponding to the second signature are consistent with the third account and the fourth account in the first transaction contract, that is, if it is determined that the third account agrees to cancel the first transaction contract and the fourth account agrees to cancel the first transaction contract, the first group may release the first asset in the first HTLC, so that the third client may send a transaction to the first group based on the first asset, thereby improving the efficiency of the cross-link transaction.
Correspondingly, the embodiment of the invention also provides a device for cross-chain transaction, which is suitable for cross-chain transaction among transaction accounts of different groups, wherein a Hash Time Lock (HTLC) corresponding to each group is deployed in each group, and the HTLC is used for locking assets of the transaction accounts of the group in the group during the cross-chain transaction; the device comprises:
the receiving and sending unit is used for receiving a retrieval transaction of the first asset sent by the first client; the retrieval transaction of the first asset comprises information of a first signature, a second signature and a first transaction contract; the first signature is obtained by the first client signing the information of the first transaction contract through a first account; the second signature is obtained by the second client signing the information of the first transaction contract through a second account; the second signature is generated after the second client confirms to cancel the first trading contract; the first transaction contract indicating that the first asset is locked into a first HTLC of a first group;
and the processing unit is used for releasing the first asset from the first HTLC after verifying that the first account corresponding to the first signature and the second account corresponding to the second signature are consistent with the third account and the fourth account in the first transaction contract.
Optionally, the transceiver is configured to receive a retrieval transaction of a second asset sent by the second client; the retrieval transaction of the second asset comprises information of a third signature, a fourth signature and a second transaction contract; the third signature is obtained by the first client signing the information of the second transaction contract through the first account; the fourth signature is obtained by the second client signing the information of the second transaction contract through the second account; the third signature is generated after the first client confirms to cancel the second trading contract; the fourth signature is generated by the second client after receiving the third signature sent by the first client; the second transaction contract indicating that the second asset is locked into a second HTLC of a second group; the second trading contract is generated based on the first trading contract;
the processing unit is configured to release the second asset from the second HTLC after verifying that the first account corresponding to the third signature and the second account corresponding to the fourth signature are consistent with the third account and the fourth account in the second transaction contract;
the receiving and sending unit is further configured to send a notification of releasing the second asset to the second client, so that the second client generates the second signature after confirming cancellation of the first transaction contract.
Optionally, the transceiver unit is further configured to receive an asset locking transaction of the third account sent by a third client before receiving the retrieval transaction of the first asset sent by the first client;
the processing unit is further configured to generate the first transaction contract after the first asset in the asset lock transaction is locked into the first HTLC, and store the first transaction contract in the first HTLC;
the first group sending the identification of the first trading contract to the third client, so that the third client sends the identification of the first trading contract to the fourth client; the identification of the first trading contract is for the fourth client to verify the locked state of the first asset in the first trading contract from the first HTLC.
Optionally, the information of the first transaction contract includes an identification of the first transaction contract and the first asset;
the processing unit is specifically configured to determine, according to the first signature, the identifier of the first transaction contract, and the first asset, that the first account is consistent with the third account if it is determined that the address of the first account is consistent with the address of the third account; and if the address of the second account is determined to be consistent with the address of the fourth account according to the second signature, the identifier of the first transaction contract and the first asset, determining that the second account is consistent with the fourth account.
Optionally, the processing unit is further configured to:
and if the retrieval transaction of the first asset of the third account is not received and the extraction transaction of the first asset of the fourth account is not received within a preset time period of locking the first asset by the first HTLC, releasing the first asset from the first HTLC.
Correspondingly, an embodiment of the present invention further provides a computing device, including:
a memory for storing program instructions;
and the processor is used for calling the program instructions stored in the memory and executing the method of the cross-chain transaction according to the obtained program.
Accordingly, embodiments of the present invention also provide a computer-readable non-volatile storage medium, which includes computer-readable instructions, and when the computer-readable instructions are read and executed by a computer, the computer is caused to execute the above method for cross-chain transaction.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the drawings needed to be used in the description of the embodiments will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Fig. 1 is a schematic diagram of a system architecture according to an embodiment of the present invention;
FIG. 2 is a flowchart illustrating a method for cross-chain transaction according to an embodiment of the present invention;
FIG. 3 is a flow chart illustrating another method for cross-chain transactions according to an embodiment of the present invention;
fig. 4 is a schematic structural diagram of a device for cross-chain transaction according to an embodiment of the present invention.
Detailed Description
In order to make the objects, technical solutions and advantages of the present invention clearer, the present invention will be described in further detail with reference to the accompanying drawings, and it is apparent that the described embodiments are only a part of the embodiments of the present invention, not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
For better explanation of the embodiments of the present invention, the key terms involved in the embodiments of the present invention are explained as follows:
HTLC: the method is characterized in that a concept of Hash password and time lock is introduced, when the specific operation is to initiate a transaction, two parties agree that a transfer party freezes a money first, a Hash value is provided, if someone can propose a ciphertext within a certain time, and the Hash value is matched with the known Hash, the money is transferred to a receiving party.
A plurality of groups: the method supports the block chain link points to start a plurality of groups, and the transaction processing, data storage and block consensus among the groups are mutually isolated, so that the operation and maintenance complexity of the system is reduced while the privacy of the block chain system is ensured.
External accounts: controlled by a private key, is an account actually controlled by the user, each external account having a pair of public and private keys, the keys of which are used to sign transactions, and whose addresses are determined by the public keys.
Contract account: is an account that contains contract code, controlled by the contract code; the address of the contract account is calculated from the address of the contract creator at the time of contract creation and the transaction issued by the address.
Fig. 1 exemplarily shows a system architecture to which the method for providing cross-chain transaction according to the embodiment of the present invention is applicable, which may be a client of a first transaction party, a client of a second transaction party, a first group and a second group.
The external accounts deployed in the first group comprise an account of a first trading party and an account of a second trading party; a first HTLC and a first asset contract are deployed in the first group, and the first HTLC is used for locking assets in the first asset contract within a first preset time period; the first counterparty has a first asset in a first asset contract.
The external account deployed in the second group also comprises a first trading party and a second trading party; a second HTLC and a second asset contract are deployed in the second group, and the second HTLC is used for locking the assets in the second asset contract within a second preset time period; the second counterparty has a second asset in a second asset contract.
Here, the first preset time period corresponds to a time period for the first HTLC to lock the asset, for example, if the first transaction party locks the first asset in the first HTLC, the first transaction party cannot retrieve the first asset within the first preset time period, which may also be referred to as a first locking time period; the second predetermined period of time corresponds to a time period for which the second HTLC locks the asset, for example, if the second transaction party locks the second asset in the second HTLC, the second transaction party cannot retrieve the second asset within the second predetermined period of time, which may also be referred to as a second locked time period.
The assets in the first asset contract of the first group and the assets in the second asset contract of the second group may be traded across a chain, which may be an exchange of a first asset of a first trading party in the first asset contract and a second asset of a second trading party in the second asset contract. When the cross-chain transaction is carried out, in order to guarantee the safety of the cross-chain transaction, two transaction parties need to lock respective assets in HTLCs of respective groups, and the locking duration of a transaction initiator needs to be longer than that of a transaction responder.
Based on the system architecture shown in fig. 1, the embodiment of the invention provides a method for cross-chain transaction. Assuming that the first transaction party is a transaction initiator of a cross-link transaction, the first transaction party needs to perform an asset locking operation first, specifically, a client of the first transaction party sends an asset locking transaction to a first group, the asset locking transaction is used for calling a first HTLC to lock a first asset in a first asset contract, specifically, the first group inputs parameters such as a contract address of the first asset contract in the asset locking transaction, an account address of a second transaction party, a first locking duration, a whisper hash and the like into an asset locking function of the first HTLC after receiving the asset locking transaction, so that the asset locking function of the first HTLC locks the first asset in the first asset contract, and the first HTLC generates a locked transaction contract and an identifier of the transaction contract after successfully performing the asset locking transaction, wherein the transaction contract is stored in the first HTLC, the identity of the trade contract is returned to the client of the first trading party, at which point the first trading party completes locking the first asset in the first HTLC. Here, the whisper hash is a hash value of a whisper text input by the first transaction part at the client of the first transaction part.
And the client of the first trading party sends a notification of successful asset locking to the client of the second trading party, wherein the notification comprises the identification of the trading contract. After receiving the notification, the client of the second trading party generates a contract query transaction according to the identification of the transaction contract in the notification, and sends the contract query transaction to the first group, the first group inputs the identification of the transaction contract in the contract query transaction into the contract query function of the first HTLC, the first group feeds back detailed information that the first asset is locked and is queried in the first HTLC to the client of the second trading party, the client of the second trading party verifies the locking state of the first asset, and if the locking state of the first asset is determined to be correct, the client of the second trading party also executes asset locking operation, locks the second asset in the second HTLC, and feeds back the identification of the transaction contract generated by the second HTLC to the client of the first trading party.
It should be noted that, when the second transaction party performs the asset locking operation, the ciphertext hash in the asset locking transaction sent to the second group by the client of the second transaction party is the same as the ciphertext hash in the asset locking transaction sent to the first group by the client of the first transaction party, so that the client of the first transaction party may take out the asset from the second HTLC according to the ciphertext original text corresponding to the ciphertext hash. The ciphertext hash adopted by the second transaction party when performing the asset locking operation may be obtained by the client of the second transaction party from the client of the first transaction party, or may be directly sent by the client of the first transaction party to the client of the second transaction party. Further, a second lock duration for the second HTLC to lock the second asset needs to be less than a first lock duration for the first HTLC to lock the first asset.
Further, the client of the first trading party sends an asset extraction transaction to the second group, wherein the asset extraction transaction comprises a ciphertext original text, and the second group inputs the ciphertext original text into an asset extraction function of the second HTLC, so that the first trading party extracts the second asset from the second group. Because the ciphertext original text is leaked to the second trading party when the first trading party executes the asset extracting operation, the client of the second trading party can also send the asset extracting transaction containing the ciphertext original text to the first group, so that the second trading party extracts the first asset from the first group. To this end, a first trading party and a second trading party complete a cross-chain trade of assets, the first trading party owns the second asset in a first group, and the second trading party owns the first asset in a second group.
In the above implementation, if the second transaction part temporarily changes the idea without performing a cross-chain transaction with the first transaction part after the first transaction part locks the first asset into the first HTLC, the first transaction part can retrieve the first asset from the first HTLC only if the first asset is unlocked after the time length for locking the first asset by the first HTLC exceeds the first locking time length; or after the first trading party locks the first asset into the first HTLC and the second trading party locks the second asset into the second HTLC, the first trading party temporarily changes the idea without performing cross-chain transaction with the second trading party, only when the time length for locking the first asset by the first HTLC exceeds the first locking time length, the first trading party unlocks the first asset, the first trading party can retrieve the first asset from the first HTLC, and when the time length for locking the second asset by the second HTLC exceeds the second locking time length, the second asset is unlocked, and the second trading party can retrieve the second asset from the second HTLC.
In the above situation, any party in the transaction wants to retrieve the locked assets from the HTLC in its own group in the middle, the locked assets can be retrieved only after the HTLC is unlocked, and the locking duration of the HTLC is long because the block-out time intervals of different groups are different and the transaction is confirmed finally after a block chain is generated to generate a plurality of blocks. Therefore, when the trading party locks the assets into the HTLC, if the trading party temporarily wants to cancel the trading, the assets cannot be taken back in time, so that the trading party cannot adopt the assets to perform other operations as soon as possible, namely the trading party cannot send the next trading based on the assets to the group as soon as possible, and the efficiency of the cross-link trading of the group is reduced.
To address the above issues, embodiments of the present invention provide a method for cross-chain transactions for a transacting party to retrieve an asset from an HTLC on-the-fly. To better describe an embodiment of the present invention in which a transacting party temporarily retrieves an asset from an HTLC, a specific implementation of the embodiment of the present invention in which a transacting party locks an asset into an HTLC is described below, and a flowchart may be shown in fig. 2.
And the two transaction parties of the cross-link transaction are a third account and a fourth account, the third account sends the transaction to the first group or the second group through the third client, and the fourth account sends the transaction to the first group or the second group through the fourth client.
The third account and the fourth account may be offline negotiations, with a first asset of the third account in the first group exchanged across links with a second asset of the fourth account in the second group. The third account is used in the first group to store contracts for the first asset, i.e., asset contracts for the third account, and the third account sends an asset lock transaction to the first group via the third client to instruct the first group to lock the first asset in the asset contracts for the third account into the first HTLC.
In the embodiment of the invention, the asset locking transaction comprises the Hash of a ciphertext original text, a contract address of an asset contract of a first asset and a third account and an account address of a fourth account; the ciphertext original text is generated by the first client, may be randomly generated by the client, or may be generated by the client according to a preset rule of the third account. The ciphertext original text is used for performing identity verification when the third account and the fourth account perform cross-link exchange of the first asset and the second asset, that is, when the third account acquires the second asset of the fourth account from the second group, if the third account provides the ciphertext original text, the second group determines that the third account passes the identity authentication and provides the second asset for the third account; when the fourth account acquires the first asset of the third account from the first group, if the fourth account provides the ciphertext original text, the first group determines that the fourth account passes the identity authentication and provides the first asset to the fourth account.
The first group inputs the ciphertext, the first asset, the contract address of the asset contract of the third account, and the account address of the fourth account into an asset locking function of the first HTLC, and the asset locking function of the first HTLC locks the first asset of the asset contract of the third account into the first HTLC and generates a first trade contract for a trade of the locked asset.
The first group may send the identifier of the first transaction contract to the third client, the third client sends the identifier of the first transaction contract to the fourth client, after receiving the identifier of the first transaction contract, the fourth client may query the transaction contract from the first HTLC according to the identifier of the first transaction contract, and verify a result that the first asset is locked into the first HTLC according to the queried first transaction contract, and if the verification passes, the fourth account also performs the asset locking operation, and locks the second asset into the second HTLC.
In the embodiment of the present invention, after the first group sends the identifier of the first transaction contract to the third client, the third client may store the identifier of the first transaction contract in a local browser of the third client, and send the identifier of the first transaction contract to the fourth client through the websocket.
To explain in a specific example below, first assume group 1 and group 2, the contract address of the asset contract for Alice deployed in group 1 is "48 d 8", and the first HTLC address is "4 cb 6"; bob's asset contracts deployed in group 2 have a contract address of "1 d 57" and a second HTLC address of "7 a 28". Alice's account address is "733 c" and Bob's account address is "160 c". The first assets of Alice in the first group are "500 a" and the second assets of Bob in the second group are "100 b". Alice wants to conduct a cross-chain transaction with "500 a" in the first group and "100 b" of Bob in the second group. Wherein, Alice is the initiator of the cross-chain transaction, and Bob is the responder of the cross-chain transaction.
Alice authorizes the first HTLC to transfer 500 a first assets of Alice, then Alice inputs 500 the assets a and the quantity for cross-chain transaction at Alice's client, Alice's client automatically generates random numbers and timeout time, and then calls the asset locking function of the first HTLC. The input parameters of the asset locking function of the first HTLC include an account address "160 c" of Bob, a contract address "48 d 8" of an asset contract of Alice, a first asset "500 a", a result of hashing a random ciphertext original text (assumed to be 1000) sha3, and a first locking time length "2 hours"; after the asset locking function of the first HTLC is successfully called, the first asset "500 a" is locked into the first HTLC, and the trade return value is the identifier "contitid 1" of the trade contract.
Alice's client stores the ContractID1 in localstorage in his browser, and then automatically pushes the ContractID1 to Bob's client via websocket.
After receiving the containment id1, Bob's client invokes the contract query function of the first group to query Alice for details of the assets that were locked in the first group. The input parameters of the contract query function are the identifier "conticid 1" of the transaction contract, and the returned values are Alice's account address "733 c", Bob's account address "160 c", Alice's asset contract address "48 d 8", first asset "500 a", the result of hash of sha3 of random ciphertext original text (assumed to be 1000), first locking time "2 hours", whether the asset is extracted, and whether the asset is retrieved.
Based on the above description of the third account locking the first asset to the first HTLC, when the third account wants to retrieve the first asset from the first HTLC immediately, there may be a method as shown in fig. 3.
In step 301, a first group receives a retrieval transaction for a first asset sent by a first client.
When the first asset is determined to be retrieved from the first HTLC, a first signature is generated according to the information of the first transaction contract by a first account corresponding to the first client, a second signature sent by a second client is obtained, the retrieval transaction of the first asset is generated according to the first signature, the second signature and the information of the first transaction contract, and the retrieval transaction of the first asset is sent to the first group. In the above embodiment, the first trading contract is generated after the first group locks the first asset into the first HTLC according to the asset locking transaction of the third account, that is, the first trading contract is used to indicate that the first asset is locked into the first HTLC of the first group.
In the embodiment of the present invention, the second signature is generated by the second client after the second client confirms to cancel the first transaction contract, and the second client may sign the information of the first transaction contract to obtain the second signature and send the second signature to the second client.
In one implementation, the information of the first trading contract may include an identification of the first asset and the first trading contract; where the identification of the first trade contract refers to the return value of the first HTLC when the first account performs asset locking of the first asset, as in the above example, Alice would like to retrieve "500 a" from the first HTLC, then "500 a" and "conticid 1" would need to be signed.
The first client may generate a first signature according to the identifiers of the first asset and the first transaction contract, and meanwhile, the first client needs to acquire a second signature generated by the second client, where the first client sends the identifiers of the first asset and the transaction contract to the second client, and if the second account agrees to cancel the cross-link transaction, the second client may generate a second signature according to the identifiers of the first asset and the first transaction contract, and send the second signature to the first client.
The first client may input the first signature and the second signature into an asset instant retrieval function of a first HTLC of the first group after receiving the second signature, the first HTLC verifies the first signature and the second signature, and if the verification is passed, it is determined to return the first asset to an asset contract of the first account. Here, the asset instant retrieval function may query the transaction contract for details based on the identification of the transaction contract and return the corresponding first asset to the asset contract of the first account.
In one implementation, the information of the first trading contract may include an identification of the first asset and the first trading contract; the first group determines that the first account is consistent with the third account if determining that the address of the first account is consistent with the address of the third account according to the first signature, the identifier of the first transaction contract and the first asset; and if the first group determines that the address of the second account is consistent with the address of the fourth account according to the second signature, the identifier of the first transaction contract and the first asset, determining that the second account is consistent with the fourth account. Specifically, the first group inputs the first signature, the identifier of the first transaction contract and the first asset into an asset instant retrieval function of a first HTLC, and after the first HTLC determines a first account address according to the first signature, the identifier of the first transaction contract and the first asset, if the address of the first account is determined to be consistent with the address of the third account, the first signature is determined to pass verification; and the first group inputs the second signature, the identifier of the first transaction contract and the first asset into an asset instant retrieval function of the first HTLC, and after the first HTLC determines the address of a second account according to the second signature, the identifier of the first transaction contract and the first asset, if the address of the second account is determined to be consistent with the address of a fourth account, the second signature is determined to pass verification.
In another implementation, the information of the first transaction contract may include an identification of the first transaction contract; if the first group determines that the address of the first account is consistent with the address of the third account according to the first signature and the identifier of the first transaction contract, determining that the first account is consistent with the third account; and if the first group determines that the address of the second account is consistent with the address of the fourth account according to the second signature and the identifier of the first transaction contract, determining that the second account is consistent with the fourth account. Specifically, the first group inputs the first signature and the identifier of the first transaction contract into an asset instant retrieval function of the first HTLC, and after the first HTLC determines the address of the first account according to the first signature and the identifier of the first transaction contract, if the address of the first account is determined to be consistent with the address of the third account, the first signature is determined to pass the verification; and the first group inputs the second signature and the identifier of the first transaction contract into an asset instant retrieval function of the first HTLC, and after the first HTLC determines the address of a second account according to the second signature and the identifier of the first transaction contract, if the address of the second account is determined to be consistent with the address of a fourth account, the second signature is determined to pass verification.
In the embodiment of the present invention, the asset instant retrieval function needs to determine that both the first signature and the second signature pass verification, and then returns the first asset to the asset contract of the first account, that is, the asset contract of the third account, otherwise, the first asset is not returned.
In the embodiment of the present invention, when the second client confirms to cancel the first transaction contract and generate the second signature, the specific steps are as follows: after confirming that the second transaction contract is cancelled, the first client signs the information of the second transaction contract through the first account to obtain a third signature, the first client sends the third signature to the second client, and the second client signs the information of the second transaction contract through the second account to obtain a fourth signature after receiving the third signature; the second client generates a retrieval transaction of the second asset containing the three parameters according to the information of the third signature, the fourth signature and the second transaction contract, and sends the retrieval transaction of the second asset to the second group, and the second group receives the retrieval transaction of the second asset sent by the second client; the second group releases the second asset from the second HTLC after verifying that the first account corresponding to the third signature, the second account corresponding to the fourth signature, and the third account and the fourth account in the second transaction contract are consistent; the second group sends a notification of the release of the second asset to the second client, so that the second client generates a second signature after confirming the cancellation of the first transaction contract.
In this embodiment of the present invention, the second transaction contract, that is, the second group in the above embodiment, is generated after the second asset is locked into the second HTLC according to the asset locking transaction of the fourth account, that is, the second transaction contract is used to indicate that the second asset is locked into the second HTLC of the second group, and the second transaction contract is generated based on the first transaction contract. In other words, the third account is the initiator of the transaction, the third account will lock the first asset in the third group to generate the first transaction contract, and the fourth account will lock the second asset in the fourth group to generate the second transaction contract after determining that the first transaction contract is generated.
In the embodiment of the invention, if both transaction parties lock the assets in the HTLCs of the respective groups, the transaction initiator can take the assets out of the HTLCs of the group where the transaction responder is located only after the transaction responder takes the assets out of the HTLCs of the group where the transaction responder is located, because the transaction initiator has the Hash original text of the transaction parties when the transaction initiator performs the asset locking operation, and if the transaction initiator takes the assets out of the HTLCs of the group where the transaction responder is located first, the transaction initiator can take the assets locked by the transaction responder out of the HTLCs of the group where the transaction responder is located by adopting the Hash original text before the transaction responder takes the assets out of the HTLCs of the group where the transaction responder is located, so that the security of the assets of both transaction parties and the consistency of transaction results can be realized through the embodiment of the invention.
To better explain the embodiments of the present invention, the description is continued with reference to the above examples. In the above example, there may be two cases, one is that Alice temporarily cancels the transaction, and the other is that Bob temporarily cancels the transaction.
In the first case, after receiving the conteractid 1, Bob's client invokes a contract query function of the first group to query Alice for detailed information of locking assets in the first group, Bob's client may verify whether the locking state of the first asset is correct according to the queried detailed information of the transaction contract, and if so, execute the above asset locking operation in the same way to lock the second asset "100 b" into the second HTLC, and then Bob's client stores the transaction return value "conteractid 2" in localstorage of its browser, and then automatically pushes the conteractid 2 to the first client through bsocket. At this time, assuming that Alice temporarily cancels the transaction, Alice needs to instantly retrieve the first asset locked in the first HTLC, Bob needs to instantly retrieve the second asset locked in the second HTLC, and since Alice actively cancels, Alice's client generates a first signature for retrieving "500 a" after signing "contid 1" and "500 a", generates a first signature for retrieving "100 b" after signing "contid 2" and "100 b", and sends two first signatures to Bob's client, Bob's client generates a second signature for retrieving the first asset after signing "contid 1" and "500 a" if he agrees to cancel the transaction, and generates a second signature for retrieving the second asset after signing "contid 2" and "100 b", at this time, Bob's client generates a second signature for retrieving the second asset after signing "100 b" and sends the first and second signature to the HTLC group, and then Bob's client can generate a group signature for retrieving the first asset, thus, the second asset is immediately retrieved, and at the same time, the client of Bob also sends the second signature for retrieving the first asset to the client of Alice, and if the client of Alice takes the first signature and the second signature for retrieving the first asset, an asset retrieval transaction can be generated and sent to the first HTLC of the first group, so that the first asset is immediately retrieved.
In this example, if Bob does not agree to cancel the transaction, Alice cannot extract the first asset from the first HTLC because Alice does not extract the second asset from the second HTLC, and therefore, Alice cannot leak the ciphertext original text to Bob. If Bob's client retrieves the second asset from the second HTLC, Alice may still retrieve the first asset from the first HTLC after the first lock duration without sending Alice's client the second signature for retrieving the first asset.
In this example, Bob needs to retrieve the second asset from the second HTLC before sending the second signature for retrieving the first asset to Alice's client, to prevent Alice from using the hash-script to remove the second asset from the second HTLC after retrieving the first asset from the first HTLC.
Based on the above example, there is also an implementation that if the first group does not receive the asset retrieval transaction of the third account and does not receive the asset extraction transaction of the fourth account within the preset period of time (within the first locking duration) that the first HTLC locks the first asset, the first group releases the first asset from the first HTLC, that is, the first group may call the asset retrieval function of the first HTLC, so that the first HTLC returns the first asset to the asset contract of the third account.
In the second case, Bob temporarily cancels the transaction after Alice has locked the first asset into the first HTLC, Bob may not need to lock the second asset into the second HTLC and Alice needs to retrieve the locked first asset from the first HTLC instantaneously. And since Bob initiatively cancels, the client of Bob generates a second signature for retrieving the first asset after signing the "conticid 1" and the "500 a" and sends the second signature to the client of Alice, and the client of Alice generates a first signature for retrieving the first asset after signing the "conticid 1" and the "500 a", and at this time, the client of Alice takes the first signature and the second signature for retrieving the first asset, and can generate an asset retrieval transaction and send the asset retrieval transaction to the first HTLC of the first group, thereby retrieving the first asset immediately.
It should be noted that the third client may be configured to monitor an event in the first HTLC, and if it is monitored that the first asset in the first HTLC is taken out by the fourth account, the third account may also take out the second asset in the second HTLC. Similarly, the fourth client may also be configured to monitor an event in the second HTLC, and if it is monitored that the second asset in the second HTLC is taken out by the third account, the fourth account may also take out the first asset in the first HTLC.
In the embodiment of the present invention, after a first group receives a first signature obtained by a first client signing information of a first transaction contract through a first account, and receives a second signature obtained by a second client signing information of the first transaction contract through a second account, if it is determined that a first account corresponding to the first signature and a second account corresponding to the second signature are consistent with a third account and a fourth account in the first transaction contract, that is, if it is determined that the third account agrees to cancel the first transaction contract and the fourth account agrees to cancel the first transaction contract, the first group may release a first asset in a first HTLC, so that the third client may send a transaction to the first group based on the first asset, thereby improving the efficiency of cross-link transaction.
Based on the same inventive concept, fig. 4 exemplarily shows a structure of a device for cross-chain transaction according to an embodiment of the present invention, which is applicable to cross-chain transactions between transaction accounts of different groups, where a hash time lock HTLC corresponding to each group is disposed in each group, and the HTLC is used for locking assets of the transaction accounts of the group in the group during the cross-chain transaction; the apparatus may perform a process of a method of cross-chain transactions.
The device comprises:
a transceiving unit 401, configured to receive a retrieval transaction of a first asset sent by a first client; the retrieval transaction of the first asset comprises information of a first signature, a second signature and a first transaction contract; the first signature is obtained by the first client signing the information of the first transaction contract through a first account; the second signature is obtained by the second client signing the information of the first transaction contract through a second account; the second signature is generated after the second client confirms to cancel the first trading contract; the first transaction contract indicating that the first asset is locked into a first HTLC of a first group;
a processing unit 402, configured to release the first asset from the first HTLC after verifying that the first account corresponding to the first signature and the second account corresponding to the second signature are consistent with the third account and the fourth account in the first transaction contract.
Optionally, the transceiver 401 is configured to receive a retrieval transaction of a second asset sent by the second client; the retrieval transaction of the second asset comprises information of a third signature, a fourth signature and a second transaction contract; the third signature is obtained by the first client signing the information of the second transaction contract through the first account; the fourth signature is obtained by the second client signing the information of the second transaction contract through the second account; the third signature is generated after the first client confirms to cancel the second trading contract; the fourth signature is generated by the second client after receiving the third signature sent by the first client; the second transaction contract indicating that the second asset is locked into a second HTLC of a second group; the second trading contract is generated based on the first trading contract;
the processing unit 402, configured to release the second asset from the second HTLC after verifying that the first account corresponding to the third signature and the second account corresponding to the fourth signature are consistent with the third account and the fourth account in the second transaction contract;
the transceiving unit 401 is further configured to send a notification of releasing the second asset to the second client, so that the second client generates the second signature after confirming to cancel the first transaction contract.
Optionally, the transceiver 401 is further configured to receive an asset locking transaction of the third account sent by a third client before receiving the retrieval transaction of the first asset sent by the first client;
the processing unit 402 is further configured to generate the first transaction contract after locking the first asset in the asset lock transaction into the first HTLC, and store the first transaction contract in the first HTLC;
the first group sending the identification of the first trading contract to the third client, so that the third client sends the identification of the first trading contract to the fourth client; the identification of the first trading contract is for the fourth client to verify the locked state of the first asset in the first trading contract from the first HTLC.
Optionally, the information of the first transaction contract includes an identification of the first transaction contract and the first asset;
the processing unit 402 is specifically configured to determine, according to the first signature, the identifier of the first transaction contract, and the first asset, that the first account is consistent with the third account if it is determined that the address of the first account is consistent with the address of the third account; and if the address of the second account is determined to be consistent with the address of the fourth account according to the second signature, the identifier of the first transaction contract and the first asset, determining that the second account is consistent with the fourth account.
Optionally, the processing unit 402 is further configured to:
and if the retrieval transaction of the first asset of the third account is not received and the extraction transaction of the first asset of the fourth account is not received within a preset time period of locking the first asset by the first HTLC, releasing the first asset from the first HTLC.
Based on the same inventive concept, an embodiment of the present invention further provides a computing device, including:
a memory for storing program instructions;
and the processor is used for calling the program instructions stored in the memory and executing the method of the cross-chain transaction according to the obtained program.
Based on the same inventive concept, the embodiment of the present invention also provides a computer-readable non-volatile storage medium, which includes computer-readable instructions, and when the computer reads and executes the computer-readable instructions, the computer is caused to execute the method for cross-chain transaction.
The present invention is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems), and computer program products according to embodiments of the invention. It will be understood that each flow and/or block of the flow diagrams and/or block diagrams, and combinations of flows and/or blocks in the flow diagrams and/or block diagrams, can be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer, special purpose computer, embedded processor, or other programmable data processing apparatus to produce a machine, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be stored in a computer-readable memory that can direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function specified in the flowchart flow or flows and/or block diagram block or blocks.
These computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions specified in the flowchart flow or flows and/or block diagram block or blocks.
While preferred embodiments of the present invention have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. Therefore, it is intended that the appended claims be interpreted as including preferred embodiments and all such alterations and modifications as fall within the scope of the invention.
It will be apparent to those skilled in the art that various changes and modifications may be made in the present invention without departing from the spirit and scope of the invention. Thus, if such modifications and variations of the present invention fall within the scope of the claims of the present invention and their equivalents, the present invention is also intended to include such modifications and variations.
Claims (12)
1. A method of cross-chain transaction is characterized in that the method is applicable to cross-chain transaction among different groups of transaction accounts, a hash time locking approximate HTLC corresponding to the groups is deployed in each group, and the HTLC is used for locking assets of the transaction accounts of the groups in the groups during the cross-chain transaction; the method comprises the following steps:
the first group receives a retrieval transaction of a first asset sent by a first client; the retrieval transaction of the first asset comprises information of a first signature, a second signature and a first transaction contract; the first signature is obtained by the first client signing the information of the first transaction contract through a first account; the second signature is obtained by the second client signing the information of the first transaction contract through a second account; the second signature is generated after the second client confirms to cancel the first trading contract; the first transaction contract indicating that the first asset is locked into a first HTLC of the first group;
the first group releases the first asset from the first HTLC upon verifying that a first account corresponding to the first signature, a second account corresponding to the second signature, and a third account and a fourth account in the first transaction contract are consistent.
2. The method of claim 1, wherein the second signature is generated after the second client confirms cancellation of the first transaction contract, comprising:
the second group receives a retrieval transaction of a second asset sent by the second client; the retrieval transaction of the second asset comprises information of a third signature, a fourth signature and a second transaction contract; the third signature is obtained by the first client signing the information of the second transaction contract through the first account; the fourth signature is obtained by the second client signing the information of the second transaction contract through the second account; the third signature is generated after the first client confirms to cancel the second trading contract; the fourth signature is generated by the second client after receiving the third signature sent by the first client; the second transaction contract indicates that the second asset is locked into a second HTLC of the second group; the second trading contract is generated based on the first trading contract;
the second group releases the second asset from the second HTLC upon verifying that the first account corresponding to the third signature, the second account corresponding to the fourth signature, and the third and fourth accounts in the second transaction contract are consistent;
and the second group sends a notice of releasing the second asset to the second client so that the second client generates the second signature after confirming to cancel the first transaction contract.
3. The method of claim 1, wherein prior to the first group receiving the retrieval transaction for the first asset sent by the first client, further comprising:
the first group receives asset locking transactions of the third account sent by a third client;
the first group generating the first transaction contract after locking a first asset in the asset lock transaction into the first HTLC, storing the first transaction contract in the first HTLC;
the first group sending the identification of the first trading contract to the third client, so that the third client sends the identification of the first trading contract to the fourth client; the identification of the first trading contract is for the fourth client to verify the locked state of the first asset in the first trading contract from the first HTLC.
4. The method of claim 3, wherein the information of the first trading contract comprises an identification of the first trading contract and the first asset;
the first group verifying that a first account corresponding to the first signature, a second account corresponding to the second signature, and a third account and a fourth account in the first transaction contract are consistent, including:
the first group determines that the first account is consistent with the third account if the address of the first account is determined to be consistent with the address of the third account according to the first signature, the identification of the first transaction contract and the first asset;
and if the first group determines that the address of the second account is consistent with the address of the fourth account according to the second signature, the identifier of the first transaction contract and the first asset, determining that the second account is consistent with the fourth account.
5. The method of any of claims 1 to 4, further comprising:
the first group releases the first asset from the first HTLC if the first HTLC does not receive the retrieval transaction of the first asset from the third account and does not receive the retrieval transaction of the first asset from the fourth account within a preset time period that the first HTLC locks the first asset.
6. An apparatus of cross-chain transaction, which is adapted to cross-chain transaction between transaction accounts of different groups, wherein each group is disposed with a Hash Time Lock (HTLC) corresponding to the group, and the HTLC is used for locking assets of the transaction accounts of the group in the group during the cross-chain transaction; the device comprises:
the receiving and sending unit is used for receiving a retrieval transaction of the first asset sent by the first client; the retrieval transaction of the first asset comprises information of a first signature, a second signature and a first transaction contract; the first signature is obtained by the first client signing the information of the first transaction contract through a first account; the second signature is obtained by the second client signing the information of the first transaction contract through a second account; the second signature is generated after the second client confirms to cancel the first trading contract; the first transaction contract indicating that the first asset is locked into a first HTLC of a first group;
and the processing unit is used for releasing the first asset from the first HTLC after verifying that the first account corresponding to the first signature and the second account corresponding to the second signature are consistent with the third account and the fourth account in the first transaction contract.
7. The apparatus of claim 6,
the receiving and sending unit is used for receiving a retrieval transaction of a second asset sent by the second client; the retrieval transaction of the second asset comprises information of a third signature, a fourth signature and a second transaction contract; the third signature is obtained by the first client signing the information of the second transaction contract through the first account; the fourth signature is obtained by the second client signing the information of the second transaction contract through the second account; the third signature is generated after the first client confirms to cancel the second trading contract; the fourth signature is generated by the second client after receiving the third signature sent by the first client; the second transaction contract indicating that the second asset is locked into a second HTLC of a second group; the second trading contract is generated based on the first trading contract;
the processing unit is configured to release the second asset from the second HTLC after verifying that the first account corresponding to the third signature and the second account corresponding to the fourth signature are consistent with the third account and the fourth account in the second transaction contract;
the receiving and sending unit is further configured to send a notification of releasing the second asset to the second client, so that the second client generates the second signature after confirming cancellation of the first transaction contract.
8. The apparatus of claim 6,
the receiving and sending unit is further used for receiving the asset locking transaction of the third account sent by a third client before the retrieval transaction of the first asset sent by the first client is received;
the processing unit is further configured to generate the first transaction contract after the first asset in the asset lock transaction is locked into the first HTLC, and store the first transaction contract in the first HTLC;
the first group sending the identification of the first trading contract to the third client, so that the third client sends the identification of the first trading contract to the fourth client; the identification of the first trading contract is for the fourth client to verify the locked state of the first asset in the first trading contract from the first HTLC.
9. The apparatus of claim 8, wherein the information of the first transaction contract comprises an identification of the first transaction contract and the first asset;
the processing unit is specifically configured to determine, according to the first signature, the identifier of the first transaction contract, and the first asset, that the first account is consistent with the third account if it is determined that the address of the first account is consistent with the address of the third account; and if the address of the second account is determined to be consistent with the address of the fourth account according to the second signature, the identifier of the first transaction contract and the first asset, determining that the second account is consistent with the fourth account.
10. The apparatus of any of claims 6 to 9, wherein the processing unit is further to:
and if the retrieval transaction of the first asset of the third account is not received and the extraction transaction of the first asset of the fourth account is not received within a preset time period of locking the first asset by the first HTLC, releasing the first asset from the first HTLC.
11. A computing device, comprising:
a memory for storing program instructions;
a processor for calling program instructions stored in said memory to execute the method of any one of claims 1 to 5 in accordance with the obtained program.
12. A computer-readable non-transitory storage medium including computer-readable instructions which, when read and executed by a computer, cause the computer to perform the method of any one of claims 1 to 5.
Priority Applications (2)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911236593.0A CN111161062B (en) | 2019-12-05 | 2019-12-05 | Cross-chain transaction method and device |
| PCT/CN2020/127875 WO2021109809A1 (en) | 2019-12-05 | 2020-11-10 | Cross-chain transaction method and device |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201911236593.0A CN111161062B (en) | 2019-12-05 | 2019-12-05 | Cross-chain transaction method and device |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111161062A true CN111161062A (en) | 2020-05-15 |
| CN111161062B CN111161062B (en) | 2023-10-03 |
Family
ID=70556405
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201911236593.0A Active CN111161062B (en) | 2019-12-05 | 2019-12-05 | Cross-chain transaction method and device |
Country Status (2)
| Country | Link |
|---|---|
| CN (1) | CN111161062B (en) |
| WO (1) | WO2021109809A1 (en) |
Cited By (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN112184245A (en) * | 2020-09-30 | 2021-01-05 | 深圳前海微众银行股份有限公司 | Cross-block-chain transaction identity confirmation method and device |
| WO2021109809A1 (en) * | 2019-12-05 | 2021-06-10 | 深圳前海微众银行股份有限公司 | Cross-chain transaction method and device |
| CN113283985A (en) * | 2021-04-27 | 2021-08-20 | 上海添玑网络服务有限公司 | HTLC-based cross-chain transaction method |
| CN113595733A (en) * | 2020-07-03 | 2021-11-02 | 支付宝实验室(新加坡)有限公司 | Method, system and apparatus for managing transactions in multiple blockchain networks |
| US11354657B2 (en) | 2020-07-03 | 2022-06-07 | Alipay Labs (singapore) Pte. Ltd. | Managing transactions in multiple blockchain networks |
| US11372848B2 (en) | 2020-07-03 | 2022-06-28 | Alipay Labs (singapore) Pte. Ltd. | Managing transactions in multiple blockchain networks |
| CN112184245B (en) * | 2020-09-30 | 2024-04-26 | 深圳前海微众银行股份有限公司 | Transaction identity confirmation method and device for cross-region block chain |
Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107679857A (en) * | 2017-10-10 | 2018-02-09 | 马晶瑶 | Across the chain method of commerce and storage medium of block chain |
| CN109146448A (en) * | 2018-07-13 | 2019-01-04 | 杭州复杂美科技有限公司 | Across chain assets transfer method, equipment and storage medium |
| CN109409877A (en) * | 2018-10-09 | 2019-03-01 | 北京网录科技有限公司 | A kind of across the chain value exchange method of block chain based on HTLC technology |
| US20190370792A1 (en) * | 2018-06-03 | 2019-12-05 | VVOW Company Limited | Peer-to-peer cryptocurrency and crypto asset trading platform |
Family Cites Families (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107784569A (en) * | 2016-08-24 | 2018-03-09 | 深圳市图灵奇点智能科技有限公司 | A kind of high-throughput quick bookkeeping methods on distributed account book |
| CN111161062B (en) * | 2019-12-05 | 2023-10-03 | 深圳前海微众银行股份有限公司 | Cross-chain transaction method and device |
-
2019
- 2019-12-05 CN CN201911236593.0A patent/CN111161062B/en active Active
-
2020
- 2020-11-10 WO PCT/CN2020/127875 patent/WO2021109809A1/en active Application Filing
Patent Citations (4)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107679857A (en) * | 2017-10-10 | 2018-02-09 | 马晶瑶 | Across the chain method of commerce and storage medium of block chain |
| US20190370792A1 (en) * | 2018-06-03 | 2019-12-05 | VVOW Company Limited | Peer-to-peer cryptocurrency and crypto asset trading platform |
| CN109146448A (en) * | 2018-07-13 | 2019-01-04 | 杭州复杂美科技有限公司 | Across chain assets transfer method, equipment and storage medium |
| CN109409877A (en) * | 2018-10-09 | 2019-03-01 | 北京网录科技有限公司 | A kind of across the chain value exchange method of block chain based on HTLC technology |
Cited By (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2021109809A1 (en) * | 2019-12-05 | 2021-06-10 | 深圳前海微众银行股份有限公司 | Cross-chain transaction method and device |
| CN113595733A (en) * | 2020-07-03 | 2021-11-02 | 支付宝实验室(新加坡)有限公司 | Method, system and apparatus for managing transactions in multiple blockchain networks |
| US11354657B2 (en) | 2020-07-03 | 2022-06-07 | Alipay Labs (singapore) Pte. Ltd. | Managing transactions in multiple blockchain networks |
| US11372848B2 (en) | 2020-07-03 | 2022-06-28 | Alipay Labs (singapore) Pte. Ltd. | Managing transactions in multiple blockchain networks |
| US11403632B2 (en) | 2020-07-03 | 2022-08-02 | Alipay Labs (singapore) Pte. Ltd. | Managing transactions in multiple blockchain networks |
| CN112184245A (en) * | 2020-09-30 | 2021-01-05 | 深圳前海微众银行股份有限公司 | Cross-block-chain transaction identity confirmation method and device |
| CN112184245B (en) * | 2020-09-30 | 2024-04-26 | 深圳前海微众银行股份有限公司 | Transaction identity confirmation method and device for cross-region block chain |
| CN113283985A (en) * | 2021-04-27 | 2021-08-20 | 上海添玑网络服务有限公司 | HTLC-based cross-chain transaction method |
Also Published As
| Publication number | Publication date |
|---|---|
| WO2021109809A1 (en) | 2021-06-10 |
| CN111161062B (en) | 2023-10-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111161062B (en) | Cross-chain transaction method and device | |
| US11095679B2 (en) | Method and apparatus for processing account in blockchain, storage medium, and computer device | |
| CN109189853B (en) | Method and device for synchronizing data between block chains | |
| CN107342867B (en) | Signature verification method and device | |
| CN110892434B (en) | Transferring digital ticket based on blockchain network | |
| CN111629039B (en) | Block chain consensus method, client, endorsement node and sequencing node | |
| EP3247070B1 (en) | Cryptocurrency-based event participation verification | |
| WO2018187410A1 (en) | Systems and methods for data backup and authentication using blockchain | |
| CN110599174B (en) | Block chain information processing method and related equipment | |
| CN111932233B (en) | Resource transfer method, device and equipment | |
| CN112215709A (en) | Block chain based bill extraction digital circulation method and device and electronic equipment | |
| CN112084234A (en) | Data acquisition method, apparatus, device and medium | |
| CN113645278B (en) | Cross-chain message transmission method, device and storage medium of block chain | |
| CN107577700A (en) | The processing method and processing device of database disaster tolerance | |
| CN110535809B (en) | Identification code pulling method, storage medium, terminal device and server | |
| CN111311261B (en) | Safe processing method, device and system for online transaction | |
| CN111680325A (en) | Data escorting method and device | |
| CN107947934B (en) | Fingerprint identification and authentication system and method of mobile terminal based on bank system | |
| CN111311260A (en) | Method and device for resetting account private key | |
| CN112734410B (en) | Method and device for pre-executing chain code in Fabric Block chain | |
| CN112307445B (en) | Identity management method and device based on block chain | |
| CN112291189B (en) | Method, device, equipment and storage medium for sending and checking ciphertext | |
| CN113904869A (en) | Method for detecting malicious node in block chain and block chain | |
| CN113487308A (en) | Bank terminal deposit system and method based on block chain | |
| CN114139121A (en) | Identity verification method and device, electronic equipment and computer readable storage medium |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |