Why it exists
BIP 143 defines the transaction message signed by ECDSA signatures for version-0 SegWit spends. It improves the efficiency of validation and makes the spent input’s value part of the signature commitment. It is a consensus signing rule, not a wallet file format or a general rule for all Bitcoin signatures.
How it works
The digest combines transaction information with the input being signed, including its previous outpoint, relevant script, amount and sequence. Shared hashes of inputs, sequences and outputs can be reused across signatures instead of repeatedly hashing the entire transaction for every check.
The selected signature-hash mode controls which transaction pieces are committed. SIGHASH_ALL normally commits to all outputs; other modes deliberately permit different changes. The exact rules matter to the signer as well as the node validating the completed transaction. Taproot uses a different message construction defined by BIP 341.
A practical example
A device signs a version-0 SegWit input worth 1,000,000 sats. Its payment has outputs totalling 990,000 sats, giving a 10,000-sat fee if that is the only input. If the coordinator supplies a false value for that input, the resulting signature will not validate against the real output amount. In a multi-input payment, the device still needs trustworthy information about the other inputs to display the overall fee correctly.
What to keep in mind
Committing the current input amount does not prove ownership of change or establish the total fee by itself. Non-default signature-hash modes change the authorization boundary, and a device must check the script and transaction context rather than merely calculate a digest.
Status & implementation
Bitcoin Core implements BIP 143 with SegWit from 0.13.0, with mainnet deployment definitions in 0.13.1. Its validation is a consensus requirement for applicable version-0 witness spends.
Specification status: Deployed · Sources checked 13 November 2026
