CN113377762A - Publishing system and method for block chain subchain - Google Patents
Publishing system and method for block chain subchain Download PDFInfo
- Publication number
- CN113377762A CN113377762A CN202010162744.9A CN202010162744A CN113377762A CN 113377762 A CN113377762 A CN 113377762A CN 202010162744 A CN202010162744 A CN 202010162744A CN 113377762 A CN113377762 A CN 113377762A
- Authority
- CN
- China
- Prior art keywords
- chain
- node
- created
- sub
- block
- 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.)
- Pending
Links
- 238000000034 method Methods 0.000 title claims abstract description 23
- 238000012795 verification Methods 0.000 claims description 12
- 230000008569 process Effects 0.000 claims description 9
- 239000000284 extract Substances 0.000 claims description 3
- 238000009825 accumulation Methods 0.000 abstract description 3
- 238000012545 processing Methods 0.000 abstract description 3
- 238000010586 diagram Methods 0.000 description 4
- 230000007246 mechanism Effects 0.000 description 2
- 238000012986 modification Methods 0.000 description 2
- 230000004048 modification Effects 0.000 description 2
- 230000001360 synchronised effect Effects 0.000 description 2
- 108091035707 Consensus sequence Proteins 0.000 description 1
- 230000001351 cycling effect Effects 0.000 description 1
- 230000007547 defect Effects 0.000 description 1
- 238000012217 deletion Methods 0.000 description 1
- 230000037430 deletion Effects 0.000 description 1
- 238000013461 design Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000007774 longterm Effects 0.000 description 1
- 239000000203 mixture Substances 0.000 description 1
- 230000004044 response Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/22—Indexing; Data structures therefor; Storage structures
- G06F16/2291—User-Defined Types; Storage management thereof
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/23—Updating
- G06F16/2379—Updates performed during online database operations; commit processing
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/27—Replication, distribution or synchronisation of data between databases or within a distributed database system; Distributed database system architectures therefor
Landscapes
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Data Mining & Analysis (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Computing Systems (AREA)
- Software Systems (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention discloses a publishing system and a publishing method for a block chain, which comprise a node manager, a created block manager and a sub-chain manager; the system generates a blank created block through a created block manager, generates a sub-chain issuing transaction, submits the transaction to a block chain, receives the transaction through a node manager, verifies the transaction and executes the transaction, completes list expansion of created nodes, synchronizes sub-chain data and completes starting of the sub-chain. The invention realizes the function of keeping the processing logic consistent among different coding chains with different architectures, and solves the problem of inconsistent data caused by inconsistent accumulation of small variables among chains and nodes in the chains.
Description
Technical Field
The invention relates to the technical field of block chains, in particular to a system and a method for releasing a block chain subchain.
Background
The block chain is an important component of future society, different social activity scenes are born by different chains, the intercommunication between the chains is necessary, due to the characteristic that the block chain is open, anyone can develop a node to access a block chain network, different nodes can have different behavior modes and different parameter preferences, the block chain is not strongly restricted to specific execution details due to the top-level design characteristics of a block chain consensus mechanism in the actual operation process, different rules are adopted among different nodes to process data in most of the time, the data cannot be immediately identified by other nodes through the consensus mechanism, the differences are always discovered when the differences influence the correctness of the consensus rule, and the errors are not corrected in time, or a traceable time of the service level has elapsed.
If the whole block chain is accessed by uniformly adopting a node of one version, the reliability of the block chain network as a whole is changed into a single one, and as long as the version has a major defect, the whole network can be broken down. The same applies to the layers between chains, and no matter between the main chain and the main chain or between the main chain and the sub-chain, the problem of intercommunication caused by different structures between different chains still exists. For the problem of whether multiple versions are used or not, different results are caused in different access layers, so that how to ensure the consistency of data processing between nodes, not influence the consistency of data between chains, and not restrict the requirements of node development versions becomes an urgent problem to be solved.
Disclosure of Invention
The invention aims to provide a publishing system and a publishing method for a block chain subchain.
A publishing system for a block chain comprises a node manager, a created block manager and a sub-chain manager; it is characterized in that: the node manager is used for managing the nodes owned by the current network, and distinguishing the current sub-chain to which the nodes belong and the positions of the created nodes of the specific sub-chain; the created block manager is used for managing created block information, creating created blocks, managing different created blocks, storing block information of different chains, extracting execution parameters from the created blocks during execution, and verifying whether the received blocks of other people meet the created block requirements; the child chain manager is used for defining and managing child chain information, creating blocks are generated from the created block manager before defining the child chain, all variable quantities in the current child chain execution process are defined as parameters before the creation is carried out, the parameters are placed into the created blocks, the child chain can be defined after the creation blocks are generated, the parameter information indicating the current child chain is defined in the definition information, a created node of the current child chain is designated, created blocks used by the current child chain are designated, and all the information is stored in the current child chain;
the system generates a blank created block through a created block manager, generates a sub-chain issuing transaction, submits the transaction to a block chain, receives the transaction through a node manager, verifies the transaction and executes the transaction, completes list expansion of created nodes, and synchronizes sub-chain data, thereby completing starting of the sub-chain.
Further, the node manager comprises a node searching module, a node information module, a node consensus mode and a node expansion module;
the node searching module is used for searching nodes in a network;
the node information module is used for recording the basic information of the node, storing the network information corresponding to the node and selecting the recorded information data according to different upper-layer applications;
the node consensus module is used for performing consensus on the effectiveness of the nodes, judging the effectiveness of data by adopting a plurality of nodes together in the block chain environment, and placing the nodes judged to be effective into an effective node range to dynamically manage the nodes;
the node expansion module is used for expanding the node list of the node according to the node lists of other nodes, the node lists acquired from other nodes are used as the search address list of the node search module, and the node list is further expanded according to the expanded node list.
Further, the searching mode of the node searching module is to search according to locally known nodes to confirm the availability of the nodes, and can also be to perform blind scanning on the network without any known nodes.
Furthermore, the creating block manager comprises a creating parameter configuration module, a creating block generation module and a creating block verification module;
the creation parameter configuration module is used for configuring all parameters required by a chain in the running process, and the parameters are components for starting a node;
the creation block generation module is used for generating a creation block, and the creation block is used for determining who a creation account of a chain is, and the assets and the consensus requirements of the chain;
the created block checking module is used for verifying whether the created block started by the local node is tampered and whether blocks sent by other nodes meet the consensus requirement of the created block.
Further, the sub-chain manager comprises a sub-chain list module, a sub-chain node module and a sub-chain synchronization module;
the sub-chain list module is used for creating basic information of the sub-chain and providing query of the sub-chain information for other modules;
the sub-chain node module is used for managing the nodes searched by the current chain, and the nodes refer to the nodes running the appointed created blocks of the current sub-chain;
and the sub-chain synchronization module is used for keeping synchronization with the main chain information, and synchronizing and responding when the main chain changes the sub-chain information or the creation block information.
Further, the sub-chains comprise public chains, private chains and alliance chains; sub-chains of public chains in the sub-chain list module can only be newly added and cannot be modified or deleted; the private chain and the alliance chain can be modified and deleted according to requirements; and the public chain in the sub-chain synchronization module is only used for synchronizing the newly added sub-chain information, and the information of the existing chain is modified or deleted in the alliance chain and the private chain according to the requirement.
A publishing method for a blockchain subchain, comprising the steps of:
s1 the created block manager generates a blank created block, fills in created parameter information, puts created parameter information into the blank created block, signs the created block, generates a sub-chain issue transaction, puts created block into the sub-chain issue transaction, signs the sub-chain issue transaction, and submits the transaction to a block chain;
s2 the node manager receives the transaction, analyzes the transaction by the blockchain, and checks the validity of the transaction;
s3, the created block manager verifies the legality of the created block carried in the transaction, and discards the transaction when all the verifications are passed; after the whole verification is passed, the transaction is executed;
s4 created block manager: other nodes switch the created blocks to the created blocks of the sub-chain and start the nodes; analyzing the contents of the created blocks for the nodes by the created block manager, and loading the parameters of the created blocks for the nodes;
s5 node manager: searching created nodes according to the definition of created blocks for the nodes, requesting the created nodes for the node condition of the child chain, acquiring a node list, and circulating the node list;
and the S6 node manages and completes the list expansion of the founding node, and the node synchronizes subchain data to the node in the node list to complete the starting of the subchain.
Further, the specific step of executing the transaction after all verification of S3 is as follows:
s31 creating a block right to execute the transaction;
s32 the sub-chain manager adds the information of a sub-chain locally;
s33 the created blocks manager saves the created blocks locally, the block chain types the transaction into blocks, the blocks are signed and broadcast to the block network;
s34 the nodes in the network receive the block to complete the creation of a chain.
Further, the step of S5 cycling the node list includes the following specific steps:
s51, the node manager extracts the node information and requests the node to return the node list of the child chain;
the S52 node checks whether the nodes of the list are available in turn;
and the S53 node merges the available list and the own list to complete the node list expansion of the node.
Compared with the prior art, the method and the device have the advantages that the function of keeping the processing logic between different coding chains with different architectures consistent is realized, and the problem of inconsistent data caused by inconsistent accumulation of small variables between chains and nodes in the chains is solved.
Drawings
FIG. 1 is a schematic diagram of a distribution system for block chain sub-chains according to the present invention
FIG. 2 is a schematic diagram of the node manager according to the present invention;
FIG. 3 is a schematic diagram of the components of the created blocks manager according to the present invention;
FIG. 4 is a schematic diagram of the sub-chain manager according to the present invention;
FIG. 5 is a schematic flow chart of a method for distributing blockchain subchains according to the present invention;
FIG. 6 is a schematic flow chart of S3 according to the present invention;
FIG. 7 is a schematic flow chart of S5 according to the present invention;
wherein: 100 node manager, 200 creating block manager, 300 child chain manager; a 101 node searching module, a 102 node information module, a 103 node consensus mode and a 104 node expanding module; a 201-generation parameter configuration module, a 202-generation block generation module and a 203-generation block verification module; 301 sub-chain list module, 302 sub-chain node module, 303 sub-chain synchronization module.
Detailed Description
The invention is described in further detail below with reference to the figures and specific examples. It should be noted that the technical features involved in the embodiments of the present invention described below may be combined with each other as long as they do not conflict with each other.
As shown in fig. 1, a publishing system for a block chain child includes a node manager 100, a created block manager 200, a child chain manager 300; the method is characterized in that: the node manager 100 is configured to manage nodes owned by a current network, and the node manager 100 distinguishes positions of a current child chain to which the node belongs and a created node of a specific child chain; the created block manager 200 is used for managing created block information, creating created blocks, managing different created blocks, storing block information of different chains, extracting execution parameters from the created blocks during execution, and verifying whether the received blocks of other people meet the requirements of the created blocks; the child chain manager 300 is configured to define and manage child chain information, generate a created block from the created block manager 200 before defining a child chain, define all variable quantities in a current child chain execution process as parameters before generating, place the parameters in the created block, define the child chain after the created block is generated, specify parameter information of the current child chain in the definition information, specify a created node of the current child chain, specify created blocks used by the current child chain, and store all the information in the current child chain;
the system generates a blank created block through the created block manager 200, expands the boundary of the traditional created block which only stores the initial block information, takes all variable quantities which can influence the correctness of the consensus result due to short-term and long-term accumulation of a block chain in the whole operation process as created parameters, blends the created parameters into the created block, and incorporates the created parameters into the signature range of the created block to form a complete created block; generating a sub-chain release transaction, and putting the complete created blocks into another chain for storage so as to ensure that the created blocks are consistent at any time; the transaction is submitted to the blockchain, received through the node manager 100, verified and executed by the founder block manager 200, and the list extension of the founder nodes is completed, and the child chain data is synchronized, thereby completing the starting of the child chain.
As shown in fig. 2, the node manager 100 includes a node search module 101, a node information module 102, a node consensus pattern 103, and a node expansion module 104;
the node searching module 101 is configured to search for a node in a network;
the node information module 102 is configured to record basic information of a node, store network information corresponding to the node, and select recorded information data according to different upper-layer applications;
the node consensus module 103 is configured to perform consensus on validity of nodes, determine validity of data by using a plurality of nodes together in the block chain environment, determine that a valid node is placed in a valid node range, and dynamically manage the node;
the node expansion module 104 is configured to expand its own node list according to the node lists of other nodes, where the node lists obtained from other nodes are used as the search address list of the node search module 101, and the node list is further expanded according to the expanded node list.
The node expansion module 104 is configured to expand its own node list according to node lists of other nodes, where the node lists obtained from other nodes are not necessarily accessible lists of its own node, but are useful for increasing network search speed, and these nodes, although they cannot be taken directly, can be used as a search address list of the node search module 101, and then quickly expand the range of available nodes, and then further expand the node list according to the expanded node list.
The node searching module 101 performs searching according to locally known nodes to confirm the availability, and may perform blind scanning on the network without any known nodes.
As shown in fig. 3, the created-world block manager 200 includes a created-world parameter configuration module 201, a created-world block generation module 202, and a created-world block verification module 203;
the created parameter configuration module 201 is configured to configure all parameters required by a chain in the running process, where the parameters are components of a node start;
the created block generation module 202 is used to generate a created block that will determine who the created account of a chain is, and the chain's assets and consensus requirements;
the created block checking module 203 is used for verifying whether the created block started by the local node is tampered and whether blocks sent by other nodes meet the consensus requirement of the created block.
As shown in fig. 4, the child chain manager 300 includes a child chain list module 301, a child chain node module 302, and a child chain synchronization module 303;
the sub-chain list module 301 is configured to create basic information of a sub-chain and provide query of sub-chain information for other modules;
the child chain node module 302 is configured to manage nodes searched by a current chain, where the nodes refer to nodes running a specified creation block of the current child chain;
the sub-chain synchronization module 303 is configured to keep synchronization with the main chain information, and perform synchronization and response when the main chain changes the sub-chain information or the founding block information.
The sub-chains comprise public chains, private chains and alliance chains; sub-chains of the public chains in the sub-chain list module 302 can only be added, and cannot be modified or deleted; the private chain and the alliance chain can be modified and deleted according to requirements; the public chain in the sub-chain synchronization module 302 is only used for synchronizing the newly added sub-chain information, and the modification or deletion information of the existing chain is synchronized between the alliance chain and the private chain as required.
As shown in fig. 5 to 7, a method for distributing a blockchain subchain includes the following steps:
s1 the created block manager generates a blank created block, fills in created parameter information, puts created parameter information into the blank created block, signs the created block, generates a sub-chain issue transaction, puts created block into the sub-chain issue transaction, signs the sub-chain issue transaction, and submits the transaction to a block chain;
s2 the node manager receives the transaction, analyzes the transaction by the blockchain, and checks the validity of the transaction;
s3, the created block manager verifies the legality of the created block carried in the transaction, and discards the transaction when all the verifications are passed; after the whole verification is passed, the transaction is executed; the specific steps of executing the transaction after all verification of S3 is passed are as follows: s31 creating a block right to execute the transaction; s32 the sub-chain manager adds the information of a sub-chain locally; s33 the create block manager locally saves the create block, the block chain types the transaction into blocks, the blocks are signed and broadcast to the block network; s34 the nodes in the network receive the block to complete the establishment of a chain;
s4 created block manager: other nodes switch the created blocks to the created blocks of the sub-chain and start the nodes; analyzing the contents of the created blocks for the nodes by the created block manager, and loading the parameters of the created blocks for the nodes;
s5 node manager: searching created nodes according to the definition of created blocks for the nodes, requesting the created nodes for the node condition of the child chain, acquiring a node list, and circulating the node list; the specific steps of the S5 loop through the node list are as follows: s51 the node manager extracts the node information and requests the node to return the node list of the child chain; the S52 node checks whether the nodes of the list are available in turn; the S53 node merges the available list and the list of the node to complete the node list expansion of the node;
and the S6 node manages and completes the list expansion of the founding node, and the node synchronizes subchain data to the node in the node list to complete the starting of the subchain.
The above-mentioned embodiments are only preferred embodiments of the present invention, and do not limit the technical scope of the present invention, so that the changes and modifications made by the claims and the specification of the present invention should fall within the scope of the present invention.
Claims (9)
1. A publishing system for a block chain comprises a node manager, a created block manager and a sub-chain manager; the method is characterized in that: the node manager is used for managing the nodes owned by the current network, and distinguishing the current sub-chain to which the nodes belong and the positions of the created nodes of the specific sub-chain; the created block manager is used for managing created block information, creating created blocks, managing different created blocks, storing block information of different chains, extracting execution parameters from the created blocks during execution, and verifying whether the received blocks of other people meet the created block requirements; the child chain manager is used for defining and managing child chain information, creating blocks are generated from the created block manager before the child chain is defined, all variable quantities in the current child chain execution process are defined as parameters before the child chain is generated and are placed into the created blocks, the child chain can be defined after the created blocks are generated, parameter information indicating the current child chain in the definition information is designated, a created node of the current child chain is designated, created blocks used by the current child chain are designated, and all the information is stored in the current child chain;
the system generates a blank created block through a created block manager, generates a sub-chain issuing transaction, submits the transaction to a block chain, receives the transaction through a node manager, verifies the transaction and executes the transaction, completes list expansion of created nodes, synchronizes sub-chain data and completes starting of the sub-chain.
2. A publication system for a blockchain sub-chain as in claim 1, wherein: the node manager comprises a node searching module, a node information module, a node consensus mode and a node expansion module;
the node searching module is used for searching nodes in a network;
the node information module is used for recording the basic information of the node, storing the network information corresponding to the node and selecting the recorded information data according to the different upper-layer applications;
the node consensus module is used for performing consensus on the effectiveness of the nodes, judging the effectiveness of data by adopting a plurality of nodes together in the block chain environment, and placing the nodes judged to be effective into an effective node range to dynamically manage the nodes;
the node expansion module is used for expanding the node list of the node according to the node lists of other nodes, the node lists acquired from other nodes are used as the search address list of the node search module, and the node list is further expanded according to the expanded node list.
3. A publication system for a blockchain sub-chain as in claim 2, wherein: the searching mode of the node searching module is to search according to locally known nodes to confirm the availability of the nodes, and can also be to perform blind scanning on the network without any known nodes.
4. A publication system for a blockchain sub-chain as in claim 1, wherein: the created block manager comprises a created parameter configuration module, a created block generation module and a created block verification module;
the creation parameter configuration module is used for configuring all parameters required by a chain in the running process, and the parameters are components for starting a node;
the creation block generation module is used for generating a creation block, and the creation block is used for determining who a creation account of a chain is, and the assets and the consensus requirements of the chain;
the created block checking module is used for verifying whether the created block started by the local node is tampered and whether blocks sent by other nodes meet the consensus requirement of the created block.
5. A publication system for a blockchain sub-chain as in claim 1, wherein: the sub-chain manager comprises a sub-chain list module, a sub-chain node module and a sub-chain synchronization module;
the sub-chain list module is used for creating basic information of the sub-chain and providing query of the sub-chain information for other modules;
the sub-chain node module is used for managing the nodes searched by the current chain, and the nodes refer to the nodes running the appointed created blocks of the current sub-chain;
and the sub-chain synchronization module is used for keeping synchronization with the main chain information, and synchronizing and responding when the main chain changes the sub-chain information or the creation block information.
6. A publication system for a blockchain sub-chain as in claim 5, wherein: the sub-chains comprise public chains, private chains and alliance chains; sub-chains of public chains in the sub-chain list module can only be newly added and cannot be modified or deleted; the private chain and the alliance chain can be modified and deleted according to requirements; and the public chain in the sub-chain synchronization module is only used for synchronizing the newly added sub-chain information, and the information of the existing chain is modified or deleted in the alliance chain and the private chain according to the requirement.
7. A publishing method for a blockchain subchain, comprising the steps of:
s1 the created block manager generates a blank created block, fills in created parameter information, puts created parameter information into the blank created block, signs the created block, generates a sub-chain issue transaction, puts created block into the sub-chain issue transaction, signs the sub-chain issue transaction, and submits the transaction to a block chain;
s2 the node manager receives the transaction, analyzes the transaction by the blockchain, and checks the validity of the transaction;
s3, the created block manager verifies the legality of the created block carried in the transaction, and discards the transaction when all the verifications are passed; after all the checks pass, executing the transaction;
s4 created block manager: other nodes switch the created blocks to the created blocks of the sub-chain and start the nodes; analyzing the contents of the created blocks for the nodes by the created block manager, and loading the parameters of the created blocks for the nodes;
s5 node manager: searching created nodes according to the definition of created blocks for the nodes, requesting the created nodes for the node condition of the sub-chain, acquiring a node list, and circulating the node list;
and the S6 node manages and completes the list expansion of the founding node, and the node synchronizes the sub-chain data to the node in the node list to complete the starting of the sub-chain.
8. A method of publishing a blockchain as recited in claim 7, wherein: the specific steps of executing the transaction after all verification of S3 is passed are as follows:
s31 creating a block right to execute the transaction;
s32 the sub-chain manager adds the information of a sub-chain locally;
s33 the created blocks manager saves the created blocks locally, the block chain types the transaction into blocks, the blocks are signed and broadcast to the block network;
s34 the nodes in the network receive the block to complete the creation of a chain.
9. A method of publishing a blockchain as recited in claim 7, wherein: the specific steps of the S5 loop through the node list are as follows:
s51, the node manager extracts the node information and requests the node to return the node list of the child chain;
the S52 node checks whether the nodes of the list are available in turn;
and the S53 node merges the available list and the own list to complete the node list expansion of the node.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010162744.9A CN113377762A (en) | 2020-03-10 | 2020-03-10 | Publishing system and method for block chain subchain |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010162744.9A CN113377762A (en) | 2020-03-10 | 2020-03-10 | Publishing system and method for block chain subchain |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN113377762A true CN113377762A (en) | 2021-09-10 |
Family
ID=77568826
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010162744.9A Pending CN113377762A (en) | 2020-03-10 | 2020-03-10 | Publishing system and method for block chain subchain |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113377762A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114363349A (en) * | 2021-12-31 | 2022-04-15 | 支付宝(杭州)信息技术有限公司 | Starting method and device of block chain subnet |
Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107612973A (en) * | 2017-08-18 | 2018-01-19 | 暨南大学 | Block chain structure, generation method and transaction verification method for intelligent sliding moved end |
| US20190258971A1 (en) * | 2018-02-20 | 2019-08-22 | Tyson York Winarski | Blockchain project management with process feedback control |
| CN110557420A (en) * | 2018-06-01 | 2019-12-10 | 厦门本能管家科技有限公司 | operation method and system of independent sub-chains |
-
2020
- 2020-03-10 CN CN202010162744.9A patent/CN113377762A/en active Pending
Patent Citations (3)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107612973A (en) * | 2017-08-18 | 2018-01-19 | 暨南大学 | Block chain structure, generation method and transaction verification method for intelligent sliding moved end |
| US20190258971A1 (en) * | 2018-02-20 | 2019-08-22 | Tyson York Winarski | Blockchain project management with process feedback control |
| CN110557420A (en) * | 2018-06-01 | 2019-12-10 | 厦门本能管家科技有限公司 | operation method and system of independent sub-chains |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN114363349A (en) * | 2021-12-31 | 2022-04-15 | 支付宝(杭州)信息技术有限公司 | Starting method and device of block chain subnet |
| CN114363349B (en) * | 2021-12-31 | 2024-04-02 | 支付宝(杭州)信息技术有限公司 | Block chain sub-network starting method and device |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP3678346A1 (en) | Blockchain smart contract verification method and apparatus, and storage medium | |
| CN107562513B (en) | Intelligent contract life cycle management method based on JAVA | |
| CN101315607B (en) | There is how synchronous transaction module control flow | |
| CN110046523B (en) | Intelligent contract checking method and device and electronic equipment | |
| JP2017514218A (en) | Running third-party applications | |
| CN110276074B (en) | Distributed training method, device, equipment and storage medium for natural language processing | |
| CN110557420B (en) | Operation method and system of independent sub-chains | |
| CN111158674A (en) | Component management method, system, device and storage medium | |
| CN109542767A (en) | Automated testing method, device, computer equipment and storage medium based on block chain | |
| CN113448862B (en) | Software version testing method and device and computer equipment | |
| CN111711623A (en) | Data verification method and device | |
| CN106095483A (en) | The Automation arranging method of service and device | |
| CN113535225A (en) | Environment configuration file processing method, device, equipment and medium of application software | |
| CN113377762A (en) | Publishing system and method for block chain subchain | |
| CN117725047A (en) | Service index processing method, device, equipment and storage medium | |
| Lascu et al. | Automatic deployment of component-based applications | |
| CN110502242A (en) | Code automatic generation method, device, computer equipment and storage medium | |
| CN111274117A (en) | Recommended service experiment and management method, device and system thereof | |
| CN112181599A (en) | Model training method, device and storage medium | |
| KR101996029B1 (en) | Method for designing network service descriptor in network function virtualization system, managing the network function descriptor and system thereof | |
| US8589360B2 (en) | Verifying consistency levels | |
| CN112256978B (en) | Data processing method, device and medium based on data model | |
| CN111861613B (en) | Electronic lock operation recording method and device | |
| CN112099879A (en) | Configuration information management method and device, computer equipment and storage medium | |
| CN111930715A (en) | Data migration method and device, computer equipment and storage medium |
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 |