<p><a href="https://bitcoincore.org/en/2016/01/26/segwit-benefits/" rel="nofollow noreferrer">Here</a> is FAQ about SEGWIT benefits.</p>

<p>If you would like to know more technical details, probably <a href="https://bitcoincore.org/en/segwit_wallet_dev/" rel="nofollow noreferrer">segwits developer guide</a> is very good start.</p>

CC BY-SA 3.0
2017-07-14T00:08:17.123Z
2017-07-14T00:08:17.123Z
CEVAP
<p>Some of the major benefits of SegWit are (in no particular order):</p>

<p>1) Effective block size limit increase<br>
2) A solution to transaction malleability (no longer possible for a third party to alter the transaction ID)<br>
3) Facilitate certain payment channel and lightning implementations by resolving the transaction malleability issue<br>
4) Addition of a script version number to allow future script upgrades to be backward compatible<br>
5) Reduced computational complexity of signature algorithm    </p>

<p>An easy explainer from Aaron van Wirdum is here (with thanks to Pieter Wuille) <a href="https://bitcoinmagazine.com/articles/segregated-witness-part-why-you-should-care-about-a-nitty-gritty-technical-trick-1450827675/" rel="nofollow noreferrer">https://bitcoinmagazine.com/articles/segregated-witness-part-why-you-should-care-about-a-nitty-gritty-technical-trick-1450827675/</a></p>

CC BY-SA 3.0
2017-07-12T19:11:59.393Z
While technically correct that SegWit does theoretically allow that, that is not implemented, hardly relevant (you can already fully prune all blocks while still validating), and really a detail compared to other advantages (removing quadratic hashing, simplified support for high-level protocol, ...).
Pieter Wuille
CC BY-SA 3.0
2017-07-12T14:39:28.397Z
2017-07-13T21:41:34.103Z
2017-07-13T21:41:34.103Z
Michael Folkson
<p>The name itself is a good hint as to what it actually does.</p>

<p>What we have today is a "witness" (i.e signature scripts) included in every Bitcoin transaction in non-segwit compliant transactions. This allows every full node within the Bitcoin network to verify the integrity of any transactions. </p>

<p>By removing the signatures in a Bitcoin transaction, you lose the ability to verify the integrity of the transaction. But in reality, not everyone needs to be able to independently verify the integrity of a transaction.</p>

<p>Thus, by segregating the signature from a transaction, we have a smaller transaction that describes the inputs and outputs exactly as it is. But if you want to know for sure that these are verified inputs, you'll look up the Segregated Witness set to find the corresponding scripts to validate the SegWit Transaction. </p>

CC BY-SA 3.0
2016-05-26T23:26:40.067Z
2016-05-26T23:26:40.067Z
rny
<p>How can I explain the potential ease of scaling and feature benefits of Segregated Witness to a non technical friend?</p>

<p>How can I explain the potential drawbacks of Segregated Witness in a non technical manner?</p>

<segregated-witness>
How would I explain SegWit to a non-technical friend?
cowboy4life
# How would I explain SegWit to a non-technical friend?

(Asked by: username_0 on 2016-05-26)

How can I explain the potential ease of scaling and feature benefits of Segregated Witness to a non technical friend?

How can I explain the potential drawbacks of Segregated Witness in a non technical manner?

**Tags:** segregated-witness


---

## 3 answers

### Answer by username_4 on 2016-05-26. Score: 12 | Accepted answer

The name itself is a good hint as to what it actually does.

What we have today is a "witness" (i.e signature scripts) included in every Bitcoin transaction in non-segwit compliant transactions. This allows every full node within the Bitcoin network to verify the integrity of any transactions.

By removing the signatures in a Bitcoin transaction, you lose the ability to verify the integrity of the transaction. But in reality, not everyone needs to be able to independently verify the integrity of a transaction.

Thus, by segregating the signature from a transaction, we have a smaller transaction that describes the inputs and outputs exactly as it is. But if you want to know for sure that these are verified inputs, you'll look up the Segregated Witness set to find the corresponding scripts to validate the SegWit Transaction.


---

### Answer by username_1 on 2017-07-14. Score: 0

[Here](https://bitcoincore.org/en/2016/01/26/segwit-benefits/) is FAQ about SEGWIT benefits.

If you would like to know more technical details, probably [segwits developer guide](https://bitcoincore.org/en/segwit_wallet_dev/) is very good start.


---

### Answer by username_2 on 2017-07-12. Score: 0

Some of the major benefits of SegWit are (in no particular order):

1) Effective block size limit increase  
2) A solution to transaction malleability (no longer possible for a third party to alter the transaction ID)  
3) Facilitate certain payment channel and lightning implementations by resolving the transaction malleability issue  
4) Addition of a script version number to allow future script upgrades to be backward compatible  
5) Reduced computational complexity of signature algorithm

An easy explainer from Aaron van Wirdum is here (with thanks to username_3) <https://bitcoinmagazine.com/articles/segregated-witness-part-why-you-should-care-about-a-nitty-gritty-technical-trick-1450827675/>

> **Comments:**
> **username_3**: While technically correct that SegWit does theoretically allow that, that is not implemented, hardly relevant (you can already fully prune all blocks while still validating), and really a detail compared to other advantages (removing quadratic hashing, simplified support for high-level protocol, ...).  

---

