One of the biggest revolutions in the history of technology has been the development of Hyperedger Fabric v1.0 VS Hyperledger Fabric V 2.0. It laid the foundation for creating solutions or applications with a modular architecture. With hyperledger fabric, the components are easy to plug and play. This fabric is a blessing for the supply chain industry as it enhances transaction traceability and transparency. Resultant, this fabric has garnered interest since its inception. Hyperledger fabric first introduced its v1.0 version in July 2017. Since then, it has continuously added new features and enhancements to make it more industry-viable. Hyperledger Fabric v 2.0 was introduced on January 29, 2020. This version entails several further modifications and features in contrast to  v 1.4.

To differentiate between the two, we are explaining the lifecycle of chaincode implementation.  

Process of Chaincode implementation – v 1.0 

Step 1: All organization admins install Chaincode to the peers.

Step 2: Anyone admin instantiates Chaincode with an endorsement policy.

Step 3: Then admin submits a proposal to the ordering agency

Step 4: The ordering agency will communicate the updated status to all the peers within that network.

Step 5:  Now, the two organizations (Org1 & Org 2) can invoke the Chaincode. 

Drawbacks of v1.4 Chaincode cycle

– Org2 admin had no say while instantiating. Only the admin of Org1 defined the endorsement policies. 

– Org2 admin also cannot upgrade or downgrade the system. 

– To change anything on Chaincode, the admin of Org2 must create a new Chaincode container. 

Chaincode lifecycle of Fabric v2.x

Step1: Chaincode packing and installation

Step2: Both Org1 and Org2 co-define the chaincode, to include their personal data. Thus, they approve their respective chaincodes. 

Step3: The admins will submit a proposal to the ordering service.

Step4: The ordering service will commit the same to the individual peers.

Step5: Now, either of the two organizations can commit the chaincode. The endorsement policy in Fabric v2.x needs endorsement from most participant organizations to verify/endorse the transactions. 

Note: Life cycle endorsement policy and chaincode endorsement policy are different.  

Step6: Then, the ordering service receives the commit transaction.

Step7: The orderer now commits the definition of chaincode to other peers in the network. 

Fabric v1.x is less decentralized.

Hyperedger Fabric v1.0 VS Hyperledger Fabric V 2.0

 

Attributes	Hyperedger Fabric v 1.0	Hyperedger Fabric v 2.0
Upgrade transaction	Only one organization could issue an upgrade transaction.	Possible only after a required a minimum number of organizations endorse chaincode upgradation.
Inspecting chaincode packages	Chaincode packaged in easily readable files.	Chaincode packaged in easily readable files. Multiple organizations can install it.
	Each chaincode carries a name and version specified at the time of chaincode installation.	One can deploy a single chaincode package multiple times. They can have different names.
Setting parameters	Only one organization could set the chaincode parameters	It supports both centralized and decentralized models. A Minimum number of organizations must agree to an endorsement policy
Chaincode lifecycle	Less decentralized Allows only 1 organization  to define the policy	More decentralized Multiple organizations agree on chaincode’s parameters
Data privacy	Data shared among few channel peers	Organizations can privately share data on a need-to-know basis
Performance improvement	fewerperformance improvements were added.	More performance improvements were added.
Framework provided	Provide framework. HACERA used this framework to create products that augment the creation of business networks	Provide framework. Offers HACERA Kore (to manage decentralized networks.

From the above table, we can conclude that compared to the first version, fabric v1.0, chaincode lifecycle in the new version, fabric v 2.0 is more decentralized. Even the process of chaincode up-gradation is simplified in v 2.0 as the process doesn’t require creating any new container. 

If you too need any help with hyperledger fabric development, look no further. Chaincode gets simplified with ChainCode Consulting