What the primary record establishes

EIP-7685 defines a common container for requests from the execution layer to the consensus layer. The header field is the SHA-256 hash of the concatenated SHA-256 hashes of nonempty entries in ascending type order. When there are no entries, the result is SHA-256 of empty bytes. EIP-7685 · General-purpose execution layer requests ↗

What the distinction changes

A matching hash attests that clients used the same ordered bytes. Each request type separately defines the meaning and validation of its payload. A placeholder with no request data or a different ordering can produce a mismatch even where the intended operation looks the same.

What to check before drawing a conclusion

Test empty, single-type and multi-type cases separately. During cross-client diagnosis, compare the serialized bytes and intermediate hashes before investigating the application rules for the individual request.