hyperledger/fabric · error

invalid key for the collection of chaincode %s:%s; expected

Error message

invalid key for the collection of chaincode %s:%s; expected '%s', received '%s'

What it means

validateRWSetAndCollection found the second LSCC write's key is not the expected collections KVS key ('chaincodeName~collection'). When two writes exist, the second must be the collections entry for the deployed chaincode.

Source

Thrown at core/handlers/validation/builtin/v13/lscc_validation_logic.go:247

	/********************************************/
	// there can only be one or two writes
	if len(lsccrwset.Writes) > 2 {
		return policyErr(fmt.Errorf("LSCC can only issue one or two putState upon deploy"))
	}

	/**********************************************************/
	/* security check 0.b - validation of the collection data */
	/**********************************************************/
	var collectionsConfigArg []byte
	if len(lsccArgs) > 5 {
		collectionsConfigArg = lsccArgs[5]
	}

	var collectionsConfigLedger []byte
	if len(lsccrwset.Writes) == 2 {
		key := privdata.BuildCollectionKVSKey(cdRWSet.Name)
		if lsccrwset.Writes[1].Key != key {
			return policyErr(fmt.Errorf("invalid key for the collection of chaincode %s:%s; expected '%s', received '%s'",
				cdRWSet.Name, cdRWSet.Version, key, lsccrwset.Writes[1].Key))
		}

		collectionsConfigLedger = lsccrwset.Writes[1].Value
	}

	if !bytes.Equal(collectionsConfigArg, collectionsConfigLedger) {
		return policyErr(fmt.Errorf("collection configuration arguments supplied for chaincode %s:%s do not match the configuration in the lscc writeset",
			cdRWSet.Name, cdRWSet.Version))
	}

	channelState, err := vscc.stateFetcher.FetchState()
	if err != nil {
		return &commonerrors.VSCCExecutionFailureError{Err: fmt.Errorf("failed obtaining query executor: %v", err)}
	}
	defer channelState.Done()

	state := &state{channelState}

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Ensure the deploy writes collection config under the proper collections key
2. Reject transactions with unexpected second LSCC writes

When it happens

Trigger: Thrown at core/handlers/validation/builtin/v13/lscc_validation_logic.go:247 when the library encounters an invalid state.

Common situations: See trigger scenarios.

AI-assisted analysis of hyperledger/fabric@2736b63f8f (2026-09-04). Data as JSON: /api/errors/cd860ea953a4d1e5. Report an issue: GitHub.