CN114465887B - Block chain configuration management method and device based on git - Google Patents
Block chain configuration management method and device based on git Download PDFInfo
- Publication number
- CN114465887B CN114465887B CN202111591157.2A CN202111591157A CN114465887B CN 114465887 B CN114465887 B CN 114465887B CN 202111591157 A CN202111591157 A CN 202111591157A CN 114465887 B CN114465887 B CN 114465887B
- Authority
- CN
- China
- Prior art keywords
- configuration
- blockchain
- git
- block chain
- consensus 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
- 238000007726 management method Methods 0.000 title claims abstract description 28
- 238000000034 method Methods 0.000 claims abstract description 47
- 239000003999 initiator Substances 0.000 claims abstract description 25
- 230000008569 process Effects 0.000 claims abstract description 13
- 230000004048 modification Effects 0.000 claims description 29
- 238000012986 modification Methods 0.000 claims description 29
- 238000012550 audit Methods 0.000 claims description 11
- 238000012545 processing Methods 0.000 claims description 9
- 230000000977 initiatory effect Effects 0.000 claims description 5
- 238000012552 review Methods 0.000 claims description 3
- 238000010586 diagram Methods 0.000 description 8
- 238000011144 upstream manufacturing Methods 0.000 description 6
- 230000006870 function Effects 0.000 description 4
- 239000010979 ruby Substances 0.000 description 4
- 229910001750 ruby Inorganic materials 0.000 description 4
- 230000005540 biological transmission Effects 0.000 description 2
- 238000005516 engineering process Methods 0.000 description 2
- 230000003993 interaction Effects 0.000 description 2
- 230000002093 peripheral effect Effects 0.000 description 2
- 238000004458 analytical method Methods 0.000 description 1
- 238000003491 array Methods 0.000 description 1
- 230000003139 buffering effect Effects 0.000 description 1
- 230000001413 cellular effect Effects 0.000 description 1
- 230000008859 change Effects 0.000 description 1
- 238000010367 cloning Methods 0.000 description 1
- 238000004590 computer program Methods 0.000 description 1
- 238000012790 confirmation Methods 0.000 description 1
- 238000001514 detection method Methods 0.000 description 1
- 230000000694 effects Effects 0.000 description 1
- 230000006872 improvement Effects 0.000 description 1
- 230000002452 interceptive effect Effects 0.000 description 1
- 230000007246 mechanism Effects 0.000 description 1
- 238000011022 operating instruction Methods 0.000 description 1
- 230000003287 optical effect Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000003068 static effect Effects 0.000 description 1
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/0813—Configuration setting characterised by the conditions triggering a change of settings
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F21/00—Security arrangements for protecting computers, components thereof, programs or data against unauthorised activity
- G06F21/60—Protecting data
- G06F21/602—Providing cryptographic facilities or services
-
- 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
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
- Y02D—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN INFORMATION AND COMMUNICATION TECHNOLOGIES [ICT], I.E. INFORMATION AND COMMUNICATION TECHNOLOGIES AIMING AT THE REDUCTION OF THEIR OWN ENERGY USE
- Y02D10/00—Energy efficient computing, e.g. low power processors, power management or thermal management
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Theoretical Computer Science (AREA)
- Computer Hardware Design (AREA)
- General Health & Medical Sciences (AREA)
- Bioethics (AREA)
- Computer Security & Cryptography (AREA)
- Software Systems (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Health & Medical Sciences (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The embodiment of the specification discloses a block chain configuration management method based on git, which comprises the following steps: the block chain initiator creates a git warehouse main branch and initializes the block chain configuration; creating a supermanager account for the blockchain; a block chain consensus node participant pulls the latest block chain configuration and creates an account of the consensus node; the consensus node participant pulls the latest block chain configuration and sets key attribute parameters of the consensus node; the blockchain super administrator pulls the latest blockchain configuration and creates a CA certificate; the consensus node pulls the latest blockchain configuration, creates a CA certificate of the consensus node and initiates a signature request; the blockchain super manager processes signature requests of the consensus nodes; the blockchain configuration is generated. According to the invention, the git is used as a source code cooperation management tool to cooperate and manage configuration files of the blockchain, so that the accuracy and efficiency of configuration of the blockchain are improved.
Description
Technical Field
The present disclosure relates to the field of computer software technologies, and in particular, to a method and apparatus for managing blockchain configuration based on git, an electronic device, and a storage medium.
Background
The blockchain configuration relates to a plurality of participants of the blockchain, and due to the decentralization characteristic of the blockchain, a great amount of information interaction can be generated among all nodes and the participants in the blockchain operation process, and the blockchain configuration can be correspondingly modified, so that the management of the blockchain configuration is a scene of multiparty collaboration. For example, during the operation of the blockchain, the blockchain configuration changes, there are newly added nodes, node exit may occur, and there may be changes in key attribute parameters such as IP address, port, domain, etc. of the nodes. How to apply these changes, how to synchronize the changes to other nodes, how to record historic changes … …, and how to address these needs is critical to accurately and efficiently accomplish blockchain configuration.
Disclosure of Invention
An object of embodiments of the present specification is to address the above problems, and to provide a method, apparatus, electronic device, and storage medium for deploying cloud native blockchain software in Kubernetes.
In order to solve the above technical problems, the embodiments of the present specification are implemented as follows:
in a first aspect, a git-based blockchain configuration management method is provided, wherein a blockchain initiator creates a git warehouse for storing blockchain configurations; registering a git account number by a blockchain participant, wherein the operation authority of the git account number to the git warehouse is set by the blockchain initiator; comprising the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest blockchain configuration, sets key attribute parameters of the consensus node, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the blockchain super administrator pulls the latest blockchain configuration, creates a CA certificate, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the consensus node pulls the latest blockchain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the blockchain configuration and submits the blockchain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the blockchain configuration is generated such that the blockchain participant pulls the latest blockchain configuration to complete the corresponding node configuration.
In a second aspect, a git-based blockchain configuration management device is provided, wherein a git warehouse is created by a blockchain initiator for storing blockchain configurations; registering a git account number by a blockchain participant, wherein the operation authority of the git account number to the git warehouse is set by the blockchain initiator; comprising the following steps:
the block chain configuration initialization module is used for creating a git warehouse main branch by the block chain initiator, initializing the block chain configuration and submitting the block chain configuration to the git warehouse;
the block chain manager module is used for creating a super manager account of the block chain, updating the block chain configuration and submitting the block chain configuration to the git warehouse;
the consensus node git account configuration module is used for pulling the latest blockchain configuration by a blockchain consensus node participant, creating an account of the consensus node, updating the blockchain configuration and submitting the updated blockchain configuration to the git warehouse;
the consensus node parameter configuration module is used for pulling the latest blockchain configuration by the consensus node participant, setting key attribute parameters of the consensus node, updating the blockchain configuration and submitting the updated blockchain configuration to the git warehouse;
the block chain super manager pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the updated block chain configuration to the git warehouse;
the consensus node CA certificate configuration module is used for pulling the latest blockchain configuration, creating a CA certificate of the consensus node and initiating a signature request, updating the blockchain configuration and submitting the updated blockchain configuration to the git warehouse;
the signature request processing module is used for processing the signature request of the consensus node by the blockchain super administrator, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
and the block chain configuration generating module is used for generating the block chain configuration so that the block chain participant can pull the latest block chain configuration to complete the corresponding node configuration.
In a third aspect, an electronic device is provided, comprising: a processor; and
a memory arranged to store computer executable instructions which, when executed, cause the processor to perform the method of the first aspect.
In a fourth aspect, a computer readable storage medium is presented, the computer readable storage medium storing one or more programs, which when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the method of the first aspect.
The specification can achieve at least the following technical effects:
aiming at the characteristic that the blockchain configuration is commonly completed by multi-party cooperation, the invention adopts git as a cooperation management tool of the blockchain configuration, after each piece of information is submitted by the blockchain participants, the blockchain participants can be combined to the git warehouse only through examination of all the participants, and meanwhile, the confidentiality setting is carried out on the blockchain configuration submitted to the git warehouse by combining with the information confidentiality requirement, so that the accuracy, the synchronism and the efficiency of the blockchain configuration are improved.
Drawings
In order to more clearly illustrate the embodiments of the present description 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 below, it being obvious that the drawings in the following description are only some of the embodiments described in the present description, 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 block chain configuration management method based on git according to an embodiment of the present disclosure.
FIG. 2 is a second diagram illustrating a block chain configuration management method based on git according to an embodiment of the present disclosure.
FIG. 3 is a third exemplary block chain configuration management method based on git according to the present embodiment of the disclosure.
FIG. 4 is a schematic diagram of a git-based blockchain configuration management device according to an embodiment of the present disclosure.
FIG. 5 is a diagram illustrating a second exemplary git-based blockchain configuration management device according to the embodiments of the present disclosure.
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present disclosure.
Detailed Description
In order to make the technical solutions in the present specification better understood by those skilled in the art, the technical solutions in the embodiments of the present specification will be clearly and completely described below with reference to the drawings in the embodiments of the present specification, and it is obvious that the described embodiments are only some embodiments of the present specification, not all embodiments. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are intended to be within the scope of the present disclosure.
A detailed description of a git-based blockchain configuration management scheme is provided below by way of specific examples.
Key terms
git: is an open-source distributed version control system and can effectively and rapidly process project version management from small to very large. The greatest difference between distributed and centralized is that developers can commit to the local, each by cloning (Git clone), copying a complete Git repository on the local machine. Github is a website for a wide range of developers to open their own code and also provides payment functions for proprietary warehouses, while the version control software it employs is git. Similarly, gitLab is an open source project for a warehouse management system, uses Git as a code management tool, and builds a Web service on this basis. The basic Git workflow is: modifying the file in the working area; selectively buffering the changes you want to commit next so that only the portion of the changes will be added to the scratch pad; and submitting the update, finding the file in the temporary storage area, and permanently storing the snapshot in the Git directory. If a file of a particular version is saved in the Git directory, it is in the committed state. If the file is modified and placed in the scratch pad, it is in the scratch pad state. If a modification has been made since the last detection but has not been placed in the staging area, it is a modified state.
PR: i.e., pull Request operation, can be considered as a distributed code audit merge tool, one of the most commonly used tools for git. Taking the Github as an example, the basic operations of PR include: for a project developer, firstly, turning a Fork project into a project under the Github of the project developer; then creating a new branch after using a command line clone to locally treat the project; associating a remote repository; after the project is modified, submitting the modification to the project of the remote project developer just for k; and submitting the changes in the project developer fork project to the project of the main developer in a PR mode to complete PR.
Example 1
Referring to fig. 1, a schematic diagram of a block chain configuration management method based on git in an embodiment of the present invention is shown. It is first noted that the blockchain configuration involves multiple participants and information interaction with each other, and that the configuration of the chain is modified accordingly. Therefore, the method is a multiparty cooperation scene, and the problem of the existing scheme can be well solved by using the git management blockchain configuration, and particularly the following advantages of the git are exerted: (1) The git can set permissions, only allowing participants to view and modify the repository of the storage chain configuration; (2) The git is pushed to be locally modified to be remote through a pull/push command, so that the local modification is safe and feedback is provided; (3) git can examine the modification through PR function, and one or more participants can be combined after confirmation; (4) Other participants can pull the latest configuration through the gitpull; (5) The git itself can record the history of modifications, as well as when and what modifications were made by anyone. Meanwhile, because the block chain configuration has sensitive information such as IP addresses, ports and the like, the risk of information leakage can be avoided by establishing a private git warehouse; configuration modifications may also be more conveniently managed through graphical interfaces provided by gitlab, gitsub, etc.
Based on the above analysis, the method of the embodiment of the present invention is performed according to the following procedure. The embodiment is described by taking Github as an example, but the method of the invention is realized by other platforms such as GitLab and the like under the condition that the scheme of the invention is not violated, and the method is also applicable to the scheme of the invention. First, a git warehouse is created by the blockchain initiator for use in maintaining blockchain configurations. Secondly, the blockchain participants register the git accounts respectively, and the operation authority of the git accounts to the git warehouse is set by the blockchain initiator. Alternatively, the gitflow may be chosen, the main branch set only allowing merging in PR and requiring agreement by all participants. In addition, in one embodiment, because the blockchain configuration can involve sensitive information such as IP addresses, port numbers and the like of the consensus nodes, a configuration tool closed-config can be selected to simultaneously generate confidential information and non-confidential information in the scheme of the invention, and only the non-confidential information is submitted to a git warehouse through a git's. Gitigore mechanism. After the preamble work is done, the method comprises the following steps:
step 101: the blockchain initiator creates a git warehouse main branch and initializes the blockchain configuration and submits the blockchain configuration to the git warehouse.
Bash
$git clone [email protected]:rink1969/chain-config-example.git
$cd chain-config-example
# Create directory Structure
$cloud-config init-chain
# set up warehouse to prevent information leakage caused by careless submission of confidential information
$echo"test-chain/accounts/*/">.gitignore
$echo"test-chain/ca_cert/key.pem">>.gitignore
$echo"test-chain/certs/*/key.pem">>.gitignore
$echo"test-chain-*">>.gitignore
$touch test-chain/accounts/.gitkeep
$touch test-chain/ca_cert/.gitkeep
$touch test-chain/certs/.gitkeep
Configuration of# initialization chain
$cloud-config init-chain-config
Initialization configuration of a# commit chain
$git add.
$git push
Step 102: and creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse.
PowerShell
$git clone [email protected]:rink1969/chain-config-example.git
$cd chain-config-example
# create admin branch and modify chain configuration
$git checkout-b admin
$cloud-config new-account
key_id:1,address:29e66df76b1d8b7a2cece994a2d3a8b7704a8281
$cloud-config set-admin--admin 29e66df76b1d8b7a2cece994a2d3a8b7704a8281
# submit (because of the previous. Gitigore, account information will not be submitted up, only the modifications to the configuration file will be submitted)
$git diff
diff--git a/test-chain/chain_config.toml b/test-chain/chain_config.toml
index 5709e4b..975f78b 100644
---a/test-chain/chain_config.toml
+++b/test-chain/chain_config.toml
@@-29,7+29,7@@prevhash＝'0x0000000000000000000000000000000000000000000000000000000000000000'
timestamp＝1638081449922
[system_config]
-admin＝”
+admin＝'29e66df76b1d8b7a2cece994a2d3a8b7704a8281'
block_interval＝3
block_limit＝100
chain_id＝'63586a3c0255f337c77a777ff54f0040b8c388da04f23ecee6bfd4953a6512b4'
$git add.
$git commit-m"set admin"
$git push--set-upstream origin admin
Step 103: and pulling the latest blockchain configuration by a blockchain consensus node participant, creating an account of the consensus node, updating the blockchain configuration and submitting the updated blockchain configuration to the git warehouse.
Assuming that the blockchain has 2 consensus nodes in total, consensus node0 operates as follows, for example:
Bash
$git clone [email protected]:rink1969/chain-config-example.git
$cd chain-config-example
creation of node0 branch and modification of chain configuration
$git checkout-b node0
$cloud-config new-account
key_id:1,address:cfc8e87ae610452da9a24c87db2981f2e1f192fb
$cloud-config append-validator--validator cfc8e87ae610452da9a24c87db2981f2e1f192fb
# submit (because of the previous. Gitigore, account information will not be submitted up, only the modifications to the configuration file will be submitted)
$git add.
$git commit-m"append node0"
$git push--set-upstream origin node0
Step 104: and the consensus node participant pulls the latest blockchain configuration, sets key attribute parameters of the consensus node, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse. Optionally, setting the key attribute parameters of the consensus node includes an IP address, a port number, and a domain of the consensus node.
Taking the configuration node key parameters of the consensus node0 as an example:
Ruby
new configuration of a# pull chain
$git checkout main
$git pull
# create new branches and modify chain configuration
$git checkout-b node0_append_node
$cloud-config append-node--node localhost:40000:node0
# commit IP address, port number and domain
$git commit-m"append node0 ip port and domain"
$git push--set-upstream origin node0_append_node
The consensus node1 also performs the setting of the key attribute parameters described above. However, when a conflict occurs in the merge, the conflict needs to be resolved and resubmitted:
PowerShell
configuration of a chain to pull main branch update
$git checkout main
$git pull
#rebase
$git checkout node1_append_node
$git rebase main
$git status
Interactive base manipulation is in progress; to 0206fd1
The last command has been completed (1 command is executed):
pick 0f2919a append node1 ip port and domain
no commands remain.
You are performing the operation of changing the branch 'node1_application_node' to '0206fd 1'.
(resolve conflicts, then run "git base- -continuous")
(use of "git base- -skip" to skip this patch)
(use of "git base- -able" to detect an original branch)
Uncombined paths:
(use "git restore- -staged < File >)" to cancel scratch pad
(use "gitadd < document >)" sign solution
Both sides modify: test-chain/chain_config.toml
Modification not yet added to commit (using "gitadd" and/or "gitcommit-a")
Resolving conflicts and resubmitting
$git add.
$git push-f
Step 105: the blockchain super administrator pulls the latest blockchain configuration, creates a CA certificate, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse.
Ruby
Configuration of a chain to pull main branch update
$git checkout main
$git pull
# create new branches and create CA certificate
$git checkout-b create_ca
$cloud-config create-ca
# submission
$git add.
$git commit-m"create ca"
$git push--set-upstream origin create_ca
Step 106: and the consensus node pulls the latest blockchain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the blockchain configuration and submits the blockchain configuration to the git warehouse.
Ruby
Configuration of a chain to pull main branch update
$git checkout main
$git pull
# create new branches
$git checkout-b create_csr
# create the certificate of the node and initiate the signature request
# domain parameters here are consistent with domain at application-node
$cloud-config create-csr--domain node0
# submission
$git add.
$git commit-m"node0 create csr"
$git push--set-upstream origin create_csr
Step 107: the blockchain super administrator processes signature requests of the consensus nodes, updates the blockchain configuration and submits the blockchain configuration to the git warehouse.
Ruby
Configuration of a chain to pull main branch update
$git checkout main
$git pull
# create new branches
$git checkout-b sign_csr
# handle signature request
# domain parameters here are consistent with domain at application-node
$cloud-config sign-csr--domain node0
$cloud-config sign-csr--domain node1
# submission
$git add.
$git commit-m"sign csr"
$git push--set-upstream origin sign_csr
Step 108: the blockchain configuration is generated such that the blockchain participant pulls the latest blockchain configuration to complete the corresponding node configuration.
It should be noted that, referring to fig. 2, when the blockchain configuration update is submitted to the git repository, the method includes:
step 151: creating a corresponding branch for the modified blockchain configuration;
step 152: initiating an audit of the modified blockchain configuration;
step 153: after the blockchain participant completes the review of the blockchain configuration modifications, the corresponding branches are merged into the primary branches.
Thus, as can be seen from the description of the method flow in the above embodiments, the method of the present invention has only one configuration file on the main branch, and in the process of configuring the blockchain and its consensus nodes, temporary branches are created, but all the temporary branches are eventually merged into the main branch. Optionally, the blockchain participant pulls the latest blockchain configuration from the git warehouse main branch.
As shown in fig. 3, in another embodiment, a method for managing a blockchain configuration based on git further includes:
step 109: when the block chain configuration is modified, the latest block chain configuration is pulled, and the block chain configuration is updated after the corresponding modification is completed and submitted to the git warehouse;
step 110: looking at the modification record of the blockchain configuration on the gitsub or gitlab, and backtracking the audit situation of the modification of the blockchain configuration by looking at the audit record.
Example two
Fig. 4 is a schematic structural diagram of a git-based blockchain configuration management device 400 according to an embodiment of the present disclosure. Referring to FIG. 4, in one embodiment, a git-based blockchain configuration management device creates a git repository for storing blockchain configurations by a blockchain initiator; registering a git account number by a blockchain participant, wherein the operation authority of the git account number to the git warehouse is set by the blockchain initiator; comprising the following steps:
a blockchain configuration initializing module 401, configured to create a git warehouse main branch and initialize the blockchain configuration by the blockchain initiator, and submit the blockchain configuration to the git warehouse;
a blockchain manager module 402 for creating a supermanager account for the blockchain, updating the blockchain configuration and submitting to the git repository;
a consensus node git account configuration module 403, wherein a blockchain consensus node participant pulls the latest blockchain configuration, creates an account of the consensus node, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
a consensus node parameter configuration module 404, wherein the consensus node participant pulls the latest blockchain configuration, sets the key attribute parameters of the consensus node, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
a blockchain manager CA certificate configuration module 405, the blockchain super manager pulling the latest blockchain configuration, creating a CA certificate, updating the blockchain configuration and submitting to the git repository;
a consensus node CA certificate configuration module 406, configured to pull the latest blockchain configuration, create a CA certificate of the consensus node and initiate a signature request, update the blockchain configuration, and submit the updated blockchain configuration to the git repository;
a signature request processing module 407, where the blockchain super administrator processes the signature request of the consensus node, updates the blockchain configuration, and submits the updated blockchain configuration to the git warehouse;
the blockchain configuration generation module 408 generates the blockchain configuration to cause the blockchain participant to pull the latest blockchain configuration to complete the corresponding node configuration.
As shown in fig. 5, in another embodiment, a git-based blockchain configuration management device 300 is provided, which further includes:
and the blockchain configuration updating module 409 is configured to pull the latest blockchain configuration when the blockchain configuration is modified, update the blockchain configuration after the corresponding modification is completed, and submit the updated blockchain configuration to the git warehouse.
A blockchain configuration modification record module 410 for viewing modification records of the blockchain configuration on the gitsub or gitlab, and for backtracking the audit conditions of the modification of the blockchain configuration by viewing the audit records.
It should be understood that the git-based blockchain configuration management device of the embodiments of the present disclosure may also perform the method performed by the git-based blockchain configuration management device (or apparatus) in fig. 1 to 3, and implement the functions of the git-based blockchain configuration management device (or apparatus) in the examples shown in fig. 1 to 3, which are not described herein.
Example IV
Fig. 6 is a schematic structural diagram of an electronic device according to an embodiment of the present specification. Referring to fig. 6, at the hardware level, the electronic device includes a processor, and optionally an internal bus, a network interface, and a memory. The Memory may include a Memory, such as a Random-Access Memory (RAM), and may further include a non-volatile Memory (non-volatile Memory), such as at least 1 disk Memory. Of course, the electronic device may also include hardware required for other services.
The processor, network interface, and memory may be interconnected by an internal bus, which may be an ISA (Industry Standard Architecture ) bus, a PCI (Peripheral Component Interconnect, peripheral component interconnect standard) bus, or EISA (Extended Industry Standard Architecture ) bus, among others. The buses may be classified as address buses, data buses, control buses, etc. For ease of illustration, only one bi-directional arrow is shown in FIG. 6, but not only one bus or type of bus.
And the memory is used for storing programs. In particular, the program may include program code including computer-operating instructions. The memory may include memory and non-volatile storage and provide instructions and data to the processor.
The processor reads the corresponding computer program from the nonvolatile memory into the memory and then runs, and forms a shared resource access control device on a logic level. The processor is used for executing the programs stored in the memory and is specifically used for executing the following operations:
creating a git repository by a blockchain initiator for preserving blockchain configuration; registering a git account number by a blockchain participant, wherein the operation authority of the git account number to the git warehouse is set by the blockchain initiator; comprising the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest blockchain configuration, sets key attribute parameters of the consensus node, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the blockchain super administrator pulls the latest blockchain configuration, creates a CA certificate, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the consensus node pulls the latest blockchain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the blockchain configuration and submits the blockchain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the blockchain configuration is generated such that the blockchain participant pulls the latest blockchain configuration to complete the corresponding node configuration.
The above-described blockchain configuration management method disclosed in the embodiments shown in fig. 1 to 3 of the present specification may be applied to a processor or implemented by a processor. The processor may be an integrated circuit chip having signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuits of hardware in a processor or by instructions in the form of software. The processor may be a general-purpose processor, including a central processing unit (Central Processing Unit, CPU), a network processor (Network Processor, NP), etc.; but also digital signal processors (Digital Signal Processor, DSP), application specific integrated circuits (Application Specific Integrated Circuit, ASIC), field programmable gate arrays (Field-Programmable Gate Array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components. The methods, steps and logic blocks disclosed in the embodiments of the present specification may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of a method disclosed in connection with the embodiments of the present specification may be embodied directly in hardware, in a decoded processor, or in a combination of hardware and software modules in a decoded processor. The software modules may be located in a random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, etc. as well known in the art. The storage medium is located in a memory, and the processor reads the information in the memory and, in combination with its hardware, performs the steps of the above method.
Of course, in addition to the software implementation, the electronic device of the embodiments of the present disclosure does not exclude other implementations, such as a logic device or a combination of software and hardware, that is, the execution subject of the following processing flow is not limited to each logic unit, but may also be hardware or a logic device.
Example five
The present description also proposes a computer-readable storage medium storing one or more programs, the one or more programs comprising instructions, which when executed by a portable electronic device comprising a plurality of application programs, enable the portable electronic device to perform the method of the embodiments shown in fig. 1-3, and in particular to perform the method of:
creating a git repository by a blockchain initiator for preserving blockchain configuration; registering a git account number by a blockchain participant, wherein the operation authority of the git account number to the git warehouse is set by the blockchain initiator; comprising the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest blockchain configuration, sets key attribute parameters of the consensus node, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the blockchain super administrator pulls the latest blockchain configuration, creates a CA certificate, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the consensus node pulls the latest blockchain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the blockchain configuration and submits the blockchain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the blockchain configuration is generated such that the blockchain participant pulls the latest blockchain configuration to complete the corresponding node configuration.
In summary, the foregoing description is only a preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Any modification, equivalent replacement, improvement, etc. made within the spirit and principle of the present specification should be included in the protection scope of the present specification.
The system, apparatus, module or unit set forth in the above embodiments may be implemented in particular by a computer chip or entity, or by a product having a certain function. One typical implementation is a computer. In particular, the computer may be, for example, a personal computer, a laptop computer, a cellular telephone, a camera phone, a smart phone, a personal digital assistant, a media player, a navigation device, an email device, a game console, a tablet computer, a wearable device, or a combination of any of these devices.
Computer readable media, including both non-transitory and non-transitory, removable and non-removable media, may implement information storage by any method or technology. The information may be computer readable instructions, data structures, modules of a program, or other data. Examples of storage media for a computer include, but are not limited to, phase change memory (PRAM), static Random Access Memory (SRAM), dynamic Random Access Memory (DRAM), other types of Random Access Memory (RAM), read Only Memory (ROM), electrically Erasable Programmable Read Only Memory (EEPROM), flash memory or other memory technology, compact disc read only memory (CD-ROM), digital Versatile Discs (DVD) or other optical storage, magnetic cassettes, magnetic tape magnetic disk storage or other magnetic storage devices, or any other non-transmission medium, which can be used to store information that can be accessed by a computing device. Computer-readable media, as defined herein, does not include transitory computer-readable media (transmission media), such as modulated data signals and carrier waves.
It should also be noted that the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or apparatus that comprises the element.
In this specification, each embodiment is described in a progressive manner, and identical and similar parts of each embodiment are all referred to each other, and each embodiment mainly describes differences from other embodiments. In particular, for system embodiments, since they are substantially similar to method embodiments, the description is relatively simple, as relevant to see a section of the description of method embodiments.
Claims (10)
1. A block chain configuration management method based on git is characterized in that a git warehouse is created by a block chain initiator for storing block chain configuration; registering a git account number by a blockchain participant, wherein the operation authority of the git account number to the git warehouse is set by the blockchain initiator; comprising the following steps:
the block chain initiator creates a git warehouse main branch and initializes the block chain configuration, and submits the block chain configuration to the git warehouse;
creating a super administrator account of the blockchain, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
a block chain consensus node participant pulls the latest block chain configuration, creates an account of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
the consensus node participant pulls the latest blockchain configuration, sets key attribute parameters of the consensus node, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the blockchain super administrator pulls the latest blockchain configuration, creates a CA certificate, updates the blockchain configuration and submits the updated blockchain configuration to the git warehouse;
the consensus node pulls the latest blockchain configuration, creates a CA certificate of the consensus node and initiates a signature request, updates the blockchain configuration and submits the blockchain configuration to the git warehouse;
the block chain super manager processes the signature request of the consensus node, updates the block chain configuration and submits the block chain configuration to the git warehouse;
generating the blockchain configuration so that the blockchain participant pulls the latest blockchain configuration to complete the corresponding node configuration;
the updating the blockchain configuration and submitting to a git repository includes:
creating a corresponding branch for the modified blockchain configuration;
initiating an audit of the modified blockchain configuration;
after the blockchain participant completes the review of the blockchain configuration modifications, the corresponding branches are merged into the primary branches.
2. The method of claim 1, wherein the consensus node participant pulls the latest blockchain configuration from a git repository main branch.
3. The method of claim 1, wherein the operating rights of the git account to the git warehouse comprises selecting a particular way to audit modifications to the blockchain configuration.
4. The method of claim 1, wherein setting the consensus node key attribute parameters comprises an IP address, a port number, and a domain of the consensus node.
5. The method of claim 1, wherein the blockchain configuration submitted to a git repository is privacy set according to information privacy requirements.
6. The method as recited in claim 1, further comprising:
when the block chain configuration is modified, the latest block chain configuration is pulled, and the block chain configuration is updated after the corresponding modification is completed and submitted to the git warehouse;
looking at the modification record of the blockchain configuration on the gitsub or gitlab, and backtracking the audit situation of the modification of the blockchain configuration by looking at the audit record.
7. A git-based blockchain configuration management device, which is characterized in that a git warehouse is created by a blockchain initiator for storing blockchain configuration; registering a git account number by a blockchain participant, wherein the operation authority of the git account number to the git warehouse is set by the blockchain initiator; comprising the following steps:
the block chain configuration initialization module is used for creating a git warehouse main branch by the block chain initiator, initializing the block chain configuration and submitting the block chain configuration to the git warehouse;
the block chain manager module is used for creating a super manager account of the block chain, updating the block chain configuration and submitting the block chain configuration to the git warehouse;
the consensus node git account configuration module is used for pulling the latest blockchain configuration by a blockchain consensus node participant, creating an account of the consensus node, updating the blockchain configuration and submitting the updated blockchain configuration to the git warehouse;
the consensus node parameter configuration module is used for pulling the latest blockchain configuration by the consensus node participant, setting key attribute parameters of the consensus node, updating the blockchain configuration and submitting the updated blockchain configuration to the git warehouse;
the block chain super manager pulls the latest block chain configuration, creates a CA certificate, updates the block chain configuration and submits the updated block chain configuration to the git warehouse;
the consensus node CA certificate configuration module is used for pulling the latest blockchain configuration, creating a CA certificate of the consensus node and initiating a signature request, updating the blockchain configuration and submitting the updated blockchain configuration to the git warehouse;
the signature request processing module is used for processing the signature request of the consensus node by the blockchain super administrator, updating the blockchain configuration and submitting the blockchain configuration to the git warehouse;
the block chain configuration generation module generates the block chain configuration so that the block chain participant pulls the latest block chain configuration to complete corresponding node configuration;
the updating the blockchain configuration and submitting to a git repository includes:
creating a corresponding branch for the modified blockchain configuration;
initiating an audit of the modified blockchain configuration;
after the blockchain participant completes the review of the blockchain configuration modifications, the corresponding branches are merged into the primary branches.
8. The apparatus as recited in claim 7, further comprising:
the block chain configuration updating module is used for pulling the latest block chain configuration when the block chain configuration is modified, updating the block chain configuration after the corresponding modification is completed and submitting the updated block chain configuration to the git warehouse;
and the blockchain configuration modification record module is used for checking the modification record of the blockchain configuration on a gituub page and backtracking the examination condition of modifying the blockchain configuration by checking the examination record.
9. An electronic device, comprising:
a processor; and
a memory arranged to store computer executable instructions which, when executed, cause the processor to perform the method of any of claims 1 to 6.
10. A computer readable storage medium storing one or more programs, which when executed by an electronic device comprising a plurality of application programs, cause the electronic device to perform the method of any of claims 1-6.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111591157.2A CN114465887B (en) | 2021-12-23 | 2021-12-23 | Block chain configuration management method and device based on git |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202111591157.2A CN114465887B (en) | 2021-12-23 | 2021-12-23 | Block chain configuration management method and device based on git |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN114465887A CN114465887A (en) | 2022-05-10 |
| CN114465887B true CN114465887B (en) | 2024-01-23 |
Family
ID=81407175
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202111591157.2A Active CN114465887B (en) | 2021-12-23 | 2021-12-23 | Block chain configuration management method and device based on git |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114465887B (en) |
Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2018100149A4 (en) * | 2018-02-02 | 2018-03-08 | Keith Stewart Alistair Redenbach | Abcde |
| CN108964982A (en) * | 2018-06-13 | 2018-12-07 | 众安信息技术服务有限公司 | For realizing the method, apparatus and storage medium of the deployment of the multinode of block chain |
| CN109165944A (en) * | 2018-08-21 | 2019-01-08 | 北京京东金融科技控股有限公司 | Multiple party signatures authentication method, device, equipment and storage medium based on block chain |
| CN109815206A (en) * | 2018-12-25 | 2019-05-28 | 上海点对点科技有限公司 | A kind of distributed storage network based on block chain |
| CN110472881A (en) * | 2019-08-21 | 2019-11-19 | 重庆华医康道科技有限公司 | Based on the state machine workflow engine of block chain and the working method of distributed storage |
| CN111130841A (en) * | 2019-11-21 | 2020-05-08 | 深圳壹账通智能科技有限公司 | Block chain network deployment method, electronic device and computer readable storage medium |
| CN111245886A (en) * | 2019-11-29 | 2020-06-05 | 武汉烽火信息集成技术有限公司 | Multi-party collaboration system, method and storage medium based on block chain |
| CN111381863A (en) * | 2020-03-17 | 2020-07-07 | 成都创流科技有限责任公司 | APP transaction and automatic online method and system based on block chain technology |
| CN112118124A (en) * | 2020-08-03 | 2020-12-22 | 西安电子科技大学 | Block chain construction method, system, storage medium, computer equipment and application |
| CN112527357A (en) * | 2020-12-14 | 2021-03-19 | 中国平安人寿保险股份有限公司 | Service hot loading updating method and device, computer equipment and storage medium |
| CN112882725A (en) * | 2021-01-22 | 2021-06-01 | 深圳市宝能投资集团有限公司 | Chain code management method and device based on Git, electronic equipment and storage medium |
| CN113268711A (en) * | 2021-05-25 | 2021-08-17 | 国网山东省电力公司电力科学研究院 | Transformer substation relay protection device software version management method based on Git and block chain |
| WO2021217868A1 (en) * | 2020-04-30 | 2021-11-04 | 平安科技（深圳）有限公司 | Git-based project version release method and apparatus, device, and medium |
| CN113626826A (en) * | 2021-07-29 | 2021-11-09 | 西安电子科技大学 | Intelligent contract security detection method, system, equipment, terminal and application |
| CN113673936A (en) * | 2021-08-31 | 2021-11-19 | 上海金融期货信息技术有限公司 | Block chain-based warehouse receipt full life cycle management method and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US11941021B2 (en) * | 2019-10-25 | 2024-03-26 | Accenture Global Solutions Limited | Automatic creation of blockchain network infrastructures |
-
2021
- 2021-12-23 CN CN202111591157.2A patent/CN114465887B/en active Active
Patent Citations (15)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| AU2018100149A4 (en) * | 2018-02-02 | 2018-03-08 | Keith Stewart Alistair Redenbach | Abcde |
| CN108964982A (en) * | 2018-06-13 | 2018-12-07 | 众安信息技术服务有限公司 | For realizing the method, apparatus and storage medium of the deployment of the multinode of block chain |
| CN109165944A (en) * | 2018-08-21 | 2019-01-08 | 北京京东金融科技控股有限公司 | Multiple party signatures authentication method, device, equipment and storage medium based on block chain |
| CN109815206A (en) * | 2018-12-25 | 2019-05-28 | 上海点对点科技有限公司 | A kind of distributed storage network based on block chain |
| CN110472881A (en) * | 2019-08-21 | 2019-11-19 | 重庆华医康道科技有限公司 | Based on the state machine workflow engine of block chain and the working method of distributed storage |
| CN111130841A (en) * | 2019-11-21 | 2020-05-08 | 深圳壹账通智能科技有限公司 | Block chain network deployment method, electronic device and computer readable storage medium |
| CN111245886A (en) * | 2019-11-29 | 2020-06-05 | 武汉烽火信息集成技术有限公司 | Multi-party collaboration system, method and storage medium based on block chain |
| CN111381863A (en) * | 2020-03-17 | 2020-07-07 | 成都创流科技有限责任公司 | APP transaction and automatic online method and system based on block chain technology |
| WO2021217868A1 (en) * | 2020-04-30 | 2021-11-04 | 平安科技（深圳）有限公司 | Git-based project version release method and apparatus, device, and medium |
| CN112118124A (en) * | 2020-08-03 | 2020-12-22 | 西安电子科技大学 | Block chain construction method, system, storage medium, computer equipment and application |
| CN112527357A (en) * | 2020-12-14 | 2021-03-19 | 中国平安人寿保险股份有限公司 | Service hot loading updating method and device, computer equipment and storage medium |
| CN112882725A (en) * | 2021-01-22 | 2021-06-01 | 深圳市宝能投资集团有限公司 | Chain code management method and device based on Git, electronic equipment and storage medium |
| CN113268711A (en) * | 2021-05-25 | 2021-08-17 | 国网山东省电力公司电力科学研究院 | Transformer substation relay protection device software version management method based on Git and block chain |
| CN113626826A (en) * | 2021-07-29 | 2021-11-09 | 西安电子科技大学 | Intelligent contract security detection method, system, equipment, terminal and application |
| CN113673936A (en) * | 2021-08-31 | 2021-11-19 | 上海金融期货信息技术有限公司 | Block chain-based warehouse receipt full life cycle management method and system |
Also Published As
| Publication number | Publication date |
|---|---|
| CN114465887A (en) | 2022-05-10 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| AU2019345040B2 (en) | Advanced smart contract with decentralized ledger in a multi-tenant environment | |
| TWI737944B (en) | Block chain-based transaction execution method and device, and electronic equipment | |
| CN110096857B (en) | Authority management method, device, equipment and medium for block chain system | |
| TWI759563B (en) | Asset management method and device, electronic equipment | |
| US11102003B2 (en) | Ledger-independent token service | |
| RU2745518C9 (en) | Data isolation in the blockchain network | |
| US10389704B1 (en) | Cluster claim | |
| EP3591510A1 (en) | Method and device for writing service data in block chain system | |
| US20210083856A1 (en) | Improved hardware security module management | |
| AU2019345039A1 (en) | Lightweight node in a multi-tenant blockchain network | |
| WO2020029629A1 (en) | Transaction method and system based on centralized settlement and block chain storage | |
| WO2019241071A1 (en) | Cryptographically secure multi-tenant data exchange platform | |
| TW201935384A (en) | Asset management method and device, and electronic equipment | |
| JP2023532959A (en) | A privacy-preserving architecture for permissioned blockchains | |
| US11354447B2 (en) | Data authorization information acquisition methods, apparatuses, and devices | |
| US11533331B2 (en) | Software release tracking and logging | |
| JP2023538497A (en) | editable blockchain | |
| JP7319461B2 (en) | METHOD AND APPARATUS FOR HOLDING PRIVATE DATA USING CONSORTIUM BLOCKCHAIN | |
| CN114465887B (en) | Block chain configuration management method and device based on git | |
| US20210081430A1 (en) | System and method for managing a role-based blockchain network | |
| CN115018499A (en) | Block chain-based digital certificate issuing method, device and system | |
| CN110297625B (en) | Application processing method and device | |
| CN111461721A (en) | Block chain-based method and device for protecting account and verifying transaction | |
| US20230153457A1 (en) | Privacy data management in distributed computing systems | |
| Patsch | Survey on Hyperledger Fabric and comparison of Blockchain as a Service Providers |
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 |