CN111526050B - Network deployment system, method, equipment and storage medium for block chain out-of-block node - Google Patents

Network deployment system, method, equipment and storage medium for block chain out-of-block node Download PDF

Info

Publication number
CN111526050B
CN111526050B CN202010305393.2A CN202010305393A CN111526050B CN 111526050 B CN111526050 B CN 111526050B CN 202010305393 A CN202010305393 A CN 202010305393A CN 111526050 B CN111526050 B CN 111526050B
Authority
CN
China
Prior art keywords
block
branch
node
data
chain
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
Application number
CN202010305393.2A
Other languages
Chinese (zh)
Other versions
CN111526050A (en
Inventor
文格彬
王晓东
孙翰韬
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Kunming Dagangke Technology Co ltd
Original Assignee
Kunming Dagangke Technology Co ltd
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Application filed by Kunming Dagangke Technology Co ltd filed Critical Kunming Dagangke Technology Co ltd
Priority to CN202010305393.2A priority Critical patent/CN111526050B/en
Publication of CN111526050A publication Critical patent/CN111526050A/en
Application granted granted Critical
Publication of CN111526050B publication Critical patent/CN111526050B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L41/00—Arrangements for maintenance, administration or management of data switching networks, e.g. of packet switching networks
    • H04L41/08—Configuration management of networks or network elements
    • H04L41/0803—Configuration setting
    • H04L41/0823—Configuration setting characterised by the purposes of a change of settings, e.g. optimising configuration for enhancing reliability
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L63/00—Network architectures or network communication protocols for network security
    • H04L63/08—Network architectures or network communication protocols for network security for authentication of entities
    • H04L63/0876—Network architectures or network communication protocols for network security for authentication of entities based on the identity of the terminal or configuration, e.g. MAC address, hardware or software configuration or device fingerprint
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1001—Protocols in which an application is distributed across nodes in the network for accessing one among a plurality of replicated servers
    • H04L67/1004—Server selection for load balancing
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/104—Peer-to-peer [P2P] networks
    • H04L67/1044—Group management mechanisms 
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1095—Replication or mirroring of data, e.g. scheduling or transport for data synchronisation between network nodes
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L67/00—Network arrangements or protocols for supporting network services or applications
    • H04L67/01—Protocols
    • H04L67/10—Protocols in which an application is distributed across nodes in the network
    • H04L67/1097—Protocols in which an application is distributed across nodes in the network for distributed storage of data in networks, e.g. transport arrangements for network file system [NFS], storage area networks [SAN] or network attached storage [NAS]

Landscapes

  • Engineering & Computer Science (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Computing Systems (AREA)
  • Physics & Mathematics (AREA)
  • Mathematical Physics (AREA)
  • Theoretical Computer Science (AREA)
  • Power Engineering (AREA)
  • Computer Hardware Design (AREA)
  • Computer Security & Cryptography (AREA)
  • General Engineering & Computer Science (AREA)
  • Information Retrieval, Db Structures And Fs Structures Therefor (AREA)

Abstract

The application relates to a network deployment system, a method, equipment and a storage medium of a blockchain out-of-block node.A ROOT server stores related data containing a block out-of-block signature key, the related data are negotiated together with a safety main chain out-of-block, a BigBang network is accessed, EDPoS negotiation on the safety main chain is performed, and data are interacted with other branch nodes in a super node to store and test the data of the safety main chain; the branch node server processes the branch data of the application branch chain and is connected with the corresponding branch nodes of other super nodes through P2P; the ROOT server obtains the connection address of the opposite-end branch node through handshake negotiation with the opposite-end ROOT server, distributes the connection address to each branch node, constructs a new safe main chain block when EDPoS negotiates that the current ROOT is selected as a block outlet node, pushes the context data of the branched chain block outlet to each branch node server, constructs and signs the data of each branched chain new block, and broadcasts the data to the whole network. The performance of the block chain out-of-block node is improved.

Description

Network deployment system, method, equipment and storage medium for block chain out-of-block node
Technical Field
The application relates to the field of blockchains, in particular to a network deployment system, a network deployment method, a network deployment equipment and a network deployment storage medium for a blockchain output node.
Background
The blockchain is a chain structure formed by connecting a series of blocks through a block hash, the blocks are mainly generated in a PoW mode and a DPoS cooperation mode, and each block generation mode has a certain performance requirement on the node itself for providing services. For example, poW, to obtain the block weight, the block to be obtained is confirmed by the whole network, so that not only excellent computing performance is required, but also good network environment is required. While the DPoS node has high demands on the computing performance of the computer, the demands on the network environment are not low, especially when the outbound nodes provide services externally.
The existing blockchain public chains are mostly of a single-chain structure, and the processing capacity of the public chains of the single-chain structure for data encounters a bottleneck as the data volume increases. Therefore, some public chains put forward the concept of a side chain, which is equivalent to deploying one public chain again, and then realizing data mutual recognition and value transfer with the original public chain. It is very difficult to actually realize the side chain.
Disclosure of Invention
In view of the above, a system, a method, a device and a storage medium for deploying a network of blockchain out nodes are provided to solve the problem of poor performance of blockchain out nodes in the prior art.
The application adopts the following technical scheme:
in a first aspect, an embodiment of the present application provides a network deployment system for a blockchain egress block node, where the system includes a ROOT server and a branch node server, where:
the ROOT server is used for storing related data containing a block-out signing key, wherein the related data are used for negotiating together and safety main chain block-out;
the ROOT server is accessed into a BigBang network and is used for EDPoS negotiation on the safety main chain and data interaction with other branch nodes in the super node;
the ROOT server is used for storing data for checking the safety main chain;
the branch node server is used for organizing block data of an application branched chain and processing the branch data of the application branched chain;
the branch node servers are connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT servers acquire connection addresses of opposite-end branch nodes through handshake negotiation with the opposite-end ROOT servers, and distribute the connection addresses to the branch nodes;
when EDPoS negotiates that the current ROOT is selected as a block outlet node, the ROOT server constructs a new block of a safe main chain, pushes the context data of the branched block outlet to each branch node server, constructs and signs the data of the respective branched new block, and broadcasts the branch nodes to the whole network, wherein each branch node stores the related data containing the block outlet signature key.
Optionally, the ROOT server is connected with the ROOT servers of other super nodes and the ROOT server is connected with other common nodes through P2P.
Optionally, the branch node server and the ROOT server are connected through a Socket API or MQ manner to interact security beacons and management data.
Optionally, each of the branch node servers is responsible for one branch chain data or a plurality of branch chain data.
Optionally, the branch chain data in charge of any two branch node servers are different.
Optionally, the distributed super node constructs a branched node server cluster in a cascading manner to split the application traffic load.
Optionally, the security beacon is used to identify the security backbone and the application branch.
In a second aspect, an embodiment of the present application provides a network deployment method for a blockchain egress block node, where the method includes:
the branch node server is connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT server obtains a connection address of the opposite-end branch node when negotiating handshake with the opposite-end ROOT server, and distributes the connection address to the branch node;
when EDPoS negotiates that the current ROOT is selected as a block outlet node, the ROOT server constructs a new block of a safety main chain, pushes the context data of the branched block outlet to the branch node servers of all branch node servers to construct and sign the data of the respective branched new block, and then broadcasts the whole network by the branch nodes, wherein the branch nodes store the related data of the block outlet signing keys.
In a third aspect, an embodiment of the present application provides an apparatus, including:
a processor, and a memory coupled to the processor;
the memory is used for storing a computer program, and the computer program is at least used for executing the network deployment method of the blockchain egress block node according to the second aspect of the embodiment of the application;
the processor is configured to invoke and execute the computer program in the memory.
In a fourth aspect, an embodiment of the present application provides a storage medium storing a computer program, where the computer program when executed by a processor implements the steps in the network deployment method of a blockchain egress block node according to the second aspect.
Compared with the scheme of realizing service capacity expansion by adopting a single-chain structure or adopting a side chain and other modes, the BigBang realizes the application logic of a 'safe main chain+an application branched chain' through a super node scheme, so that the safe main chain is mainly responsible for processing transactions from the safe main chain, and all applications are submitted to the application branched chain for completion, thereby solving the performance problem. Meanwhile, the safety main chain and the application branched chains are identified through random beacons so as to keep synchronization, all branched chains of the whole public chain have the same algorithm basis, the transaction and the value transfer are realized by adopting the same hash algorithm, and the problems of complexity, deceptive transfer, centralization, soft bifurcation risks and the like are solved well.
Drawings
In order to more clearly illustrate the embodiments of the application or the technical solutions in the prior art, the drawings that are required in the embodiments or the description of the prior art will be briefly described, it being obvious that the drawings in the following description are only some embodiments of the application, and that other drawings may be obtained according to these drawings without inventive effort for a person skilled in the art.
FIG. 1 is a schematic diagram of a network deployment system for a blockchain egress block node according to an embodiment of the present application;
FIG. 2 is a schematic diagram of a network deployment of blockchain egress block nodes suitable for use in embodiments of the present application;
FIG. 3 is a schematic diagram of a cascade of network deployment systems of blockchain egress block nodes, as applicable in embodiments of the present application;
FIG. 4 is a flowchart of a method for deploying a network of blockchain egress block nodes provided by an embodiment of the present application;
fig. 5 is a schematic structural diagram of an apparatus according to an embodiment of the present application.
Detailed Description
In order to make the objects, technical solutions and advantages of the present application more apparent, the technical solutions of the present application will be described in detail below. It will be apparent that the described embodiments are only some, but not all, embodiments of the application. All other embodiments, based on the examples herein, which are within the scope of the application as defined by the claims, will be within the scope of the application as defined by the claims.
First, the prior art of the embodiments of the present application and the drawbacks of the prior art will be described, which mainly refer to problems in terms of complexity, fraudulent transfer, centralization, risk of soft bifurcation, etc.
First, complexity. At the network level, there are many independent, unsynchronized blockchains that support inter-transfer. They must support transaction scripts or smart contracts that can be declared dead by a later reorganization proof. In addition, software is required to automatically detect fraud and to generate and issue relevant proofs. At the asset level, the simple "one chain, one asset" criteria no longer exist; a single chain may support any number of assets, including even assets that do not exist when the chain is first created. Each of these assets is marked with a chain of sources for that asset to ensure that the transfer of the asset can be resolved correctly. It is not enough for the blockchain infrastructure to handle only high-level functions: the user interface for managing the purse also needs to be reconsidered. Currently, in the world of competing coins, each chain has its own wallet to support transactions of coins on that chain. These purses need to be rewritten to support multiple chains, possibly with different sets of functionality, and transfer of inter-chain assets. Of course, if the user interface is made too complex, it is entirely possible to choose not to use certain functions.
Second, fraudulent transfers. Theoretically, any depth of reorganization is possible, which allows an attacker to make a reorganization longer than the racing period of the send chain, transferring coins completely between the side chains before the send chain cancels the transfer on the half side. The result will be an unequal number of coins on the receive chain to the number of redeemable lock outputs on the transmit chain. If an attacker were allowed to transfer coins back to the original chain, the number of own coins would be increased, giving other users on the side chain a penalty. Before discussing how this problem can be handled, this risk can be made arbitrarily small by simply extending the racing period of the transfer. A function may be generated using the relative hash forces of the two chains to determine the duration of the race period: the receiving chain may unlock the coin only when an SPV (Special Purpose Vehicle, special purpose carrier) proof equivalent to 1 day of work on the chain is seen, which may correspond to a few days of work on the sending chain. A security parameter like this is a property specific to the side chain, which can be optimized for each side chain application.
Examples
Fig. 1 is a schematic structural diagram of a network deployment system of a blockchain egress block node according to an embodiment of the present application, where the system may execute the network deployment method of the blockchain egress block node according to the embodiment of the present application. Referring to fig. 1, the system may specifically include: a ROOT server 11 and a branch node server 12.
The ROOT server 11 is configured to store related data including a block-out signing key, where the related data is used for negotiating together and securing a main chain block-out; the ROOT server 11 is accessed into a BigBang network and is used for EDPoS negotiation on a safety main chain and data interaction with other branch nodes in the super node; the ROOT server 11 is used for storing data for checking the security backbone; the branch node server 12 is used for organizing block data of the application branch chain and processing branch data of the application branch chain; the branch node server 12 is connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT server 11 obtains the connection address of the opposite-end branch node through handshake negotiation with the opposite-end ROOT server 11, and distributes the connection address to each branch node; when EDPoS negotiates that the current ROOT is selected as a block outlet node, the ROOT server 11 constructs a new block of a safety main chain, pushes the context data of the branched block outlet to each branch node server, each branch node server 12 constructs and signs the data of the respective branched new block, and the branch nodes broadcast to the whole network, wherein each branch node stores related data containing a block outlet signing key.
First, in the embodiment of the present application, the main objective of the distributed super node is EDPoS with a main chain, and the node solves the problem of expansibility. BigBang Core acts as a multi-branched block system, and nodes participating in EDPoS need to be synchronized out for all valuable branches. With the increase of the number of application branches, the burden of the block-out node becomes more and more heavy, and a single server cannot meet the scalability requirement of the system, so that the distributed super node is an effective solution to the problem.
Specifically, in the distributed super node scheme, main roles are divided into a ROOT node server and a branch node server according to different services. The ROOT node server is mainly responsible for consensus negotiation, main chain block output, main chain data management, branch node management and other works. The ROOT node server stores relevant data of the output block signing key for consensus negotiation and main chain output block use. The ROOT node server is accessed to the BigBang network, on one hand, EDPoS negotiation on the safety main chain is carried out, and on the other hand, data interaction is carried out with other branch nodes in the super node. Optionally, in the BigBang Core, since the BigBang Core adopts a tree-shaped block chain structure, and the data is constructed by using a secure main chain and an application branched chain, the BigBang Core is a public chain specially designed for the internet of things, so that if each node provides services to the outside, a certain performance requirement is required for the BigBang Core. Particularly, when the node is the DPoS block-out node of the security main chain, and provides data service to the outside and provides block service for the application branch chain, the performance requirement of the system on the node is high. BigBang Core is a public chain generated for the internet of things, and higher service processing capacity and throughput are required naturally. In particular, in the practical application process, the application branched node can directly interact with the IOT device, and in this application scenario, the existence of the super node is necessary. In one specific example, FIG. 2 illustrates a schematic diagram of a network deployment of blockchain egress block nodes. The LWS (light wallet service ) client may implement the light wallet service function, among other things.
In addition, the ROOT node server stores only data for verifying the security backbone, and the application branch data is processed by the branch node server. The branch node server is dedicated to organizing block data of the application branches. The branch node server is connected with corresponding branch nodes of other super nodes through P2P or Socket API (Application Programming Interface, application program interface), and in detail, the ROOT node server obtains the connection address of the opposite-end branch node when in handshake negotiation with the opposite-end ROOT node server, and distributes the connection address to the branch node. When EDPoS negotiates that the current ROOT node is selected as a block outlet node, the ROOT node server constructs a main chain new block, pushes the branched chain block outlet context data to each branched node server, constructs and signs the respective branched chain new block data, and after the branched nodes self-broadcast the whole network, the branched nodes store the related data of the block outlet signing keys.
Optionally, the ROOT server 11 is connected with the ROOT servers 11 of other super nodes, and the ROOT server 11 is connected with other common nodes through P2P. The ROOT node server is connected with the ROOT node servers of other super nodes through P2P or Socket API, or is connected with the common node through P2P or Socket API.
Optionally, the branch node server 12 and the ROOT server 11 are connected through a Socket API or MQ manner to interact security beacons and manage data. Such as receive processing security beacons, etc., to achieve data synchronization of the security backbone and application branches. Optionally, a security beacon is used to identify the security backbone and the application branches.
Optionally, each branch node server 12 is responsible for one branch chain data or multiple branch chain data. The branch chain data for which any two branch node servers are responsible is different. Each branch node server is responsible for only one or more pieces of branch chain data, and there cannot be two branch node servers responsible for the same branch chain data.
Optionally, the distributed super node constructs a branched node server cluster in a cascading manner to split the application traffic load. When the load of the application branched chain is overlarge and further upgrading and expanding are needed, the distributed super nodes can build a branched chain node server cluster in a cascading mode and are used for shunting huge application service loads. In one specific example, FIG. 3 shows a cascading schematic diagram of a network deployment system of blockchain egress block nodes.
Compared with the scheme of realizing service capacity expansion by adopting a single-chain structure or adopting a side chain and other modes, the BigBang realizes the application logic of a 'safe main chain+an application branched chain' through a super node scheme, so that the safe main chain is mainly responsible for processing transactions from the safe main chain, and all applications are submitted to the application branched chain for completion, thereby solving the performance problem. Meanwhile, the safety main chain and the application branched chains are identified through random beacons so as to keep synchronization, all branched chains of the whole public chain have the same algorithm basis, the transaction and the value transfer are realized by adopting the same hash algorithm, and the problems of complexity, deceptive transfer, centralization, soft bifurcation risks and the like are solved well.
In addition, based on the tree structure characteristic of BigBang Core, the safety main chain ensures stability and the application branch chain executes application logic of application, and the safety main chain is mainly responsible for processing transactions from the safety main chain, so that the transactions are relatively less, and all the applications are submitted to the application branch chain for completion, thereby solving the performance problem. Meanwhile, the safety main chain and the application branched chain are identified through random beacons, synchronization is kept, all branched chains of the whole public chain have the same algorithm basis, the transaction and the value transfer are realized by adopting the same hash algorithm, and the problems of complexity, deceptive transfer, centralization, soft bifurcation risks and the like are solved well.
Fig. 4 is a flowchart of a network deployment method of a blockchain egress block node according to an embodiment of the present application, where the method is implemented on the basis of the foregoing embodiments. Referring to fig. 4, the method may specifically include the steps of:
s401, the branch node server is connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT server obtains a connection address of the opposite-end branch node when negotiating handshake with the opposite-end ROOT server, and distributes the connection address to the branch node.
S402, when EDPoS negotiates that the current ROOT is selected as a block outlet node, the ROOT server constructs a new block of a safety main chain, pushes the context data of the branched block outlet to the branch node servers of all branch node servers to construct and sign the data of the respective branched new block, and then broadcasts the whole network by the branch nodes, wherein the branch nodes store the related data of the block outlet signing keys.
Compared with the scheme of realizing service capacity expansion by adopting a single-chain structure or adopting a side chain and other modes, the BigBang realizes the application logic of a 'safe main chain+an application branched chain' through a super node scheme, so that the safe main chain is mainly responsible for processing transactions from the safe main chain, and all applications are submitted to the application branched chain for completion, thereby solving the performance problem. Meanwhile, the safety main chain and the application branched chains are identified through random beacons so as to keep synchronization, all branched chains of the whole public chain have the same algorithm basis, the transaction and the value transfer are realized by adopting the same hash algorithm, and the problems of complexity, deceptive transfer, centralization, soft bifurcation risks and the like are solved well.
An embodiment of the present application further provides an apparatus, referring to fig. 5, fig. 5 is a schematic structural diagram of an apparatus, as shown in fig. 5, where the apparatus includes: a processor 510 and a memory 520 connected to the processor 510; the memory 520 is configured to store a computer program, where the computer program is configured to at least perform a network deployment method of a blockchain egress block node in an embodiment of the present application; the processor 510 is used to invoke and execute the computer program in memory; the network deployment method of the block chain out-of-block node at least comprises the following steps: the branch node server is connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT server obtains a connection address of the opposite-end branch node when negotiating handshake with the opposite-end ROOT server, and distributes the connection address to the branch node; when EDPoS negotiates that the current ROOT is selected as a block outlet node, the ROOT server constructs a new block of a safety main chain, pushes the context data of the branched block outlet to the branch node servers of all branch node servers to construct and sign the data of the respective branched new block, and then broadcasts the whole network by the branch nodes, wherein the branch nodes store the related data of the block outlet signing keys.
The embodiment of the application also provides a storage medium, which stores a computer program, and when the computer program is executed by a processor, the steps of the network deployment method of the blockchain out block node in the embodiment of the application are realized: the branch node server is connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT server obtains a connection address of the opposite-end branch node when negotiating handshake with the opposite-end ROOT server, and distributes the connection address to the branch node; when EDPoS negotiates that the current ROOT is selected as a block outlet node, the ROOT server constructs a new block of a safety main chain, pushes the context data of the branched block outlet to the branch node servers of all branch node servers to construct and sign the data of the respective branched new block, and then broadcasts the whole network by the branch nodes, wherein the branch nodes store the related data of the block outlet signing keys.
It should be noted that in the description of the present application, the terms "first," "second," and the like are used for descriptive purposes only and are not to be construed as indicating or implying relative importance. Furthermore, in the description of the present application, unless otherwise indicated, the meaning of "plurality" means at least two.
Any process or method descriptions in flow charts or otherwise described herein may be understood as representing modules, segments, or portions of code which include one or more executable instructions for implementing specific logical functions or steps of the process, and further implementations are included within the scope of the preferred embodiment of the present application in which functions may be executed out of order from that shown or discussed, including substantially concurrently or in reverse order, depending on the functionality involved, as would be understood by those reasonably skilled in the art of the present application.
It is to be understood that portions of the present application may be implemented in hardware, software, firmware, or a combination thereof. In the above-described embodiments, the various steps or methods may be implemented in software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, may be implemented using any one or combination of the following techniques, as is well known in the art: discrete logic circuits having logic gates for implementing logic functions on data signals, application specific integrated circuits having suitable combinational logic gates, programmable Gate Arrays (PGAs), field Programmable Gate Arrays (FPGAs), and the like.
Those of ordinary skill in the art will appreciate that all or part of the steps carried out in the method of the above-described embodiments may be implemented by a program to instruct related hardware, and the program may be stored in a computer readable storage medium, where the program when executed includes one or a combination of the steps of the method embodiments.
In addition, each functional unit in the embodiments of the present application may be integrated in one processing module, or each unit may exist alone physically, or two or more units may be integrated in one module. The integrated modules may be implemented in hardware or in software functional modules. The integrated modules may also be stored in a computer readable storage medium if implemented as software functional modules and sold or used as a stand-alone product.
The above-mentioned storage medium may be a read-only memory, a magnetic disk or an optical disk, or the like.
In the description of the present specification, a description referring to terms "one embodiment," "some embodiments," "examples," "specific examples," or "some examples," etc., means that a particular feature, structure, material, or characteristic described in connection with the embodiment or example is included in at least one embodiment or example of the present application. In this specification, schematic representations of the above terms do not necessarily refer to the same embodiments or examples. Furthermore, the particular features, structures, materials, or characteristics described may be combined in any suitable manner in any one or more embodiments or examples.
While embodiments of the present application have been shown and described above, it will be understood that the above embodiments are illustrative and not to be construed as limiting the application, and that variations, modifications, alternatives and variations may be made to the above embodiments by one of ordinary skill in the art within the scope of the application.

Claims (10)

1. A network deployment system of a blockchain out-block node, comprising a ROOT server and a branch node server, wherein:
the ROOT server is used for storing related data containing a block-out signing key, wherein the related data are used for negotiating together and safety main chain block-out;
the ROOT server is accessed into a BigBang network and is used for EDPoS negotiation on the safety main chain and data interaction with other branch nodes in the super node;
the ROOT server is used for storing data for checking the safety main chain;
the branch node server is used for organizing block data of an application branched chain and processing the branch data of the application branched chain;
the branch node servers are connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT servers acquire connection addresses of opposite-end branch nodes through handshake negotiation with the opposite-end ROOT servers, and distribute the connection addresses to the branch nodes;
when EDPoS negotiates that the current ROOT is selected as a block outlet node, the ROOT server constructs a new block of a safe main chain, pushes the context data of the branched block outlet to each branch node server, constructs and signs the data of the respective branched new block, and broadcasts the branch nodes to the whole network, wherein each branch node stores the related data containing the block outlet signature key.
2. The system of claim 1, wherein the ROOT server is connected to the ROOT servers of other supernodes and to other common nodes via P2P.
3. The system of claim 1, wherein the branch node server and the ROOT server are connected by a Socket API or MQ to interact security beacons and management data.
4. The system of claim 1, wherein each of the branch node servers is responsible for one branch chain data or multiple branch chain data.
5. The system of claim 1, wherein any two of said branch node servers are responsible for different branch chain data.
6. The system of claim 1, wherein the distributed supernodes build a cluster of branched node servers in a cascading fashion to offload application traffic loads.
7. The system of claim 3, wherein the security beacon is used to identify the security backbone and the application branch.
8. The network deployment method of the block chain out-of-block node is characterized in that the method is applied to a block chain system comprising a ROOT server and a branch node server; the method comprises the following steps:
the branch node server is connected with corresponding branch nodes of other super nodes through P2P, wherein the ROOT server obtains a connection address of the opposite-end branch node when negotiating handshake with the opposite-end ROOT server, and distributes the connection address to the branch node;
when EDPoS negotiates that the current ROOT is selected as a block-out node, the ROOT server constructs a new block of a safety main chain, pushes the context data of the branched block-out to each branch node server, and broadcasts the whole network by the branch nodes after each branch node server constructs and signs the data of the respective branched new block, wherein the branch nodes store the related data of the block-out signing keys.
9. An apparatus, comprising:
a processor, and a memory coupled to the processor;
the memory is used for storing a computer program at least for executing the network deployment method of the blockchain egress block node of claim 8;
the processor is configured to invoke and execute the computer program in the memory.
10. A storage medium storing a computer program which, when executed by a processor, performs the steps of the network deployment method of blockchain egress block nodes of claim 8.
CN202010305393.2A 2020-04-17 2020-04-17 Network deployment system, method, equipment and storage medium for block chain out-of-block node Active CN111526050B (en)

Priority Applications (1)

Application Number Priority Date Filing Date Title
CN202010305393.2A CN111526050B (en) 2020-04-17 2020-04-17 Network deployment system, method, equipment and storage medium for block chain out-of-block node

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
CN202010305393.2A CN111526050B (en) 2020-04-17 2020-04-17 Network deployment system, method, equipment and storage medium for block chain out-of-block node

Publications (2)

Publication Number Publication Date
CN111526050A CN111526050A (en) 2020-08-11
CN111526050B true CN111526050B (en) 2023-09-12

Family

ID=71912131

Family Applications (1)

Application Number Title Priority Date Filing Date
CN202010305393.2A Active CN111526050B (en) 2020-04-17 2020-04-17 Network deployment system, method, equipment and storage medium for block chain out-of-block node

Country Status (1)

Country Link
CN (1) CN111526050B (en)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105827410A (en) * 2016-03-11 2016-08-03 邓迪 Block chain transmission method and system with trusted node/satellite node construction
CN108269090A (en) * 2018-01-19 2018-07-10 中国科学院软件研究所 Based on the common recognition method and apparatus for block catenary system drawn lots at random without negotiation
CN110474765A (en) * 2019-07-29 2019-11-19 广东工业大学 A kind of quantum block chain building method proving extension based on commission equity
CN110647503A (en) * 2019-10-09 2020-01-03 重庆特斯联智慧科技股份有限公司 Distributed storage method and device

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN105827410A (en) * 2016-03-11 2016-08-03 邓迪 Block chain transmission method and system with trusted node/satellite node construction
CN108269090A (en) * 2018-01-19 2018-07-10 中国科学院软件研究所 Based on the common recognition method and apparatus for block catenary system drawn lots at random without negotiation
CN110474765A (en) * 2019-07-29 2019-11-19 广东工业大学 A kind of quantum block chain building method proving extension based on commission equity
CN110647503A (en) * 2019-10-09 2020-01-03 重庆特斯联智慧科技股份有限公司 Distributed storage method and device

Also Published As

Publication number Publication date
CN111526050A (en) 2020-08-11

Similar Documents

Publication Publication Date Title
CN110868438A (en) Block chain network system
CN109493050B (en) Transfer method based on block chain main chain and parallel multiple sub-chains
CN106452785B (en) Block chain network, branch node and block chain network application method
Kaur et al. Scalability in blockchain: Challenges and solutions
CN109472572B (en) Contract system based on block chain main chain and parallel multiple sub-chains
KR20200107772A (en) Blockchain World State Merkle Patricia Tri Subtree Update
TW201911837A (en) Method and apparatus for configuring local consensus and computer-readable storage medium
Wang et al. Performance benchmarking and optimization for blockchain systems: A survey
CN108269072A (en) For the transaction processing method and network node of block chain
CN109493052B (en) Cross-chain contract system based on main chain and parallel multiple sub-chains
CN110766410B (en) Trusted cross-chain event construction and verification method and device based on Merker tree
CN112163950A (en) Block chain network construction method and system convenient for expansion and node resource reuse and terminal equipment
US20220237153A1 (en) Synchronization processing method and related apparatus
CN112951357A (en) Block chain-based virtual medical resource transverse expansion method
Qin et al. A secure and effective construction scheme for blockchain networks
Su et al. Cross-chain exchange by transaction dependence with conditional transaction method
CN111526050B (en) Network deployment system, method, equipment and storage medium for block chain out-of-block node
CN116777631B (en) Transaction uplink method and device based on blockchain, equipment and medium
Yang et al. Generic-NFT: A generic non-fungible token architecture for flexible value transfer in web3
CN117370460A (en) Block chain storage optimization method and device based on double-chain storage
Bogdanov et al. A multilayer approach to the security of blockchain networks of the future
CN115603903A (en) Snowman consensus-based alliance chain multi-chain system and interaction and deployment method thereof
Xu et al. Ecom: Epoch randomness-based consensus committee configuration for iot blockchains
KR102386922B1 (en) Blockchain system
Chang et al. Research on epidemic data sharing model based on cross-chain mechanism

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