CN107945017B - Hybrid chain accounting method based on multi-stage verification - Google Patents
Hybrid chain accounting method based on multi-stage verification Download PDFInfo
- Publication number
- CN107945017B CN107945017B CN201711139660.8A CN201711139660A CN107945017B CN 107945017 B CN107945017 B CN 107945017B CN 201711139660 A CN201711139660 A CN 201711139660A CN 107945017 B CN107945017 B CN 107945017B
- Authority
- CN
- China
- Prior art keywords
- domain
- accounting
- verification
- account
- node
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q40/00—Finance; Insurance; Tax strategies; Processing of corporate or income taxes
- G06Q40/04—Trading; Exchange, e.g. stocks, commodities, derivatives or currency exchange
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q20/00—Payment architectures, schemes or protocols
- G06Q20/38—Payment protocols; Details thereof
- G06Q20/40—Authorisation, e.g. identification of payer or payee, verification of customer or shop credentials; Review and approval of payers, e.g. check credit lines or negative lists
- G06Q20/401—Transaction verification
Abstract
The invention discloses a hybrid chain accounting method based on multi-level verification, which comprises the steps of establishing a multi-layer domain with a tree structure, and adding an accounting node with an accounting right to any bottom layer domain according to a consensus mechanism; and then initiating a transfer transaction request, if the account transfer party account is in an accounting node of the bottommost layer domain, broadcasting a transaction information verification request to the bottommost layer domain and an upper layer domain to which the accounting node belongs, performing accounting after receiving the verification information, and synchronizing a transaction account book to the bottommost layer domain and the upper layer domain to which the accounting node belongs. The account book is dispersed in each bottommost domain, the accounting nodes participate in the domain where the account of the account transfer party on the bottommost layer is located, and other related domains and upper domains only participate in the synchronous account book, so that the efficiency of synchronizing the account book is improved; meanwhile, the upper layer domain can participate in the verification of the account book of the lower layer domain, and the accounting safety of the block chain is improved.
Description
Technical Field
The invention relates to the technical field of block chains, in particular to a hybrid chain accounting method based on multi-level verification.
Background
The existing block chain is a system which can carry out transaction or data safe storage and verification without any central mechanism; the Data is a volatile, volatile and heterogeneous substance, and the substance is a way for describing objective physical worlds such as logistics packages, automobile parts, financial currencies and the like, which causes 2-time accounting difficulties of a block chain, namely the Data block chain is used for recording Data which records physical world entities. With full decentralized management, data is difficult to correlate with real-world assets.
The existing blockchain is a shared distributed accounting system. The transaction is stored in a global ledger, with mathematical algorithms to ensure transaction records. Without a central supervisor, the participating objects, the user identities and the transaction conditions are difficult to completely verify, and the accounting data with public confidence cannot be realized.
The records of the account book can be recorded by adopting a hierarchical structure, however, in the existing hierarchical structure, the records of the upper layer domain are usually a region summary of the lower layer domain, in the hierarchical structure, the upper layer domain only has the function of simple aggregation, and the lowest layer domain only is equivalent to the fact that the accounts are dispersed into different bottom layers according to a certain rule, so that the efficiency of the records of the account book and the safety of the accounts in a block chain are reduced; meanwhile, the uppermost domain records all the accounts, which results in low operating efficiency of the uppermost domain.
Disclosure of Invention
Based on this, in order to solve the above problems, it is necessary to provide a hybrid chain accounting method based on multi-level verification, in which the accounts are dispersed in each bottommost domain, accounting nodes participate in the domain where the account of the account roll-out party on the bottommost layer is located, and other related domains and upper domains only participate in synchronizing the accounts, so that the efficiency of account book synchronization is improved; meanwhile, the upper layer domain can participate in the verification of the lower layer domain account book, and the accounting safety of the block chain is improved.
The technical scheme of the invention is as follows:
a hybrid chain accounting method based on multi-stage verification comprises the following steps:
a. establishing a multi-layer domain with a tree structure, and adding a billing node with a billing right to any bottom layer domain according to a consensus mechanism;
b. initiating a transfer transaction request, judging whether the account of the account transfer party is in an accounting node of the bottommost layer domain, if so, entering the step c; if not, rejecting the transfer transaction request;
c. d, broadcasting a transaction information verification request to the lowest layer domain and the upper layer domain to which the accounting node belongs, judging whether verification confirmation information is received, if so, successfully verifying, and entering the step d; if not, the verification fails and the transfer transaction request is rejected;
d. and carrying out accounting, and synchronously trading the account book to the bottommost layer domain where the accounting node is located and the upper layer domain.
The block chain structure is a hierarchical structure model, each layer is a netlike intercommunicated grape vine structure, nodes of different levels contained in each layer are called a domain, in the bottommost layer domain, a full account book is dispersed into each bottommost layer domain, the upper layer domain is a larger account book formed by upward transmission of the lower layer domain, and the topmost layer domain has account books of all accounts; the invention also adopts a wheel disc mode to confirm the addition of the effective block, and the specific confirmation mode is as follows:
accounting nodes participate in the domain where the lowest-layer accounting transfer party account is located, blocks are generated by the accounting nodes, each lowest-layer domain has a unique accounting node at the same time, an accounting node (the time is defined as bastion time) is generated again every 326 seconds, and the generation of new accounting nodes is generated according to the last accounting behavior parameter and a certain random rule, so that a node target cannot be found and attacked in the time range; other related domains and upper-layer domains only participate in the synchronous account book, so that the efficiency of account book synchronization is improved; meanwhile, the upper layer domain is the union of accounts of all the lower layer domains, and can participate in the verification of the accounts of the lower layer domains, so that the accounting safety of the block chain is improved.
As a further optimization of the above scheme, in the step a, the adding step of the accounting node specifically includes:
a1, voting by a consensus mechanism, after the voting result is determined and the voting result is effective, all nodes of the upper domain add the address, the public key and the domain parameter of the added accounting node into a node list, and initiate handshake request information to the accounting node;
a2, after the accounting node is online and connected with the network, acquiring the latest upper domain list, broadcasting the latest upper domain list to all upper domains, and replying handshake confirmation information to the nodes of all upper domains;
a3, after confirming and recording handshake information of all upper domains, respectively sending out an announcement to the node of the uppermost domain;
a4, the upper domain node periodically sends confirmation requests to other nodes except the accounting node in a plurality of random bottom domain, judges whether the notification of the accounting node is true, if the notification exceeds 67% of the nodes, the accounting node is added into the corresponding bottom domain, otherwise, the notification is not added;
a5, after the accounting node joins, synchronizing the related account book of the lowest layer domain where the accounting node is located.
The invention is based on a model of federated blockchains, so that the generation of accounting blocknodes is contractually generated by authorization; only if the effective nodes which meet a certain rule and exceed 67 percent jointly determine that the effective nodes can be added into the accounting right through a consensus mechanism, the nodes can participate in accounting; after a newly added node is started and connected with a network, a request is automatically initiated to a whole network voting system (similar to a super node in a block chain) and broadcasted to all upper-layer domains, after the upper-layer domains record, the request is periodically initiated to a node of the bottommost domain where a non-new node is located, whether the announcement of the new node is real or not is confirmed, and if more than 67% of effective nodes confirm that the new node is valid, the new node is real; if the confirmation is not obtained within 72 periods, the confirmation is not true, the joining of the new node is abandoned, and the joining notice of the next new node is waited; meanwhile, when the domain where the new node is located updates the node list of the domain where the non-new node is located, a verification request is sent to the failed node, the node passes through recording and does not pass through recycling again, and the record is discarded after 8 times of recycling at most; after a new node is added, the related account book of the domain where the new node is located is synchronized, and different domains have the full account book records of all the nodes of the domain; the reliability of the added new node is guaranteed, the trust degree of the node is improved, and meanwhile, the recording and synchronization of the account book are more convenient, faster and safer.
As a further optimization of the above scheme, the step c comprises the following steps:
broadcasting the transaction information verification request to other nodes except the accounting node in the bottommost layer domain where the accounting node is located; judging whether the verification confirmation information sent by more than 67% of nodes is received or not, if so, successfully verifying, and continuing to execute the verification judgment of the upper layer domain; if not, the verification fails and the transfer transaction request is denied.
Each transaction generates two paths of verification requests, one is to broadcast the verification request to the bottommost domain where the accounting node is located, the other is to send the verification request to the upper domain, and the upper domain verification is performed only after the verification in the bottommost domain where the accounting node is located passes; the integrity of the verification is ensured, and the verification result is more reliable.
As a further optimization of the above scheme, the upper domain verification and judgment step includes:
according to the security level of the transfer transaction, judging whether a transaction information verification request needs to be initiated to an upper layer domain, if so, initiating the transaction information verification request to the upper layer domain; if not, the transaction information verification request is not initiated to the upper layer domain, and the accounting operation is directly carried out.
Because the lower layer domains are all subsets of the account book of the upper layer domain, the bottommost domain can initiate a verification request of transaction information to the upper layer domain during accounting, and the upper layer domain can determine whether to initiate verification of transaction data to the higher layer according to the security level attribute of the transaction; therefore, a multi-stage transaction data verification process is formed, the comprehensiveness of verification is guaranteed, and after multiple times of verification, the safety of transaction is guaranteed.
As a further optimization of the above solution, the transaction information verification request initiating step includes:
after initiating a transaction information verification request to an upper domain, judging whether verification confirmation information sent by more than 67% of nodes is received or not, if so, successfully verifying, and entering the verification judgment step of the upper domain again; if not, the verification fails and the transfer transaction request is denied.
In the verification process of the upper layer domain, the private key signatures of the account transfer-in party account and the account transfer-out party account are transmitted to the upper layer domain, meanwhile, the upper layer domain has the public keys of the two accounts, the public keys are used for opening the private key signatures of the account transfer-in party and the account transfer-out party, and the transaction contents of the two parties are confirmed to be consistent, so that the transaction is considered to be real and effective, the security of the transaction is ensured, the transaction confirmation efficiency is greatly improved, and the transaction confirmation efficiency can reach millisecond level.
As a further optimization of the above scheme, the step d comprises the following steps:
carrying out accounting, and synchronously trading the account book to all nodes of the bottommost domain where the accounting node is located;
judging whether an upper layer domain exists, if so, continuing to synchronously transact the account book to the upper layer domain, and circularly judging the account book; if not, the synchronization of the transaction ledger is stopped.
Once the accounting is finished at the accounting node where the bottommost layer domain is located, accounts are synchronized to all nodes of the domain, and the accounts are synchronized layer by layer to the upper layer domain, and the synchronization is stopped until no upper layer domain exists; all the domain nodes are ensured to synchronously record the accounting information, a non-tampering and non-loss backup mechanism is formed, all transactions are completed in the blocks of the accounting nodes, and the rest nodes and all the upper domains only carry out synchronous accounting, verifying and confirming operations, so that the transaction efficiency is accelerated.
As a further optimization of the above scheme, the method further comprises the following steps:
after the synchronous transaction of the account book to the upper layer domain is completed, whether the account transferring party account and the account transferring party account are in the same bottommost domain is judged, and if yes, the synchronous transaction of the account book is not carried out; if not, the account book is synchronously transacted in the bottommost layer domain where the account of the account transfer party is located.
In the scheme, when the upper layer domain finds that the account transferring-in party account and the account transferring-out party account are not in the same bottommost domain, the account book is synchronously transacted layer by layer downwards to the domain where the account transferring-in party account is located, the account transferring-in party account can be guaranteed to receive and backup the transaction book, and the transaction process is more transparent and clear.
As a further optimization of the above scheme, the period T in step a4 is 10 min. The method and the device realize that the nodes of the upper layer domain periodically initiate confirmation requests to other nodes except the accounting node in a plurality of random bottommost domains, the period time can reserve enough time for the informed judgment of the accounting node to the maximum extent, and the judgment efficiency is improved while the judgment reliability is ensured.
The invention has the beneficial effects that:
1. the invention disperses the account book in each bottommost domain, the accounting nodes participate in the domain where the account of the account transfer party at the bottommost layer is located, and other related domains and upper domains only participate in the synchronous account book, thereby improving the efficiency of the synchronization of the account book.
2. The invention is based on a model of federated blockchains, so that the generation of accounting blocknodes is contractually generated by authorization; only if the effective nodes which meet a certain rule and exceed 67 percent jointly determine that the effective nodes can be added into the accounting right through a consensus mechanism, the nodes can participate in accounting, the reliability of the added new nodes is guaranteed, the trust degree of the nodes is improved, and meanwhile, the recording and synchronization of the account book are more convenient, faster and safer.
3. Each transaction generates two paths of verification requests, one is to broadcast the verification request to the bottommost layer domain where the accounting node is located, and the other is to send the verification request to the upper layer domain, so that a multi-stage transaction data verification process is formed, the integrity of verification is ensured, the verification result is more reliable, and the accounting safety of a block chain is improved.
4. In the verification process of the upper layer domain, private key signatures of the account transfer-in party and the account transfer-out party are opened through public keys of the account transfer-in party account and the account transfer-out party account owned by the upper layer domain, and the transaction contents of the two parties are confirmed to be consistent, so that the transaction is considered to be real and effective, the security of the transaction is ensured, the transaction confirmation efficiency is greatly improved, and the transaction confirmation efficiency can reach millisecond level.
5. The upper domain node initiates confirmation requests to other nodes except the accounting node in a plurality of random bottommost domains by taking 10min as a period, the period time can reserve enough time for the informed judgment of the accounting node to the maximum extent, and the judgment efficiency is improved while the judgment reliability is ensured.
Drawings
FIG. 1 is a flow chart of a hybrid chain accounting method based on multi-level verification according to an embodiment of the present invention;
FIG. 2 is a flow chart of accounting node join according to an embodiment of the present invention;
fig. 3 is a flow chart of validating and synchronizing a transaction ledger according to an embodiment of the present invention.
Detailed Description
Embodiments of the present invention will be described in detail below with reference to the accompanying drawings.
Examples
As shown in fig. 1, a hybrid chain accounting method based on multi-level verification includes the following steps:
a. establishing a multi-layer domain with a tree structure, and adding a billing node with a billing right to any bottom layer domain according to a consensus mechanism;
b. initiating a transfer transaction request, judging whether the account of the account transfer party is in an accounting node of the bottommost layer domain, if so, entering the step c; if not, rejecting the transfer transaction request;
c. d, broadcasting a transaction information verification request to the lowest layer domain and the upper layer domain to which the accounting node belongs, judging whether verification confirmation information is received, if so, successfully verifying, and entering the step d; if not, the verification fails and the transfer transaction request is rejected;
d. and carrying out accounting, and synchronously trading the account book to the bottommost layer domain where the accounting node is located and the upper layer domain.
The block chain structure is a hierarchical structure model, each layer is a netlike intercommunicated grape vine structure, nodes of different levels contained in each layer are called a domain, in the bottommost layer domain, a full account book is dispersed into each bottommost layer domain, the upper layer domain is a larger account book formed by upward transmission of the lower layer domain, and the topmost layer domain has account books of all accounts; the invention also adopts a wheel disc mode to confirm the addition of the effective block, and the specific confirmation mode is as follows:
accounting nodes participate in the domain where the lowest-layer accounting transfer party account is located, blocks are generated by the accounting nodes, each lowest-layer domain has a unique accounting node at the same time, an accounting node (the time is defined as bastion time) is generated again every 326 seconds, and the generation of new accounting nodes is generated according to the last accounting behavior parameter and a certain random rule, so that a node target cannot be found and attacked in the time range; other related domains and upper-layer domains only participate in the synchronous account book, so that the efficiency of account book synchronization is improved; meanwhile, the upper layer domain is the union of accounts of all the lower layer domains, and can participate in the verification of the accounts of the lower layer domains, so that the accounting safety of the block chain is improved.
In another embodiment, as shown in fig. 2, in step a, the adding step of the accounting node specifically includes:
a1, voting by a consensus mechanism, after the voting result is determined and the voting result is effective, all nodes of the upper domain add the address, the public key and the domain parameter of the added accounting node into a node list, and initiate handshake request information to the accounting node;
a2, after the accounting node is online and connected with the network, acquiring the latest upper domain list, broadcasting the latest upper domain list to all upper domains, and replying handshake confirmation information to the nodes of all upper domains;
a3, after confirming and recording handshake information of all upper domains, respectively sending out an announcement to the node of the uppermost domain;
a4, the upper domain node periodically sends confirmation requests to other nodes except the accounting node in a plurality of random bottom domain, judges whether the notification of the accounting node is true, if the notification exceeds 67% of the nodes, the accounting node is added into the corresponding bottom domain, otherwise, the notification is not added;
a5, after the accounting node joins, synchronizing the related account book of the lowest layer domain where the accounting node is located.
The invention is based on a model of federated blockchains, so that the generation of accounting blocknodes is contractually generated by authorization; only if the effective nodes which meet a certain rule and exceed 67 percent jointly determine that the effective nodes can be added into the accounting right through a consensus mechanism, the nodes can participate in accounting; after a newly added node is started and connected with a network, a request is automatically initiated to a whole network voting system (similar to a super node in a block chain) and broadcasted to all upper-layer domains, after the upper-layer domains record, the request is periodically initiated to a node of the bottommost domain where a non-new node is located, whether the announcement of the new node is real or not is confirmed, and if more than 67% of effective nodes confirm that the new node is valid, the new node is real; if the confirmation is not obtained within 72 periods, the confirmation is not true, the joining of the new node is abandoned, and the joining notice of the next new node is waited; meanwhile, when the domain where the new node is located updates the node list of the domain where the non-new node is located, a verification request is sent to the failed node, the node passes through recording and does not pass through recycling again, and the record is discarded after 8 times of recycling at most; after a new node is added, the related account book of the domain where the new node is located is synchronized, and different domains have the full account book records of all the nodes of the domain; the reliability of the added new node is guaranteed, the trust degree of the node is improved, and meanwhile, the recording and synchronization of the account book are more convenient, faster and safer.
In another embodiment, as shown in fig. 3, the step c includes the steps of:
broadcasting the transaction information verification request to other nodes except the accounting node in the bottommost layer domain where the accounting node is located; judging whether the verification confirmation information sent by more than 67% of nodes is received or not, if so, successfully verifying, and continuing to execute the verification judgment of the upper layer domain; if not, the verification fails and the transfer transaction request is denied.
Each transaction generates two paths of verification requests, one is to broadcast the verification request to the bottommost domain where the accounting node is located, the other is to send the verification request to the upper domain, and the upper domain verification is performed only after the verification in the bottommost domain where the accounting node is located passes; the integrity of the verification is ensured, and the verification result is more reliable.
In another embodiment, as shown in fig. 3, the upper domain verification determining step includes:
according to the security level of the transfer transaction, judging whether a transaction information verification request needs to be initiated to an upper layer domain, if so, initiating the transaction information verification request to the upper layer domain; if not, the transaction information verification request is not initiated to the upper layer domain, and the accounting operation is directly carried out.
Because the lower layer domains are all subsets of the account book of the upper layer domain, the bottommost domain can initiate a verification request of transaction information to the upper layer domain during accounting, and the upper layer domain can determine whether to initiate verification of transaction data to the higher layer according to the security level attribute of the transaction; therefore, a multi-stage transaction data verification process is formed, the comprehensiveness of verification is guaranteed, and after multiple times of verification, the safety of transaction is guaranteed.
In another embodiment, as shown in fig. 3, the transaction information verification request initiating step includes:
after initiating a transaction information verification request to an upper domain, judging whether verification confirmation information sent by more than 67% of nodes is received or not, if so, successfully verifying, and entering the verification judgment step of the upper domain again; if not, the verification fails and the transfer transaction request is denied.
In the verification process of the upper layer domain, the private key signatures of the account transfer-in party account and the account transfer-out party account are transmitted to the upper layer domain, meanwhile, the upper layer domain has the public keys of the two accounts, the public keys are used for opening the private key signatures of the account transfer-in party and the account transfer-out party, and the transaction contents of the two parties are confirmed to be consistent, so that the transaction is considered to be real and effective, the security of the transaction is ensured, the transaction confirmation efficiency is greatly improved, and the transaction confirmation efficiency can reach millisecond level.
In another embodiment, as shown in fig. 3, the step d comprises the steps of:
carrying out accounting, and synchronously trading the account book to all nodes of the bottommost domain where the accounting node is located;
judging whether an upper layer domain exists, if so, continuing to synchronously transact the account book to the upper layer domain, and circularly judging the account book; if not, the synchronization of the transaction ledger is stopped.
Once the accounting is finished at the accounting node where the bottommost layer domain is located, accounts are synchronized to all nodes of the domain, and the accounts are synchronized layer by layer to the upper layer domain, and the synchronization is stopped until no upper layer domain exists; all the domain nodes are ensured to synchronously record the accounting information, a non-tampering and non-loss backup mechanism is formed, all transactions are completed in the blocks of the accounting nodes, and the rest nodes and all the upper domains only carry out synchronous accounting, verifying and confirming operations, so that the transaction efficiency is accelerated.
In another embodiment, as shown in fig. 3, the method further comprises the following steps:
after the synchronous transaction of the account book to the upper layer domain is completed, whether the account transferring party account and the account transferring party account are in the same bottommost domain is judged, and if yes, the synchronous transaction of the account book is not carried out; if not, the account book is synchronously transacted in the bottommost layer domain where the account of the account transfer party is located.
In the scheme, when the upper layer domain finds that the account transferring-in party account and the account transferring-out party account are not in the same bottommost domain, the account book is synchronously transacted layer by layer downwards to the domain where the account transferring-in party account is located, the account transferring-in party account can be guaranteed to receive and backup the transaction book, and the transaction process is more transparent and clear.
In another embodiment, the period T of step a4 is 10 min. The method and the device realize that the nodes of the upper layer domain periodically initiate confirmation requests to other nodes except the accounting node in a plurality of random bottommost domains, the period time can reserve enough time for the informed judgment of the accounting node to the maximum extent, and the judgment efficiency is improved while the judgment reliability is ensured.
The above-mentioned embodiments only express the specific embodiments of the present invention, and the description thereof is more specific and detailed, but not construed as limiting the scope of the present invention. It should be noted that, for a person skilled in the art, several variations and modifications can be made without departing from the inventive concept, which falls within the scope of the present invention.
Claims (6)
1. A hybrid chain accounting method based on multi-stage verification is characterized by comprising the following steps:
a. establishing a multi-layer domain with a tree structure, and adding a billing node with a billing right to any bottom layer domain according to a consensus mechanism;
b. initiating a transfer transaction request, judging whether the account of the account transfer party is in an accounting node of the bottommost layer domain, if so, entering the step c; if not, rejecting the transfer transaction request;
c. d, broadcasting a transaction information verification request to the lowest layer domain and the upper layer domain to which the accounting node belongs, judging whether verification confirmation information is received, if so, successfully verifying, and entering the step d; if not, the verification fails and the transfer transaction request is rejected;
d. accounting is carried out, and an account book is synchronously transacted to the bottommost layer domain where the accounting node is located and the upper layer domain;
after the synchronous transaction of the account book to the upper layer domain is completed, whether the account transferring party account and the account transferring party account are in the same bottommost domain is judged, and if yes, the synchronous transaction of the account book is not carried out; if not, synchronously trading the account book to the bottommost layer domain where the account of the account transfer party is located;
in the step a, the adding step of the accounting node is as follows:
a1, voting by a consensus mechanism, after the voting result is determined and the voting result is effective, all nodes of the upper domain add the address, the public key and the domain parameter of the added accounting node into a node list, and initiate handshake request information to the accounting node;
a2, after the accounting node is online and connected with the network, acquiring the latest upper domain list, broadcasting the latest upper domain list to all upper domains, and replying handshake confirmation information to the nodes of all upper domains;
a3, after confirming and recording handshake information of all upper domains, respectively sending out an announcement to the node of the uppermost domain;
a4, the upper domain node periodically sends confirmation requests to other nodes except the accounting node in a plurality of random bottom domain, judges whether the notification of the accounting node is true, if the notification exceeds 67% of the nodes, the accounting node is added into the corresponding bottom domain, otherwise, the notification is not added;
a5, after the accounting node joins, synchronizing the related account book of the lowest layer domain where the accounting node is located.
2. The hybrid chain accounting method based on multi-level verification according to claim 1, wherein the step c comprises the following steps:
broadcasting the transaction information verification request to other nodes except the accounting node in the bottommost layer domain where the accounting node is located; judging whether the verification confirmation information sent by more than 67% of nodes is received or not, if so, successfully verifying, and continuing to execute the verification judgment of the upper layer domain; if not, the verification fails and the transfer transaction request is denied.
3. The hybrid chain accounting method based on multi-level verification according to claim 2, wherein the upper domain verification judging step comprises:
according to the security level of the transfer transaction, judging whether a transaction information verification request needs to be initiated to an upper layer domain, if so, initiating the transaction information verification request to the upper layer domain; if not, the transaction information verification request is not initiated to the upper layer domain, and the accounting operation is directly carried out.
4. The multi-level verification-based hybrid chain accounting method as claimed in claim 3, wherein the transaction information verification request initiation step comprises:
after initiating a transaction information verification request to an upper domain, judging whether verification confirmation information sent by more than 67% of nodes is received or not, if so, successfully verifying, and entering the verification judgment step of the upper domain again; if not, the verification fails and the transfer transaction request is denied.
5. The hybrid chain accounting method based on multi-level verification according to claim 1, wherein the step d comprises the following steps:
performing accounting, synchronously trading the account book to all nodes of the bottommost domain where accounting nodes are located, judging whether an upper domain exists, if so, continuously trading the account book to the upper domain synchronously, and circularly performing the judgment; if not, the synchronization of the transaction ledger is stopped.
6. The hybrid chain accounting method based on multi-level verification according to claim 1, wherein the period T in step a4 is 10 min.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711139660.8A CN107945017B (en) | 2017-11-16 | 2017-11-16 | Hybrid chain accounting method based on multi-stage verification |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN201711139660.8A CN107945017B (en) | 2017-11-16 | 2017-11-16 | Hybrid chain accounting method based on multi-stage verification |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN107945017A CN107945017A (en) | 2018-04-20 |
| CN107945017B true CN107945017B (en) | 2021-11-12 |
Family
ID=61932657
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN201711139660.8A Active CN107945017B (en) | 2017-11-16 | 2017-11-16 | Hybrid chain accounting method based on multi-stage verification |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN107945017B (en) |
Families Citing this family (10)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN109410049A (en) * | 2018-09-18 | 2019-03-01 | 深圳周百通科技有限公司 | Block chain bookkeeping methods, device, computer equipment and storage medium |
| CN109525633B (en) * | 2018-10-08 | 2021-08-27 | 上海点融信息科技有限责任公司 | Block chain network, message sending method and message receiving method based on block chain network |
| CN109493225B (en) * | 2018-11-12 | 2022-02-18 | 夸克链科技（深圳）有限公司 | Domain-divided verification mechanism of block chain |
| CN109727132B (en) * | 2018-12-28 | 2021-03-23 | 合肥达朴汇联科技有限公司 | Method and device for acquiring block chain consensus node, electronic equipment and storage medium |
| WO2020155167A1 (en) * | 2019-02-02 | 2020-08-06 | Microsoft Technology Licensing, Llc | Application of cross-organizational transactions to blockchain |
| CN110322352A (en) * | 2019-07-09 | 2019-10-11 | 深圳市炳德区块链技术有限公司 | A kind of account book foundation and querying method, electronic equipment based on block chain |
| CN110457956B (en) * | 2019-08-16 | 2021-05-28 | 重庆华医康道科技有限公司 | Consensus supervision method and system for data supervision-oriented block chain network |
| CN111127007B (en) * | 2019-12-06 | 2023-09-22 | 环球数科集团有限公司 | Offline ticket reuse prevention method based on distributed account book principle |
| CN111143381B (en) * | 2019-12-11 | 2023-05-19 | 支付宝(杭州)信息技术有限公司 | Method and device for updating trust points in multi-layer block chain structure |
| CN112950208A (en) * | 2021-03-29 | 2021-06-11 | 建信金融科技有限责任公司 | Accounting information processing method and device based on block chain |
Family Cites Families (8)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US7757942B1 (en) * | 2006-09-18 | 2010-07-20 | Ford Sr Ronald | Biometric charge card verification system and associated method |
| US20160321751A1 (en) * | 2015-04-28 | 2016-11-03 | Domus Tower, Inc. | Real-time settlement of securities trades over append-only ledgers |
| CN105719185B (en) * | 2016-01-22 | 2019-02-15 | 杭州复杂美科技有限公司 | The data comparison and common recognition method of block chain |
| CN107077674B (en) * | 2016-12-29 | 2021-06-11 | 达闼机器人有限公司 | Transaction verification processing method and device and node equipment |
| CN107146087A (en) * | 2017-04-11 | 2017-09-08 | 广东网金控股股份有限公司 | A kind of quick common recognition bookkeeping methods and system based on block chain alliance chain |
| CN107239940A (en) * | 2017-05-11 | 2017-10-10 | 北京博晨技术有限公司 | Network trading method and device based on block catenary system |
| CN107147735B (en) * | 2017-05-12 | 2020-08-11 | 北京博晨技术有限公司 | Distributed account book system based on hierarchical structure |
| CN107341660B (en) * | 2017-05-27 | 2021-06-29 | 唐盛（北京）物联技术有限公司 | Block chain bottom layer consensus mechanism and block chain system based on same |
-
2017
- 2017-11-16 CN CN201711139660.8A patent/CN107945017B/en active Active
Also Published As
| Publication number | Publication date |
|---|---|
| CN107945017A (en) | 2018-04-20 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107945017B (en) | Hybrid chain accounting method based on multi-stage verification | |
| US11348095B2 (en) | Rapid distributed consensus on blockchain | |
| CN107147735B (en) | Distributed account book system based on hierarchical structure | |
| CN109871669B (en) | Data sharing solution based on block chain technology | |
| CN109360100B (en) | Transaction rapid confirmation method and device based on block chain technology | |
| EP3639468B1 (en) | Systems and methods for avoiding or reducing cryptographically stranded resources on a blockchain network | |
| US11177939B2 (en) | Blockchain system including a distributed network of a plurality of nodes and a method for achieving an agreement between the plurality of nodes executed by processors of the block chain system | |
| CN108154367B (en) | Block chain service checking method and device | |
| US9635000B1 (en) | Blockchain identity management system based on public identities ledger | |
| CN112541758A (en) | Multi-round voting type fault-tolerant sequencing consensus mechanism and method based on block chain | |
| CN110046998B (en) | Cross-chain right using system, method, device, electronic equipment and storage medium | |
| CN110351133A (en) | Method and device for the host node hand-off process in block catenary system | |
| TW202025045A (en) | Invoice reimbursement method and device based on block chain and electronic device | |
| CN107609876A (en) | A kind of method and system for recovering block chain assets | |
| EP4318362A1 (en) | Blockchain-based data processing method, apparatus and device, and storage medium | |
| CN112907252B (en) | Block chain transaction method and system based on multi-person chain lower channel | |
| CN110751468A (en) | Multi-directional state channel method, system and medium for block chain expansion | |
| JP2023076628A (en) | Computer-implemented systems and methods relating to binary blockchain comprising one pair of coupled blockchains | |
| CN110377635B (en) | Block chain architecture-based RMB cross-border payment inquiry and retrieval method and device | |
| CN111585767A (en) | Data exchange method and device for main chain and side chain | |
| CN110992035A (en) | Block chain link point management method, device and system | |
| CN112116349B (en) | High-throughput-rate-oriented random consensus method and device for drawing account book | |
| US20200202349A1 (en) | Multiple asset transactions | |
| KR102100178B1 (en) | System for check falsify recording file based on block chain and method performing thereof | |
| CN110008739B (en) | Block chain system based on group, group management method and 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 |