we already needed the capacity increase and it was increased. the block size has not been 1 MB for nearly a year now. in fact there is no block size anymore, it is block weight. basically capacity has increased about 20-30% so far but it can go up to about 80% if more people start using SegWit.
hopefully we get something for aggregating signatures so the big transactions with many inputs can also become smaller and that will increase the capacity further.
...and the block size increases is the last resort which will eventually happen also.
that is where you are wrong
there is still a legacy limit of 1mb.
although they have twistd it around and hidden it you will never be able to have more than 1mb of legacy transactions..
and also the Segwit transactions partially sit in this same still 1mb existant area. meaning there is a limit to how many segwit transactions too.
there has been 0% legacy increase of limit
2.1x potential of segwit.. but only 1.1mb has ben the average increase
yep they say 4mb but actual utility of transactions per block will not be 4x
might be worth you reading code. with all their 4x fudging the numbers to hide the 1mb
https://github.com/bitcoin/bitcoin/blob/master/src/consensus/consensus.h#L13heres a hint.. there would be no need for scale factors or other variables revolve around 4x or a quarter of.... if 1mb was irrelevant
think about it 4mb/4=??
also the stats about segwit is not 20-30%
read the small print of the stats page you got that from
a transaction of many LEGACY inputs but only 1 segwit input. is treated (wrongly) as a segwit tx.
meaning
if i had a tx of thoudands of legacy inputs and only 1 segwit input.
the stats page will call it a segwit tx.. BUT you will not see 2001 signatures in the "weight" area.. you will only see 1 signature in the weight area