Topic: 2MB Pros and Cons - page 7. (Read 9735 times)

you know, it's sad how true this rings.

the project has been lead with a certain vision of how it would scale, that vision had not changed up until they took over the project.

Hmm, could also be the fork had already happened when blockstream came into the game and we already are on BSC = Blockstreamcoins ....

So its the try to get old BTC back

1MB Bitcoin + 1MB Ethereum

problem solved

If you manage not to fall into asleep you ll get some pros here after 15 min

http://youtu.be/i93dNBW4NEM

Fee market yet is totally crap guys...

I feel the Cons side is a bit thin and has to much red.
I do believe there are more CONS.
I will want to expand on this point "Increased resource usage (capacity, bandwidth, processing power)"

OP has not at made any guidelines regarding this.
I do agree it's a good idea to not mention  "Core or Classic" in OP, but for the purpose of the discussion, i believe its OK to ref. Core or Classic in the explanations.
When you're trying to prove a point like i just did about, it helps to be able to point to real world events surrounding the block limit debate.

It's not the idea of 2MB that poeple are obsessed about, it's about cores vision for bitcoin's future. not everyone agrees we should consider the specs of a 60$ raspberry pi when designing the world's financial settlement layer.

but.... they are risking it, right now.

gavin left core and created XT and now helping Classic and Unlimited, in an attempt at forking bitcoin.
did you miss the part when like 20 of the top bitcoin businesses sign a document that explained why they wanted bigger blocks?
the bitcoin market has drop several times because this kind of fork was seen as a credible threat.

sure this it's unlikely bitcoin will fork over this in the near future, but should core refuse to comply with >80% of hashing power, that's not only risking it, thats asking for it.


Yes poeple are "obsessed", many are willing to fork over this issue.

lol will you look at this http://nodecounter.com/


i guess this kinda thing is to be expected from nodecounter.com.....

The thread was solely designed to not mentioned any implementation. It seems that the 'forkers' are unable to follow simple rules. Why am I not surprised?

Exactly. People are obsessed with the 2 MB block size limit.

I really doubt it. People who are really working for the best of Bitcoin would never risk this.

You could also just start using Classic.

http://nodecounter.com/

I kind of doubt it.

What is happening is certain people want to take over development. The TX capacity of Bitcoin is what they saw as a way to socially engineer the public into believing there is a problem the core developers are not addressing.

It's an easy target for that. For most people, doubling the block size means doubling the TX rate. That makes sense. Reality is it is *one* way to increase the TX rate.

The core developers have to look at other ways, and determine which method has the least negative side effects.

While the core developers do this, it gives opportunity for those who wish to take over to point a finger and cry that core devs aren't acting on this problem. That however is deception, core is addressing the issue.

Pro: Not bumping limit to 2MB could cause a fork.

it's no secret poeple want 2MB, we've seen open letters signed by many many top bitcoin businesses stating they want bigger blocks, we've also see the same thing coming from the a huge % of hashrate, it's not unreasonable to assume, inaction on this issue will cause a fork.

I added a fun little poll, make sure you read the pros and cons before voting.

I will now try to catch up on the discussion and add some pros, cons, and comments to OP.

Well technically yes, but still no. If the fees drop by half, and the amount of empty block space is 50% then such attacks would be as expensive as they are now. There are just a lot of variables and factors to consider.

Segwit comes first though. I'd say a 2 MB block size limit would be easier to deploy after IBLT and Weak blocks.

You could use a big microSD card and keep it charging constantly, however I don't see why one would want to do this.

No, finding a hash that meets the difficulty has nothing to do with the size of the block.


Sure, if you have a >200GiB/month data plan and >70GB free disk space. Not sure about the battery, but it would probably only last a few hours.

Sorry I need to understand something here... as a noob

2mb blocks at current difficulty... takes twice as long to process = more energy, more cost, angry miners... wouldnt the bitcoin network adjust the difficulty accordingly. i.e 1mb with 160 difficulty(didnt feel like typing the rest of the numbers) would be the same as 2mb with 80...

Resource usage would stay the same in terms of electricity. transaction fees stay the same per transaction yet miners would get a little more... i.e you not charging the client more just the same...but the batch done at a time is more so hence you get more.

Now about the nodes... someone using dial up connection as a node is already obsolete... and yes usually they in the bum fuck of no where
BUT the guys in the bum fuck of nowhere use cell phones usually with 3G... and if its really remote gsm.... but then again how many transaction are happening in gsm only areas???.... realistically speaking.

Maybe cell phones can be adopted as node (just a thought)....

no need to fork.. fork for what... just because you have increased demand for a product or service you dont go start a whole new company... you increase production capacity... plain stupid idea to run two seperate entities for the same thing and compete against one another???...

Will groups be left behind.. YES... it happens in business... we see it happen with miners... the main worry is with nodes.. and the reasn that would happen is simple... nodes arent getting paid... if there was remuneration for nodes I think you would get a spike in just nodes another thought...

just my useless 5c

sweet

Regarding HF, there is talk on the dev list about making the network adapt faster to a sudden drop in mining nodes, I believe related to the upcoming halving.

I haven't read all the posts because I don't believe it will happen, but if the network does auto-adjust difficulty more quickly when there is a sudden drop in hash power, that could makes hard forks even more dangerous because both forks could continue to grow at near same rate even if one has much more consensus.

Maybe they are addressing that, I don't know, I don't like the dev list posting policies so I won't ask.

But that means a 2 MB fork should happen sooner rather than later if they are thinking about difficulty adjustment, the fork should happen before it becomes even more dangerous to fork.

Well if we have more room in blocks won't fees be lower? Lower minimum fees means spam attacks are cheaper no?

I agree with points. Quite of those 'pros' are directly or indirectly related to the first one. It does not make sense to list them all separately.

It won't.

This is not a pro and not related to OP.

Elaborate?