TWM593602U - Cross-chain and non-custodial entity performance guarantee transaction system - Google Patents

Abstract

A performance guarantee transaction system based on cross-chain and non-custodial entities. The buyer-side host and seller-side host respectively host digital assets in different blockchain smart contracts, and transfer or refund each other according to the results of the transaction entity's delivery outside the chain. Digital assets managed by each other in smart contracts, and allowing third-party hosts to conduct transaction arbitration to determine whether the off-chain delivery is successful without hosting the transaction entity. When judging the success of the off-chain delivery, it is possible without the consent of the buyer's host Transfer the digital assets hosted by the buyer's host and the seller's host to each other to achieve the technical effect of improving the reliability of the performance guarantee.

Description

Cross-chain and non-custodial entity performance guarantee transaction system

This creation relates to a performance guarantee system, especially a performance guarantee transaction system based on cross-chain and non-custodial entities.

In recent years, with the popularity and vigorous development of e-commerce, various related applications have sprung up. Among them, third-party custodians that provide transaction guarantees are the most common.

Generally speaking, the traditional third-party custody refers to that the buyer and seller deliver assets (including: currency, physical goods, etc.) to a third-party entity for custody. After the buyer and seller complete the transaction in accordance with the agreement, the third-party entity will deliver the custody. Assets to buyers and sellers in order to avoid transaction risks. Since today's trading environment has been largely digitized, third-party escrow in the form of networks, such as third-party payment and other services, relies on highly trusted third-party entities for asset custody or transaction arbitration.

In view of this, some manufacturers have proposed blockchain technology, which uses the blockchain mechanism to conduct transactions in order to use its difficult-to-tamper and non-repudiation features to achieve highly trusted third-party escrow transactions, however, at the same time In multiple independent blockchain network environments, because different blockchains may use different protocols, even if the same protocol is used, the independent blockchain networks cannot directly communicate records. Therefore, although it can be hosted on the blockchain, there is no effective arbitration mechanism, which leads to the problem of poor reliability of the performance guarantee.

In summary, it can be seen that the prior art has had a problem of poor reliability of performance guarantee for a long time, so it is necessary to propose improved technical means to solve this problem.

This creation discloses a performance guarantee transaction system based on cross-chain and non-custodial entities.

First, the author discloses a performance guarantee transaction system based on cross-chain and non-custodial entities. This system includes: a first blockchain, a second blockchain, a third-party host, a buyer-side host, and a seller-side host. Among them, the first blockchain is used to run the published first smart contract, and provides the buyer's first wallet address and the seller's first wallet address; the second blockchain is used to run the published second smart contract, and provides The buyer's second wallet address and the seller's second wallet address, where the second smart contract includes a second extraction function to receive the unlock secret code, and hash the unlock secret code to hash with the buyer's side in the second smart contract The value or the third-party hash value is compared, and when the comparison matches, the second digital asset in the custody of the second smart contract is transferred to the buyer's second wallet address, and then the unlock secret code is stored in the second smart contract ; The third-party host is connected to the first blockchain and the second blockchain at the same time. This third-party host is used to set the third-party hash value in the first smart contract and execute the second when it detects that the off-chain delivery is successful. The second extraction function of the smart contract and the unlock secret code is transmitted.

Next, in the part of the buyer-side host, it is connected to the first blockchain and the second blockchain at the same time. The buyer-side host includes: a buyer-side publishing module and a buyer-side detection module. Wherein, the buyer-side publishing module is used to publish the first smart contract on the first blockchain, and set the buyer-side hash value in the first smart contract, and transfer the first digital asset to the first smart contract escrow The buyer-side detection module is used to execute the second extraction function of the second smart contract and send an unlock secret when it detects that the off-chain delivery is successful.

In the part of the seller-side host, it is connected to the first blockchain and the second blockchain at the same time. The seller-side host includes: a seller-side publishing module and a seller-side detection module. Wherein, the seller-side release module is used to obtain the buyer-side hash value and the third-party hash value from the first smart contract, release the second smart contract on the second blockchain, and transfer the second digital asset to Second smart contract escrow; the seller-side detection module is used to execute the first extraction function of the first smart contract when the unlocking secret word is detected in the second smart contract, wherein the first extraction function Hash the detected unlock ciphers to compare with the buyer-side hash value or third-party hash value in the first smart contract, and when the comparison matches, the first digit in the first smart contract escrow The assets are transferred to the first wallet address of the seller.

The system disclosed in this creation is as above, and the difference from the previous technology is that this creation is to host digital assets in different blockchain smart contracts through the buyer-side host and the seller-side host, and according to the results of the transaction entity's delivery outside the chain, mutual Transfer or refund each other’s digital assets hosted in smart contracts, and allow third-party hosts to conduct transaction arbitration to determine whether the off-chain delivery is successful without hosting the transaction entity. When the off-chain delivery is successful, no buyer-side host’s consent is required , That is, the digital assets hosted by the buyer's host and the seller's host can be transferred to each other.

