Quote from: franky1 on November 25, 2016, 10:01:41 AM

Quote from: Killerpotleaf on November 25, 2016, 07:28:09 AM

how can you claim to know what the majority want?

even people that love core want dynamic blocksize. the only argument they can come up with though is that they would only TRUST gmaxwell to write the code for it. they are even screaming to tell the community that core never said no to a increase of the base blocksize, they just waiting for gmaxwell who proposed a dynamic blocksize LAST YEAR!

afterall the altcoin dooms day myth has been busted. all that will happen is an elevation of possible orphan rate due to how small or large the minority is (hense 95%+ acceptability to implement). making under 5% (under 250 of 5000 nodes) not sync and need to upgrade.

afterall the bloat doomsday myth has been busted. 4mb bloat is acceptable

so the solution/compromise is obvious. core tweak their segwit code to 2mb base 4mb weight.. call it 0.13.1b release it alongside 0.13.1 and let the community choose to download either 0.13.1 or 0.13.1b

atleast if everyone happily downloads 0.13.1b segwit also gets activated by default too.
if there is no desire of a jump in base block.. then no one will download 0.13.1b and it wont activate. meaning no harm either fanboys just download 0.13.1 instead

but simply preventing even letting the community have the release to even have a choice under their 'trusted' brand they wont run away from. is no longer the right course of action

then. when activated and we have more REAL capacity because the buffer has increased. that gives alot more time to code new features instead of these stupid delays

Personally I'd like to see some research on what effect 4mb weight blocks would have on further centralization, but that's what i foresee most likely to happen. If 0.13.1 won't get enabled, bump up blocks to 2MB+segwit and let people vote on that.