Skip to main content

DevProvider

Boost Your Team Productivity Quickly Hire Expert Developers Without Delay Scale Your Business With Ease Get Access To Top Talent Accelerate Projects With Skilled Teams Trusted By Leading Global Companies Build Your Dream Team Fast Transform Ideas Into Real Solutions Remote Developers Available On Demand Hire Dedicated Teams For Success Expert Guidance For Your Projects Quality Developers Ready To Join Achieve Goals With Skilled Professionals Support For Businesses Around The Globe Trusted Partners For Your Growth Deliver Projects Faster With Experts Experienced Teams For Every Industry Flexible Staffing Solutions For Companies Hire Remote Talent Without Hassle Helping Startups And Enterprises Scale Access pre-vetted experts for your team Experts integrate seamlessly with your team Scale your business faster with experts Cut hiring delays and save time Deliver projects with confidence and speed
devprovider
Claim $99 Offer
Upgrading to fabric 2.0
Claim $99 Offer
Home / Blog / Upgrading to fabric 2.0

Upgrading to fabric 2.0

Published on November 8, 2023
hyperledge

Table of Contents

When upgrading to Fabric 2.0, network operators and enterprise developers must follow a systematic migration process to maintain network availability, preserve data integrity, and take full advantage of newly introduced architecture improvements.

High-Level 4-Step Process for Upgrading to Fabric 2.0

Upgrading nodes and channels follows a simple four-step process:

  1. Backup the ledger and MSPs: Save all channel state databases and block ledgers. Back up all cryptographic MSP keys before making any changes.

  2. Upgrade the orderer binaries: Update orderer nodes one by one. This rolling update prevents downtime in the ordering service.

  3. Upgrade the peer binaries: Perform rolling binary updates across all peers. This keeps endorsement and validation active throughout the upgrade.

  4. Update channel capability levels: Update the system and application channels to the latest capability levels. Some releases introduce new capabilities across all groups. Others may introduce few or none.

Key Changes in the Fabric 2.0 Architecture

Fabric 2.0 brings major improvements to decentralized governance, privacy, and performance:

  • Decentralized Chaincode Lifecycle: Organizations must agree on chaincode rules before committing contracts to a channel.

  • External Chaincode Launchers: Chaincode can now run outside peer environments. This simplifies deployments on platforms like Kubernetes.

  • State Database Cache Performance: Fabric 2.0 improves read and write speeds for CouchDB and LevelDB.

    IT staff augmentation serivices hire dedicated developers
    Upgrading to fabric 2.0
    Claim $99 Offer

    Need skilled IT professionals?

    Claim $99 Offer

Recommended Upgrade Tutorials & Guides

Consult these guides along with the official Hyperledger Fabric documentation:

  • Upgrading your components: Learn how to update binaries and Docker containers safely. Complete this step before updating capabilities.

  • Updating the capability level of a channel: Learn how to sign and submit channel configuration updates. Complete this step after updating node binaries.

  • Enabling the new chaincode lifecycle: Set up the required endorsement policies for Fabric 2.0 chaincode packages.

Automation Scripts and Command Support

Upgrading nodes and raising channel capabilities is now a standard routine. Because of this, specific commands are not listed here.

The fabric-samples repository no longer provides an automated upgrade script. Teams should use standard rolling upgrade practices. You can also use CI/CD pipelines to manage each phase safely.

Upgrade Automation & Command Notes

As the upgrading of nodes and increasing the capability levels of channels is by now considered a standard Fabric process, we will not show the specific commands for upgrading to the newest release. Similarly, there is no script in the fabric-samples repo that will upgrade a sample network from the previous release to this one, as there has been for previous releases.