<p>Segwit was designed in such a way that segwit transactions, after removing the witness, are <strong>valid</strong> but <strong>non-standard</strong> to old nodes.</p>

<p>This guarantees that old nodes won't reject such transactions when they're seen in blocks, but still won't be relayed or mined by old software.</p>

CC BY-SA 4.0
2019-01-29T16:21:21.433Z
Does this apply to all SegWit transactions, including P2SH-nested types?
Chris Chen
CC BY-SA 4.0
2019-01-29T19:04:08.393Z
@ChrisChen Indeed. All segwit spends violate the "clean stack" standardness rule implemented by most pre-segwit Bitcoin Core versions.
Pieter Wuille
CC BY-SA 3.0
2018-04-01T17:55:48.333Z
2018-04-01T18:38:32.343Z
2018-04-01T18:38:32.343Z
Pieter Wuille
<p>If non segwit nodes view segwit transactions as anyone can spend ,why can't you broadcast a segwit transaction using them?</p>

<transactions><segregated-witness>
Can you broadcast a segwit transaction using a non segwit node?
John
# Can you broadcast a segwit transaction using a non segwit node?

(Asked by: username_0 on 2018-03-31)

If non segwit nodes view segwit transactions as anyone can spend ,why can't you broadcast a segwit transaction using them?

**Tags:** transactions, segregated-witness


---

## 1 answers

### Answer by username_1 on 2018-04-01. Score: 3 | Accepted answer

Segwit was designed in such a way that segwit transactions, after removing the witness, are **valid** but **non-standard** to old nodes.

This guarantees that old nodes won't reject such transactions when they're seen in blocks, but still won't be relayed or mined by old software.

> **Comments:**
> **username_2**: Does this apply to all SegWit transactions, including P2SH-nested types?  
> **username_1**: @username_2 Indeed. All segwit spends violate the "clean stack" standardness rule implemented by most pre-segwit Bitcoin Core versions.  

---

