Create_channel.md

Here are the instructions to make a config update to a system channel

The below instructions are carried out from the cli container

docker exec -it cli bash

Export the ORDERER_CA variable

export ORDERER_CA=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/orderers/orderer.example.com/msp/tlscacerts/tlsca.example.com-cert.pem

Now install the jq tool into the container. This tool allows us script interactions with JSON objects returned by the configtxlator tool

apt update && apt install -y jq

The default channel name for system channel is testchainid and to make a channel config update on this channel need to be working as Orderer admin

Switch to Orderer

CORE_PEER_LOCALMSPID="OrdererMSP"
CORE_PEER_TLS_ROOTCERT_FILE=$ORDERER_CA
CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/github.com/hyperledger/fabric/peer/crypto/ordererOrganizations/example.com/users/Admin@example.com/msp

start configtxlator and export the URL

configtxlator start &
CONFIGTXLATOR_URL=http://127.0.0.1:7059

Fetch the genesis block for system channel

peer channel fetch config sys_config_block.pb -o orderer.example.com:7050 -c testchainid --tls --cafile $ORDERER_CA

Decode the block to json format

curl -X POST --data-binary @sys_config_block.pb "$CONFIGTXLATOR_URL/protolator/decode/common.Block" | jq . > sys_config_block.json

Isolating current config

jq .data.data[0].payload.data.config sys_config_block.json > sys_config.json

To understand the pre-requisites and detailed instructions on how to add Org3 refer to the adding an org to a channel sample in hyperledger docs

Append and add org3.json and then write the output to sys_updated_config.json

jq -s '.[0] * {"channel_group":{"groups":{"Consortiums":{"groups": {"SampleConsortium": {"groups": {"Org3MSP":.[1]}}}}}}}' sys_config.json ./channel-artifacts/org3.json >& sys_updated_config.json

Translating original config to proto

curl -X POST --data-binary @sys_config.json "$CONFIGTXLATOR_URL/protolator/encode/common.Config" > sys_config.pb

Translating updated config to proto

curl -X POST --data-binary @sys_updated_config.json "$CONFIGTXLATOR_URL/protolator/encode/common.Config" > sys_updated_config.pb

Computing config update

curl -X POST -F channel=testchainid -F "original=@sys_config.pb" -F "updated=@sys_updated_config.pb" "${CONFIGTXLATOR_URL}/configtxlator/compute/update-from-configs" > sys_config_update.pb

Decoding config update

curl -X POST --data-binary @sys_config_update.pb "$CONFIGTXLATOR_URL/protolator/decode/common.ConfigUpdate" | jq . > sys_config_update.json

Generating config update and wrapping it in an envelope

echo '{"payload":{"header":{"channel_header":{"channel_id":"testchainid", "type":2}},"data":{"config_update":'$(cat sys_config_update.json)'}}}' | jq . > sys_config_update_in_envelope.json

Encoding config update envelope

curl -X POST --data-binary @sys_config_update_in_envelope.json "$CONFIGTXLATOR_URL/protolator/encode/common.Envelope" > sys_config_update_in_envelope.pb

The mod policy for system channel requires the Orderer admin to send the config update

Sending config update to orderer

peer channel update -f sys_config_update_in_envelope.pb -c testchainid -o orderer.example.com:7050 --tls true --cafile $ORDERER_CA

Now Org3 is added to the consortium

Follow the steps below to create a new channel using Org3

To create a new channel the profile needs to be updated and defined as TwoOrgsChannel1 in the configtx.yaml file with only Org1 and Org3 since we want only Org1 and Org3 as the members of this new channel

The below steps should be done outside of cli container in a separate terminal window from org3-artifacts dir

Next we need to set the path for configtxgen

FABRIC_CFG_PATH=$PWD

Generate channel configuration transaction

../bin/configtxgen -profile TwoOrgChannel1 -outputCreateChannelTx ./channel-artifacts/channel1.tx -channelID mychannel1

Switch to cli terminal and create a new channel with peer0.Org3

peer channel create -o orderer.example.com:7050 -c mychannel1 -f ./channel-artifacts/channel1.tx --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA

Switch to Peer0.Org1 and Join the channel

peer channel join -b mychannel1.block

Install chaincode on Org1

peer chaincode install -n newcc -v 1.0 -p github.com/hyperledger/fabric/examples/chaincode/go/chaincode_example02

Instantiate the chaincode

peer chaincode instantiate -o orderer.example.com:7050 --tls $CORE_PEER_TLS_ENABLED --cafile $ORDERER_CA -C mychannel1 -n newcc -v 1.0 -c '{"Args":["init","a","100","b","200"]}' -P "OR	('Org1MSP.member','Org3MSP.member')"

Make an invoke and query from peer of org3