Through the above-mentioned technical means, this creation can achieve the technical effect of improving the reliability of the performance guarantee.

In the following, the implementation of the creation will be described in detail with reference to the drawings and examples, so as to fully understand and implement the implementation process of how the creation uses technical means to solve technical problems and achieve technical efficacy.

Before explaining the performance guarantee transaction system based on cross-chain and non-custodial entities disclosed by this creation, the environment used by this creation will be explained first. This creation is applied in a multi-blockchain environment, for example: there are two or For more than two blockchains, each blockchain can run the same blockchain agreement or different blockchain agreements. For example, one is a Bitcoin blockchain and the other is an Ethereum blockchain. chain. However, whether it is the same blockchain agreement or not, both the buyer-side host and the seller-side host are allowed to publish smart contracts on the blockchain, and the third-party host, buyer-side host, and seller-side host are allowed to pass through the blockchain network. Any node operates on each blockchain, for example: managing digital assets (including digital currency) on the blockchain, performing smart contract functions, and so on.

Next, to explain the terms defined by this creation, the "first smart contract" and "second smart contract" mentioned in this creation refer to the smart contracts issued (Deploy) on the blockchain network, where, The first smart contract is published on the first blockchain; the second smart contract is published on the second blockchain. In fact, the smart contract refers to a computer program that drives execution of instructions based on established conditions and transmitted information. Specifically, the smart contract uses programming languages such as Solidity, Serpent, LLL, EtherScript, Sidechain, etc. To write, it can contain various functions, events, parameter status, etc. Taking "Ethereum" as an example, its smart contract is compiled to get a binary code and apply a binary interface ( Application Binary Interface, ABI) in order to broadcast the smart contract to the blockchain network, waiting for the miner to put the smart contract on the blockchain and get the corresponding address, so that the smart contract is released through the blockchain transaction . After that, each node can execute the corresponding smart contract according to this address, and change the state of the smart contract on the blockchain and detect whether the event is triggered by different instructions. In addition, the "first digital asset" and "second digital asset" refer to the content presented in digital form, with the concept of ownership, and various records that can be held and transferred for ownership, such as: digital currency, electronic Tickets, digital property rights registration, electronic invoices, etc., where "first digital asset" is the digital asset of the first smart contract hosted on the first blockchain; "second digital asset" is the second block of assets Digital assets of the second smart contract of the chain. In other words, the first digital asset is implemented in the first blockchain; the second digital asset is implemented in the second blockchain. Next, the "off-chain delivery" refers to the value delivery behavior independent of the blockchain, such as: physical commodity delivery, offline services, non-blockchain digital asset delivery, etc. In particular, this creation can be regarded as an "unmanaged entity (Unmanaged Entity)", the difference between it and traditional third-party escrow (Escrow) is that the former does not actually escrow the trading entity or digital assets to a third party, and In the latter case, a third party other than the buyer and seller will take care of the trading entity or digital assets, such as: specific documents, contracts, money, securities, or other property. Only when certain conditions are met or legal events occur, will this third party Deliver its deposit to a specific person. Specifically, the third-party host as a third party in this creation does not actually host any entities or digital assets, and is only used to determine whether the off-chain delivery is successful for arbitration. If it is successful, the unlock secret code is transmitted, otherwise, no operation is performed. , As the buyer’s host on the buyer’s side, it deposits its digital assets in a smart contract that it publishes on the blockchain. Similarly, the seller’s host on the seller’s side will also host its digital assets on its own in another. Blockchain smart contracts. Therefore, unlike the traditional third-party custody, when the transaction dispute occurs, the deposit will be frozen in the third party. This creation uses the third-party host to arbitrate whether the off-chain delivery is successful. If it is successful, it will be allowed without the buyer’s consent. When the digital assets of the buyer and seller are transferred, and when the off-chain delivery fails, wait for the overtime of the escrow of the smart contract to be satisfied, so that the smart contract automatically returns the custodial digital assets to the corresponding buyer and seller.

The following describes the creation of a performance guarantee transaction system based on cross-chain and non-custodial entities with the help of diagrams. Please refer to "Picture 1", which is the creation of performance guarantee transactions based on cross-chain and non-custodial entities A system block diagram of the system. The system includes: a first blockchain 110, a second blockchain 120, a third-party host 130, a buyer-side host 140, and a seller-side host 150. The third-party host 130, the buyer-side host 140, and the seller-side host 150 can be implemented using computer devices such as personal computers, notebook computers, tablet computers, smart phones, and servers. Among them, the first blockchain 110 is used to run the published first smart contract, and provide the "buyer's first wallet address" and "seller's first wallet address", which is the wallet address information possessed by the digital wallet. Represents a unique identification code on the blockchain. In actual implementation, the "buyer-side first wallet address" refers to the wallet address used by the buyer-side host 140 in the first blockchain 110; the "seller-side first wallet address" refers to the seller-side host 150 The wallet address used in the first blockchain 110. In fact, since the third-party host 130 is also connected to the first blockchain 110 and the second blockchain 120 at the same time, the first blockchain 110 will also provide a "third-party first wallet address" (ie: a third-party host 130 is the wallet address used in the first blockchain 110), but because it does not involve the transfer of digital assets and for convenience of explanation, it is not specifically pointed out.

