<p>Just like a hard-fork blocksize increase SegWit  will not solve the scalability issue by itself. Either provides chiefly a fixed factor increase in capacity. </p>

<p>SegWit is also a way to kick the can down the road, but in comparison to the hard-fork blocksize increase, it also solves other issues, doesn't require a hard-fork, and makes blocksize increases less problematic: SegWit resolves an issue where transactions require quadratic effort for verification. The problem was highlighted by the <a href="http://rusty.ozlabs.org/?p=522" rel="nofollow noreferrer">"megatransaction" created by f2pool last July</a>. While capacity only increases linearly with bigger blocks, effort to verify blocks increases at a super-linear rate. For SegWit transactions the transaction verification takes linear effort, making bigger blocks cause less of an advantage for the author of the latest block. Hence, SegWit helps reduces centralizing pressure on mining in the face of capacity increases.</p>

<p>On-chain scalability is always limited to linear growth anyway: For every transaction that you resolve on-chain, you need to provide the storage space on-chain. While we will be able to go down that route for a bit, it is unsustainable for large amounts of transactions and we wouldn't be able to reach e.g. the transaction counts corresponding to the payment counts of credit card companies.</p>

<p>Scalability improvements need to make better than linear use of the blockchain capacity.<br>
Unlike a hard-fork blocksize increase, SegWit sets the stage for further improvements in the future. One promising proposal is the <a href="https://bitcoin.stackexchange.com/q/43700/5406">Lightning Network</a>, which compounds numerous payments at the cost of two or three on-chain transactions. Another exciting improvement is the introduction of Schnorr signatures. Schnorr signatures are smaller than ECDSA signatures, but due to their homomorphic nature allow for both signature aggregation and key aggregation. In addition, Schnorr signatures enable the use of adaptor signatures that allow for a wide range of smartcontracts to be created with Scriptless Scripts.</p>

<p>Last but not least, SegWit introduces Script versioning. This allows to specify which version of Script to use to interpret a transaction, allowing multiple versions of Script to coexist safely at the same time in the network. Script versioning allows much easier deployment of Script improvements to expunge bugs and vulnerabilities, or to add new features like Schnorr signatures.</p>

CC BY-SA 3.0
2016-04-22T12:32:12.533Z
2017-12-14T17:22:59.620Z
2017-12-14T17:22:59.620Z
Murch
<p>Yes we would. Segwit just gives us time to do a well-prepared hard-fork or give the opportunity/time for some other enhancement (lightning network, sidechains?) to deal with scalability properly.</p>

<p>Note that a hard-fork for larger blocks would also just delay the problem. </p>

CC BY-SA 3.0
2016-04-22T05:53:41.633Z
2016-04-22T05:53:41.633Z
karask
<p>Firstly, it depends on how you define the "problem". Nothing is infinitely scalable. If we are to assume that bitcoin network capacity needs to increase, then no solution that still contains a limit (such as block size limit increases) will forever be a solution, they all will just "buy time". SegWit is a better solution than increasing the block size, as the increased data needed can bring with it it's own issues and the concept of "unlimited" block sizes is unlikely to be a solution - to suddenly remove a limit entirely would be quite reckless given that the impact of this on the network is quite untested.</p>

CC BY-SA 3.0
2016-11-04T04:09:39.547Z
2016-11-04T04:09:39.547Z
Rebroad
<p>If I understand correctly. SegWit is one of the solutions to the full 1MB block problem that doesn't require a hard fork. But I've read this only increases the 1MB to maybe about 2-4x only. If that is the case, wouldn't we have the same problem down the line when transactions reach that level again? </p>

<segregated-witness>
If SegWit only increases the capacity to only 2-4x only. Wouldn't we have the same issue in a few years again?
Patoshi パトシ
# If SegWit only increases the capacity to only 2-4x only. Wouldn't we have the same issue in a few years again?

(Asked by: username_0 on 2016-04-21)

If I understand correctly. SegWit is one of the solutions to the full 1MB block problem that doesn't require a hard fork. But I've read this only increases the 1MB to maybe about 2-4x only. If that is the case, wouldn't we have the same problem down the line when transactions reach that level again?

**Tags:** segregated-witness


---

## 3 answers

### Answer by username_1 on 2016-04-22. Score: 7

Just like a hard-fork blocksize increase SegWit will not solve the scalability issue by itself. Either provides chiefly a fixed factor increase in capacity.

SegWit is also a way to kick the can down the road, but in comparison to the hard-fork blocksize increase, it also solves other issues, doesn't require a hard-fork, and makes blocksize increases less problematic: SegWit resolves an issue where transactions require quadratic effort for verification. The problem was highlighted by the ["megatransaction" created by f2pool last July](http://rusty.ozlabs.org/?p=522). While capacity only increases linearly with bigger blocks, effort to verify blocks increases at a super-linear rate. For SegWit transactions the transaction verification takes linear effort, making bigger blocks cause less of an advantage for the author of the latest block. Hence, SegWit helps reduces centralizing pressure on mining in the face of capacity increases.

On-chain scalability is always limited to linear growth anyway: For every transaction that you resolve on-chain, you need to provide the storage space on-chain. While we will be able to go down that route for a bit, it is unsustainable for large amounts of transactions and we wouldn't be able to reach e.g. the transaction counts corresponding to the payment counts of credit card companies.

Scalability improvements need to make better than linear use of the blockchain capacity.  
Unlike a hard-fork blocksize increase, SegWit sets the stage for further improvements in the future. One promising proposal is the [Lightning Network](https://bitcoin.stackexchange.com/q/43700/5406), which compounds numerous payments at the cost of two or three on-chain transactions. Another exciting improvement is the introduction of Schnorr signatures. Schnorr signatures are smaller than ECDSA signatures, but due to their homomorphic nature allow for both signature aggregation and key aggregation. In addition, Schnorr signatures enable the use of adaptor signatures that allow for a wide range of smartcontracts to be created with Scriptless Scripts.

Last but not least, SegWit introduces Script versioning. This allows to specify which version of Script to use to interpret a transaction, allowing multiple versions of Script to coexist safely at the same time in the network. Script versioning allows much easier deployment of Script improvements to expunge bugs and vulnerabilities, or to add new features like Schnorr signatures.


---

### Answer by username_2 on 2016-04-22. Score: 6

Yes we would. Segwit just gives us time to do a well-prepared hard-fork or give the opportunity/time for some other enhancement (lightning network, sidechains?) to deal with scalability properly.

Note that a hard-fork for larger blocks would also just delay the problem.


---

### Answer by username_3 on 2016-11-04. Score: 1

Firstly, it depends on how you define the "problem". Nothing is infinitely scalable. If we are to assume that bitcoin network capacity needs to increase, then no solution that still contains a limit (such as block size limit increases) will forever be a solution, they all will just "buy time". SegWit is a better solution than increasing the block size, as the increased data needed can bring with it it's own issues and the concept of "unlimited" block sizes is unlikely to be a solution - to suddenly remove a limit entirely would be quite reckless given that the impact of this on the network is quite untested.


---

