CN111640017B - Transaction correctness verification method and device applied to alliance chain cross-chain transfer - Google Patents
Transaction correctness verification method and device applied to alliance chain cross-chain transfer Download PDFInfo
- Publication number
- CN111640017B CN111640017B CN202010374241.8A CN202010374241A CN111640017B CN 111640017 B CN111640017 B CN 111640017B CN 202010374241 A CN202010374241 A CN 202010374241A CN 111640017 B CN111640017 B CN 111640017B
- Authority
- CN
- China
- Prior art keywords
- transaction
- cross
- link
- asset
- 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.)
- Active
Links
- 238000000034 method Methods 0.000 title claims abstract description 54
- 238000012546 transfer Methods 0.000 title claims abstract description 35
- 238000012795 verification Methods 0.000 title claims abstract description 32
- 238000012545 processing Methods 0.000 claims description 12
- 230000005540 biological transmission Effects 0.000 claims description 11
- 230000004044 response Effects 0.000 claims description 7
- 238000003860 storage Methods 0.000 claims description 6
- 238000005516 engineering process Methods 0.000 abstract description 8
- 230000006870 function Effects 0.000 description 9
- 238000004590 computer program Methods 0.000 description 6
- 238000010586 diagram Methods 0.000 description 6
- 239000003999 initiator Substances 0.000 description 3
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000008569 process Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 230000006399 behavior Effects 0.000 description 1
- 238000004891 communication Methods 0.000 description 1
- 238000010276 construction Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000003993 interaction Effects 0.000 description 1
- 230000002427 irreversible effect Effects 0.000 description 1
- 238000012423 maintenance Methods 0.000 description 1
- 238000004519 manufacturing process Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 238000005096 rolling process Methods 0.000 description 1
- 230000001131 transforming effect Effects 0.000 description 1
- 101150116173 ver-1 gene Proteins 0.000 description 1
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2228—Indexing structures
- G06F16/2255—Hash tables
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2308—Concurrency control
- G06F16/2315—Optimistic concurrency control
- G06F16/2322—Optimistic concurrency control using timestamps
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
-
- 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/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Physics & Mathematics (AREA)
- Accounting & Taxation (AREA)
- Databases & Information Systems (AREA)
- Finance (AREA)
- General Engineering & Computer Science (AREA)
- Data Mining & Analysis (AREA)
- General Business, Economics & Management (AREA)
- Strategic Management (AREA)
- Technology Law (AREA)
- Computer Security & Cryptography (AREA)
- Marketing (AREA)
- Economics (AREA)
- Development Economics (AREA)
- Software Systems (AREA)
- Computing Systems (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The invention discloses a transaction correctness verification method and device applied to alliance chain cross-chain transfer, wherein the method comprises the following steps: the first cross-link route sends a first locking asset request to the second cross-link route; the first cross-link route obtains a first transaction receipt sent by the second cross-link route; the first cross-link is used for generating first transaction snapshot information corresponding to the first transaction receipt according to a preset format; the first cross-link router generates second transaction snapshot information according to the preset format based on the fourth transaction asset, the contract number and the second contract address; and if the first cross-link slave determines that the first transaction snapshot information is consistent with the second transaction snapshot information, determining that the second cross-link slave locks the fourth transaction asset. When the method is applied to the financial science and technology (Fintech), the transaction correctness of the alliance chain can be supported.
Description
Technical Field
The invention relates to the field of computer software in the field of financial science and technology (Fintech), in particular to a transaction correctness verification method and device applied to alliance chain cross-chain transfer.
Background
With the development of computer technology, more and more technologies are applied in the financial field, and the traditional financial industry is gradually changed to the financial technology (Fintech), but due to the requirements of safety and real-time performance of the financial industry, the requirements of the technology are also higher. The security requirements for financial transactions in the field of financial science and technology are extremely high, so financial transactions are often implemented through a blockchain (blockchain).
Currently, public chain cross-chain transfer of blockchains is generally realized based on classical hash time locking contracts, and the classical hash time locking approximately needs to publicly verify the locking condition of transaction assets, namely the correctness verification of transactions. However, the contract and transaction information of the coalition chain is not fully disclosed, so the classical hash time-locking contract model cannot be directly used for coalition chain cross-chain transfer. Therefore, the federation chain cannot verify the correctness of the transaction, which is a problem to be solved urgently.
Disclosure of Invention
The invention provides a transaction correctness verification method and device applied to alliance chain cross-chain transfer, which solve the problem that the prior art cannot verify the correctness of a transaction at present.
In a first aspect, the present invention provides a transaction correctness verification method applied to alliance chain cross-chain transfer, comprising: the first cross-link route sends a first locking asset request to the second cross-link route; the first locking asset request is to indicate a fourth transaction asset to lock a second account of a second user on a second blockchain based on a transaction request of the first account of the first user on the first blockchain; the first cross-link route obtains a first transaction receipt sent by the second cross-link route; the first transaction receipt being descriptive of the second cross-link by declared locked fourth transaction asset; the first transaction receipt is generated based on a fourth declarative asset, a second execution contract number, and a second execution contract address of the fourth transaction asset; the first cross-link is used for generating first transaction snapshot information corresponding to the first transaction receipt according to a preset format; the first cross-link router generates second transaction snapshot information according to the preset format based on the fourth transaction asset, the contract number and the second contract address; the contract number of the contract is the contract number corresponding to the contract data contracted by the first user and the second user; the second contracted contract address is a contract address where the first user and the second user store the contract data in the second blockchain; and if the first cross-link slave determines that the first transaction snapshot information is consistent with the second transaction snapshot information, determining that the second cross-link slave locks the fourth transaction asset.
In the method, since the first locked asset request is used for indicating the fourth transaction asset of the second account of the second user on the second blockchain based on the transaction request of the first account of the first user on the first blockchain, after the first cross-link is obtained from the first transaction receipt sent by the second cross-link, the first transaction snapshot information corresponding to the first transaction receipt can be generated according to the preset format, and the second transaction snapshot information is generated according to the preset format based on the fourth transaction asset, the contract number and the second contract address, so that when the actually received first transaction snapshot is consistent with the expected second transaction snapshot information, the second cross-link is determined to lock the fourth transaction asset, and the method suitable for the transaction verification correctness of the alliance chain is provided.
Optionally, after the determining that the second cross-link is locked by the fourth transaction asset, the method further comprises: the first cross-link is made of a first transaction asset that locks a first account of the first user; generating a second transaction receipt by the first cross-link based on a first declarative asset of the first transaction asset, a first execution contract number, and a first execution contract address of the first user; the second transaction receipt for the first cross-link by declaring that the first transaction asset has been locked; the first cross-link router sends the second transaction receipt, a first unlock asset request and a hash primitive to the second cross-link router; the hash original image is an original image of the contracted contract number, and the hash original image is used for unlocking the fourth transaction asset after the second cross-link receipt passes through verification of the second transaction receipt.
In the above method, the first cross-link generates a second transaction receipt from a first declarative asset based on the first transaction asset, a first execution contract number, and a first execution contract address of the first user; the second transaction receipt for the first cross-link by declaring that the first transaction asset has been locked; the first cross-link route sends the second transaction receipt, a first unlock asset request and a hash primitive to the second cross-link route for the second cross-link route verification, and unlocks the fourth transaction asset, thereby providing a way of passing the second cross-link route verification.
Optionally, after the first cross-link route sends the second transaction receipt, the first unlock asset request, and the hash primitive to the second cross-link route, the method further includes: the first cross-link slave receives a second lock asset request sent by the second cross-link slave; the first cross-link route locks a second transaction asset of a second account of the first user on the first blockchain; generating a third transaction receipt by the first cross-link from a second declarative asset based on the second transaction asset, a third execution contract number, and a third execution contract address; the third transaction receipt for the first cross-link by declaring that the second transaction asset has been locked; the first cross-link route sends the third transaction receipt to the second cross-link route for use by the second cross-link route in verifying whether the first cross-link route locks the second transaction asset.
In the method, after the first cross-link slave receives the second lock asset request sent by the second cross-link slave, the second transaction asset of the second account of the first user on the first blockchain is locked, a third transaction receipt is generated, and the third transaction receipt is sent to the second cross-link slave, so that a mode of verifying whether the first cross-link slave locks the second transaction asset through the second cross-link slave is provided.
Optionally, after the first cross-link router sends the third transaction receipt to the second cross-link router, further comprising: the first cross-link slave receives a fourth transaction receipt, a second unlock asset request and the hash original image sent by the second cross-link slave; the fourth transaction receipt is descriptive information that the second cross-link has been locked by a third transaction asset declared to be the first account of the second user on the second blockchain; the fourth transaction receipt is generated based on a third declarative asset, a fourth execution contract number, and a fourth execution contract address of the third transaction asset; the first cross-link router generates seventh transaction snapshot information according to the fourth transaction receipt and the preset format; the first cross-link is used for generating eighth transaction snapshot information according to the preset format based on the third transaction asset, the appointed contract number and the second appointed contract address; and if the first cross-link router verifies that the seventh transaction snapshot information and the eighth transaction snapshot information are consistent, unlocking the second transaction asset according to the hash original image.
In the above manner, after receiving the fourth transaction receipt, the second unlock asset request and the Ha Xiyuan image sent by the second cross-link unit, the first cross-link unit generates seventh transaction snapshot information according to the preset format and the fourth transaction receipt; the first cross-link is used for generating eighth transaction snapshot information according to the preset format based on the third transaction asset, the appointed contract number and the second appointed contract address; a method of verifying that the second cross-link route locks the third transaction asset is thereby provided.
Optionally, the contract data includes a first timestamp; the first timestamp is to trigger the first blockchain to rollback the first transaction asset to a first account of the first user when the first timestamp arrives but the first transaction asset is not unlocked.
In the mode, the first transaction asset is rolled back to the first account of the first user in time through the first timestamp, so that the security of transaction verification is ensured.
Optionally, the contract data includes Ha Xiyuan images, contracted contract numbers and transaction attributes; the first user stores first contract data in the first blockchain, wherein the first contract data records the Ha Xiyuan images, the appointed contract numbers and the transaction attributes; the second user stores second contract data in the second blockchain, wherein the contracted contract number and the transaction attribute are recorded in the second contract data.
In the above manner, the first contract data and the second contract data are stored in the blockchain in advance, so that the first user and the second user can know the transaction attribute in advance.
Optionally, the transaction snapshot information includes the following: function name of transaction execution; input parameters for the transaction; outputting a transaction result; contract addresses for executing transactions.
In the above manner, the transaction snapshot information can record the outline of the transaction through the content, so that the transaction is verified to be correct or not with a smaller data volume.
In a second aspect, the present invention provides a transaction correctness verification apparatus for use in coalition chain cross-chain transfer, comprising: a transmission module for transmitting a first locked asset request to a second cross-link router; the first locking asset request is to indicate a fourth transaction asset to lock a second account of a second user on a second blockchain based on a transaction request of the first account of the first user on the first blockchain; and a first transaction receipt for obtaining the second cross-link response piece sent by the first cross-link; the first transaction receipt being descriptive of the second cross-link by declared locked fourth transaction asset; the first transaction receipt is generated based on a fourth declarative asset, a second execution contract number, and a second execution contract address of the fourth transaction asset; the processing module is used for generating first transaction snapshot information corresponding to the first transaction receipt according to a preset format; and generating second transaction snapshot information according to the preset format based on the fourth transaction asset, the contract number and the second contract address; the contract number of the contract is the contract number corresponding to the contract data contracted by the first user and the second user; the second contracted contract address is a contract address where the first user and the second user store the contract data in the second blockchain; and the determining module is used for determining that the first transaction snapshot information is consistent with the second transaction snapshot information, and determining that the fourth transaction asset is locked by the second cross-link.
Optionally, the processing module is further configured to: locking a first transaction asset of a first account of the first user; generating a second transaction receipt based on the first declarative asset of the first transaction asset, a first execution contract number, and a first execution contract address of the first user; the second transaction receipt for the first cross-link by declaring that the first transaction asset has been locked; the transmission module is further configured to: sending the second transaction receipt, a first unlock asset request, and a hash primitive to the second cross-link; the hash original image is an original image of the contracted contract number, and the hash original image is used for unlocking the fourth transaction asset after the second cross-link receipt passes through verification of the second transaction receipt.
Optionally, the transmission module is further configured to: receiving a second lock asset request sent by the second cross-link; the processing module is further configured to: locking a second transaction asset of a second account of the first user on the first blockchain; generating a third transaction receipt based on the second declarative asset, a third execution contract number, and a third execution contract address of the second transaction asset; the third transaction receipt for the first cross-link by declaring that the second transaction asset has been locked; the transmission module is further configured to: the third transaction receipt is sent to the second cross-link route for use by the second cross-link route in verifying whether the first cross-link route locks the second transaction asset.
Optionally, the transmission module is further configured to: receiving the second cross-link transmitted fourth transaction receipt, a second unlock asset request and the hash original image; the fourth transaction receipt is descriptive information that the second cross-link has been locked by a third transaction asset declared to be the first account of the second user on the second blockchain; the fourth transaction receipt is generated based on a third declarative asset, a fourth execution contract number, and a fourth execution contract address of the third transaction asset; the processing module is further configured to: generating seventh transaction snapshot information according to the fourth transaction receipt and the preset format; generating eighth transaction snapshot information according to the preset format based on the contract number and the second contract address; and if the seventh transaction snapshot information and the eighth transaction snapshot information are verified to be consistent, unlocking the second transaction asset according to the hash original image.
Optionally, the contract data includes a first timestamp; the first timestamp is to trigger the first blockchain to rollback the first transaction asset to a first account of the first user when the first timestamp arrives but the first transaction asset is not unlocked.
Optionally, the contract data includes Ha Xiyuan images, contracted contract numbers and transaction attributes; the first user stores first contract data in the first blockchain, wherein the first contract data records the Ha Xiyuan images, the appointed contract numbers and the transaction attributes; the second user stores second contract data in the second blockchain, wherein the contracted contract number and the transaction attribute are recorded in the second contract data.
Optionally, the transaction snapshot information includes the following: function name of transaction execution; input parameters for the transaction; outputting a transaction result; contract addresses for executing transactions.
The advantages of the foregoing second aspect and the advantages of the foregoing optional apparatuses of the second aspect may refer to the advantages of the foregoing first aspect and the advantages of the foregoing optional methods of the first aspect, and will not be described herein.
In a third aspect, the present invention provides a computer device comprising a program or instructions which, when executed, is operable to perform the above-described first aspect and the respective alternative methods of the first aspect.
In a fourth aspect, the present invention provides a storage medium comprising a program or instructions which, when executed, is adapted to carry out the above-described first aspect and the respective alternative methods of the first aspect.
Drawings
FIG. 1 is a schematic block chain architecture;
FIG. 2 is a schematic flow chart of steps of a transaction correctness verification method applied to alliance chain cross-chain transfer according to an embodiment of the present application;
Fig. 3 is a schematic structural diagram of a transaction correctness verification device applied to alliance chain cross-chain transfer according to an embodiment of the present application.
Detailed Description
In order to better understand the above technical solutions, the following detailed description will be made with reference to the accompanying drawings and specific embodiments of the present application, and it should be understood that specific features in the embodiments and examples of the present application are detailed descriptions of the technical solutions of the present application, and not limiting the technical solutions of the present application, and the technical features in the embodiments and examples of the present application may be combined with each other without conflict.
The terms appearing in the embodiments of the present application are explained first below.
Blockchain: as shown in fig. 1, a blockchain is a chain of blocks, each block being recorded with a Hash value of the previous block in addition to the data of the block, in such a way that the chain is formed. The block chain has two core concepts, one is a cryptography technology, the other is a decentralization concept, and the history information on the block chain cannot be tampered based on the two concepts.
Intelligent contract: an intelligent contract is a computer protocol that aims to propagate, verify, or execute contracts in an informative manner. Smart contracts allow trusted transactions to be made without third parties, which transactions are traceable and irreversible. The smart contracts are in the form of code deployed on a blockchain to perform a specific function.
And (3) node: each participant in the network is a node that participates in network construction and data exchange. In a blockchain network, a node refers to a participant with a unique identity, the node having a complete ledger copy with the ability to participate in blockchain network consensus and ledger maintenance.
Transaction: a transaction is a request by a user for an operation of an intelligent contract interface deployed on a blockchain. The transaction is initiated by a user, the transaction is sent to a blockchain node from a client of the user, and after the blockchain node receives the transaction, the corresponding intelligent contract is called according to a contract address and an interface appointed by the transaction.
And (3) straddling a chain: there are currently various types of blockchains. In some traffic scenarios, data interworking is required between different types of blockchains. Such traffic scenarios are referred to as cross-link scenarios. For users, the user needs to operate on different types of blockchains at the same time, and send transactions to different types of blockchains.
Transaction presence verification: under the cross-chain scene, different chains need to mutually judge whether the transaction of the opposite side is uplink or not. For example, two blockchains are respectively built by the two parties A and B, the transaction t is sent to the chain of A, and after the transaction t is executed and uplink in the chain of A, B needs to verify that the transaction t is uplink in the chain of A, and then another transaction can be sent to the chain of B for corresponding operation. B verifies the behavior of the transaction which is already up-chain on the chain of A, and becomes transaction existence verification.
Hash time lock contract:
A technique for guaranteeing the atomicity of a multi-chain asset exchange, essentially an intelligent contract. The hash time lock approximately comprises three interfaces lock, unlock, rollback for respectively locking, unlocking and rolling back after overtime of the asset. Wherein lock needs to make an asset unlocking condition, generally a hash, and unlock is transmitted into a hash original image, and if the unlock matches with the hash of lock, the asset can be successfully unlocked.
The cross-link is defined by:
the service component independent of the blockchain can adapt to the blockchain, has the functions of account management, transaction signature, transaction verification and the like, can synchronize block header information and transaction information among cross-link routers, and can mutually call contracts on the opposite chain, and is commonly called as 'cross-chain relay', 'Peer'.
In the running process of a financial institution (banking institution, insurance institution or securities institution) in doing business (such as loan business, deposit business of bank, etc.), the public chain cross-chain transfer of blockchain is generally realized based on classical hash time locking contract, and the locking condition of transaction property, namely the correctness verification of transaction, needs to be publicly verified by the classical hash time locking. However, the contract and transaction information of the coalition chain is not fully disclosed, so the classical hash time-locking contract model cannot be directly used for coalition chain cross-chain transfer. This situation does not meet the requirements of financial institutions such as banks, and cannot guarantee efficient operation of various businesses of the financial institutions.
To this end, as shown in fig. 2, the present application provides a transaction correctness verification method applied to alliance chain cross-chain transfer.
Step 201: the first cross-link route sends a first lock asset request to the second cross-link route.
Step 202: the first cross-link response piece is sent by the second cross-link response piece.
Step 203: and generating first transaction snapshot information corresponding to the first transaction receipt by the first cross-link according to a preset format.
Step 204: and the first cross-link router generates second transaction snapshot information according to the preset format based on the fourth transaction asset, the appointed contract number and the second appointed contract address.
Step 205: and if the first cross-link slave determines that the first transaction snapshot information is consistent with the second transaction snapshot information, determining that the second cross-link slave locks the fourth transaction asset.
In steps 201 to 205, the first cross-link route is a cross-link route of a first blockchain, the second cross-link route is a cross-link route of a second blockchain, and the first locking asset request is used for indicating to lock a fourth transaction asset of a second account of a second user on the second blockchain based on a transaction request of a first account of the first user on the first blockchain; the first transaction receipt being descriptive of the second cross-link by declared locked fourth transaction asset; the first transaction receipt is generated based on a fourth declarative asset, a second execution contract number, and a second execution contract address of the fourth transaction asset; the contract number of the contract is the contract number corresponding to the contract data contracted by the first user and the second user; the second contracted contract address is a contract address where the first user and the second user store the contract data in the second blockchain. In the present application, the expression XXX is expressed by sound, and is not necessarily true XXX, but true XXX can be confirmed after verification. The application can lock the transaction asset through contract numbers, and can unlock the transaction asset through Ha Xiyuan images.
It should be noted that, the first user has a first account of the first user on the first blockchain, the second user has a first account of the second user on the first blockchain, the first user has a second account of the first user on the second blockchain, and the second user has a second account of the second user on the second blockchain. The first blockchain also has a first intermediate account thereon for hosting a transaction asset locked on the first blockchain, and the second blockchain also has a second intermediate account thereon for hosting a transaction asset locked on the second blockchain.
In an alternative embodiment, the contract data includes a first timestamp therein; the first timestamp is to trigger the first blockchain to rollback the first transaction asset to a first account of the first user when the first timestamp arrives but the first transaction asset is not unlocked. Correspondingly, the contract data also comprises a second timestamp; the second timestamp is to trigger the second blockchain to rollback the fourth transaction asset to the first account of the first user when the second timestamp arrives but the fourth transaction asset is not unlocked.
In an alternative embodiment, the contract data includes Ha Xiyuan images, a contract number, and transaction attributes; the first user stores first contract data in the first blockchain, wherein the first contract data records the Ha Xiyuan images, the appointed contract numbers and the transaction attributes; the second user stores second contract data in the second blockchain, wherein the contracted contract number and the transaction attribute are recorded in the second contract data.
After step 205, further verification of transaction correctness may be performed, specifically:
Step 206: the first cross-link is comprised of a first transaction asset that locks a first account of the first user.
Step 207: the first cross-link generates a second transaction receipt from a first declarative asset based on the first transaction asset, a first execution contract number, and a first execution contract address of the first user.
Step 208: the second transaction receipt is for the first cross-link by declaring that the first transaction asset has been locked.
Step 209: the first cross-link route sends the second transaction receipt, a first unlock asset request, and a hash primitive to the second cross-link route.
The hash original image is an original image of the contracted contract number, and the hash original image is used for unlocking the fourth transaction asset after the second cross-link receipt passes through verification of the second transaction receipt.
It should be noted that, after step 209, the second cross-link route also has a hash original image, so that the second cross-link route may be executed again according to steps 201 to 209, and details may refer to the first cross-link route, which will not be described herein. The corresponding first cross-link is shown by steps 210-216. After step 209, after the second cross-link receipt of the second transaction receipt, the first unlock asset request, and Ha Xiyuan images, the following steps may be further performed:
The second cross-link server generates third transaction snapshot information according to the second transaction receipt and the preset format; the second cross-link is used for generating fourth transaction snapshot information according to the preset format based on the first transaction asset, the appointed contract number and the second appointed contract address; and if the second cross-link route verifies that the third transaction snapshot information and the fourth transaction snapshot information are consistent, unlocking the fourth transaction asset according to the hash original image.
After step 209, the first cross-link router may further perform the following steps:
Step 210: the first cross-link is requested by receiving a second locked asset sent by the second cross-link.
Step 211: the first cross-link route locks a second transaction asset of a second account of the first user on the first blockchain.
Step 212: the first cross-link generates a third transaction receipt from a second declarative asset based on the second transaction asset, a third execution contract number, and a third execution contract address.
The third transaction receipt is for the first cross-link by declaring that the second transaction asset has been locked.
Step 213: the first cross-link route sends the third transaction receipt to the second cross-link route for use by the second cross-link route in verifying whether the first cross-link route locks the second transaction asset.
After step 213, after the second cross-link receipt of the third transaction receipt, the following steps may be further performed:
Generating fifth transaction snapshot information according to the third transaction receipt and the preset format by the second cross-link; the second cross-link is used for generating sixth transaction snapshot information according to the preset format based on the second transaction asset, the appointed contract number and the third appointed contract address; and if the first cross-link router verifies that the fifth transaction snapshot information and the sixth transaction snapshot information are consistent, unlocking the third transaction asset according to the hash original image.
After step 213, the first cross-link router may further perform the following steps:
Step 214: the first cross-link slave receives the fourth transaction receipt, the second unlock asset request, and the hash primitive sent by the second cross-link slave.
Step 215: the first cross-link router generates seventh transaction snapshot information according to the fourth transaction receipt and the preset format; and generating eighth transaction snapshot information according to the preset format by the first cross-link based on the third transaction asset, the appointed contract number and the second appointed contract address.
Step 216: and if the first cross-link router verifies that the seventh transaction snapshot information and the eighth transaction snapshot information are consistent, unlocking the second transaction asset according to the hash original image.
The fourth transaction receipt is descriptive information that the second cross-link has been locked by a third transaction asset declared to be the first account of the second user on the second blockchain; the fourth transaction receipt is generated based on a third declarative asset, a fourth execution contract number, and a fourth execution contract address of the third transaction asset.
It should be noted that, in an alternative embodiment, the transaction snapshot information (the first transaction snapshot information to the eighth transaction snapshot information) appearing in the present application may include the following: function name of transaction execution; input parameters for the transaction; outputting a transaction result; contract addresses for executing transactions.
The transaction correctness checking method of the present application is described in detail below in connection with a specific implementation procedure.
The main part that involves: two users (first user_1, second user_2), two blockchains (first blockchain chain_a, second blockchain_b), two cross-link routes (first cross-link connected by router_a to chain_a, second cross-link connected by router_b to chain_b), two hash time lock contracts (hash time lock about address of blockchain chain_a is address_a, hash time lock about address of blockchain chain_b is address_b). Wherein user1 has an account accoun_a1 in the blockchain chain_a, an account accoun_b1 in the blockchain_b, and user2 has an account accoun_a2 in the blockchain chain_a, and an account accoun_b2 in the blockchain chain_b.
Blockchain cross chain transfer: i.e., to effect atomic exchange of assets on both chains. When accoun_a1 on blockchain chain_a transfers the first transaction asset to accoun_a2, accoun_b2 on blockchain_b is guaranteed to also transfer the fourth transaction asset to accoun_b1. Such asset transfer is either successful or fails.
Assume that user1 is the initiator, i.e., master Secret, user2 is the participant, and they are opponents to each other.
Transforming the hash time lock contract: a. adding a contract state variable of the opponent, wherein the variable supports a set and get method, the set stores contract addresses of the opponent in a k-v mode, the contract number k is a character string constant 'counterpartyAddress', v is the contract address of the opponent, such as '0 x 1', and the get returns the contract address of the opponent according to k; b. newly added transfer contract state variables (contract data), the contract fields include: hash, secret, sender0, receiver0, amount0, timelock0, sender0, receiver0, amount0, timelock0, wherein the Secret is held by the transfer initiator only, i.e. the Secret is initially present in the first contract data but not in the second contract data, the variables support the set and get method, set stores the contract information in k-v, k is the contract number, i.e. Hash, v is the contract structure, and get returns the contract structure according to Hash.
The contract field is explained as follows:
The user user_1 deploys a hash time lock contract on the blockchain chain_a to obtain a first contract address_a, the user user_2 deploys a hash time lock contract on the blockchain chain_b to obtain a second contract address address_b, and then the two users can tell the own contract address to each other based on any communication mode.
Initializing a hash time lock contract: by the set method of the contract state variables of the counter-parties in the contract, the contract addresses of the counter-parties are saved in a k-v data structure, for example:
user _1 performs set (counterpartyAddress, address _ b),
User_2 performs set (counterpartyAddress, address_a).
Both sides transfer the set method of the contract state variable through the contract, take the contract number Hash as k, the contract structure body as v, and save the contract data through the k-v data structure, for example:
User_1 performs:
set(Hash,[Hash,Secret,Sender0,Receiver0,Amount0,Timelock0,Sender1,Recei ver1,Amount1,Timelock1]),
user_2 performs:
set(Hash,[Hash,null,Sender0,Receiver0,Amount0,Timelock0,Sender1,Receiver1,Amount1,Timelock1])。
The user_1 initiates a cross-link transfer request from the router_a, the field of the request is contract number Hash, the user_2 initiates a cross-link transfer request from the router_b, and the field of the request is contract number Hash (how the user and the cross-link transfer interact is not in the discussion of the patent).
The cross-links of both parties are queried by the get method get (Hash) according to Hash, which is to perform transfer of contract state variables, if router_a can obtain Secret from the contract data, if router_b, it will be found that Secret in the contract data is empty, and query will be continued until the result is obtained (when his asset is unlocked by the initiator).
Router_a requests router_b to perform a lock_b (Hash) transaction of a Hash time lock contract on blockchain chain_b (how inter-link-route interactions do not belong to this patent discussion).
The router_b performs a lock_b (Hash) transaction to lock the fourth transaction asset on the chain_b, i.e., account_b2 transfers the fourth transaction asset to the intermediate account account_b, and then the router_b returns the return of the lock transaction acknowledgement lock_b_ receipt to the router_a.
Router_a does not trust router_b and therefore verifies the correctness of the transaction as follows: a. constructing an actual transaction snapshot real_lock_b_snapshot: { Method, inputes, outputs, address }, according to the Method name, input, output and contract Address of the transaction receipt;
Transaction snapshot: an outline of the execution of a transaction on the blockchain is recorded, and the data structure is as follows:
Struct Snapshot{
string Method,// Method name of transaction execution
Input parameter list of String [ ] Inputs,// transactions
String [ ] Outputs, output list of/transaction
STRING ADDRESS// contract Address to perform the transaction
}
B. The get method get (Hash) of the transfer contract state variable that performs the Hash time lock contract on chain_a obtains contract data, the get method get (counterpartyAddress) that performs the counter-party contract state variable obtains the counter-party contract address, constructs the desired snapshot from the contract data and the counter-party contract address, excepted _lock_b_snapshot:
{ lock, [ Hash Lock ], [ "success" ], address_b };
Verify that real_lock_b_snapshot and excepted _lock_b_snapshot are equal, and if not, wait for timeout rollback.
The router_a executes the lock_a (Hash) transaction to lock the first transaction asset on the chain_a, that is, the account_a1 transfers the first transaction asset to the intermediate account account_a, and obtains the transaction response piece lock_a_ receipt.
Router_a requests router_b to unlock the fourth transaction asset on chain_b according to Hash and Secret, performs unlock_b (Hash, secret) transaction, and requests transaction receipt lock_a_ receipt with the lock-own chain asset attached.
Router_b does not trust router_a, and therefore verifies the correctness of the lock_a (Hash) transaction on chain_a:
a. an actual transaction snapshot is constructed according to lock_a_ receipt:
real_lock_a_snapshot:{Method,Inputes,Outputs,Address}；
b. The get method get (Hash) of transferring contract state variables of Hash time lock contracts on chain_b obtains contract data, the get method get (counterpartyAddress) of executing opponent contract state variables obtains opponent contract addresses, and expected snapshots are constructed according to the contract data and the opponent contract addresses, excepted _lock_a_snapshot: { lock, [ Hash ], [ "success" ], address_a }; verify that real_lock_a_snapshot and excepted _lock_a_snapshot are opposite, and if not, wait for timeout rollback.
If the verification is successful, the router_b performs a unlock_b (Hash, secret) transaction to unlock the asset on the blockchain_b, i.e., accout _b transfers the fourth transaction asset to the accoun_b1.
At this time, the router_b obtains the Secret, and then the step of router_a in (6-13) is performed, so that the unlocking of the asset on the blockchain chain_a can be completed, namely accout _a transfers the asset to the accoun_a2.
In the process, a timer is set by a timestamp field in contract data according to a hash time lock contract, and the asset is rolled back when the time is overtime at any time.
As shown in fig. 3, the present invention provides a transaction correctness verification apparatus applied to a coalition chain cross-chain transfer, comprising: a transmission module 301 for sending a first locked asset request to a second cross-link router; the first locking asset request is to indicate a fourth transaction asset to lock a second account of a second user on a second blockchain based on a transaction request of the first account of the first user on the first blockchain; and a first transaction receipt for obtaining the second cross-link response piece sent by the first cross-link; the first transaction receipt being descriptive of the second cross-link by declared locked fourth transaction asset; the first transaction receipt is generated based on a fourth declarative asset, a second execution contract number, and a second execution contract address of the fourth transaction asset; the processing module 302 is configured to generate first transaction snapshot information corresponding to the first transaction receipt according to a preset format; and generating second transaction snapshot information according to the preset format based on the fourth transaction asset, the contract number and the second contract address; the contract number of the contract is the contract number corresponding to the contract data contracted by the first user and the second user; the second contracted contract address is a contract address where the first user and the second user store the contract data in the second blockchain; a determining module 303 is configured to determine that the first transaction snapshot information is consistent with the second transaction snapshot information, and then determine that the second cross-link is locked with the fourth transaction asset.
Optionally, the processing module 302 is further configured to: locking a first transaction asset of a first account of the first user; generating a second transaction receipt based on the first declarative asset of the first transaction asset, a first execution contract number, and a first execution contract address of the first user; the second transaction receipt for the first cross-link by declaring that the first transaction asset has been locked; the transmission module 301 is further configured to: sending the second transaction receipt, a first unlock asset request, and a hash primitive to the second cross-link; the hash original image is an original image of the contracted contract number, and the hash original image is used for unlocking the fourth transaction asset after the second cross-link receipt passes through verification of the second transaction receipt.
Optionally, the transmission module 301 is further configured to: receiving a second lock asset request sent by the second cross-link; the processing module 302 is further configured to: locking a second transaction asset of a second account of the first user on the first blockchain; generating a third transaction receipt based on the second declarative asset, a third execution contract number, and a third execution contract address of the second transaction asset; the third transaction receipt for the first cross-link by declaring that the second transaction asset has been locked; the transmission module 301 is further configured to: the third transaction receipt is sent to the second cross-link route for use by the second cross-link route in verifying whether the first cross-link route locks the second transaction asset.
Optionally, the transmission module 301 is further configured to: receiving the second cross-link transmitted fourth transaction receipt, a second unlock asset request and the hash original image; the fourth transaction receipt is descriptive information that the second cross-link has been locked by a third transaction asset declared to be the first account of the second user on the second blockchain; the fourth transaction receipt is generated based on a third declarative asset, a fourth execution contract number, and a fourth execution contract address of the third transaction asset; the processing module 302 is further configured to: generating seventh transaction snapshot information according to the fourth transaction receipt and the preset format; generating eighth transaction snapshot information according to the preset format based on the contract number and the second contract address; and if the seventh transaction snapshot information and the eighth transaction snapshot information are verified to be consistent, unlocking the second transaction asset according to the hash original image.
Optionally, the contract data includes a first timestamp; the first timestamp is to trigger the first blockchain to rollback the first transaction asset to a first account of the first user when the first timestamp arrives but the first transaction asset is not unlocked.
Optionally, the contract data includes Ha Xiyuan images, contracted contract numbers and transaction attributes; the first user stores first contract data in the first blockchain, wherein the first contract data records the Ha Xiyuan images, the appointed contract numbers and the transaction attributes; the second user stores second contract data in the second blockchain, wherein the contracted contract number and the transaction attribute are recorded in the second contract data.
Optionally, the transaction snapshot information includes the following: function name of transaction execution; input parameters for the transaction; outputting a transaction result; contract addresses for executing transactions.
The embodiment of the application provides a computer device which comprises a program or an instruction, wherein the program or the instruction is used for executing the transaction correctness verification method and any optional method applied to the alliance chain cross-chain transfer.
The embodiment of the application provides a storage medium comprising a program or an instruction, which is used for executing the transaction correctness verification method and any optional method applied to the alliance chain cross-chain transfer provided by the embodiment of the application when being executed.
Finally, it should be noted that: it will be appreciated by those skilled in the art that embodiments of the present application may be provided as a method, system, or computer program product. Accordingly, the present application may take the form of an entirely hardware embodiment, an entirely software embodiment or an embodiment combining software and hardware aspects. Furthermore, the present application may take the form of a computer program product embodied on one or more computer-usable storage media (including, but not limited to, disk storage, optical storage, and the like) having computer-usable program code embodied therein.
The present application is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to the application. It will be understood that each flow and/or block of the flowchart illustrations and/or block diagrams, and combinations of flows and/or blocks in the flowchart illustrations 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.
It will be apparent to those skilled in the art that various modifications and variations can be made to the present application without departing from the scope of the application. Thus, it is intended that the present application also include such modifications and alterations insofar as they come within the scope of the appended claims or the equivalents thereof.
Claims (10)
1. A transaction correctness verification method applied to federated chain cross-chain transfer, comprising:
the first cross-link route sends a first locking asset request to the second cross-link route; the first locking asset request is to indicate a fourth transaction asset to lock a second account of a second user on a second blockchain based on a transaction request of the first account of the first user on the first blockchain;
The first cross-link route obtains a first transaction receipt sent by the second cross-link route; the first transaction receipt being descriptive of the second cross-link by declared locked fourth transaction asset; the first transaction receipt is generated based on a fourth declarative asset, a second execution contract number, and a second execution contract address of the fourth transaction asset;
The first cross-link is used for generating first transaction snapshot information corresponding to the first transaction receipt according to a preset format;
The first cross-link router generates second transaction snapshot information according to the preset format based on the fourth transaction asset, the contract number and the second contract address; the contract number of the contract is the contract number corresponding to the contract data contracted by the first user and the second user; the second contracted contract address is a contract address where the first user and the second user store the contract data in the second blockchain;
And if the first cross-link slave determines that the first transaction snapshot information is consistent with the second transaction snapshot information, determining that the second cross-link slave locks the fourth transaction asset.
2. The method of claim 1, wherein the determining that the second cross-link slave has locked the fourth transaction asset further comprises:
the first cross-link is made of a first transaction asset that locks a first account of the first user;
Generating a second transaction receipt by the first cross-link based on a first declarative asset of the first transaction asset, a first execution contract number, and a first execution contract address of the first user; the second transaction receipt for the first cross-link by declaring that the first transaction asset has been locked;
The first cross-link router sends the second transaction receipt, a first unlock asset request and a hash primitive to the second cross-link router; the hash original image is an original image of the contracted contract number, and the hash original image is used for unlocking the fourth transaction asset after the second cross-link receipt passes through verification of the second transaction receipt.
3. The method of claim 2, wherein the first cross-link routing to the second cross-link routing after sending the second transaction receipt, first unlock asset request, and hash primitive further comprises:
The first cross-link slave receives a second lock asset request sent by the second cross-link slave;
The first cross-link route locks a second transaction asset of a second account of the first user on the first blockchain;
generating a third transaction receipt by the first cross-link from a second declarative asset based on the second transaction asset, a third execution contract number, and a third execution contract address; the third transaction receipt for the first cross-link by declaring that the second transaction asset has been locked;
the first cross-link route sends the third transaction receipt to the second cross-link route for use by the second cross-link route in verifying whether the first cross-link route locks the second transaction asset.
4. The method of claim 3, wherein after the first cross-link router sends the third transaction response piece to the second cross-link router, further comprising:
The first cross-link slave receives a fourth transaction receipt, a second unlock asset request and the hash original image sent by the second cross-link slave; the fourth transaction receipt is descriptive information that the second cross-link has been locked by a third transaction asset declared to be the first account of the second user on the second blockchain; the fourth transaction receipt is generated based on a third declarative asset, a fourth execution contract number, and a fourth execution contract address of the third transaction asset;
The first cross-link router generates seventh transaction snapshot information according to the fourth transaction receipt and the preset format; the first cross-link is used for generating eighth transaction snapshot information according to the preset format based on the third transaction asset, the appointed contract number and the second appointed contract address;
and if the first cross-link router verifies that the seventh transaction snapshot information and the eighth transaction snapshot information are consistent, unlocking the second transaction asset according to the hash original image.
5. The method of any one of claims 1 to 4, wherein the contract data includes a first timestamp therein; the first timestamp is to trigger the first blockchain to rollback the first transaction asset to a first account of the first user when the first timestamp arrives but the first transaction asset is not unlocked.
6. The method of any one of claims 1 to 4, wherein the contract data includes Ha Xiyuan images, contracted contract numbers, and transaction attributes; the first user stores first contract data in the first blockchain, wherein the first contract data records the Ha Xiyuan images, the appointed contract numbers and the transaction attributes; the second user stores second contract data in the second blockchain, wherein the contracted contract number and the transaction attribute are recorded in the second contract data.
7. The method of any of claims 1 to 4, wherein the transaction snapshot information includes the following: function name of transaction execution; input parameters for the transaction; outputting a transaction result; contract addresses for executing transactions.
8. A transaction correctness verification apparatus for use in coalition chain cross-chain transfer, comprising:
A transmission module for transmitting a first locked asset request to a second cross-link router; the first locking asset request is to indicate a fourth transaction asset to lock a second account of a second user on a second blockchain based on a transaction request of the first account of the first user on the first blockchain; and a first transaction receipt for obtaining the second cross-link response piece sent by the first cross-link; the first transaction receipt being descriptive of the second cross-link by declared locked fourth transaction asset; the first transaction receipt is generated based on a fourth declarative asset, a second execution contract number, and a second execution contract address of the fourth transaction asset;
The processing module is used for generating first transaction snapshot information corresponding to the first transaction receipt according to a preset format; and generating second transaction snapshot information according to the preset format based on the fourth transaction asset, the contract number and the second contract address; the contract number of the contract is the contract number corresponding to the contract data contracted by the first user and the second user; the second contracted contract address is a contract address where the first user and the second user store the contract data in the second blockchain;
and the determining module is used for determining that the first transaction snapshot information is consistent with the second transaction snapshot information, and determining that the fourth transaction asset is locked by the second cross-link.
9. A computer device comprising a program or instructions which, when executed, performs the method of any of claims 1 to 7.
10. A storage medium comprising a program or instructions which, when executed, perform the method of any one of claims 1 to 7.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010374241.8A CN111640017B (en) | 2020-05-06 | 2020-05-06 | Transaction correctness verification method and device applied to alliance chain cross-chain transfer |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010374241.8A CN111640017B (en) | 2020-05-06 | 2020-05-06 | Transaction correctness verification method and device applied to alliance chain cross-chain transfer |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111640017A CN111640017A (en) | 2020-09-08 |
| CN111640017B true CN111640017B (en) | 2024-05-28 |
Family
ID=72330943
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010374241.8A Active CN111640017B (en) | 2020-05-06 | 2020-05-06 | Transaction correctness verification method and device applied to alliance chain cross-chain transfer |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111640017B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN111934990B (en) * | 2020-09-25 | 2021-02-09 | 支付宝(杭州)信息技术有限公司 | Message transmission method and device |
| CN112148796B (en) * | 2020-09-28 | 2024-05-31 | 中钞***产业发展有限公司杭州区块链技术研究院 | Electronic trade bill sharing method, device, equipment and medium |
| CN111970129B (en) * | 2020-10-21 | 2021-01-01 | 腾讯科技（深圳）有限公司 | Data processing method and device based on block chain and readable storage medium |
| CN112787999B (en) * | 2020-12-25 | 2023-02-17 | 深圳前海微众银行股份有限公司 | Cross-chain calling method, device, system and computer readable storage medium |
| CN112804262B (en) * | 2021-03-19 | 2021-07-27 | 北京万物智链科技有限公司 | Safety guarantee method and system in block chain cross-chain communication |
| CN113269545A (en) * | 2021-05-26 | 2021-08-17 | 杭州云象网络技术有限公司 | Hash time locking method and system based on cloud cross-chain transfer protocol |
| CN113191756B (en) * | 2021-06-04 | 2022-07-19 | 杭州复杂美科技有限公司 | Cross-chain asset security management method, computer device and storage medium |
| CN113259478B (en) * | 2021-06-17 | 2021-11-02 | 支付宝(杭州)信息技术有限公司 | Method and device for executing transaction in blockchain system and blockchain system |
| CN115708119A (en) * | 2021-08-20 | 2023-02-21 | 华为云计算技术有限公司 | Cross-chain transaction system, method, device and storage medium |
| CN113706148B (en) * | 2021-08-27 | 2023-09-29 | 杭州云象网络技术有限公司 | Cross-link method, system, storage medium and device based on channel authority control |
Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018120057A1 (en) * | 2016-12-30 | 2018-07-05 | 深圳前海达闼云端智能科技有限公司 | Currency management method and system based on block chain |
| CN108492105A (en) * | 2018-03-07 | 2018-09-04 | 物数（上海）信息科技有限公司 | Transaction in assets monitoring and managing method, system, equipment and storage medium based on block chain |
| CN108492108A (en) * | 2018-03-29 | 2018-09-04 | 深圳前海微众银行股份有限公司 | Across the chain communication means of block chain, system and computer readable storage medium |
| CN108647965A (en) * | 2018-05-07 | 2018-10-12 | 北京柏链基石科技有限公司 | Across chain method of commerce, device, storage medium and electronic equipment |
| CN108876369A (en) * | 2018-06-05 | 2018-11-23 | 上海和数软件有限公司 | Data communications method, device and computer readable storage medium based on block chain |
| CN109146448A (en) * | 2018-07-13 | 2019-01-04 | 杭州复杂美科技有限公司 | Across chain assets transfer method, equipment and storage medium |
| CN109359959A (en) * | 2018-09-29 | 2019-02-19 | 衢州学院 | Across chain assets transfer method, equipment and storage medium |
| CN109493027A (en) * | 2018-11-19 | 2019-03-19 | 众安信息技术服务有限公司 | A kind of method and device realized across chain transactional operation |
| CN109685489A (en) * | 2018-12-28 | 2019-04-26 | 杭州云象网络技术有限公司 | A kind of assets across chain method of commerce between block chain |
| CN110033243A (en) * | 2019-03-06 | 2019-07-19 | 华南师范大学 | Main chain based on block chain intelligence contract deposits card method, system and storage medium |
| CN110223178A (en) * | 2019-06-06 | 2019-09-10 | 杭州趣链科技有限公司 | It is a kind of for alliance's chain across catenary system and across chain method |
| WO2019174430A1 (en) * | 2018-03-14 | 2019-09-19 | 郑杰骞 | Block chain data processing method, management terminal, user terminal, conversion device, and medium |
| CN110471931A (en) * | 2019-08-13 | 2019-11-19 | 山大地纬软件股份有限公司 | A kind of digital asset trade identity maintaining method based on transaction in assets chain |
| WO2020042934A1 (en) * | 2018-08-28 | 2020-03-05 | 白杰 | Non-repudiation cross-chain transaction method and blockchain system |
| CN110868439A (en) * | 2018-08-28 | 2020-03-06 | 傲为信息技术(江苏)有限公司 | Block chain system |
| CN111080449A (en) * | 2019-12-03 | 2020-04-28 | 深圳前海微众银行股份有限公司 | Block chain cross-chain transaction method, management node and block chain network |
-
2020
- 2020-05-06 CN CN202010374241.8A patent/CN111640017B/en active Active
Patent Citations (16)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| WO2018120057A1 (en) * | 2016-12-30 | 2018-07-05 | 深圳前海达闼云端智能科技有限公司 | Currency management method and system based on block chain |
| CN108492105A (en) * | 2018-03-07 | 2018-09-04 | 物数（上海）信息科技有限公司 | Transaction in assets monitoring and managing method, system, equipment and storage medium based on block chain |
| WO2019174430A1 (en) * | 2018-03-14 | 2019-09-19 | 郑杰骞 | Block chain data processing method, management terminal, user terminal, conversion device, and medium |
| CN108492108A (en) * | 2018-03-29 | 2018-09-04 | 深圳前海微众银行股份有限公司 | Across the chain communication means of block chain, system and computer readable storage medium |
| CN108647965A (en) * | 2018-05-07 | 2018-10-12 | 北京柏链基石科技有限公司 | Across chain method of commerce, device, storage medium and electronic equipment |
| CN108876369A (en) * | 2018-06-05 | 2018-11-23 | 上海和数软件有限公司 | Data communications method, device and computer readable storage medium based on block chain |
| CN109146448A (en) * | 2018-07-13 | 2019-01-04 | 杭州复杂美科技有限公司 | Across chain assets transfer method, equipment and storage medium |
| CN110868439A (en) * | 2018-08-28 | 2020-03-06 | 傲为信息技术(江苏)有限公司 | Block chain system |
| WO2020042934A1 (en) * | 2018-08-28 | 2020-03-05 | 白杰 | Non-repudiation cross-chain transaction method and blockchain system |
| CN109359959A (en) * | 2018-09-29 | 2019-02-19 | 衢州学院 | Across chain assets transfer method, equipment and storage medium |
| CN109493027A (en) * | 2018-11-19 | 2019-03-19 | 众安信息技术服务有限公司 | A kind of method and device realized across chain transactional operation |
| CN109685489A (en) * | 2018-12-28 | 2019-04-26 | 杭州云象网络技术有限公司 | A kind of assets across chain method of commerce between block chain |
| CN110033243A (en) * | 2019-03-06 | 2019-07-19 | 华南师范大学 | Main chain based on block chain intelligence contract deposits card method, system and storage medium |
| CN110223178A (en) * | 2019-06-06 | 2019-09-10 | 杭州趣链科技有限公司 | It is a kind of for alliance's chain across catenary system and across chain method |
| CN110471931A (en) * | 2019-08-13 | 2019-11-19 | 山大地纬软件股份有限公司 | A kind of digital asset trade identity maintaining method based on transaction in assets chain |
| CN111080449A (en) * | 2019-12-03 | 2020-04-28 | 深圳前海微众银行股份有限公司 | Block chain cross-chain transaction method, management node and block chain network |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111640017A (en) | 2020-09-08 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN111640017B (en) | Transaction correctness verification method and device applied to alliance chain cross-chain transfer | |
| US20200143366A1 (en) | Methods for decentralized digital asset transfer and smart contract state transition | |
| CN110147994B (en) | Instant execution method of block chain based on homomorphic encryption | |
| WO2020258848A1 (en) | Method and apparatus for cross-chain transmission of resources | |
| Kiayias et al. | Fair and robust multi-party computation using a global transaction ledger | |
| CN107301600B (en) | Core construction method of block chain Internet model for cross-chain transaction | |
| Kiayias et al. | A composable security treatment of the lightning network | |
| Goes | The interblockchain communication protocol: An overview | |
| WO2018232493A1 (en) | A network of doubly-chained blockchains capable of cross-chain transactions | |
| WO2019042101A1 (en) | Cross-chain trading method and apparatus | |
| CN111371905B (en) | Block chain layering consensus proving system and method based on cloud computing | |
| WO2016122740A1 (en) | Manicoding for communication verification | |
| US20220311607A1 (en) | Key generation method and apparatus, device, and medium | |
| CN111461723A (en) | Data processing system, method and device based on block chain | |
| EP3726774A1 (en) | Transparent blockchain sidechains to support blockchain processing heterogeneity | |
| CN112488682B (en) | Three-party transfer method and device for block chain | |
| CN111294339A (en) | Homogeneous alliance chain cross-chain method and device based on Fabric architecture | |
| CN112581130A (en) | Cross-chain transaction method based on multi-chain interconnection | |
| CN111915308A (en) | Transaction processing method of blockchain network and blockchain network | |
| Ranchal-Pedrosa et al. | Platypus: Offchain protocol without synchrony | |
| Ren et al. | Interoperability in blockchain: A survey | |
| CN112488683B (en) | Under-chain transaction method and device of blockchain | |
| KR20220045025A (en) | Method and system for communication protocol of decentralized transaction | |
| CN112926983A (en) | Block chain-based deposit certificate transaction encryption system and method | |
| Decker | On the scalability and security of bitcoin |
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 |