Topic: What is the expected throughput limit of Bitcoin now? (Read 238 times)
Thanks everyone for your answers
legacy is about 4x bigger when it's compared with segwit transaction using weight units.
Legacy is about 1.6x bigger for the most common cases. The link you posted yourself has a good example, the size is decreased about 37% (from 904 to 561 weight units).
TPS isn't really accurate measurement because :
1. That depends on average transaction size.
2. That depends whether it's legacy or segwit transaction, legacy is about 4x bigger when it's compared with segwit transaction using weight units.
But assuming all transaction using segwit and contain 1 input/2 output using P2SH SegWit which have 561 weight unit[1]. That means :
1. Maximum transaction in a block are 7130 (4000000 max block weight size / 561 transaction's weight unit)
2. Average block time is 10 minutes, which means maximum TPS is 11.8833 (7130 transaction / 600 second)
Most research using 1 input/2 output as standard/common transaction type, so IMO it's safe to say 11 TPS is expected TPS of Bitcoin even though the reality (common transaction type) might be different.
References :
1. https://en.bitcoin.it/wiki/Weight_units
1. That depends on average transaction size.
2. That depends whether it's legacy or segwit transaction, legacy is about 4x bigger when it's compared with segwit transaction using weight units.
But assuming all transaction using segwit and contain 1 input/2 output using P2SH SegWit which have 561 weight unit[1]. That means :
1. Maximum transaction in a block are 7130 (4000000 max block weight size / 561 transaction's weight unit)
2. Average block time is 10 minutes, which means maximum TPS is 11.8833 (7130 transaction / 600 second)
Most research using 1 input/2 output as standard/common transaction type, so IMO it's safe to say 11 TPS is expected TPS of Bitcoin even though the reality (common transaction type) might be different.
References :
1. https://en.bitcoin.it/wiki/Weight_units
The thing about TPS is that there is no "expected value", there is only a minimum and a maximum. The minimum is when there is only 1 transaction per block (like Block #364292 and a bunch of others) where TPS becomes 0.0016 and when the blocks are filled with 100% SegWit transactions in their smallest form which that SO link is explaining. In the end we will reside somewhere in between depending how how people are using bitcoin, for example the more they use multisignatures the less transaction is going to fit in a block and the lower the final TPS is going to be.
P.S. To clarify the limit is not longer 1 MB size, it is instead 4 MB weight.
P.S. To clarify the limit is not longer 1 MB size, it is instead 4 MB weight.
Hi, I am interested in the update from the maximum throughput since we have segwit. Assuming average 250 bytes tx, the often mentioned number is a max throughput of 7 tx/s before segwit. What is it now?
Some academic papers say 11tx/s but I don't remember seeing any justification of the final estimations.
I am aware of [this explanation](https://bitcoin.stackexchange.com/questions/59408/with-100-segwit-transactions-what-would-be-the-max-number-of-transaction-confi) and [this one](https://medium.com/@jimmysong/understanding-segwit-block-size-fd901b87c9d4)
Thanks
Some academic papers say 11tx/s but I don't remember seeing any justification of the final estimations.
I am aware of [this explanation](https://bitcoin.stackexchange.com/questions/59408/with-100-segwit-transactions-what-would-be-the-max-number-of-transaction-confi) and [this one](https://medium.com/@jimmysong/understanding-segwit-block-size-fd901b87c9d4)
Thanks
Jump to: