News for hackers. Stuff that matters.
Re:Skyrocketing Bitcoin Fees Hit Carders in Wallet by xorcist on Thursday December 28, 2017 @11:12PM (#16027460)
The fixed lock size cap was removed last August and block sizes increased. Now it's just the problem of making people use the newly available space. Pricing out legacy transactions is a perfectly valid method.
Re:Skyrocketing Bitcoin Fees Hit Carders in Wallet by gizmo686 on Friday December 29, 2017 @01:14AM (#16027953)
This isn't entirely true. There is still a fixed max block size; it is just that some bytes are counted as "bigger" than others. In particular, the maximum block weight is currently 4MB. However, most bytes count as if they were 4 bytes; which returns us to an effective blocksize of 1MB. However, bytes that are part of SegWit's witness area only count as 1 byte.

This leaves a hard upper bound of 4MB block size, with a "typical" size of ~2.3MB if everyone uses SegWit.

Re:Skyrocketing Bitcoin Fees Hit Carders in Wallet by xorcist on Friday December 29, 2017 @03:35AM (#16028411)
While technically true that the block size cap has a hard limit of 4MB, which would be a block consisting of one transaction with only inputs, a 4MB transaction isn't valid for other reasons.

So it's not meaningful to talk about a fixed block cap anymore. Perhaps it is better to talk about "typical" block sizes the way you do.

What's important is that the 1MB limit is history, unless you have to make legacy transactions for some reason.