<p>SegWit nodes simply won't download blocks from non-SegWit peers. Preferential peering tries to make sure outgoing connections go to other SegWit peers, but even if not, downloading of blocks only happens from compatible peers.</p>

<p>If we receive a block from a peer which claims to be SegWit compatible, but it lacks witnesses, it will be treated as if the block were invalid, and the peer who gave it will be banned and/or disconnected.</p>

CC BY-SA 3.0
2017-08-29T07:56:36.397Z
2017-08-29T17:08:19.673Z
2017-08-29T17:08:19.673Z
Pieter Wuille
<p>Scenario: segwit node receives all blocks from legacy node without segwit support, eg using --connect parameter.</p>

<p>The legacy node stores/forwards max 1Mb blocks, so the extra segwit data logically could not be transferred to the segwit node.</p>

<ol>
<li>how will the segwit node view segwit transactions?   Will it see them as anyonecanspend, like the legacy node?</li>
</ol>

<p>Sometime later, the segwit node is allowed to connect to the main network.</p>

<ol start="2">
<li>What will the segwit node do?  Will it download blocks for which it is missing segwit data?   Or will it just have a "wrong" view of the blockchain?</li>
</ol>

<p>If the latter, isn't that a problem?</p>

<segregated-witness>
What happens if segwit node receives blocks from legacy node?
Curious George
# What happens if segwit node receives blocks from legacy node?

(Asked by: username_0 on 2017-08-29)

Scenario: segwit node receives all blocks from legacy node without segwit support, eg using --connect parameter.

The legacy node stores/forwards max 1Mb blocks, so the extra segwit data logically could not be transferred to the segwit node.

1. how will the segwit node view segwit transactions? Will it see them as anyonecanspend, like the legacy node?

Sometime later, the segwit node is allowed to connect to the main network.

2. What will the segwit node do? Will it download blocks for which it is missing segwit data? Or will it just have a "wrong" view of the blockchain?

If the latter, isn't that a problem?

**Tags:** segregated-witness


---

## 1 answers

### Answer by username_1 on 2017-08-29. Score: 1

SegWit nodes simply won't download blocks from non-SegWit peers. Preferential peering tries to make sure outgoing connections go to other SegWit peers, but even if not, downloading of blocks only happens from compatible peers.

If we receive a block from a peer which claims to be SegWit compatible, but it lacks witnesses, it will be treated as if the block were invalid, and the peer who gave it will be banned and/or disconnected.


---

