fabric: github.com/hyperledger/fabric/core/handlers/validation/api/capabilities Index | Files

package validation

import "github.com/hyperledger/fabric/core/handlers/validation/api/capabilities"

Index

Package Files

capabilities.go

type Capabilities Uses

type Capabilities interface {
    validation.Dependency
    // Supported returns an error if there are unknown capabilities in this channel which are required
    Supported() error

    // ForbidDuplicateTXIdInBlock specifies whether two transactions with the same TXId are permitted
    // in the same block or whether we mark the second one as TxValidationCode_DUPLICATE_TXID
    ForbidDuplicateTXIdInBlock() bool

    // ACLs returns true if the peer supports ACLs in the channel config
    ACLs() bool

    // PrivateChannelData returns true if support for private channel data (a.k.a. collections) is enabled.
    PrivateChannelData() bool

    // CollectionUpgrade returns true if this channel is configured to allow updates to
    // existing collection or add new collections through chaincode upgrade (as introduced in v1.2)
    CollectionUpgrade() bool

    // V1_1Validation returns true is this channel is configured to perform stricter validation
    // of transactions (as introduced in v1.1).
    V1_1Validation() bool

    // V1_2Validation returns true is this channel is configured to perform stricter validation
    // of transactions (as introduced in v1.2).
    V1_2Validation() bool

    // V1_3Validation returns true if this channel supports transaction validation
    // as introduced in v1.3. This includes:
    //  - policies expressible at a ledger key granularity, as described in FAB-8812
    //  - new chaincode lifecycle, as described in FAB-11237
    V1_3Validation() bool

    // StorePvtDataOfInvalidTx returns true if the peer needs to store
    // the pvtData of invalid transactions.
    StorePvtDataOfInvalidTx() bool

    // MetadataLifecycle indicates whether the peer should use the deprecated and problematic
    // v1.0/v1.1 lifecycle, or whether it should use the newer per channel peer local chaincode
    // metadata package approach planned for release with Fabric v1.2
    MetadataLifecycle() bool

    // KeyLevelEndorsement returns true if this channel supports endorsement
    // policies expressible at a ledger key granularity, as described in FAB-8812
    KeyLevelEndorsement() bool

    // FabToken returns true if fabric token function is supported.
    FabToken() bool
}

Capabilities defines what capabilities the validation should take into account when validating a transaction

Package validation imports 1 packages (graph) and is imported by 4 packages. Updated 2019-07-01. Refresh now. Tools for package owners.