<p>This is defined in <a href="https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#Abstract" rel="nofollow noreferrer">bip-0141</a>:</p>

<blockquote>
  <p>This BIP defines a new structure called a "witness" that is committed
  to blocks separately from the transaction merkle tree. This structure
  contains data required to check transaction validity but not required
  to determine transaction effects. In particular, scripts and
  signatures are moved into this new structure.</p>
  
  <p>The witness is committed in a tree that is nested into the block's
  existing merkle root via the coinbase transaction for the purpose of
  making this BIP soft fork compatible. A future hard fork can place
  this tree in its own branch.</p>
</blockquote>

<p>This new structure represents the extended block which is attached to the merkle root of the coinbase. </p>

<p>If a full node doesn't understand SegWit format it won't be able to validate the transaction. But it can accept it as is, just like lightweight clients do.</p>

CC BY-SA 3.0
2018-03-13T19:56:07.653Z
2018-03-13T19:56:07.653Z
Stan Mots
<p>I understand where normal blocks get stored. They’re passed along and saved by various nodes. What about the extended blocks of a segwit transaction. </p>

<segregated-witness>
Where does the extended block in a segwit transaction get stored?
Shamoon
# Where does the extended block in a segwit transaction get stored?

(Asked by: username_0 on 2017-12-24)

I understand where normal blocks get stored. They’re passed along and saved by various nodes. What about the extended blocks of a segwit transaction.

**Tags:** segregated-witness


---

## 1 answers

### Answer by username_1 on 2018-03-13. Score: 1 | Accepted answer

This is defined in [bip-0141](https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#Abstract):

> This BIP defines a new structure called a "witness" that is committed
> to blocks separately from the transaction merkle tree. This structure
> contains data required to check transaction validity but not required
> to determine transaction effects. In particular, scripts and
> signatures are moved into this new structure.
>
> The witness is committed in a tree that is nested into the block's
> existing merkle root via the coinbase transaction for the purpose of
> making this BIP soft fork compatible. A future hard fork can place
> this tree in its own branch.

This new structure represents the extended block which is attached to the merkle root of the coinbase.

If a full node doesn't understand SegWit format it won't be able to validate the transaction. But it can accept it as is, just like lightweight clients do.


---

