On Sat, Apr 1, 2017 at 3:15 PM, Natanael <natanae...@gmail.com> wrote: > > > Den 1 apr. 2017 14:33 skrev "Jorge Timón via bitcoin-dev" > <bitcoin-dev@lists.linuxfoundation.org>: > > Segwit replaces the 1 mb size limit with a weight limit of 4 mb. > > > That would make it a hardfork, not a softfork, if done exactly as you say. > > Segwit only separates out signature data. The 1 MB limit remains, but would > now only cover the contents of the transaction scripts. With segwit that > means we have two (2) size limits, not one. This is important to remember. > Even with segwit + MAST for large complex scripts, there's still going to be > a very low limit to the total number of possible transactions per block. And > not all transactions will get the same space savings.
No, because of the way the weight is calculated, it is impossible to create a block that old nodes would perceive as bigger than 1 mb without also violating the weight limit. After segwit activation, nodes supporting segwit don't need to validate the 1 mb size limit anymore as long as they validate the weight limit. The weight is also the only notion of cost miners need to consider when comparing txs by feerate (fee per cost, before segwit tx_fee/tx_size, post-segwit tx_fee/tx_weight). This is important to remember, because having 2 separated limits or costs would make block creation and relay policies much harder to implement. Therefore a hardfork after segwit can just increase the weight limit and completely forget about the pre-segwit 1 mb size limit. _______________________________________________ bitcoin-dev mailing list bitcoin-dev@lists.linuxfoundation.org https://lists.linuxfoundation.org/mailman/listinfo/bitcoin-dev
