Block Body

Overview

A block body is the main payload carried by a block after the header. Depending on the blockchain, it may include ordered transactions, attestations, withdrawals, receipts, uncle references, evidence, or other protocol objects needed to execute and validate the state transition. The header usually commits cryptographically to body contents through roots or hashes. A node can reject a block if the body is missing, malformed, exceeds limits, contains invalid objects, or does not match those commitments.

Indexers and payment systems should not treat a header announcement as proof that transaction data has been received and validated. They need the canonical body or trustworthy derived data, transaction position, execution result, and finality status. Pruned nodes may discard older body data, affecting historical queries and audits. Pruned, archive, light, and indexing services may expose different historical fields or proofs. Teams should document which component supplies the data and how missing, malformed, or version-unknown records are handled. Operational use of Block Body depends on node mode and data retention.

Parsing should be version-aware and fail closed when an unknown format affects validation, accounting, or settlement decisions. Test fixtures for Block Body should cover normal blocks, boundary sizes, protocol upgrades, and invalid encodings.

Block Body must be interpreted under the exact chain rules and software version that define its encoding and validation. Field names can appear similar across networks while using different byte order, commitment schemes, size limits, activation heights, or relationships to the block header and body. Operational takeaway: The block body carries executable content, while the header commits to it and enables integrity checks.