Quote from: Odalv on January 13, 2015, 10:05:49 PM

Quote from: justusranvier on January 13, 2015, 09:43:40 PM

Quote from: smooth on January 13, 2015, 09:02:57 PM

Perhaps he should stick with "the real Bitcoin" from before the hard fork that created the 1 MB limit.

Hilarious how many people defend the 1 MB limit without realizing that it wasn't part of the original release.

I would prefer 256k limit.

That was tried and it did not work. Users started to experience significant delays:

Quote from: Mike Hearn on March 06, 2013, 09:44:20 AM

By default Bitcoin will not created blocks larger than 250kb even though it could do so without a hard fork. We have now reached this limit. Transactions are stacking up in the memory pool and not getting cleared fast enough.

What this means is, you need to take a decision and do one of these things:

Start your node with the -blockmaxsize flag set to something higher than 250kb, for example -blockmaxsize=1023000. This will mean you create larger blocks that confirm more transactions. You can also adjust the size of the area in your blocks that is reserved for free transactions with the -blockprioritysize flag.
Change your nodes code to de-prioritize or ignore transactions you don't care about, for example, Luke-Jr excludes SatoshiDice transactions which makes way for other users.
Do nothing.

If everyone does nothing, then people will start having to attach higher and higher fees to get into blocks until Bitcoin fees end up being uncompetitive with competing services like PayPal.

If you mine on a pool, ask your pool operator what their policy will be on this, and if you don't like it, switch to a different pool.

Fortunately it was a soft-limit and only a few large mining pools needed to quickly do a change.