a CR from the same local branch as your previous CR) unless they are related. This will minimize merge conflicts and allow changes to be merged more quickly. If you stack requests your subsequent requests a rebase. It only further delays getting it merged and adds more work for you - to remediate the merge conflicts. Communication We use RocketChat [https://chat.hyperledger.org/] for communication and available to the submitter only; it allows a committer to abandon a change and remove it from the merge queue. Change-ID: This ID is generated by Gerrit (or system). It becomes useful when the review process

available to the submitter only; it allows a committer to abandon a change and remove it from the merge queue. • Change-ID: This ID is generated by Gerrit (or system). It becomes useful when the review will all emit their opinion, voting +1 if they agree to the merge, -1 if they disagree. Gerrit users with a Maintainer role can agree to the merge or refuse it by voting +2 or -2 respectively. Notifications project is hosted. • status Indicates the topic’s current status: open , merged, abandoned, draft, merge conflict. • project Refers to the current name of the project, in this case fabric. • branch The

a CR from the same local branch as your previous CR) unless they are related. This will minimize merge conflicts and allow changes to be merged more quickly. If you stack requests your subsequent requests a rebase. It only further delays getting it merged and adds more work for you - to remediate the merge conflicts. Communication We use RocketChat [https://chat.hyperledger.org/] for communication and available to the submitter only; it allows a committer to abandon a change and remove it from the merge queue. Change-ID: This ID is generated by Gerrit (or system). It becomes useful when the review process

a rebase. It only further delays getting it merged and adds more work for you - to remediate the merge conflicts. Legal stuff Note: Each source file must include a license header for the Apache Software feature branch, build the changes locally to check they’re OK, and submit a Pull request (PR) to merge your branch with the appropriate Fabric repository branch. Once your PR has been reviewed and approved Checkout one of the existing branches git checkout -t origin/master Merge the upstream counterpart into your local master git merge upstream/master Update your fork on GitHub with any changes from the

available to the submitter only; it allows a committer to abandon a change and remove it from the merge queue. • Change-ID: This ID is generated by Gerrit (or system). It becomes useful when the review will all emit their opinion, voting +1 if they agree to the merge, -1 if they disagree. Gerrit users with a Maintainer role can agree to the merge or refuse it by voting +2 or -2 respectively. Notifications project is hosted. • status Indicates the topic’s current status: open , merged, abandoned, draft, merge conflict. • project Refers to the current name of the project, in this case fabric. • branch The

a CR from the same local branch as your previous CR) unless they are related. This will minimize merge conflicts and allow changes to be merged more quickly. If you stack requests your subsequent requests a rebase. It only further delays getting it merged and adds more work for you - to remediate the merge conflicts. Communication We use RocketChat [https://chat.hyperledger.org/] for communication and available to the submitter only; it allows a committer to abandon a change and remove it from the merge queue. Change-ID: This ID is generated by Gerrit (or system). It becomes useful when the review process

available to the submitter only; it allows a committer to abandon a change and remove it from the merge queue. • Change-ID: This ID is generated by Gerrit (or system). It becomes useful when the review will all emit their opinion, voting +1 if they agree to the merge, -1 if they disagree. Gerrit users with a Maintainer role can agree to the merge or refuse it by voting +2 or -2 respectively. Notifications project is hosted. • status Indicates the topic’s current status: open , merged, abandoned, draft, merge conflict. • project Refers to the current name of the project, in this case fabric. • branch The

generate_all_certificates 根据node_deployment.ini生成相关节点证书和私钥 generate_*_certificate 生成相应链、机构、节点、sdk证书及私钥 merge_config 将两个节点配置文件中的P2P部分合并 deploy_private_key 将私钥批量导入生成的节点配置文件夹中 add_peers 将节点连接文件批量导入节点配置文件夹中 add_group key生成相应的节点证书。 如果用户缺少上述三个文件，则无法生成节点证书，程序会抛出异常。 执行完成后会在./cert文件夹下生成节点的相关证书与私钥，并将节点证书放 置于./meta下 merge_config (-m) 使用–merge_config命令可以合并两个config.ini中的p2p section 如 A目录下的config.ini文件的p2p section为 $ ./generator 1:30302 node.3 = 127.0.0.1:30303 node.4 = 127.0.0.1:30300 node.5 = 127.0.0.1:30301 $ ./generator --merge_config ~/mydata/node_A/config.ini ~/mydata/node_B/config.ini $./generator --deploy_private_key

generate_all_certificates 根据node_deployment.ini生成相关节点证书和私钥 generate_*_certificate 生成相应链、机构、节点、sdk证书及私钥 merge_config 将两个节点配置文件中的P2P部分合并 deploy_private_key 将私钥批量导入生成的节点配置文件夹中 add_peers 将节点连接文件批量导入节点配置文件夹中 add_group key生成相应的节点证书。 如果用户缺少上述三个文件，则无法生成节点证书，程序会抛出异常。 执行完成后会在./cert文件夹下生成节点的相关证书与私钥，并将节点证书放 置于./meta下 merge_config (-m) 使用–merge_config命令可以合并两个config.ini中的p2p section 如 A目录下的config.ini文件的p2p section为 $ ./generator 1:30302 node.3 = 127.0.0.1:30303 node.4 = 127.0.0.1:30300 node.5 = 127.0.0.1:30301 $ ./generator --merge_config ~/mydata/node_A/config.ini ~/mydata/node_B/config.ini $./generator --deploy_private_key

generate_all_certificates 根据node_deployment.ini生成相关节点证书和私钥 generate_*_certificate 生成相应链、机构、节点、sdk证书及私钥 merge_config 将两个节点配置文件中的P2P部分合并 deploy_private_key 将私钥批量导入生成的节点配置文件夹中 add_peers 将节点连接文件批量导入节点配置文件夹中 add_group key生成相应的节点证书。 如果用户缺少上述三个文件，则无法生成节点证书，程序会抛出异常。 执行完成后会在./cert文件夹下生成节点的相关证书与私钥，并将节点证书放 置于./meta下 merge_config (-m) 使用–merge_config命令可以合并两个config.ini中的p2p section 如 A目录下的config.ini文件的p2p section为 $ ./generator 1:30302 node.3 = 127.0.0.1:30303 node.4 = 127.0.0.1:30300 node.5 = 127.0.0.1:30301 $ ./generator --merge_config ~/mydata/node_A/config.ini ~/mydata/node_B/config.ini $./generator --deploy_private_key