The second blockchain 120 is used to run the released second smart contract and provide the "buyer's second wallet address" and "seller's second wallet address", wherein the second smart contract includes a second extraction function , Which is used to receive the unlocking cipher, and hash the unlocking cipher to compare with the buyer-side hash value or the third-party hash value in the second smart contract, and when the comparison matches, the first The two-digit asset is transferred to the buyer's second wallet address, and then the unlock secret code is stored in the second smart contract. In actual implementation, the "buyer-side second wallet address" refers to the wallet address used by the buyer-side host 140 in the second blockchain 120; the "seller-side second wallet address" refers to the seller-side host 150 The wallet address used in the second blockchain 120. Similarly, since the third-party host 130 is also connected to the first blockchain 110 and the second blockchain 120 at the same time, the second blockchain 120 will also provide a "third-party second wallet address" (ie: a third-party host 130 is the wallet address used in the second blockchain 120), and because the third-party second wallet address does not involve digital asset transfer and for convenience of explanation, it is not specifically pointed out.

The third-party host 130 is connected to the first blockchain 110 and the second blockchain 120 at the same time. The third-party host 130 is used to set a third-party hash value in the first smart contract and when it detects that the off-chain delivery is successful, Execute the second extraction function of the second smart contract and transmit the unlock password. That is to say, when calling the second extraction function, the unlock secret cipher is taken as a parameter to the second extraction function, so as to perform hash calculation and compare whether it matches the third-party hash value.

The buyer-side host 140 is simultaneously connected to the first blockchain 110 and the second blockchain 120. The buyer-side host 140 includes: a buyer-side publishing module 141 and a buyer-side detection module 142. Among them, the buyer-side publishing module 141 is used to publish the first smart contract on the first blockchain 110, and set the buyer-side hash value in the first smart contract, and transfer the first digital asset to the first smart contract escrow . The buyer-side detection module 142 is used to execute the second extraction function of the second smart contract and send an unlock secret when it detects that the off-chain delivery is successful.

The seller-side host 150 is simultaneously connected to the first blockchain 110 and the second blockchain 120. The seller-side host 150 includes: a seller-side publishing module 151 and a seller-side detection module 152. Among them, when the seller-side release module 151 is used to obtain the buyer-side hash value and the third-party hash value from the first smart contract, the second smart contract is issued on the second blockchain 120, and the second digital asset is transferred to Second smart contract escrow. Next, the seller-side detection module 152 is used to execute the first extraction function of the first smart contract when the unlock secret code is detected in the second smart contract, wherein the first extraction function will detect the unlock secret code Perform hashing to compare with the buyer-side hash value or third-party hash value in the first smart contract, and when the comparison is met, transfer the first digital asset in the custody of the first smart contract to the seller's first Wallet address.

It should be added that when both the buyer-side host 140 and the third-party host 130 detect the off-chain delivery failure, the second smart contract is exceeded the escrow time-out time, so that the second digital asset in the second smart contract escrow The seller’s second wallet address transferred to the seller’s host 150, and the first smart contract exceeding the escrow timeout, so as to transfer the first digital asset in the escrow of the first smart contract to the buyer’s first of the buyer’s host 140 Wallet address. In other words, assuming that the off-chain delivery fails, the first smart contract returns the first digital asset to the buyer host 140, and the second smart contract returns the second digital asset to the seller host 150. In actual implementation, detecting whether the off-chain delivery is successful can be achieved through the Application Programming Interface (API) or a function that directly calls the smart contract. For example, the buyer receives the purchased goods or logistics personnel to confirm the delivery Commodities can be delivered a delivery confirmation message through the API to provide the buyer host 140 to determine that the delivery was successful. Conversely, if the delivery confirmation message is not received or the return message is received after a preset time, the delivery is determined to be failed. In addition, you can also directly call the function of the smart contract to trigger a delivery confirmation event. When the buyer-side host 140 and the third-party host 130 detect that the delivery confirmation event is triggered, it is determined that the off-chain delivery is successful, otherwise, suppose If the delivery confirmation event is not detected beyond the preset time, it will be judged that the off-chain delivery fails.

