Re: What channel capabilities should be turned on when using v1.4 of Fabric?


David Enyeart
 

Setting V1_4_3 capability to true implicitly sets the prior capabilities to true as well. You can leave as-is.

I've pushed a clarification to the file as well: https://gerrit.hyperledger.org/r/#/c/fabric/+/34081/1/sampleconfig/configtx.yaml


Dave Enyeart

"Siddharth Jain" ---10/23/2019 04:22:03 PM---according to this link: INVALID URI REMOVED

From: "Siddharth Jain" <siddjain@...>
To: "fabric@..." <fabric@...>
Date: 10/23/2019 04:22 PM
Subject: [EXTERNAL] [Hyperledger Fabric] What channel capabilities should be turned on when using v1.4 of Fabric?
Sent by: fabric@...





according to this link: https://hyperledger-fabric.readthedocs.io/en/release-1.4/msp.html
    The 1.1 channel capability needs to be enabled before identities can be classified as clients or peers. The 1.4.3 channel capability needs to be enabled for identities to be classified as an admin or orderer.
but when i look at https://github.com/hyperledger/fabric-samples/blob/release-1.4/first-network/configtx.yaml it has
Channel: &ChannelCapabilities
        # V1.4.3 for Channel is a catchall flag for behavior which has been
        # determined to be desired for all orderers and peers running at the v1.4.3
        # level, but which would be incompatible with orderers and peers from
        # prior releases.
        # Prior to enabling V1.4.3 channel capabilities, ensure that all
        # orderers and peers on a channel are at v1.4.3 or later.
        V1_4_3: true
        # V1.3 for Channel enables the new non-backwards compatible
        # features and fixes of fabric v1.3
        V1_3: false
        # V1.1 for Channel enables the new non-backwards compatible
        # features and fixes of fabric v1.1
        V1_1: false

shouldn't V1_1 be set to true?




Join fabric@lists.hyperledger.org to automatically receive all group messages.