Quote from: franky1 on March 30, 2017, 04:12:34 AM

Quote from: Wind_FURY on March 30, 2017, 02:21:15 AM

That does not compute. I have just read that the 1MB maxblocksize was added as an anti spam measure. We all know that the flooding of the mempool is because some group is spamming the network, so if we hard fork to an 32MB maxblocksize and some other group is not happy and decide to spam the network that will lead to more blockchain bloat.

someone making 1mb of spam today will make 1mb of spam filling the baseblock after segwit activation with native keys.
so that no segwit tx's can fit txdata in the baseblock, thus not hang their sigs outside the baseblock.. thus not even use any of the 3mb extra weight but still have the 'blocks are full' issue.

someone making 1mb of spam today will make 1mb of segwit txdata spam filling the baseblock after segwit activation using segwit tx's. so that it has 2mb of txdata+sig spam and still no moral / normal user transactions able to get in

inshort: segwit does not stop spam because segwit is reliant on the baseblock.

Yes I agree the spamming will not stop as long as there are certain groups who are unhappy with the way things are now. I am sure there will be another group who will be unhappy if we hard fork to bigger blocks and have a new set of developers who may not be popular.

If that is a possible scenario then I ask this question from jonald_fyookball's ball comment.

Quote

At this point, I'd be happy as a peach if everyone just got behind a hardfork to 32mb or 8mb.

Will that lead to more blockchain bloat or not? There is also the mining centralization issue that comes with bigger blocks.