In particular, in actual implementation, each module described in this creation can be implemented in various ways, including software, hardware, or any combination thereof. For example, in some embodiments, each module may Using software and hardware or one of them, in addition, this creation can also be implemented partially or completely based on hardware, for example, one or more modules in the system can be integrated circuit chip, System on Chip (SoC), Complex Programmable Logic Device (CPLD), Field Programmable Gate Array (FPGA), etc. are implemented. This creation can be a system and/or computer program. The computer program may include a computer-readable storage medium that is loaded with computer-readable program instructions for enabling the processor to implement various aspects of the present creation. The computer-readable storage medium may be a tangible form that can hold and store instructions used by the instruction execution device equipment. The computer-readable storage medium may be, but not limited to, an electrical storage device, a magnetic storage device, an optical storage device, an electromagnetic storage device, a semiconductor storage device, or any suitable combination of the foregoing. More specific examples (non-exhaustive lists) of computer-readable storage media include hard disks, random access memory, read-only memory, flash memory, optical disks, floppy disks, and any suitable combination of the foregoing. The computer-readable storage media used herein are not to be interpreted as transient signals themselves, such as radio waves or other freely propagating electromagnetic waves, electromagnetic waves propagating through waveguides or other transmission media (eg, optical signals through fiber optic cables), or through wires The transmitted electrical signal. In addition, the computer-readable program instructions described herein can be downloaded from computer-readable storage media to various computing/processing devices, or via a network, such as the Internet, local area network, wide area network, and/or wireless network To external computer equipment or external storage devices. The network may include copper transmission cables, fiber optic transmission, wireless transmission, routers, firewalls, switches, hubs, and/or gateways. The network card or network interface in each computing/processing device receives computer-readable program instructions from the network and forwards the computer-readable program instructions for computer-readable storage media stored in each computing/processing device in. The computer program instructions to perform this creation operation may be combined language instructions, instruction set architecture instructions, machine instructions, machine-related instructions, microinstructions, firmware instructions, or source code or object code written in any combination of one or more programming languages (Object Code), the programming language includes object-oriented programming languages, such as: Common Lisp, Python, C++, Objective-C, Smalltalk, Delphi, Java, Swift, C#, Perl, Ruby, PHP, etc., as well as conventional programs Procedural programming language, such as: C language or similar programming language. Computer readable program instructions can be executed entirely on the computer, partly on the computer, as a stand-alone software, partly on the client computer and partly on the remote computer, or entirely on the remote computer or server On the implementation.

Please refer to "Picture 2A" and "Picture 2B". "Picture 2A" and "Picture 2B" are flow charts of methods for creating performance-based guarantee transaction methods based on cross-chain and non-custodial entities. In the network environment of the blockchain 110 and the second blockchain 120, the steps include: providing a third-party host 130, a buyer-side host 140, and a seller-side that simultaneously connect the first blockchain 110 and the second blockchain 120 Host 150 (step 210); buyer-side host 140 issues the first smart contract on the first blockchain 110, and sets the buyer-side hash value in the first smart contract, and transfers the first digital asset to the first smart contract Escrow (step 220); the third-party host 130 sets the third-party hash value in the first smart contract (step 230); when the seller-side host 140 obtains the buyer-side hash value and the third-party hash value from the first smart contract, at The second smart contract is issued on the second blockchain 120, and the second digital asset is transferred to the second smart contract escrow (step 240); the buyer-side host 140 and the third-party host 130 detect the off-chain delivery, when the buyer When at least one of the end host 140 and the third-party host 130 detects that the off-chain delivery is successful, the second extraction function of the second smart contract is executed, where the second extraction function is from the buyer-side host 140 and the third-party host 130 At least one of them receives the corresponding unlocking cipher and hash the unlocking cipher to compare with the buyer-side hash value or the third-party hash value in the second smart contract, and when the comparison matches, escrow the second smart contract The second digital asset in is transferred to the buyer’s second wallet address of the buyer’s host 140, and then the unlock secret is stored in the second smart contract (step 250); the seller’s host 150 unlocks the second smart contract The secret code is detected, and when the seller-side host 150 detects the unlock secret code in the second smart contract, the first extraction function of the first smart contract is executed, wherein the first extraction function will detect the unlock The secret word is hashed to compare with the buyer-side hash value or third-party hash value in the first smart contract, and when the comparison is met, the first digital asset in the custody of the first smart contract is transferred to the seller-side host 150 Seller's first wallet address (step 260). Through the above steps, you can use the buyer's host 140 and the seller's host 150 to host digital assets in different blockchain smart contracts, and transfer or refund each other based on the results of the transaction entity's off-chain delivery. Digital assets, and allow third-party host 130 to conduct transaction arbitration to determine whether the off-chain delivery is successful without escrowing the transaction entity. When the off-chain delivery is successful, the buyer's host 140 can transfer each other without the consent of the buyer's host 140 The digital assets hosted by the host 140 and the seller-side host 150.

