hyperledger/fabric · error

nil header in payload

Error message

nil header in payload

What it means

Returned by deliverclient.ConfigFromBlock for non-genesis blocks when the transaction payload lacks a header. Config blocks after genesis embed a config update envelope whose payload must be well-formed; a nil header means the payload is malformed and cannot be classified.

Source

Thrown at common/deliverclient/util.go:41

	}
	txn := block.Data.Data[0]
	env, err := protoutil.GetEnvelopeFromBlock(txn)
	if err != nil {
		return nil, errors.WithStack(err)
	}
	payload, err := protoutil.UnmarshalPayload(env.Payload)
	if err != nil {
		return nil, errors.WithStack(err)
	}
	if block.Header.Number == 0 {
		configEnvelope, err := configtx.UnmarshalConfigEnvelope(payload.Data)
		if err != nil {
			return nil, errors.Wrap(err, "invalid config envelope")
		}
		return configEnvelope, nil
	}
	if payload.Header == nil {
		return nil, errors.New("nil header in payload")
	}
	chdr, err := protoutil.UnmarshalChannelHeader(payload.Header.ChannelHeader)
	if err != nil {
		return nil, errors.WithStack(err)
	}
	if common.HeaderType(chdr.Type) != common.HeaderType_CONFIG {
		return nil, ErrNotAConfig
	}
	configEnvelope, err := configtx.UnmarshalConfigEnvelope(payload.Data)
	if err != nil {
		return nil, errors.Wrap(err, "invalid config envelope")
	}
	return configEnvelope, nil
}

View on GitHub (pinned to 2736b63f8f)

Solutions

1. Rebuild the block from a valid envelope with a populated payload header
2. Treat the block as corrupt and re-fetch it

When it happens

Trigger: Thrown at common/deliverclient/util.go:41 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/8513d7d20df91146. Report an issue: GitHub.