Quote from: Meuh6879 on December 14, 2016, 11:14:13 PM

Quote from: franky1 on December 14, 2016, 10:31:40 PM

i think you need to call your cries a 'block exaggeration'.. because its only you inflating the numbers of the real debate
wake up to reality and learn whats real.

I'm really award of a congestion scenario ... and Block Inflate is NOT a spam protection.
If you want block Inflate, run 100 nodes ... and deal with this after 3 months.

lol you are really scraping the bottom of the barrel.
the funny thing is
2mb base 4mb weight.
or
1mb base 4mb weight.

amount to the SAME maximum bloat potential either way, for CONFIRMED BLOCKS (not in mempool anymore)

allowing more tx's into a block, does not actually cause mempools to get flooded. quite the opposite

this 4mb max is also on the contingent that EVERYONE uses segwit to achieve the 4mb max. or we will see a more realistic well under 2mb expectation within under 3 months time frame you gave.
after all when any scalability is activated. it takes time for nodes to use the feature and takes time for pools to test the water at 1.001mb for orphan risk and slowly grow once they get confident. so dont expect max bloat straight away

again learn reality and stop exaggerating.

as for running 100 nodes.. why would someone do that and why would running 100 nodes mean anything.
if your currently running 100 nodes then your shooting yourself in the foot with a sybil attempt that is only hurting yourself.

but if you are worried about mempool bottleneck . worry more about nlocktime of 1 hour 59 minutes. that can force mempools to fill up