After step 260, it is assumed that both the buyer-side host 140 and the third-party host 130 detect that the off-chain delivery fails, causing the second smart contract to exceed the custody timeout time to transfer the second digital asset in the custody of the second smart contract to the seller The seller's second wallet address of the end host 150, and the first smart contract exceeding the escrow timeout to transfer the first digital asset in the custody of the first smart contract to the buyer's first wallet address of the buyer's host (step 270 ). In this way, the process of returning digital assets to the original holder can be completed.

The following description will be made in conjunction with "Picture 3" to "Picture 5" by way of example. Please refer to "Picture 3" first. "Picture 3" is a schematic diagram of the performance guarantee transaction process applying this creation. First of all, in an environment with a first blockchain 110 and a second blockchain 120, the buyer-side host 140, the third-party host 130, and the seller-side host 150 can all communicate with the first blockchain 110 and the second block The chain 120 is connected, and executes the smart contracts (such as the first smart contract and the second smart contract) and the functions contained therein. Therefore, the buyer-side host 140 has the buyer-side first wallet address on the first blockchain 110 and the buyer-side second wallet address on the second blockchain 120; the seller-side host 150 has the seller-side on the first blockchain 110 The first wallet address has the seller's second wallet address on the second blockchain 120; the third-party host 130 has the third-party first wallet address on the first blockchain 110 and the third-party first wallet address on the second blockchain 120 Second wallet address. Among them, the buyer-side host 140 can be regarded as the buyer, the seller-side host 150 can be regarded as the seller, and the third-party host 130 can be regarded as the trading platform or logistics platform. The overall performance guarantee delivery process is as follows:

1. The initiator (or buyer) can set an unlock passphrase on the buyer host 140, and the buyer host 140 performs a hash calculation to obtain a corresponding buyer hash value. Then, the buyer host 140 is in the first area The first smart contract is published on the block chain 110. This first smart contract allows setting corresponding parameters, such as: the seller's first wallet address, the third party's first wallet address, the first digital asset to be escrowed to the first smart contract, Custodian timeout, buyer-side hash value, third-party hash value and hash algorithm used, such as: Message Digest Algorithm 5 (MD5) and Secure Hash Algorithm (SHA) )and many more.

2. The buyer-side host 140 hands the first digital asset to the first smart contract for escrow, that is, transfers the first digital asset to the contract address of the first smart contract, so as to transfer the ownership of the first digital asset to be managed to the first A smart contract, where the first smart contract holds and manages the first digital asset until it is successfully paid to the seller-side host 150 or returned to the buyer-side host 140.

3. After the first smart contract is published on the first blockchain 110, the third-party host 130 also sets an unlock secret, and the third-party host 130 performs a hash calculation to obtain a corresponding third-party hash value, and then This third-party hash value is set in the first smart contract. In actual implementation, the third-party host 130 and the buyer-side host 140 each set an independent unlock password, and there is no way to know the unlock password set by the other party. In addition, the hash algorithm used by the third-party host 130 and the buyer-side host 140 may be the same or different, except that the hash algorithm used in the first smart contract needs to be recorded to avoid using the correct unlock password but A different hash algorithm results in a situation where the calculated hash value cannot match. In fact, if the same hash algorithm is used, the hash algorithm used by the first smart contract can be directly detected, and then the third party hash value can be calculated by the same hash algorithm.

4. The seller-side host 150 will continue to detect whether the first smart contract has a buyer-side hash value and a third-party hash value. If it exists, it will obtain the buyer-side hash value, third-party hash value, and used hash from the first smart contract Algorithms, custody timeouts, etc.

5. After obtaining the buyer-side hash value and the third-party hash value, the seller-side host 150 will release the second smart contract and set its parameters, such as: the buyer's second wallet address, the third-party second wallet address, and the delivery Second digital assets, custody timeout (need to be earlier than the custody timeout of the first smart contract), buyer-side hash value, third-party hash value and hash algorithm used, etc.

6. The seller-side host 150 hands the second digital asset to the second smart contract for custody, in the same manner as the buyer-side host 140 hands the first digital asset to the first smart contract for custody. Taking e-commerce (including cross-border business or e-commerce platforms) as an example, the second digital asset can be a digital product guarantee, warranty card, electronic invoice, etc.; taking the real estate performance guarantee transaction as an example, the second digital asset can be Digitalized land and house title; take warrant transactions as an example (such as: equity, debt, P2P lending, intellectual property rights, etc.), the second digital asset is a digital warrant; take the Internet of Things (Internet of Things, IoT) as an example, The second digital asset may be a digital activation right certificate, such as: activation serial number.

7. When the buyer-side host 140 or the third-party host 130 detects that the off-chain delivery is successful, it executes the second extraction function of the second smart contract and transmits the corresponding unlock password, and stores the unlock password in the second smart contract.

