Block Weight

Overview

Bitcoin block weight measures serialized block data under SegWit’s accounting rules. Non-witness bytes count more heavily than witness bytes, and the total block must remain within the consensus weight limit. This replaced a simple one-megabyte size rule with a more nuanced resource measure. Transaction weight determines virtual size, which fee markets commonly use to quote satoshis per virtual byte. Two transactions with the same raw byte size can therefore have different effective fee rates depending on how much data is witness material.

Wallets should estimate weight from the actual input and output script types, signatures, and change. Mining systems select transactions using fee rate and dependencies while respecting total weight. Payment analytics should not confuse raw bytes, virtual bytes, weight units, and transaction count. Test fixtures for Block Weight 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 Weight must be interpreted under the exact chain rules and software version that define its encoding and validation.

Verification of Block Weight should begin with a canonical block identifier rather than a height alone. Competing blocks can temporarily occupy the same height, and a reorganization can replace data that was previously observed, so applications should retain hashes and update dependent records when canonicality changes.

Risk-control point: Bitcoin block weight discounts witness data and drives capacity and fee calculations more accurately than raw byte size.