hyperledger/fabric · error

error mapping WriteSet

Error message

error mapping WriteSet

What it means

mapConfig failed while converting the update's WriteSet into the internal comparable map, wrapping an underlying structural error (bad group path, misplaced item type, invalid key). The WriteSet could not be interpreted, so the update is rejected before policy checks.

Source

Thrown at common/configtx/update.go:141

		return nil, err
	}

	if configUpdate.ChannelId != vi.channelID {
		return nil, errors.Errorf("ConfigUpdate for channel '%s' but envelope for channel '%s'", configUpdate.ChannelId, vi.channelID)
	}

	readSet, err := mapConfig(configUpdate.ReadSet, vi.namespace)
	if err != nil {
		return nil, errors.Wrapf(err, "error mapping ReadSet")
	}
	err = vi.verifyReadSet(readSet)
	if err != nil {
		return nil, errors.Wrapf(err, "error validating ReadSet")
	}

	writeSet, err := mapConfig(configUpdate.WriteSet, vi.namespace)
	if err != nil {
		return nil, errors.Wrapf(err, "error mapping WriteSet")
	}

	deltaSet := computeDeltaSet(readSet, writeSet)
	signedData, err := protoutil.ConfigUpdateEnvelopeAsSignedData(configUpdateEnv)
	if err != nil {
		return nil, err
	}

	if err = vi.verifyDeltaSet(deltaSet, signedData); err != nil {
		return nil, errors.Wrapf(err, "error validating DeltaSet")
	}

	fullProposedConfig := vi.computeUpdateResult(deltaSet)
	if err := verifyFullProposedConfig(writeSet, fullProposedConfig); err != nil {
		return nil, errors.Wrapf(err, "full config did not verify")
	}

	return fullProposedConfig, nil

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Inspect the wrapped inner error to find the offending WriteSet entry.
2. Regenerate the WriteSet with configtxlator by diffing the current config against the desired config.
3. Ensure each WriteSet entry sits in the correct ConfigUpdate field (groups, values, or policies) for its type.
4. Re-encode the update from valid JSON/YAML instead of patching binary protos.

Example fix

// before: value placed under write_set.groups
// after: move it to write_set.values with a proper ModPolicy set
ws.Values["BatchSize"] = &cb.ConfigValue{Value: bytes, ModPolicy: "Admins"}

// Sanity-check WriteSet structure before submission
func validWriteSet(update *cb.ConfigUpdate) error {
    ws := update.GetWriteSet()
    for g, grp := range ws.GetGroups() {
        if g == "" || grp == nil { return fmt.Errorf("invalid group %q in write_set", g) }
    }
    for k, v := range ws.GetValues() {
        if k == "" || v == nil || v.GetModPolicy() == "" {
            return fmt.Errorf("value %q missing or has no mod_policy", k)
        }
    }
    return nil
}

if _, err := validator.ProposeConfigUpdate(env, seq); err != nil {
    if strings.Contains(err.Error(), "error mapping WriteSet") {
        // fix write_set structure: correct types in correct fields, valid keys
    }
    return err
}

When it happens

Trigger: Calling proposeConfigUpdate/Validate with a ConfigUpdate whose WriteSet contains entries with invalid group paths or item types that mapConfig cannot map into the config namespace.

Common situations: Hand-crafted or corrupted write-sets; update files edited between encode/decode steps; tooling writing groups where values (or vice versa) belong; truncated updates after transfer.

Related errors

• writeset contained key %s which did not appear in proposed c
• error mapping ReadSet
• full config did not verify
• Attempted to set the batch size max message count to an inva
• Attempted to set the batch size absolute max bytes to an inv

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