8. The second extraction function will hash the received unlock cipher with the hash algorithm used in the second smart contract, and the hash result with the corresponding buyer-side hash value or third-party hash value in the second smart contract. The comparison is performed, and when the comparison result matches, the second digital asset is transferred to the buyer-side second wallet address of the buyer-side host 140.

9. The seller-side host 150 obtains its stored unlock cipher from the second smart contract, so as to use the unlock cipher to request the transfer of the first digital asset to the first smart contract. For example, assuming that the unlock cipher sent by the buyer's host 140 matches the buyer's hash value of the second smart contract, the seller's host 150 obtains the unlock cipher that is disclosed in the second smart contract and corresponds to the buyer's host 140; The unlock cipher sent by the third-party host 130 matches the third-party hash value of the second smart contract, and the seller-side host 150 obtains the unlock cipher that is disclosed in the second smart contract and corresponds to the third-party host 130.

10. The seller-side host 150 executes the first extraction function of the first smart contract and transmits the unlock password obtained in the previous step. This first extraction function compares the hash value of the unlock password with the buyer's hash value or Whether the three-party hash value matches. For example, assuming that the seller-side host 150 obtains the unlocking cipher of the buyer-side host 140 in the second smart contract, the seller-side host 150 will execute the first extraction function of the first smart contract and use the unlocking cipher as a parameter band Into the first extraction function, this first extraction function will use the same hash algorithm as the buyer's hash value to hash the unlock password. If the hash result is the same as the buyer's hash value, it means that the two match.

11. When the hash value of the unlock cipher matches the buyer's hash value or third-party hash value, transfer the first digital asset to the seller's first wallet address of the seller's host 150. So far, the completion of the performance guarantee transaction based on the cross-chain and non-custodial entity is completed, that is, the completion of the delivery of the digital assets hosted by the buyer-side host 140 and the seller-side host 150 in the smart contract. Although the delivery is not simultaneous in the process, it can be guaranteed that once the delivery of the seller-side host 150 is performed, the seller-side host 150 can request the delivery of the buyer-side host 140 to also be performed.

In addition, assuming that the buyer-side host 140 determines that the off-chain delivery has failed, and wants to return the digital asset, no action is taken. After the first smart contract expires, the buyer-side host 140 retrieves the first digital asset escrowed in the first smart contract. Then, after the second smart contract expires, the seller-side host 150 retrieves the second digital asset escrowed in the second smart contract. At this point, the return of all digital assets is completed, although not at the same time, but it can be guaranteed that if the buyer-side host 140 does not withdraw the second digital asset that the seller-side host 150 intends to deliver, the seller-side host 150 cannot obtain the necessary unlock password. It is used to extract the first digital asset to be delivered by the buyer host 140. Therefore, after the custody expires, both parties can retrieve the digital assets under their custody, that is, the digital assets will be returned to the holders.

In addition, suppose that the transaction is disputed, for example, the buyer-side host 140 wants to request the return of the first digital asset in custody, and the seller-side host 150 requires the payment of the first digital asset. At this time, the third-party host 130 may intervene in the escrow transaction for arbitration. If the third-party host 130 judges that the off-chain delivery has been completed, it will arbitrate for the delivery process of all digital assets. Specifically, the third-party host 130 will execute the second extraction function of the second smart contract and send it before the custody timeout. Unlock the secret code, so that when the hashed unlock secret code matches the third-party hash value in the second smart contract, the second smart contract transfers the second digital asset in custody to the buyer's second wallet address, and the unlock secret code is made public Stored in the second smart contract. Then, when the seller-side host 150 detects the unlock secret cipher that is publicly stored in the second smart contract, it can execute the first extraction function of the first smart contract, whereby the first extraction function will detect the unlock secret cipher Hashing is performed to compare with the third-party hash value in the first smart contract, and when the comparison is met, the first digital asset in the custody of the first smart contract is transferred to the seller's first wallet address. At this point, based on the arbitration result of the third-party host 130 (ie, the off-chain delivery is completed), the delivery process of all digital assets is completed. On the other hand, if the third-party host 130 judges that the off-chain delivery fails, it will arbitrate for the return process of all digital assets, by making the first smart contract and the second smart contract both expire, such as: no operation The smart contract is caused to time out so that the buyer-side host 140 retrieves the escrowed first digital asset from the first smart contract, and the seller-side host 150 retrieves the escrowed second digital asset from the second smart contract. So far, based on the arbitration result of the third-party host 130 (that is, the off-chain delivery fails), the return process of all digital assets is completed.

