Witness Data

💡 The Plain-English Definition

Witness data is the signature attached to a Bitcoin transaction — the proof that whoever is sending the bitcoin actually owns it. SegWit — Segregated Witness, a 2017 protocol upgrade — moved signatures into their own separate section of the transaction, which fixed a bug, enabled Lightning, and made modern address formats cheaper to use.

🤔 But Why Though?

First, a quick grounding in how ownership works. Your private key is a huge secret number — the raw cryptographic proof of ownership, impossible to memorise and dangerous to handle directly. A seed phrase is the same secret in human-friendly form: ordinary words you can write down that encode that one private key (and every address derived from it). And a Bitcoin address, like bc1qar0srrr7xfkvy5l643lydnw9re59gtzzwf5mdq, is what you share with someone who wants to pay you. The address is derived from the private key by a one-way process, so it reveals nothing about the key itself.

Witness data is the signature a private key produces when it authorises a transaction. When you send bitcoin, your wallet uses your private key to create a unique digital signature — proof that you, the owner, approved this exact transaction. That signature is what SegWit moved into the witness section.

Before SegWit, the signature lived inside the main transaction body, and the transaction ID (the transaction’s unique fingerprint) was calculated from everything, signature included. The trouble was that a third party could tweak a signature slightly without invalidating it, which changed the transaction ID — a bug called transaction malleability. It directly blocked the Lightning Network from being built, because Lightning needs to reliably refer to transactions that haven’t confirmed yet. SegWit fixed it by moving signatures into a witness section that doesn’t feed into the transaction ID.

A fee discount followed. Witness data is given a lower block weight — 1 weight unit per byte, versus 4 for non-witness data — which makes SegWit and Taproot transactions cheaper. Ordinals inscriptions take advantage of the same discount, storing images and text in the witness field at the cheaper rate, which is why they only became economically viable after SegWit.

🌍 The Real-World Analogy

Think of a Bitcoin transaction like a cheque. The main body holds the payment details — who it’s payable to, how much, the date. The signature at the bottom is the witness data, the proof of authorisation. The cheque’s reference number (the transaction ID) should be fixed by the payment details, not by the signature. Before SegWit, someone could slightly alter the signature without invalidating the cheque, yet the reference number changed — chaos for any system tracking that cheque by its reference. SegWit moved the signature to a separate attached slip, so changing it no longer changes the cheque’s reference number.