CN109472572A - Contract deployment and transaction based on the more subchains of block chain main chain adduction row - Google Patents
Contract deployment and transaction based on the more subchains of block chain main chain adduction row Download PDFInfo
- Publication number
- CN109472572A CN109472572A CN201811392134.7A CN201811392134A CN109472572A CN 109472572 A CN109472572 A CN 109472572A CN 201811392134 A CN201811392134 A CN 201811392134A CN 109472572 A CN109472572 A CN 109472572A
- Authority
- CN
- China
- Prior art keywords
- subchain
- node
- chain
- user
- contract
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/04—Payment circuits
- G06Q20/06—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme
- G06Q20/065—Private payment circuits, e.g. involving electronic currency used among participants of a common payment scheme using e-cash
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/08—Payment architectures
- G06Q20/10—Payment architectures specially adapted for electronic funds transfer [EFT] systems; specially adapted for home banking systems
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/30—Payment architectures, schemes or protocols characterised by the use of specific devices or networks
- G06Q20/36—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes
- G06Q20/367—Payment architectures, schemes or protocols characterised by the use of specific devices or networks using electronic wallets or electronic money safes involving electronic purses or money safes
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3825—Use of electronic signatures
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3827—Use of message hashing
-
- 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/42—Confirmation, e.g. check or permission by the legal debtor of payment
-
- 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
Landscapes
- Business, Economics & Management (AREA)
- Accounting & Taxation (AREA)
- Engineering & Computer Science (AREA)
- Finance (AREA)
- General Physics & Mathematics (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- Theoretical Computer Science (AREA)
- Computer Security & Cryptography (AREA)
- Development Economics (AREA)
- Economics (AREA)
- Marketing (AREA)
- Technology Law (AREA)
- Computer Networks & Wireless Communication (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present invention is based on the deployment of the contract of the more subchains of block chain main chain adduction row and transaction, it is characterized by: the more subchain frameworks of main chain adduction row include a main chain and the parallel subchain of N item, each node stores main chain data, the main chain data do not store particular transactions, and storage system global information, user's login user end wallet, source address is sent to the subchain position that direct interaction node inquires its account by user terminal wallet, return to its corresponding source subchain, and the corresponding subchain node link information of source address, and analysis contract dependence, the content for whether relying on other subchain contracts returned；If user receives the content for not depending on other subchain contracts, user confirms signature, contract is deployed on user's subchain node, and then subchain is committed to main chain, and main chain increases the mapping relations of contract and contract and subchain newly, completes contract and is deployed to main chain；The reason of if receiving the content for relying on other subchain contracts, disposing and fail, returning to deployment failure.
Description
Technical field
It is especially a kind of based on the more subchains of block chain main chain adduction row the present invention relates to the scalability scheme of block chain
Contract deployment and transaction.
Background technique
Each ordinary node in present block chain will: 1, storage institute is stateful；2, All Activity is serially executed；3, with
Other all machines are reached common understanding.
Extension basic ideas for existing block chain are: 1, individual node storage section state；2, individual node
It trades processing part；3, part of nodes is only allowed to participate in common recognition.
Refering to Figure 1, it is the schematic diagram by user's fragment.If pressing user's fragment, it is difficult to handle different points
Transferring accounts between piece user, contract are also difficult to dispose, if be deployed on all fragments, contract state can not be consistent, if
It is only deployed on some fragment, and the request of other fragmented users can not be handled.
It please refers to shown in Fig. 2, for by the schematic diagram of contract fragment.If pressing contract fragment, each contract requires energy
The transaction of all users is handled, and every transaction can all check/modify that the account status of user (for example, for ether mill, owns
Transaction all will modify account balance because of consumption gas, for EOS, CPU/ bandwidth/storage quota of Yao Xiugai account), contract is simultaneously
What row executed, it not can guarantee the consistency of User Status, in addition, often calling mutually between contract, if being distributed in different points
On piece, and can not call.
And third extends thinking, part of nodes participates in common recognition, can cause 1% attack, that is, suppose there is 100 fragments, attack
The person of hitting only needs to control 1% node, can fully control a fragment.
Existing expansion scheme mainly have ether mill sharding, ether mill plasma, Cosmos Network,
Polkadot, Lisk, A Xilian, Zilliqa, VBFT, DPOS, Algorand, Dfinity etc..
Ether mill sharding: long-range solution ether mill scaling problem.Main at present to consider 1% attack, fragment chain cannot be held
Row transaction has relatively remote from practical application.
Ether mill plasma: being contract fragment by application, and part contract stores and executes on side chain, token can be turned
To side chain, subsequent transaction carries out on side chain, even if side chain is insincere, token can also be gone back to safely to main chain, represent and realize
There is the game chain of Loom network.Limitation is that side chain must go back to token consumption using UTXO model, practical application narrow limits
When it is too long, need at least 7 days.
Cosmos Network, Polkadot: by fragment is applied, there is a main chain, each using the side chain of oneself,
Main chain/side chain interaction protocol is defined, while providing underlying platform and tool facilitates third party to develop customized side chain.Limitation is
Subchain is opaque to user, and subchain has 1% attack problem, and all in exploitation, shortage is discussed in detail two projects.
Lisk, A Xilian: by fragment is applied, the ease for use of creation side chain is laid particular emphasis on.Limitation is that subchain is opaque to user,
Subchain has 1% attack problem, compares Cosmos/Polkadot, and side chain customizes weak.
Zilliqa: pressing user's fragment, and transaction (i.e. user and contract are in the same fragment) can be simultaneously in the chain of different subchains
Row executes.Limitation is to be unable to complete parallel, does not have state fragment, across chain communication, in exploitation, shortage is discussed in detail.
VBFT, DPOS, Algorand, Dfinity: part of nodes participates in common recognition, while avoiding 1% attack, and DPOS is ballot
Node is elected, VBFT/Algorand/Dfinity, which is used, can verify that random selection common recognition node.Limitation is still to be limited to single machine
Storage/processing/network capabilities.
In summary, scalability is still a difficult point at present, and being extended by fragment and multichain is one basic
Resolving ideas, but critical issue is how to carry out fragment, so that multichain is externally rendered as a chain, how to guarantee safety
Under the premise of, lower across chain expense is kept, realizes linear expansion.This is also exactly that the present invention will be studied and be solved the problems, such as.
Summary of the invention
It is an object of the invention to not sacrificing security and it is distributed under the premise of, solve current block chain scalability
Problem.
Present invention firstly provides a kind of, and the contract based on the more subchains of block chain main chain adduction row is disposed and trades, the main chain
The more subchain frameworks of adduction row include a main chain and the parallel subchain of N item, wherein n=1 ... .X, wherein each node stores main chain number
Particular transactions are not stored according to, main chain data, and storage system global information, include at least across chain request/response notice letter
Breath；Each node is stored the total data of a subchain by system original allocation, and each node also includes across the chain message team of subchain
Column；Across the chain request/response notification information corresponds to the notice of across chain request/response queue, is free of details；User passes through
User terminal wallet software is interacted with some node, which is known as direct interaction node；One user belongs to and is pertaining only to a certain
Subchain, a node possess and only possess the data of a subchain, and the request of a user can only be by possessing the section of its data
Point processing, the node are known as user's subchain node；User's login user end wallet, user terminal wallet are connected to directly interaction section
Source address is sent to the subchain position that direct interaction node inquires its account by point, user terminal wallet, which returns
Return its corresponding source subchain and the corresponding subchain node link information of source address, and analysis contract dependence, return whether according to
Rely the content of other subchain contracts；If user receives the content for not depending on other subchain contracts, user confirms signature, will close
It is about deployed on user's subchain node, then subchain is committed to main chain, and main chain increases the mapping relations of contract and contract and subchain newly,
It completes contract and is deployed to main chain；If receiving the content for relying on other subchain contracts, dispose and fail, returns to the original of deployment failure
Cause.
The present invention also provides a kind of schemes for submitting transaction: transaction request is committed to user terminal wallet software by user, is used
The request of subchain position and contract where family end wallet software sends inquiry source address and receive address to its direct interaction node
The request of place subchain position；Direct interaction node return corresponding source subchain, the corresponding subchain node link information of source address,
It receives subchain and whether relies on other subchain contracts；If user belongs to some subchain, and contract also belongs to some subchain,
If the two subchains are identical, user's subchain node can directly handle contract transaction；If belonging to different subchains, money
Contract can be traded and be revised as across chain transaction by packet, by across catenary system contract, finally by user's subchain node processing.
System structure of the invention has following features:
1, versatility: not only may be implemented to transfer accounts across chain, can also realize any across chain message transmission.
2, reliability: similar with Transmission Control Protocol, communication is that reliably, it is not one-way transmission that request, which centainly has response,.
3, safety: any node has main chain information, namely has the subchain build of all subchains, can be used as all sons
The SPV client of chain can verify the request/response of any subchain by Merkle Proof, directly connect without trusting
The subchain node connect.
Across chain communication be also efficiently and it is expansible, this is embodied in:
1, across the chain communication details of subchain are not sent to main chain, and that does not also propagate in main chain P2P Internet communication, main chain is only new
Request/response notification information.
2, across the chain communication notifications message of subchain is that All Activity summarizes in subchain block, is submitted to subchain build
Main chain, not additional communication overhead.
3, there is no particular transactions on main chain, the transaction number in a main chain block is only related with subchain number, at one
Know together the period in, only one node of each subchain submit transaction arrive main chain, transaction content be main chain modification, subchain build and
Across the chain notification information summarized, so the transaction of main chain, network communication, storage etc. are not bottlenecks.
4, subchain node disjoint application main chain block is directly connected to other neighbouring subchain node acquisition request/response details,
This process be it is parallel, distributed, no node is bottleneck.
In summary, although across chain communication is via main chain, the load of main chain is very low, is not bottleneck, the son that can be accommodated
The number of deals that may include in chain number and main chain block is related, is calculated with block size 1MB, single transaction 1KB, can accommodate 1024
A subchain, before subchain number reaches the value, whole system processing capacity can increase and linear expansion with subchain number.
Detailed description of the invention
Fig. 1 is to expand schematic diagram by the block chain of user's fragment in the prior art.
Fig. 2 is to expand schematic diagram by the block chain of contract fragment in the prior art.
Fig. 3 is the system logic figure that the more subchains of main chain adduction row are used in the present invention.
Fig. 4 is the architecture diagram based on the individual node under the more subchain logics of main chain adduction row in the present invention.
Fig. 5 is the multipoint architecture scheme disposed in the present invention based on single-point in Fig. 4.
Fig. 6 is the flow chart of main chain and subchain interaction.
Fig. 7 is to obtain node link information according to transaction Hash txhash and block Hash blockhash and trade detailed with block
The flow chart of feelings.
Fig. 8 is user and the process that user terminal is transferred accounts based on the framework of main chain adduction row subchain of the present invention.
Fig. 9 is the internal logic figure of money transfer transactions.
Figure 10 is across chain request and responding process.
Figure 11 is across chain money transfer transactions process.
Figure 12 is the flow chart that contract is disposed in the present invention.
Figure 13 is the flow chart that contract transaction is submitted in the present invention.
Figure 14 is the storage schematic diagram of node and subchain.
Figure 15 is the flow chart of Node registry.
Figure 16 is that main chain and subchain store schematic diagram.
Figure 17 is that account distributes and migrates flow chart.
Specific embodiment
It please refers to shown in Fig. 3, the system logic figure of parallel subchain is added for main chain proposed by the present invention.The present invention includes
1 main chain and the parallel subchain of n item, wherein n=1 ... .X, each node stores main chain data, and stores certain by system original allocation
The total data of subchain, each node also includes across the chain message queue of subchain.Wherein, the main chain data do not store specific friendship
Easily, storage system global information includes at least: subchain number, subchain build, the mapping relations of account and subchain, contract with
The mapping relations of subchain, the mapping relations of back end and subchain, mapping relations, across the chain request/sound for verifying node and subchain
Answer whether notification information, all contract codes, subchain load, subchain come into force.Wherein, across the chain notification message is and subchain
The corresponding notification message of service management in across chain message queue.Each subchain has a subchain id, each node
With a node i d, subchain information herein refers to subchain id, and subchain position includes subchain id and the corresponding subchain section of source subchain
Point link information, the subchain node link information are stored in back end<->subchain mapping table, are mainly located at comprising a subchain
On those nodes, the IP address of these nodes and port.
Wherein, each node includes the account of corresponding subchain, contract by the total data of the initially allocated subchain of system
And transaction.Contract in the total data of the subchain is removed comprising contract code, also the complete informations such as state comprising contract.Its
In, across the chain message queue of subchain includes two classes, and one kind is across chain request queue, and each target subchain creates one, storage
The request message details of target subchain are sent to, different target subchains is divided into different queues；Another kind of is across chain response queue,
Each source chain creation one, storage are sent to the response message details of source chain, and different source chains is divided into different queues.
Each node is realized above-mentioned architectural schemes, in network layer, is removed by the point-to-point access of P2P network implementations
It also include subchain P2P outside comprising main chain P2P, main chain P2P network submits data (subchain build, subchain pair for subchain chain linked to owner
The modification information of main chain, across chain notification information), propagate main chain data, (across chain notification information is in each node for across chain communication-cooperation
Between communication).Subchain P2P is divided into two classes: subchain data P 2 P and subchain verifying P2P again.Store the total data of certain subchain
Each node by subchain data P 2 P Network Synchronization subchain trade and block.It is responsible for each section of the same subchain transaction of verifying
Point verifies P2P by subchain and transaction and block is verified and signed.For some node, it may be some subchain number
According to storage person, participate in subchain data P 2 P network, while may be the same subchain or the verifier of other subchains, participate in son
Chain verifies P2P network.The subchain role of node is that system is initially allocated, and storage person role is relatively constant, and is responsible for which strip
The verifying of chain is then that dynamic random adjusts, and each block period is different out, this is to guarantee peace while realizing expansible
Entirely, the method for 1% attack is avoided.
It please refers to shown in Fig. 4, for the architecture diagram of individual node in the present invention.Each node storage main chain data are divided
Across the chain message queue of the subchain data and the subchain matched.Please refer to shown in Fig. 5, for based under Fig. 4 interior joint framework
Multinode deployment scheme.It is exemplary in the program to list 6 nodes A, B, C, D, E, F.Each node is stored with main chain
Data, interior joint A, B and C form the data P 2 P network of subchain x by the data of system original allocation storage subchain x.Node
D, E and F forms the data P 2 P network of subchain y by the data of system original allocation storage subchain y.The scheme packet shown in the figure
Containing a main chain and 2 parallel x, y subchain.The moment in figure, node A, D and E are responsible for the verifying of subchain x data, node B, C
It is responsible for the verifying of subchain y data with F.
It please refers to shown in Fig. 6, is the interaction of main chain and subchain under the more subchain system architectures of main chain adduction row.Subchain goes out block
It afterwards, can be by main chain P2P Web broadcast subchain build, subchain to the modification of main chain and across chain request/response notification information
Subchain collection.The submission of all subchains will form main chain block, be broadcast to all nodes.Each node, can more after receiving main chain block
New local main chain is notified with keeping the main chain of all nodes consistent according to across the chain request/response notification message in main chain build
Other subchain information of acquisition request or the current subchain of response, are directly connected to other subchain node acquisition request/response details simultaneously
It is handled.
Under this framework, main chain build can be used and verify the transaction of other subchains.Under this framework, each node is because be
System original allocation stores the total data of a certain subchain, is its full node for corresponding to subchain, while each node stores
Main chain data, are the light nodes of other all subchains, and each node is the full node of main chain.Merkel proves: referring to one light section
O'clock to a full node initiate it is primary prove request, inquire in the complete Merkel tree of full node, if specified there are one
Data or transaction；Full node, which returns to a Gadamer gram to light node, proves path, is calculated by light node, and verifying exists
Property.
In the present solution, Merkel proves to can be used for checking request/response details.
It please refers to shown in Fig. 7, to obtain node link information according to transaction Hash txhash and block Hash blockhash
And the flow chart of transaction and block details.Subchain id value is embedded in hash, inquiry is parsed from transaction hash and block hash
Source subchain id and/or reception subchain id, and subchain node link information is inquired according to subchain id, the subchain node link information
It is stored in the back end of main chain data and the mapping relations of subchain, is mainly located on those nodes comprising a subchain, this
The IP address of a little nodes and port.
Above scheme, real trade are not completed by main chain, and main chain only records the summary info of subchain, greatlys improve
The performance of block chain, randomly selects the verifying node of subchain, can to avoid 1% it is total, substantially increase security performance.
It being made of inside this system main chain and a plurality of subchain, each node has main chain information, but only subchain
Information.However, from the user's point of view, the concept of subchain is simultaneously not present, each node only has a chain, all about this chain
Complete information, its all interactions can be completed by the node.The trading function of traditional main chain switchs to coordination function, by it
Parallel subchain is specifically traded to handle each pen, since each node stores main chain data, each user and some section
When point interaction, final transaction can be realized by the system global information recorded in main chain data.
User is interacted by user terminal wallet software with some node, which is known as direct interaction node, but the node
The request of the user may cannot be handled without the information of the user.In systems, a user belongs to and is pertaining only to a certain item
Subchain, a node possess and only possess the data of a subchain, and the request of a user can only be by possessing the node of its data
Processing, the node are known as user's subchain node.User terminal wallet software, direct interaction node and user's subchain node phase interworking
It closes, provides a simple experience to user.
Based on the framework of the more subchains of main chain adduction row, but to external user be rendered as one it is single-stranded, realize it is transparent to user
Routing, the present invention devises four kinds of typical interaction scenarios, introduces its implementation process, and analyzes its security feature, these four
Scene is: 1) transferring accounts；2) contract is disposed；3) contract transaction is submitted；4) transaction/block inquiry.
It please refers to shown in Fig. 8, is transferred accounts for user and user terminal based on the framework of main chain adduction row subchain of the present invention
Process.Fig. 9 is the internal logic figure of money transfer transactions.Figure 10 is across chain request and responding process.Figure 11 is across chain money transfer transactions
Process.
Please referring to the process shown in Fig. 8, transferred accounts includes:
S1: user opens user terminal wallet, and user terminal wallet accesses direct interaction node, and user inputs in user terminal wallet and connects
Receive address destAddr and transfer amounts bill.
S2: user terminal wallet inquires the son of the source address srcAddr of active user to direct interaction node direct-connected therewith
The node link information of chain information and the subchain, and receive the subchain information of address destAddr.Wherein subchain information is subchain
id。
S3: the direct interaction node inquires local main chain information, and the source address srcAddr for obtaining active user is corresponding
The node link information of the subchain id and source subchain srcChain of source subchain srcChain are corresponding with address destAddr is received
Reception subchain destChain subchain id return wallet.
Whether S4: wallet X-ray source subchain srcChain and reception subchain destChain is same chain, if identical,
Direct money transfer transactions are then constructed, otherwise construct across chain money transfer transactions, and request user's signature.
User confirms Transaction Information and signs that wallet sends transaction and handles to user's subchain node.
S5: user's subchain node processing request.
It please refers to shown in Fig. 9, is the internal logic figure of user's subchain node processing money transfer transactions.At user's subchain node
The specific request of reason.
S5-1: user's subchain node receives the source address srcAddr to transfer accounts, receives address destAddr and transfer amounts
Bill, judges whether source address srcAddr is responsible for by current subchain.If it is not, then trading processing fails, the letter of failure is returned
Breath, is responsible for if it is by current subchain, and continuing judgement reception address destAddr whether there is, if it does not exist, then needing to create
Build a new account.
S5-1-1 increases account process newly:
Judge that intended recipient address destAddr whether there is in main chain data, if it does not exist, then distribution one
DestChain, user increase main chain transaction set (destaddr, destChain) newly, and the mapping relations of account and subchain are stored
In main chain data.
S5-2: judge source address srcAddr, receive whether address destAddr is responsible for by current subchain, if it is, directly
Row money transfer transactions are tapped into, if it is not, carrying out across chain money transfer transactions by across catenary system contract.
Wherein, direct money transfer transactions: for the prior art.
Wherein, across chain money transfer transactions are to be completed by across catenary system contract, please refer to shown in Figure 10, to ask across chain
The process asked/responded.The external interface of across catenary system contract is send method, its parameter source address srcAddr, target
Subchain destChain, address destAddr, payment amount bill and request message reqMsg are received.Have in across catenary system contract
There is an address across catenary system contract, which is the fixed value of a not no private key, which is fixed, public in code
It opens, as long as the address is correctly, to receive address and the amount of money is also correctly, to transfer accounts across chain exactly safe.
In figure, chain A is source subchain, and A node is user's subchain node, and chain B is to receive subchain, and B node is intended recipient section
Point, the transaction of each node by subchain where it carry out data submission, verifying, out block with it is synchronous etc., chain A node contains
The concept of node also contain where chain concept, text in and figure in simplify common recognition process, use a node as representative.
User pays across the catenary system contract of chain A first, and the source subchain A node where user receives request message details
After reqMsg, it can be put into local for across the chain request queue for receiving subchain destChain.After in source, subchain A goes out block, source
Chain A node can submit source chain A build information by main chain P2P network chain linked to owner, submit in the block also converged in information and own
Across the chain request notification information of transaction, such as the request [req, A- > B] of chain A directed chain B, but without request details.Each subchain
The transaction that chain linked to owner is submitted will form main chain block, and comprising across chain notification information therein, pass through main chain P2P Web broadcast to institute
There is node.
When reception subchain B node receives main chain block, discovery wherein has chain A to notify to the request of chain B, is just directly connected to chain A
Node, acquisition request details, and the Merkel of request prove (Merkle Proof) data.Chain B node is according to local main chain
The chain A build for including in information and Merkel prove the solicited message of (Merkle Proof) data verification chain A node, and verifying is used
After family is paid really, processing request pays destination address, generates across chain response detail information, be stored in and update across chain sound
Answer quene state.When chain B node submits build information by main chain P2P network chain linked to owner, across chain response notice letter can be submitted
Breath, such as the response of chain B directed chain A, but without response details.
When the submission of chain B is incorporated into main chain block and is synchronized to chain A node, chain A node is directly connected to chain B section
Point, obtains response details, and the Merkel including response proves (Merkle Proof) data.Chain A node is according to local main chain
The chain B build for including in information and Merkel prove the response of (Merkle Proof) data verification chain B node, are verified
Afterwards, request queue is updated, possible failure rollback is handled, if chain B payment failure, gives user's reimbursement, finally call and use
The call back function that family provides.
It please refers to shown in Figure 11, for the process of user's payment, user pays across the catenary system contract of chain A first, across
Catenary system contract implementation procedure be Fig. 8 described in process, reception chain A node by A build information and comprising across chain request notice believe
Breath is committed to main chain, and when main chain is synchronous, chain B has found across the chain request notification information of A, and chain B connection chain A, request request is in detail
Feelings, and the Merkle Proof data of request.Chain B node after being paid really using Merkle Proof verifying user, payment
Intended recipient address is given, generates across chain response notification information, chain B goes out block, and build information and across chain response notification information are mentioned
It hands over to main chain, when main chain is synchronous, chain A node connection chain B obtains response details, and request Merkle Proof data, chain A are received
To after response details, the same response for using Merkle Proof validation chain B, if chain B payment failure, gives user's reimbursement.
Above-mentioned about in the process transferred accounts, it appears that introduce some safety problems.In no introducing multichain technology,
User does not need to inquire any information and can construct offline transaction and sign, and does not need to trust wallet software and any node.
And in above-mentioned process, it appears that then need to trust wallet and direct interaction node, in fact, it's not necessary, separately below
The possibility that direct interaction node and wallet are done evil under analysis.
If directly interaction node be malice, it return to wallet information be it is wrong, such as srcAddr and
DestAddr be physically located in same subchain but return be that different subchains or srcAddr and destAddr are physically located in difference
Subchain but return be same subchain, in both cases, subchain information can be verified and refuse to hand over by handling the node transferred accounts all
Easily, agree to that most common recognitions will not be obtained transaction even if respective nodes.If the corresponding subchain node connection of the srcAddr returned
Information is wrong, and wallet may not connect, it is also possible to the transaction after signature is sent to error node, which can refuse to hand over
Easily, even if agreeing to, most common recognitions will not be obtained.In summary, as when no introducing multichain technology, user does not need letter
Appoint direct interaction node, if the node is malice, transferring accounts may be will fail, but the assets of user are safe.
In the scene of high security, wallet software does not have private key, it is only responsible for constructing wait sign transaction, logical wait sign transaction
It crosses offline mode and issues user, user signs in the environment of high safety, then that the transaction off-line after signature issued wallet is soft
Part, wallet software re-send to network.In this process, user does not need to trust wallet software, as long as it verifies transaction
It receives address and the amount of money is correctly.
In the case where multichain, needs to distinguish and directly transfer accounts and transfer accounts across chain.For directly transferring accounts, with single-stranded identical, use
Family, which need to only be verified, receives address and the amount of money.For transferring accounts across chain, destination address does not receive address, and across chain fund transfer system closes
How address about, user ensure the correctness of the address.Answer is the fixed value that the address is a not no private key, the ground
Location is fixed, disclosed in code, as long as the address is correctly, to receive address and the amount of money is also correctly, to turn across chain
Account is exactly safe.In summary, after introducing multichain technology, user does not need to trust wallet software yet, but needs to know across chain
The address of fund transfer system contract, this sacrifices certain transparency, but in most of everyday scenes, the private key of user generally by
Wallet management is to trust wallet, and at this moment multichain technology is exactly transparent to user.
It please refers to shown in Figure 12, for the process of deployment contract.Contract can be deployed in the subchain where its founder, main
It will record the mapping relations (and there are on subchain x by about A) of contract and subchain on chain.Contract can analyze the conjunction of its dependence when disposing
About, if relying on the contract of other subchains, deployment be will fail.
Detailed process are as follows: user's login user end wallet, user terminal wallet are connected to direct interaction node, user terminal wallet
Source address srcAddr is sent to the subchain position that direct interaction node inquires its account, it is right which returns to its
The corresponding subchain node link information of source subchain srcChain and source address srcAddr answered, and analysis contract dependence,
The content for whether relying on other subchain contracts returned.If user receives the content for not depending on other subchain contracts, user is true
Recognize signature, deployment subchain is completed, and then subchain is committed to main chain, and main chain increases the mapping relations of contract and contract and subchain newly, complete
Main chain is deployed at contract.If receiving the content for relying on other subchain contracts, dispose and fail, returns to the original of deployment failure
Cause.
It please refers to shown in Figure 13, for a kind of flow chart of submission contract transaction.User by transaction request [destAddr,
Req] it is committed to user terminal wallet, user terminal wallet sends inquiry source address scrAddr to its direct interaction node and receives ground
The request of subchain position where the request of subchain position where the destAddr of location and contract.Direct interaction node returns to corresponding source
Whether the corresponding subchain node link information of subchain srcChain, source address scrAddr receives subchain destChain and relies on
Other subchain contracts.If user belongs to some subchain, and contract also belongs to some subchain, if the two subchain phases
Together, user's subchain node can directly handle contract transaction.If belonging to different subchains, contract can be traded and be repaired by wallet
It is changed to across chain transaction, by above-mentioned across catenary system contract, finally by user's subchain node processing
In the present system, it please refers to shown in Figure 14, is the storage of node and subchain, also sets up two systems in main chain data and match
Set parameter, first is that minimum nodes number-min Nodes and it is another be maximum node number-max Nodes, the corresponding node of subchain
Number can just come into force not less than minimum nodes number-minNodes, and subchain number of nodes is no more than maximum node number-maxNodes.
Please refer to Figure 15, when register node, chain linked to owner system contract submits registration request, and system judges whether there is node
Otherwise subchain of the number less than maxNodes, just expands one if so, just node is assigned in the least subchain of number of nodes
The new subchain of item, but the subchain does not come into force also.If after Node registry, the number of nodes of corresponding subchain is not less than minNodes for the first time,
New subchain is then set to come into force.Subchain number and system capability are dynamic expansions in this programme, and participation node is more, and subchain is more,
System capability is also stronger.
It please refers to shown in Figure 16 and Figure 17, the mapping relations of account and subchain is stored on main chain, while being stored with every
The load of a subchain, the load of subchain are obtained according to user, contract, transaction, storage COMPREHENSIVE CALCULATING.The regular reconciliation of block node out
Family transaction is analyzed, and to each account, is analyzed the number of deals of transaction and other each subchain transaction in its chain, is obtained each
Subchain trading frequency.
The process of account distribution and migration are as follows:
S1: account is initially allocated in subchain most lightly loaded.
S2: going out block node and periodically analyze account trading, on dynamic migration to the most frequent subchain of interaction, specific mistake
Cheng Shi:
S2-1: to each account, the number of deals of transaction and other each subchain transaction in its chain is analyzed, each subchain is obtained and hands over
Easy frequency；
S2-2: judging whether to migrate, and migrates to which subchain；
S2-3: if necessary to migrate, submit account migration transaction, which includes two parts, first is that modification main chain on account with
The mapping relations of subchain, because being account of the same name, do not need account signature second is that transferring accounts across chain to target subchain account of the same name.
It is worth noting that, creating the account of contract cannot migrate, do not need to analyze, this is because if the portion account A
It has affixed one's name to and about C1 is migrated to chain X, A to chain Y, if disposing C2 again, and C2 relies on C1, then deployment will fail.
The node of other same subchain is migrated according to same proof of algorithm and is traded, and after verifying block, is submitted to main chain, main
Chain is synchronized to all nodes after going out block, modifies the mapping relations on main chain, and target subchain node creates an account, completes to transfer accounts.
Claims (4)
1. contract deployment and transaction based on the more subchains of block chain main chain adduction row, it is characterised in that: the main chain adduction row is more
Subchain framework includes a main chain and the parallel subchain of N item, wherein n=1 ... .X, wherein each node stores main chain data, the master
Chain data do not store particular transactions, and storage system global information, include at least across chain request/response notification information；Each section
Point is stored the total data of a subchain by system original allocation, and each node also includes across the chain message queue of subchain；It is described across
Chain request/response notification information corresponds to the notice of across chain request/response queue, is free of details；User passes through user terminal money
Packet software is interacted with some node, which is known as direct interaction node；One user belongs to and is pertaining only to a certain subchain, and one
A node possesses and only possesses the data of a subchain, and the request of a user can only be by possessing the node processing of its data, should
Node is known as user's subchain node；
User's login user end wallet, user terminal wallet are connected to direct interaction node, and source address is sent to by user terminal wallet
Direct interaction node inquires the subchain position of its account, which returns to its corresponding source subchain and source address pair
The subchain node link information answered, and analysis contract dependence, return to the content for whether relying on other subchain contracts；
If user receives the content for not depending on other subchain contracts, user confirms signature, contract is deployed to user's subchain
On node, then subchain is committed to main chain, and main chain increases the mapping relations of contract and contract and subchain newly, completes contract and is deployed to master
Chain；
The reason of if receiving the content for relying on other subchain contracts, disposing and fail, returning to deployment failure.
2. contract deployment and transaction based on the more subchains of block chain main chain adduction row as described in claim 1, it is characterised in that: use
Transaction request is committed to user terminal wallet software by family, and user terminal wallet software sends inquiry source address to its direct interaction node
With the request of the request and contract place subchain position that receive address place subchain position；
Direct interaction node returns to corresponding source subchain, the corresponding subchain node link information of source address, receive subchain and whether
Rely on other subchain contracts；
If user belongs to some subchain, and contract also belongs to some subchain, if the two subchains are identical, user's subchain
Node can directly handle contract transaction；
If belonging to different subchains, contract can be traded and be revised as across chain transaction by wallet, by across catenary system contract, finally
By user's subchain node processing.
3. contract deployment and transaction based on the more subchains of block chain main chain adduction row as claimed in claim 2, it is characterised in that: institute
State the workflow across catenary system contract are as follows:
Across the chain money transfer transactions are completed by across catenary system contract, and the external interface of across the catenary system contract is the side send
Method, its parameter source address, receive address, payment amount and/or request message, across the catenary system contract at target subchain
In there is an address across catenary system contract, which is the fixed value of a not no private key, which is fixed in code
, it is disclosed；
The workflow across catenary system contract are as follows:
User pays across the catenary system contract of source subchain first, and it is detailed that source subchain user's subchain node at place receives request message
After feelings, it can be put into local across the chain request queue for reception subchain, and after in source, subchain goes out block, source subchain node can pass through master
Chain P2P network chain linked to owner submits source chain build information, submits across the chain request of All Activity in the block also converged in information logical
Know information；The transaction that each subchain chain linked to owner is submitted will form main chain block, and comprising across chain notification information therein, pass through main chain
P2P Web broadcast is to all nodes；
When reception subchain destination node receives main chain block, wherein active subchain is notified to across the chain request for receiving subchain for discovery,
The Merkel for being just directly connected to source subchain node, acquisition request message details, and request proves data；Receive subchain destination node
The request letter of data verification user subchain node is proved according to the source subchain build and Merkel that include in local main chain information
Breath is verified after user pay really, and destination address is paid in processing request, generates across chain response detail information, deposit and more
Newly across chain response queue's state；When receiving subchain destination node by main chain P2P network chain linked to owner submission build information, can mention
Hand over across chain response notification information；
When the submission for receiving subchain is incorporated into main chain block and is synchronized to user's subchain node, user's subchain node is direct
Connection receives subchain destination node, obtains response details, and the Merkel including response demonstrate,proves data；User's subchain node is according to local
Main chain information in include reception subchain build and Merkel prove data verification chain destination node response, be verified
Afterwards, request queue is updated, possible failure rollback is handled, if receiving subchain payment failure, user's reimbursement is given, finally calls
The call back function that user provides.
4. contract deployment and transaction based on the more subchains of block chain main chain adduction row as claimed in claim 3, it is characterised in that:
When node returns to any transaction or block hash, subchain id value is embedded in hash, inquiry is from transaction hash and block
Source subchain id is parsed in hash and/or receives subchain id, and subchain node link information, the subchain are inquired according to subchain id
Node link information is stored in the back end of main chain data and the mapping relations of subchain.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811392134.7A CN109472572B (en) | 2018-11-21 | 2018-11-21 | Contract system based on block chain main chain and parallel multiple sub-chains |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811392134.7A CN109472572B (en) | 2018-11-21 | 2018-11-21 | Contract system based on block chain main chain and parallel multiple sub-chains |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109472572A true CN109472572A (en) | 2019-03-15 |
| CN109472572B CN109472572B (en) | 2021-08-03 |
Family
ID=65674247
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811392134.7A Active CN109472572B (en) | 2018-11-21 | 2018-11-21 | Contract system based on block chain main chain and parallel multiple sub-chains |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109472572B (en) |
Cited By (14)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110223178A (en) * | 2019-06-06 | 2019-09-10 | 杭州趣链科技有限公司 | It is a kind of for alliance's chain across catenary system and across chain method |
| CN110428332A (en) * | 2019-07-29 | 2019-11-08 | 杭州复杂美科技有限公司 | A kind of across the chain method of commerce of parallel chain, equipment and storage medium |
| CN111046437A (en) * | 2019-10-31 | 2020-04-21 | 中国科学院计算技术研究所 | Block chain parallel transaction processing method and system based on isomorphic multi-chain and terminal |
| CN111489156A (en) * | 2020-03-18 | 2020-08-04 | 平安国际智慧城市科技股份有限公司 | Transaction method based on block chain, electronic device and readable storage medium |
| CN111552573A (en) * | 2020-05-06 | 2020-08-18 | 行星算力(深圳)科技有限公司 | Block chain heterogeneous system and artificial intelligence computational power network |
| CN111597228A (en) * | 2020-05-13 | 2020-08-28 | 山大地纬软件股份有限公司 | Multi-chain system and method for improving block chain expansibility |
| CN111741114A (en) * | 2020-06-24 | 2020-10-02 | 陈鹏 | System, method and equipment capable of monitoring cross-chain interaction based on block chain |
| CN111769957A (en) * | 2020-09-02 | 2020-10-13 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain query method, device, equipment and storage medium |
| CN112054928A (en) * | 2020-09-02 | 2020-12-08 | 杭州复杂美科技有限公司 | Parallel chain node configuration method, equipment and storage medium |
| CN112633868A (en) * | 2019-10-08 | 2021-04-09 | 橙载(上海)信息技术有限公司 | Cross-chain asset transfer method based on intelligent contract implementation |
| CN113205424A (en) * | 2020-10-28 | 2021-08-03 | 支付宝(杭州)信息技术有限公司 | Method and apparatus for deploying and invoking contracts in blockchain |
| CN113393313A (en) * | 2021-08-17 | 2021-09-14 | 环球数科集团有限公司 | Writing mechanism for carrying out trusted deposit certificate on accounting tool for telecommunication value-added service |
| CN113822656A (en) * | 2021-11-23 | 2021-12-21 | 江苏荣泽信息科技股份有限公司 | Cross-chain cooperation method based on block chain technology |
| CN114866478A (en) * | 2022-04-26 | 2022-08-05 | 深圳大学 | 1.5-layer block chain and operation method, device and readable storage medium thereof |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107742210A (en) * | 2017-10-13 | 2018-02-27 | 布比（北京）网络技术有限公司 | Across the chain fund transfer system and method for a kind of different blocks interchain |
| CN108288158A (en) * | 2018-01-29 | 2018-07-17 | 张天 | A kind of storage method based on block chain technology, computer readable storage medium |
| US20180225640A1 (en) * | 2017-02-06 | 2018-08-09 | Northern Trust Corporation | Systems and methods for issuing and tracking digital tokens within distributed network nodes |
-
2018
- 2018-11-21 CN CN201811392134.7A patent/CN109472572B/en active Active
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20180225640A1 (en) * | 2017-02-06 | 2018-08-09 | Northern Trust Corporation | Systems and methods for issuing and tracking digital tokens within distributed network nodes |
| CN107742210A (en) * | 2017-10-13 | 2018-02-27 | 布比（北京）网络技术有限公司 | Across the chain fund transfer system and method for a kind of different blocks interchain |
| CN108288158A (en) * | 2018-01-29 | 2018-07-17 | 张天 | A kind of storage method based on block chain technology, computer readable storage medium |
Cited By (21)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110223178A (en) * | 2019-06-06 | 2019-09-10 | 杭州趣链科技有限公司 | It is a kind of for alliance's chain across catenary system and across chain method |
| CN110428332A (en) * | 2019-07-29 | 2019-11-08 | 杭州复杂美科技有限公司 | A kind of across the chain method of commerce of parallel chain, equipment and storage medium |
| CN112633868A (en) * | 2019-10-08 | 2021-04-09 | 橙载(上海)信息技术有限公司 | Cross-chain asset transfer method based on intelligent contract implementation |
| CN112633868B (en) * | 2019-10-08 | 2023-04-14 | 橙载(上海)信息技术有限公司 | Cross-chain asset transfer method based on intelligent contract implementation |
| CN111046437A (en) * | 2019-10-31 | 2020-04-21 | 中国科学院计算技术研究所 | Block chain parallel transaction processing method and system based on isomorphic multi-chain and terminal |
| CN111489156A (en) * | 2020-03-18 | 2020-08-04 | 平安国际智慧城市科技股份有限公司 | Transaction method based on block chain, electronic device and readable storage medium |
| CN111552573A (en) * | 2020-05-06 | 2020-08-18 | 行星算力(深圳)科技有限公司 | Block chain heterogeneous system and artificial intelligence computational power network |
| CN111552573B (en) * | 2020-05-06 | 2024-02-09 | 行星算力(深圳)科技有限公司 | Blockchain heterogeneous system and artificial intelligence power calculation network |
| CN111597228A (en) * | 2020-05-13 | 2020-08-28 | 山大地纬软件股份有限公司 | Multi-chain system and method for improving block chain expansibility |
| CN111741114A (en) * | 2020-06-24 | 2020-10-02 | 陈鹏 | System, method and equipment capable of monitoring cross-chain interaction based on block chain |
| CN111769957B (en) * | 2020-09-02 | 2020-12-15 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain query method, device, equipment and storage medium |
| CN112054928A (en) * | 2020-09-02 | 2020-12-08 | 杭州复杂美科技有限公司 | Parallel chain node configuration method, equipment and storage medium |
| CN112054928B (en) * | 2020-09-02 | 2022-06-24 | 杭州复杂美科技有限公司 | Parallel chain node configuration method, equipment and storage medium |
| CN111769957A (en) * | 2020-09-02 | 2020-10-13 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain query method, device, equipment and storage medium |
| CN113205424A (en) * | 2020-10-28 | 2021-08-03 | 支付宝(杭州)信息技术有限公司 | Method and apparatus for deploying and invoking contracts in blockchain |
| CN113205424B (en) * | 2020-10-28 | 2023-08-25 | 支付宝(杭州)信息技术有限公司 | Method and apparatus for deploying and invoking contracts in blockchain |
| CN113393313A (en) * | 2021-08-17 | 2021-09-14 | 环球数科集团有限公司 | Writing mechanism for carrying out trusted deposit certificate on accounting tool for telecommunication value-added service |
| CN113822656A (en) * | 2021-11-23 | 2021-12-21 | 江苏荣泽信息科技股份有限公司 | Cross-chain cooperation method based on block chain technology |
| CN113822656B (en) * | 2021-11-23 | 2022-02-11 | 江苏荣泽信息科技股份有限公司 | Cross-chain cooperation method based on block chain technology |
| CN114866478A (en) * | 2022-04-26 | 2022-08-05 | 深圳大学 | 1.5-layer block chain and operation method, device and readable storage medium thereof |
| CN114866478B (en) * | 2022-04-26 | 2024-01-05 | 深圳大学 | 1.5-layer blockchain, and operation method, device and readable storage medium thereof |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109472572B (en) | 2021-08-03 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN109493050A (en) | Transfer process based on the more subchains of block chain main chain adduction row | |
| CN109472572A (en) | Contract deployment and transaction based on the more subchains of block chain main chain adduction row | |
| CN109286685A (en) | The system architecture of the more subchains of main chain adduction row of subchain can be expanded | |
| CN109493052A (en) | Across catenary system contract and its transfer process based on the more subchains of main chain adduction row | |
| CN109471744A (en) | The more subchain system architectures of main chain adduction row based on block chain | |
| US20190354518A1 (en) | Chain mesh network for decentralized transaction systems | |
| CN110266655A (en) | A kind of across chain interconnected method, equipment and system based on block chain | |
| CN112132447A (en) | Calculation power network trust evaluation and guarantee algorithm based on block chain | |
| CN109493051A (en) | The more subchain system architectures of main chain adduction row of account distribution and migration can dynamically be carried out | |
| CN109118214A (en) | The method and apparatus for running intelligent contract | |
| EP4318362A1 (en) | Blockchain-based data processing method, apparatus and device, and storage medium | |
| CN108009811A (en) | Inter-cloud computing environment value exchange-oriented cross-chain communication method | |
| CN111681003A (en) | Resource cross-chain transfer method and device, computer equipment and storage medium | |
| CN110084594A (en) | A kind of block chain method of commerce and device by lightning network | |
| CN109636610A (en) | A kind of data transacting system and method for decentralization | |
| CN114567643B (en) | Cross-blockchain data transfer method, device and related equipment | |
| Guan et al. | Blockchain: A distributed solution to UAV‐enabled mobile edge computing | |
| CN110400217A (en) | The regular changing process method and device of intelligent contract | |
| CN111507851A (en) | Block chain-based medical insurance claim settlement processing method, device and system and storage medium | |
| Lin et al. | A Blockchain-enabled decentralized settlement model for IoT data exchange services | |
| Garriga et al. | Blockchain and cryptocurrency: A comparative framework of the main architectural drivers | |
| Hoepman | Distributed double spending prevention | |
| Lee et al. | Blockchain-based perfect sharing project platform based on the proof of atomicity consensus algorithm | |
| Bu et al. | Cross hyperledger fabric transactions | |
| Zhu et al. | A study on the challenges and solutions of blockchain interoperability |
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 |