Next, please refer to "Picture 4". "Picture 4" is a schematic diagram of using this book to perform performance guarantee transactions on the buyer's host. Assuming that the buyer at the buyer’s host 140 wants to pay for the purchased goods on the trading platform, he can open the checkout window 400 provided by the trading platform, and after confirming that the product picture 411, the seller’s wallet address 412, and the product price 413 are correct In the input block 414, enter a customized unlock password, and select a hash algorithm (such as MD5, SHA, etc.) in the selection element 415, and then click the payment element 416 to perform payment. At this time, the buyer-side host 140 will publish the first smart contract in the first smart contract, use the digital asset corresponding to the price 413 as the first digital asset and deposit it in the first smart contract. In actual implementation, the parameters of the first smart contract include: the buyer's wallet address on the first blockchain 110 (ie: the buyer's first wallet address), and the seller's wallet address on the first blockchain 110 (ie : The first wallet address of the seller's end), the wallet address of the trading platform on the first blockchain 110 (ie: the third-party first wallet address), and the first digital asset to be delivered by escrow (for example: an Ethereum "1 ETH" ), escrow timeout, buyer-side hash value, third-party hash value, hash algorithm used, etc. Among them, the buyer-side hash value is generated by hashing the input unlock password with the selected hash algorithm; the hash algorithm used is set according to the hash algorithm selected by the selection component 415; the third-party hash value is left to the third party The host 130 makes settings. As for the custody timeout time, you can use the preset value or any specified way to set.

Next, as shown in "Picture 5", "Picture 5" is a schematic diagram of applying this creation to a third-party host to set an unlock password. After the first smart contract is released, the third-party host 130 as a trading platform can generate a setting window 500 to prompt the user to enter the unlock password for the corresponding transaction in the input block 510, and after completing the input, click the confirm element 520, in order to hash the unlock cipher according to the hash algorithm used in the first smart contract, and then obtain a third-party hash value and set it in the first smart contract. In actual implementation, in addition to the method of generating the setting window 500 prompting for the input of the unlock password, the setting window 500 may not be generated when the transaction is generated, but the corresponding corresponding transaction of the transaction may be automatically generated directly by random random numbers. Unlock the cipher, and then use the hash algorithm recorded in the first smart contract to hash to generate a third-party hash value, and set the generated third-party hash value as a parameter in the first smart contract. It should be noted that no matter how the unlock secret code is generated, the third-party host 130 needs to record each transaction and its corresponding unlock secret code, so that the third-party host 130 can provide the unlock secret code to the transaction when the third-party host 130 determines that the transaction is successfully delivered outside the chain. The second smart contract is used to publicly unlock the secret word, and at the same time transfer the second digital asset to the buyer's second wallet address.

In summary, the difference between this creation and the previous technology is that the buyer-side host and the seller-side host respectively host digital assets in smart contracts in different blockchains, and transfer each other according to the results of the transaction entity's delivery outside the chain. Or refund each other’s digital assets hosted in smart contracts, and allow third-party hosts to conduct transaction arbitration to determine whether the off-chain delivery is successful without hosting the transaction entity. When the off-chain delivery is successful, the buyer’s host is not required to agree. That is, the digital assets hosted by the buyer's host and the seller's host can be transferred to each other, and by this technical means, the problems of the previous technology can be solved, and then the technical effect of improving the reliability of the performance guarantee can be achieved.

Although this creation is disclosed as above with the foregoing embodiments, it is not intended to limit this creation. Anyone who is familiar with similar arts and crafts can make some changes and retouching without departing from the spirit and scope of this creation. The scope of patent protection shall be determined by the scope of the patent application attached to this specification.

110: the first blockchain 120: Second blockchain 130: Third-party host 140: Buyer's host 141: Buyer release module 142: Buyer-side detection module 150: seller host 151: The seller releases the module 152: Seller-side detection module 400: checkout window 411: Product picture 412: Seller's wallet address 413: price 414: Input block 415: Select component 416: Payment element 500: setting window 510: input block 520: Identify components Step 210: Provide a buyer-side host, a seller-side host, and a third-party host that simultaneously connect the first blockchain and the second blockchain Step 220: The buyer host issues a first smart contract on the first blockchain, and sets a buyer hash value in the first smart contract, and transfers a first digital asset to the first smart Contract custody Step 230: The third-party host sets a third-party hash value in the first smart contract Step 240: When the seller-side host obtains the buyer-side hash value and the third-party hash value from the first smart contract, a second smart contract is issued on a second blockchain, and a second digital Asset transfer to the second smart contract escrow Step 250: The buyer-side host and the third-party host detect off-chain delivery. When at least one of the buyer-side host and the third-party host detects that the off-chain delivery is successful, the second smart contract is executed. A second extraction function, wherein the second extraction function receives a corresponding unlock password from at least one of the buyer-side host and the third-party host, and hashs the unlock password to the second smart contract Compare the buyer’s hash value or the third party’s hash value, and when the comparison matches, transfer the second digital asset in the custody of the second smart contract to a buyer’s second wallet address of the buyer’s host , And then store the unlock code in the second smart contract Step 260: The seller-side host detects the unlocking cipher in the second smart contract, and when the seller-side host detects the unlocking cipher in the second smart contract, execute the first smart contract A first extraction function of the first extraction function, wherein the first extraction function hashes the detected unlock cipher for use with the buyer-side hash value or the third-party hash value in the first smart contract Compare, and when the match is met, transfer the first digital asset in the custody of the first smart contract to a seller's first wallet address of the seller's host Step 270: When both the buyer-side host and the third-party host detect out-of-chain delivery failure, make the second smart contract exceed a escrow time-out time to escrow the second digital asset in the second smart contract Transfer to a seller-side second wallet address of the seller-side host, and make the first smart contract exceed the escrow timeout to transfer the first digital asset in the escrow of the first smart contract to the buyer-side host's A buyer's first wallet address

Figure 1 is a system block diagram of creating a performance guarantee transaction system based on cross-chain and non-custodial entities. Figures 2A and 2B are flowcharts of methods for creating a performance guarantee transaction method based on cross-chain and non-custodial entities. Figure 3 is a schematic diagram of the performance guarantee transaction process using this creation. Figure 4 is a schematic diagram of using this book to perform performance guarantee transactions on the buyer's host. Figure 5 is a schematic diagram of applying this creation to a third-party host to set an unlock password.

110: the first blockchain

120: Second blockchain

130: Third-party host

140: Buyer's host

141: Buyer release module

142: Buyer-side detection module

150: seller host

151: The seller releases the module

152: Seller-side detection module

Claims (5)

A performance guarantee transaction system based on cross-chain and non-custodial entities, the system includes: A first blockchain for running a first smart contract issued, and providing a buyer's first wallet address and a seller's first wallet address; A second blockchain for running a second smart contract issued, and providing a buyer-side second wallet address and a seller-side second wallet address, where the second smart contract includes a second extraction function , Used to receive an unlocking cipher, and hash the unlocking cipher to compare with a buyer-side hash value or a third-party hash value in the second smart contract, and when the comparison matches, the second smart contract Transfer a second digital asset in custody to the buyer’s second wallet address, and then store the unlocked secret in the second smart contract; A third-party host is connected to the first blockchain and the second blockchain at the same time. The third-party host is used to set a third-party hash value in the first smart contract and detect successful delivery outside the chain When, execute the second extraction function of the second smart contract and transmit the unlock password; A buyer-side host, which connects the first blockchain and the second blockchain at the same time, the buyer-side host includes: A buyer-side publishing module is used to publish the first smart contract on the first blockchain, and set a buyer-side hash value in the first smart contract, and transfer a first digital asset to the first A smart contract escrow; and A buyer-side detection module, which is used to execute the second extraction function of the second smart contract and transmit the unlock secret code when it detects that the off-chain delivery is successful; and A seller-side host, which connects the first blockchain and the second blockchain at the same time, the seller-side host includes: A seller-side release module is used to obtain the buyer-side hash value and the third-party hash value from the first smart contract, and then publish the second smart contract on the second blockchain and transfer a second Digital assets are transferred to the second smart contract escrow; and A seller-side detection module is used to execute a first extraction function of the first smart contract when the unlocking cipher is detected in the second smart contract, wherein the first extraction function will detect Measure the unlocked ciphers for hashing to compare with the buyer-side hash value or the third-party hash value in the first smart contract, and when the comparison meets, escrow the first smart contract The first digital asset is transferred to the first wallet address of the seller. According to the performance guarantee transaction system based on cross-chain and non-custodial entities in item 1 of the patent application scope, where both the buyer-side host and the third-party host detect out-of-chain delivery failure, the second smart contract exceeds one escrow Time-out time to transfer the second digital asset in the custody of the second smart contract to the seller-side second wallet address of the seller-side host, and to make the first smart contract exceed the custody time-out time to transfer the The first digital asset in the custody of a smart contract is transferred to the buyer's first wallet address of the buyer's host. According to the performance guarantee transaction system based on cross-chain and non-custodial entities in item 1 of the patent scope, where the buyer-side host and the third-party host receive a delivery confirmation message through an application interface, it is determined that the off-chain delivery is successful When the delivery confirmation message is not received or a return message is received after a preset time, it is determined that the off-chain delivery has failed. According to the performance guarantee transaction system based on cross-chain and non-custodial entities in item 1 of the patent application scope, the buyer-side host and the third-party host continuously detect a delivery confirmation event of the second smart contract when the delivery confirmation event If it is triggered, it is determined that the off-chain delivery is successful. When the delivery confirmation event is not detected beyond a preset time, it is determined that the off-chain delivery has failed. According to the performance guarantee transaction system based on cross-chain and non-custodial entities in item 1 of the patent application scope, wherein the third-party hash value and the buyer-side hash value are generated by hash calculation of the unlocking cipher using a hash algorithm, the The hash algorithm is at least one of the Message Digest Algorithm 5 (MD5) and the Secure Hash Algorithm (SHA).

Images