Definition
SegWit is a 2017 Bitcoin protocol upgrade, defined in BIP141, that moves the witness data (the signatures that prove a transaction is authorized) out of the main body of a transaction and into a separate structure. By “segregating the witness,” it fixed transaction malleability and restructured how block space is measured, paving the way for the Lightning Network and Taproot.
Also known as: Segregated Witness, BIP141.
What SegWit actually changed
Before SegWit, a transaction’s identifier (its txid) was a hash of the whole transaction, signatures included. Because signatures could be re-encoded without changing what the transaction did, the txid could shift unexpectedly. SegWit solves this by computing the txid from everything except the witness, while tracking the witness separately under a second identifier (the wtxid). This single change made transaction IDs stable, which is the foundation that off-chain protocols like the Lightning Network are built on.
SegWit also replaced the old 1 MB block size limit with a “block weight” budget. Witness data counts less toward that budget than non-witness data, so SegWit blocks can hold more transactions while staying compatible with older nodes. Because old nodes still see valid blocks, SegWit shipped as a soft fork rather than a hard fork — no chain split required, just a coordinated upgrade.
Why a miner builds blocks differently after SegWit
SegWit reshaped how a mining pool constructs work. When a pool assembles a block template, the coinbase transaction must now include a “witness commitment” — a hash of all the block’s witness data placed in an OP_RETURN output. This commitment is what lets nodes verify that nobody tampered with the segregated signatures.
There is a subtlety that matters for anyone running mining gear. The merkle root in the block header is still calculated from the stripped (non-witness) coinbase txid, not the wtxid. D-Central’s protocol research confirms this directly: in the Stratum work a pool sends to your machine, the coinbase data has its witness stripped precisely because the miner only needs the non-witness txid to compute the merkle root. The full witness data is reattached later, by the pool or the block-assembly layer, when the solved block is propagated to the network.
Where it touches your ASIC at home
For a home miner, SegWit is mostly invisible at the hardware level — your ASIC still grinds the same 80-byte header with the same double SHA-256, hunting for a valid nonce. The miner does not parse witness data at all; it receives a merkle root (or coinbase fragments to build one) over the Stratum protocol and hashes. That clean separation is exactly why SegWit could be deployed without anyone needing to swap their rigs.
Where it does matter to your bottom line is fee economics. More transactions per block and a richer fee market shape the transaction fees that flow into the coinbase reward you are competing for — increasingly important as the block subsidy shrinks with each halving. SegWit also unlocked Taproot, which the same soft-fork machinery later activated, continuing Bitcoin’s pattern of upgrading without forcing a chain split. If you want to put a small machine on the network and watch this play out yourself, the open-source builds in the Bitaxe hub connect to SegWit-aware pools out of the box, and the broader open-source mining gear we curate all speaks the same protocol — one more layer of the network kept decentralized by people running their own hardware.
Related terms: Taproot, Soft Fork, Coinbase Transaction, Merkle Root, Block Template, Lightning Network
In Simple Terms
A 2017 upgrade that increased block capacity by separating signature data and enabled the Lightning Network.
SegWit is a 2017 Bitcoin protocol upgrade, defined in BIP141, that moves the witness data (the signatures that prove a transaction is authorized) out of the main body of a transaction and into a separate structure. By "segregating the witness," it fixed transaction malleability and restructured how block space is measured, paving the way for the Lightning Network and Taproot.
Also known as: Segregated Witness, BIP141.
What SegWit actually changed
Before SegWit, a transaction's identifier (its txid) was a hash of the whole transaction, signatures included. Because signatures could be re-encoded without changing what the transaction did, the txid could shift unexpectedly. SegWit solves this by computing the txid from everything except the witness, while tracking the witness separately under a second identifier (the wtxid). This single change made transaction IDs stable, which is the foundation that off-chain protocols like the Lightning Network are built on.
SegWit also replaced the old 1 MB block size limit with a "block weight" budget. Witness data counts less toward that budget than non-witness data, so SegWit blocks can hold more transactions while staying compatible with older nodes. Because old nodes still see valid blocks, SegWit shipped as a soft fork rather than a hard fork — no chain split required, just a coordinated upgrade.
Why a miner builds blocks differently after SegWit
SegWit reshaped how a mining pool constructs work. When a pool assembles a block template, the coinbase transaction must now include a "witness commitment" — a hash of all the block's witness data placed in an OP_RETURN output. This commitment is what lets nodes verify that nobody tampered with the segregated signatures.
There is a subtlety that matters for anyone running mining gear. The merkle root in the block header is still calculated from the stripped (non-witness) coinbase txid, not the wtxid. D-Central's protocol research confirms this directly: in the Stratum work a pool sends to your machine, the coinbase data has its witness stripped precisely because the miner only needs the non-witness txid to compute the merkle root. The full witness data is reattached later, by the pool or the block-assembly layer, when the solved block is propagated to the network.
Where it touches your ASIC at home
For a home miner, SegWit is mostly invisible at the hardware level — your ASIC still grinds the same 80-byte header with the same double SHA-256, hunting for a valid nonce. The miner does not parse witness data at all; it receives a merkle root (or coinbase fragments to build one) over the Stratum protocol and hashes. That clean separation is exactly why SegWit could be deployed without anyone needing to swap their rigs.
Where it does matter to your bottom line is fee economics. More transactions per block and a richer fee market shape the transaction fees that flow into the coinbase reward you are competing for — increasingly important as the block subsidy shrinks with each halving. SegWit also unlocked Taproot, which the same soft-fork machinery later activated, continuing Bitcoin's pattern of upgrading without forcing a chain split. If you want to put a small machine on the network and watch this play out yourself, the open-source builds in the Bitaxe hub connect to SegWit-aware pools out of the box, and the broader open-source mining gear we curate all speaks the same protocol — one more layer of the network kept decentralized by people running their own hardware.
Related terms: Taproot, Soft Fork, Coinbase Transaction, Merkle Root, Block Template, Lightning Network