Block Witness

Overview

Block witness refers to supporting data required for verification. In Bitcoin, witness data contains signatures and scripts separated from the traditional transaction serialization under SegWit. In other designs, a block witness can include state proofs or values needed for stateless validation. The exact meaning is protocol-specific. Witness data may be committed through a dedicated root or commitment and can have different storage, propagation, or fee treatment from the main transaction payload. Missing or malformed witness material makes validation fail.

Node and wallet software must parse the correct protocol version and include witness data when calculating identifiers, fees, and signing messages. Indexers should distinguish transaction identifiers from witness-inclusive hashes where applicable. Pruning witness-related data can limit later verification even if headers remain available. Operational use of Block Witness depends on node mode and data retention. 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.

Test fixtures for Block Witness should cover normal blocks, boundary sizes, protocol upgrades, and invalid encodings. Parsing should be version-aware and fail closed when an unknown format affects validation, accounting, or settlement decisions. 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. Block Witness must be interpreted under the exact chain rules and software version that define its encoding and validation. Practical implication: Witness data supplies essential validation evidence, with commitment and fee treatment determined by each blockchain protocol.