CN109493050A - Transfer process based on the more subchains of block chain main chain adduction row - Google Patents
Transfer process based on the more subchains of block chain main chain adduction row Download PDFInfo
- Publication number
- CN109493050A CN109493050A CN201811392139.XA CN201811392139A CN109493050A CN 109493050 A CN109493050 A CN 109493050A CN 201811392139 A CN201811392139 A CN 201811392139A CN 109493050 A CN109493050 A CN 109493050A
- Authority
- CN
- China
- Prior art keywords
- subchain
- chain
- node
- main chain
- user
- 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/38—Payment protocols; Details thereof
- G06Q20/382—Payment protocols; Details thereof insuring higher security of transaction
- G06Q20/3829—Payment protocols; Details thereof insuring higher security of transaction involving key management
Landscapes
- Business, Economics & Management (AREA)
- Engineering & Computer Science (AREA)
- Accounting & Taxation (AREA)
- Computer Security & Cryptography (AREA)
- Finance (AREA)
- Strategic Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Theoretical Computer Science (AREA)
- Financial Or Insurance-Related Operations Such As Payment And Settlement (AREA)
Abstract
The present invention provides a kind of transfer process based on the more subchains of block chain main chain adduction row, the more subchain frameworks of main chain adduction row include a main chain and the parallel subchain of N item, wherein each node stores main chain data, the main chain data do not store particular transactions, and storage system global information, user opens user terminal wallet, user terminal wallet accesses the node link information subchain information for receiving subchain corresponding with address is received of the subchain information and source subchain of the corresponding source subchain of source address of direct interaction node acquisition active user, returns to wallet；Whether wallet X-ray source subchain and reception subchain are same chains, if identical, construct direct money transfer transactions, otherwise across chain money transfer transactions are constructed, and user's signature is requested, user confirms Transaction Information and signs that wallet sends transaction and handles to user's subchain node；Finally by user's subchain node processing transfer request.
Description
Technical field
The present invention relates to the scalability schemes of block chain.
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.
The present invention provides a kind of transfer process based on the more subchains of block chain main chain adduction row, and how sub the main chain adduction row is
Chain framework includes a main chain and the parallel subchain of N item, wherein n=1 ... .X, wherein each node stores main chain data, the main chain
Data do not store particular transactions, and storage system global information, include at least: the mapping relations of account and subchain, data section
Mapping relations and across chain request/response notification information of the point with subchain；Each node stores a subchain by system original allocation
Total data, each node also includes across the chain message queue of subchain；Across the chain request/response notification information correspond to across
The notice of chain request/response queue is free of details；User is interacted by user terminal wallet software with some node, which claims
For direct interaction node；One user belongs to and is pertaining only to a certain subchain, and a node possesses and only possesses a subchain
Data, the request of user can only be by possessing the node processing of its data, which is known as user's subchain node；Based on above-mentioned
User's transfer process of framework are as follows:
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 and transfer amounts；
S2: user terminal wallet inquires the subchain information of the source address of active user to direct interaction node direct-connected therewith, and should
The node link information of subchain, and receive the subchain information of address；
S3: the direct interaction node inquires local main chain data, obtains the son of the corresponding source subchain of source address of active user
The node link information of the chain information and source subchain subchain information for receiving subchain corresponding with address is received, returns to wallet；
S4: whether wallet X-ray source subchain is same chain with reception subchain, if identical, constructs direct money transfer transactions, no
Across chain money transfer transactions are then constructed, and request user's signature, user confirms Transaction Information and signs, and wallet sends transaction and gives user's
Chain link point is handled；
S5: user's subchain node processing transfer request.
Wherein, the process that user's subchain node processing is transferred accounts is:
S5-1: whether user's subchain node receives the source address transferred accounts, receives address and transfer amounts, judge source address by current
Subchain is responsible for, if it is not, then trading processing fails, returns to the information of failure；If it is, carrying out in next step；
S5-2: judging source address, receive whether address is responsible for by current subchain, if it is, money transfer transactions are directly carried out, if
It is not that will carry out across chain money transfer transactions.
Wherein, before user's subchain node is traded, to judge that receiving address whether there is, if it does not exist, then needing
A new account is created, the newly-increased account process are as follows:
Judge that intended recipient address whether there is in main chain data, if it does not exist, then distributing a subchain for it, uses simultaneously
Family increases main chain transaction set (destaddr, destChain) newly, and the mapping relations of account and subchain are stored in main chain data
In.
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
Address about, which is fixed, disclosed in code, as long as the address is correctly, to receive address and the amount of money is also
Correctly, it transfers accounts across chain exactly safe.In summary, after introducing multichain technology, user does not need to trust wallet software yet, but
It needs to know the address of across chain fund transfer system contract, although sacrificing certain transparency, in most of everyday scenes, uses
The private key at family is to trust wallet, at this moment multichain technology is exactly transparent to user generally by wallet management.
System structure of the invention also has a characteristic that
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 subchains
SPV client can verify the request/response of any subchain by Merkle Proof, be directly connected to without trust
Subchain node.
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, submits to master with subchain build
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, knows together at one
In period, only one node of each subchain submits transaction to arrive main chain, and transaction content is main chain modification, subchain build and summarizes
Across chain notification information, 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 user's subchain node processing 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 is believed to the subchain of the source address srcAddr of direct interaction node inquiry active user direct-connected therewith
The node link information of breath 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, obtains corresponding source of source address srcAddr of active user
The node link information of the subchain id and source subchain srcChain of chain srcChain with receive that address destAddr is corresponding connects
The subchain id for receiving subchain destChain returns to wallet；
Whether S4: wallet X-ray source subchain srcChain and reception subchain destChain is same chain, if identical, structure
Direct money transfer transactions are made, otherwise construct across chain money transfer transactions, and request user's signature；User's confirmation Transaction Information is simultaneously signed, money
Packet 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, returns to the letter of failure
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 should increase account process newly: judge that intended recipient address destAddr whether there is in main chain data, such as
Fruit is not present, then distributes a destChain, user increases main chain transaction set (destaddr, destChain) newly, by account
It is stored in main chain data with the mapping relations of subchain.
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, and 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 setting up two in main chain data is
Unite configuration parameter, first is that minimum nodes number-min Nodes and it is another be maximum node number-max Nodes, the corresponding section of subchain
Point number can just come into force not less than minimum nodes number-min Nodes, and subchain number of nodes is no more than maximum node number-max
Nodes。
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 max Nodes, 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 min Nodes 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, detailed process
It is:
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 (9)
1. the transfer process based on the more subchains of block chain main chain adduction row, it is characterised in that: the more subchain framves of main chain adduction row
Structure includes a main chain and the parallel subchain of N item, wherein n=1 ... .X, wherein each node stores main chain data, the main chain data
Do not store particular transactions, and storage system global information, include at least: the mapping relations of account and subchain, back end with
The mapping relations of subchain and across chain request/response notification information；Each node stores the complete of a subchain by system original allocation
Portion's data, each node also include across the chain message queue of subchain；Across the chain request/response notification information corresponds to ask across chain
/ the notice of response queue is sought, details are free of；User is interacted by user terminal wallet software with some node, and the node is referred to as straight
Connect interaction node；One user belongs to and is pertaining only to a certain subchain, and a node possesses and only possess the data of a subchain,
The request of one user can only be by possessing the node processing of its data, which is known as user's subchain node；Based on above-mentioned framework
User's transfer process are as follows:
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 and transfer amounts；
S2: user terminal wallet inquires the subchain information of the source address of active user to direct interaction node direct-connected therewith, and should
The node link information of subchain, and receive the subchain information of address；
S3: the direct interaction node inquires local main chain data, obtains the son of the corresponding source subchain of source address of active user
The node link information of the chain information and source subchain subchain information for receiving subchain corresponding with address is received, returns to wallet；
S4: whether wallet X-ray source subchain is same chain with reception subchain, if identical, constructs direct money transfer transactions, no
Across chain money transfer transactions are then constructed, and request user's signature, user confirms Transaction Information and signs, and wallet sends transaction and gives user's
Chain link point is handled；
S5: user's subchain node processing transfer request.
2. the transfer process as described in claim 1 based on the more subchains of block chain main chain adduction row, it is characterised in that: the use
The process that family subchain node processing is transferred accounts is:
S5-1: whether user's subchain node receives the source address transferred accounts, receives address and transfer amounts, judge source address by current
Subchain is responsible for, if it is not, then trading processing fails, returns to the information of failure；If it is, carrying out in next step；
S5-2: judging source address, receive whether address is responsible for by current subchain, if it is, money transfer transactions are directly carried out, if
It is not that will carry out across chain money transfer transactions.
3. the transfer process as claimed in claim 2 based on the more subchains of block chain main chain adduction row, it is characterised in that: Yong Huzi
Before chain link point is traded, to judge that receiving address whether there is, if it does not exist, then need to create a new account, it should
Newly-increased account process are as follows: judge that intended recipient address whether there is in main chain data, if it does not exist, then distributing one for it
Subchain, while user increases main chain transaction set (destaddr, destChain) newly, and the mapping relations of account and subchain are stored
In main chain data.
4. the transfer process as claimed in claim 2 or claim 3 based on the more subchains of block chain main chain adduction row, it is characterised in that: institute
Across chain money transfer transactions to be stated to complete by across catenary system contract, the external interface of across the catenary system contract is send method, it
Parameter source address, target subchain receive address, payment amount and/or request message, have one in across the catenary system contract
Address across catenary system contract, the address are the fixed values of a not no private key, which is fixed, openly in code
's；
The workflow across catenary system contract are as follows: user pays across the catenary system contract of source subchain, the source at place first
After subchain user's subchain node receives request message details, it can be put into local across the chain request queue for reception subchain,
After source subchain goes out block, source subchain node can propose source interlinkage build information by main chain P2P network chain linked to owner, submit in information also
Across the chain request notification information of All Activity in the block of convergence；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 to all nodes；Master is received when receiving subchain destination node
When chain block, wherein active subchain is just directly connected to source subchain node, acquisition request to across the chain request notice for receiving subchain for discovery
Message details, and the Merkel of request prove data；Subchain destination node is received according to the source for including in local main chain information
Subchain build and Merkel prove the solicited message of data verification user subchain node, verify after user pay really, handle
Destination address is paid in request, is generated across chain response detail information, is stored in and updates across chain response queue's state；Receiving son
When chain destination node submits build information by main chain P2P network chain linked to owner, across chain response notification information can be submitted；It is sub when receiving
When the submission of chain is incorporated into main chain block and is synchronized to user's subchain node, user's subchain node is directly connected to receive subchain
Destination node, obtains response details, and the Merkel including response demonstrate,proves data；User's subchain node is according in local main chain information
The reception subchain build for including and Merkel prove the response of data verification chain destination node, after being verified, update request team
Column handle possible failure rollback if receiving subchain pays failure and give user's reimbursement, time for finally calling user to provide
Letter of transfer number.
5. the transfer process as claimed in claim 4 based on the more subchains of block chain main chain adduction row, it is characterised in that: the son
The total data of chain includes account, contract and the transaction of corresponding subchain；The main chain data include at least: subchain number, subchain
Build, the mapping relations of account and subchain, contract and the mapping relations of subchain, the mapping relations of back end and subchain, verifying
The mapping relations of node and subchain, all contract codes and subchain load.
6. the transfer process based on the more subchains of block chain main chain adduction row as described in any claim in claim 1 to 5,
It is characterized by: two systems configuration parameter is arranged in the main chain data, first is that minimum nodes number min Nodes, another is most
Big number of nodes max Nodes, the corresponding node number of subchain can just come into force not less than minimum nodes number, and subchain number of nodes is no more than
Maximum node number, the status data also whether to come into force comprising subchain in main chain data；When register node, chain linked to owner system contract is mentioned
Registration request is handed over, system judges whether there is the subchain that number of nodes is less than max Nodes, if so, node is just assigned to section
It counts in least subchain, otherwise, just expands a new subchain, but the subchain does not come into force also；If corresponding after Node registry
The number of nodes of subchain is not less than min Nodes for the first time, then new subchain is made to come into force.
7. the transfer process based on the more subchains of block chain main chain adduction row as described in any claim in claim 1 to 5,
It is characterized by: this system also includes account distribution and migration, the process of the account distribution and migration are as follows:
S1: account is initially allocated in subchain most lightly loaded；
S2: go out block node and periodically account trading is analyzed, on dynamic migration to the most frequent subchain of interaction, created contract
Account cannot migrate, do not need to analyze, detailed process is:
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；
The node of other same subchain is migrated according to same proof of algorithm and is traded, and after verifying block, main chain is submitted to, after main chain goes out block
All nodes are synchronized to, the mapping relations on main chain are modified.
8. the transfer process as claimed in claim 6 based on the more subchains of block chain main chain adduction row, it is characterised in that: this system
Also distributes and migrate comprising account, the process of the account distribution and migration are as follows:
S1: account is initially allocated in subchain most lightly loaded；
S2: go out block node and periodically account trading is analyzed, on dynamic migration to the most frequent subchain of interaction, created contract
Account cannot migrate, do not need to analyze, detailed process is:
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；
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 goes out
It is synchronized to all nodes after block, modifies the mapping relations on main chain.
9. the stream of transferring accounts based on the more subchains of block chain main chain adduction row as described in any claim in claim 1-5 or 8
Journey, it is characterised in that: node returns to any transaction or when block hash, is embedded in subchain id value in hash, inquiry be from
Source subchain id is parsed in transaction hash and block hash and/or receives subchain id, and subchain node is inquired according to subchain id and is connected
Information is connect, which 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 |
|---|---|---|---|
| CN201811392139.XA CN109493050B (en) | 2018-11-21 | 2018-11-21 | Transfer method based on block chain main chain and parallel multiple sub-chains |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201811392139.XA CN109493050B (en) | 2018-11-21 | 2018-11-21 | Transfer method based on block chain main chain and parallel multiple sub-chains |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN109493050A true CN109493050A (en) | 2019-03-19 |
| CN109493050B CN109493050B (en) | 2021-08-03 |
Family
ID=65697231
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201811392139.XA Active CN109493050B (en) | 2018-11-21 | 2018-11-21 | Transfer method based on block chain main chain and parallel multiple sub-chains |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN109493050B (en) |
Cited By (20)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110336853A (en) * | 2019-05-08 | 2019-10-15 | 重庆天蓬网络有限公司 | A kind of block chain horizontal extension solution of big data quantity |
| CN110874798A (en) * | 2019-10-30 | 2020-03-10 | 链农(深圳)信息科技有限公司 | Network platform based on regional chain and safe communication method thereof |
| CN110928953A (en) * | 2019-12-03 | 2020-03-27 | 上海墨珩网络科技有限公司 | Data synchronization method and system based on block chain technology |
| CN111127190A (en) * | 2019-12-25 | 2020-05-08 | 上海优扬新媒信息技术有限公司 | Block chain based installment loan processing system |
| CN111401895A (en) * | 2020-03-11 | 2020-07-10 | 北京价值互联科技有限公司 | Decentralized chain-crossing transfer-in and transfer-out method and system |
| 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 |
| CN112184433A (en) * | 2020-08-31 | 2021-01-05 | 武汉市果壳璐网络科技有限公司 | Block chain system |
| CN112269838A (en) * | 2020-11-18 | 2021-01-26 | 网易（杭州）网络有限公司 | Block chain-based supervision method and device, electronic equipment and storage medium |
| CN112669159A (en) * | 2021-01-11 | 2021-04-16 | 上海能链众合科技有限公司 | Trust-based value circulation method in different block chain systems |
| CN112801661A (en) * | 2021-02-02 | 2021-05-14 | 深圳前海益链网络科技有限公司 | Block chain cross-chain rule management method and system |
| CN113052607A (en) * | 2021-03-31 | 2021-06-29 | 山大地纬软件股份有限公司 | Multi-chain management method and system based on collaboration chain and work chain decoupling |
| CN113065956A (en) * | 2020-12-29 | 2021-07-02 | 上海能链众合科技有限公司 | Block chain cross-chain asset transfer method |
| CN113177092A (en) * | 2021-05-21 | 2021-07-27 | 中船黄埔文冲船舶有限公司 | Ship manufacturing inspection data sharing method, alliance chain and system |
| CN113421097A (en) * | 2021-08-23 | 2021-09-21 | 腾讯科技（深圳）有限公司 | Data processing method and device, computer equipment and storage medium |
| CN113537991A (en) * | 2021-09-16 | 2021-10-22 | 中国信息通信研究院 | Cross-chain transaction ordered execution method and cross-chain system |
| CN113592644A (en) * | 2021-07-02 | 2021-11-02 | 中国人民银行数字货币研究所 | Transaction method and device based on block chain UTXO model |
| CN114154982A (en) * | 2021-08-16 | 2022-03-08 | 北京天德科技有限公司 | Real-time settlement and supervision method based on block chain and big data platform |
| CN115796868A (en) * | 2022-11-22 | 2023-03-14 | 紫绶(上海)信息科技有限公司 | Method for realizing multi-block chain simultaneous casting launch and multi-chain NFT application |
| CN116012164A (en) * | 2023-03-17 | 2023-04-25 | 安徽中科晶格技术有限公司 | Block chain cross-fragment transaction method based on virtual account |
Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9875510B1 (en) * | 2015-02-03 | 2018-01-23 | Lance Kasper | Consensus system for tracking peer-to-peer digital records |
| CN108009811A (en) * | 2017-11-30 | 2018-05-08 | 中国人民解放军国防科技大学 | Inter-cloud computing environment value exchange-oriented cross-chain communication method |
| CN108399572A (en) * | 2018-03-22 | 2018-08-14 | 深圳市网心科技有限公司 | block chain transaction processing method, device and storage medium |
| CN108765129A (en) * | 2018-05-17 | 2018-11-06 | 北京众享比特科技有限公司 | Traditional bank assets distribution based on block chain and system for settling account and method |
| CN108805704A (en) * | 2018-05-16 | 2018-11-13 | 深圳市网心科技有限公司 | Block chain service implementation method, audiomonitor, storage medium and system |
-
2018
- 2018-11-21 CN CN201811392139.XA patent/CN109493050B/en active Active
Patent Citations (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US9875510B1 (en) * | 2015-02-03 | 2018-01-23 | Lance Kasper | Consensus system for tracking peer-to-peer digital records |
| CN108009811A (en) * | 2017-11-30 | 2018-05-08 | 中国人民解放军国防科技大学 | Inter-cloud computing environment value exchange-oriented cross-chain communication method |
| CN108399572A (en) * | 2018-03-22 | 2018-08-14 | 深圳市网心科技有限公司 | block chain transaction processing method, device and storage medium |
| CN108805704A (en) * | 2018-05-16 | 2018-11-13 | 深圳市网心科技有限公司 | Block chain service implementation method, audiomonitor, storage medium and system |
| CN108765129A (en) * | 2018-05-17 | 2018-11-06 | 北京众享比特科技有限公司 | Traditional bank assets distribution based on block chain and system for settling account and method |
Cited By (26)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN110336853A (en) * | 2019-05-08 | 2019-10-15 | 重庆天蓬网络有限公司 | A kind of block chain horizontal extension solution of big data quantity |
| CN110874798A (en) * | 2019-10-30 | 2020-03-10 | 链农(深圳)信息科技有限公司 | Network platform based on regional chain and safe communication method thereof |
| CN110928953A (en) * | 2019-12-03 | 2020-03-27 | 上海墨珩网络科技有限公司 | Data synchronization method and system based on block chain technology |
| CN111127190A (en) * | 2019-12-25 | 2020-05-08 | 上海优扬新媒信息技术有限公司 | Block chain based installment loan processing system |
| CN111401895A (en) * | 2020-03-11 | 2020-07-10 | 北京价值互联科技有限公司 | Decentralized chain-crossing transfer-in and transfer-out method and system |
| CN111741114A (en) * | 2020-06-24 | 2020-10-02 | 陈鹏 | System, method and equipment capable of monitoring cross-chain interaction based on block chain |
| CN112184433A (en) * | 2020-08-31 | 2021-01-05 | 武汉市果壳璐网络科技有限公司 | Block chain system |
| CN111769957A (en) * | 2020-09-02 | 2020-10-13 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain query method, device, equipment and storage medium |
| CN111769957B (en) * | 2020-09-02 | 2020-12-15 | 百度在线网络技术（北京）有限公司 | Block chain cross-chain query method, device, equipment and storage medium |
| CN112269838A (en) * | 2020-11-18 | 2021-01-26 | 网易（杭州）网络有限公司 | Block chain-based supervision method and device, electronic equipment and storage medium |
| CN112269838B (en) * | 2020-11-18 | 2023-07-25 | 网易（杭州）网络有限公司 | Blockchain-based supervision method and device, electronic equipment and storage medium |
| CN113065956A (en) * | 2020-12-29 | 2021-07-02 | 上海能链众合科技有限公司 | Block chain cross-chain asset transfer method |
| CN112669159A (en) * | 2021-01-11 | 2021-04-16 | 上海能链众合科技有限公司 | Trust-based value circulation method in different block chain systems |
| CN112801661A (en) * | 2021-02-02 | 2021-05-14 | 深圳前海益链网络科技有限公司 | Block chain cross-chain rule management method and system |
| CN112801661B (en) * | 2021-02-02 | 2023-06-30 | 深圳前海益链网络科技有限公司 | Block chain cross-chain rule management method and system |
| CN113052607A (en) * | 2021-03-31 | 2021-06-29 | 山大地纬软件股份有限公司 | Multi-chain management method and system based on collaboration chain and work chain decoupling |
| CN113177092B (en) * | 2021-05-21 | 2023-07-25 | 中船黄埔文冲船舶有限公司 | Sharing method, alliance chain and system for ship manufacturing inspection data |
| CN113177092A (en) * | 2021-05-21 | 2021-07-27 | 中船黄埔文冲船舶有限公司 | Ship manufacturing inspection data sharing method, alliance chain and system |
| CN113592644A (en) * | 2021-07-02 | 2021-11-02 | 中国人民银行数字货币研究所 | Transaction method and device based on block chain UTXO model |
| CN114154982A (en) * | 2021-08-16 | 2022-03-08 | 北京天德科技有限公司 | Real-time settlement and supervision method based on block chain and big data platform |
| CN114154982B (en) * | 2021-08-16 | 2022-07-01 | 北京天德科技有限公司 | Real-time settlement and supervision method based on block chain and big data platform |
| CN113421097A (en) * | 2021-08-23 | 2021-09-21 | 腾讯科技（深圳）有限公司 | Data processing method and device, computer equipment and storage medium |
| CN113537991A (en) * | 2021-09-16 | 2021-10-22 | 中国信息通信研究院 | Cross-chain transaction ordered execution method and cross-chain system |
| CN115796868A (en) * | 2022-11-22 | 2023-03-14 | 紫绶(上海)信息科技有限公司 | Method for realizing multi-block chain simultaneous casting launch and multi-chain NFT application |
| CN116012164A (en) * | 2023-03-17 | 2023-04-25 | 安徽中科晶格技术有限公司 | Block chain cross-fragment transaction method based on virtual account |
| CN116012164B (en) * | 2023-03-17 | 2023-06-30 | 安徽中科晶格技术有限公司 | Block chain cross-fragment transaction method based on virtual account |
Also Published As
| Publication number | Publication date |
|---|---|
| CN109493050B (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 | |
| 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 | |
| CN101102257B (en) | Method and device for transmitting data objects | |
| CN108650182A (en) | Network communication method, system, device, equipment and storage medium | |
| CN108009811A (en) | Inter-cloud computing environment value exchange-oriented cross-chain communication method | |
| EP4318362A1 (en) | Blockchain-based data processing method, apparatus and device, and storage medium | |
| CN107291862A (en) | Business datum storage method, device, storage medium and electronic equipment | |
| CN108769150A (en) | Data processing method, device, clustered node and the storage medium of block chain network | |
| CN110084594A (en) | A kind of block chain method of commerce and device by lightning network | |
| CN114567643B (en) | Cross-blockchain data transfer method, device and related equipment | |
| Chakrabarti et al. | A blockchain based incentive scheme for post disaster opportunistic communication over DTN | |
| Lin et al. | A Blockchain-enabled decentralized settlement model for IoT data exchange services | |
| CN109166040A (en) | Transaction auditing method, device, equipment and storage medium based on block chain | |
| CN111507851A (en) | Block chain-based medical insurance claim settlement processing method, device and system and storage medium | |
| CN1595890B (en) | Virtual connectivity with subscribe-notify service | |
| Hoepman | Distributed double spending prevention | |
| Zhu et al. | A study on the challenges and solutions of blockchain interoperability | |
| Bu et al. | Cross hyperledger fabric transactions | |
| CN116567631B (en) | Mobile terminal security authentication method based on segmented block chain | |
| CN108833110A (en) | Digital asset processing method and processing device |
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 |