[arcatek]

If they start to play with different rules, one of the hard fork remaining branches (or both) will be refused by everyone on the network and be worthless.

There's no telling whether it'd be the "hijacked" branch or the original one - assuming they control 50%+ of the mining power, there's a decent argument that the remaining miners would follow their lead if only to stay on the largest branch.

[dannyw]

What miners do is irrelevant: the code known as bitcoin, with a 21M hard cap, simply will reject any block that creates more than its allowed bitcoins as invalid, the same way it rejects a random string of bytes as invalid.

[danbruc]

Depending on your definitions this might or might no be true but it also might be totally irrelevant.

There is a protocol and system specification. There are implementations of that specifications. There is a distributed system running those implementations. And the distributed system has a state. Each of those can change and each of those or a combination of them could arguably be called Bitcoin.

If everyone would run new implementations with a different coin cap, you can argue that it is no longer Bitcoin because Bitcoin is a very specific specification with a 21M coin cap, but this would have little bearing on the actual situation.

[tinus_hn]

This is like saying because some people own the majority of printing presses, money is worthless.

Money has worth because people accept it in exchange for goods and services.

Bitcoin has worth because people accept it in exchange for goods and services.

It’s not the miners that create value, it’s the merchants. If miners start some fork they’ll leave the main blockchain, which will run fine without them. And they have absolutely no way of forcing anyone to use their fork. Only if the merchants start accepting coins from the forked blockchain will it become valuable. But that’s up to the merchants, not the miners.

There are problems with one miner controlling over 50% of the mining power. This is not such a problem.

[namaria]

Cryptoheads really gone from "printed money is becoming worthless, we need currency with enforced scarcity" to "it's all arbitrary anyway".

It's been quite educational watching the whole cryptocurrency community re-invent economics 101 and find out the problem has never been technical, always been political.

[jstanley]

The point is you need the economic majority to be on side in order to succeed with a hard fork. Just the top 50 miners switching on their own isn't enough.

[thesz]

Add 50 more - to reduce hash rate even more. Announce hard fork right after difficulty adjustment. And then, suddenly, these who have not forked will be stalled for several weeks. Instead of 10 minutes per block, the time will be 30 minutes and possibly more. And to adjust the difficulty those who have not forked would need... a hard fork?

Yes, these 100 miners are pools. But where pool participants will go then? Will pools who have not forked keep pool participation fees low?

Etc.

The game here is not quite simple. It is much more complex than appears at first sight.

[tinus_hn]

The difficulty adjusts automatically. Bitcoin wouldn’t have come this far if it were that fragile.

[jstanley]

It doesn't adjust immediately though. If a large majority of miner suddenly disappears then the block mining rate does indeed drop until the next difficulty adjustment.

[UncleMeat]

In the sense that updating the code to do something else would make it “not Bitcoin”, sure. But I really don’t think this matters to much of anybody if the “OG Bitcoin” drops to zero and the hard fork with new behavior wins.

[capableweb]

Developers of the core protocol would notice, add a flag and then miners/clients/exchanges who want to remain with the same dev team can signal they want to follow the "dev" chain instead of the "miner" chain.

Usually forks have checkpoints as well so things can't change willy-nilly.

[jstanley]

If blocks in the "miner" chain break the rules of the "dev" chain, then no flag is required. You'll automatically stick with the chain that contains valid blocks, as determined by the implementation that you're running.