Lifecycle of Hyperledger Fabric Chaincode Development and Deployment

Lifecycle of Hyperledger Fabric Chaincode Development and Deployment

On , by

In this example, we’ll be using the Fabcar Chaincode example provided by Fabric sample. [] which uses the basic network [] as the Hyperledger Fabric network.

Here I assume that you’ve a good understanding about how Fabric works and how the docker instances for the Fabric network is managed.

Clone the Fabric sample#

As the first step, clone the Fabric to your local machine by cloneing it.

git clone
cd fabric-samples

Starting the fabric network#

In order to start the fabcar chaincode, go into the fabcar folder and run the script.

cd fabcard

After this if you want to modify the chaincode and re-deploy you can use the cli container that is running along with the other services.

set -e
# don't rewrite paths for Windows Git Bash users

starttime=$(date +%s)
if [ "$LANGUAGE" = "node" -o "$LANGUAGE" = "NODE" ]; then

docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/" cli peer chaincode install -n fabcar -v $CC_VERSION -p "$CC_SRC_PATH" -l "$LANGUAGE"

docker exec -e "CORE_PEER_LOCALMSPID=Org1MSP" -e "CORE_PEER_MSPCONFIGPATH=/opt/gopath/src/" cli peer chaincode upgrade -o -C mychannel -n fabcar -l "$LANGUAGE" -v $CC_VERSION -c '{"Args":[""]}' -P "OR ('Org1MSP.member','Org2MSP.member')"

The above commands installs a new version of chaincode and upgrades the chaincode by calling the init function. Make sure you change the CC_VERSION everytime you call the script to update chaincode.

Also this will create a new image for each version, so make sure you delete the old images to avoid running out of storage.

Previous Blog Post: Getting smart with React Navigation
Subscribe to Sudo vs Root

Our newsletter rolls out every month. No fluff. Pure content.


Connect with Skcript Global

In 72-hours, your business gets a clear blueprint of what we can do for your organization.

Contact us