[fidelramos]

That is one of the important points point made by jtoomin in the first post of this thread: the energy consumption of a PoW blockchain if not proportional to the number of transactions. This means we could have everyone, everywhere, using a PoW blockchain with the same percentage of energy consumption as today (although it would probably rise as price would arguably also rise as demand increases, but it would eventually find an equilibrium, it will never "consume all electricity").

[michaelt]

Didn't bitcoin have the chance to double their transactions-per-second for a constant amount of power consumption, in the form of Segwit2x, and decide not to do so?

The fact Bitcoin could be more efficient and chooses not to isn't really an improvement over being unable to be more efficient IMHO - in fact arguably it's worse.

[fidelramos]

I completely agree, increasing the maximum block size is the simplest way to scale. Bitcoin BTC refused to do that, keeping the 1 MiB maximum block size instituted by Satoshi Nakamoto in 2010 as a spam-prevention measure, which led to raising transaction fees as users compete for the scarce block space. That is also the reason why Bitcoin Cash BCH was born in August 2017: to raise the maximum block size and allow the Bitcoin blockchain to process more transactions per second while keeping fees low.

At the technical level BCH has showed that the network is stable in production with 20 MiB blocks, but the goal and ongoing work is to support gigabyte and eventually terabyte blocks so it would scale to worldwide usage while keeping transaction fees low. The counterargument by Bitcoin BTC is that large blocks centralize the network, as not everyone can afford to run a full node. That's a different debate that I would be happy to discuss, but I want to start by pointing out that keeping the block size low also centralizes the network, as many users will not be able to afford the increasing transaction fees (which rose to $50 at recent times). Does it make sense to restrict the network so anyone can run a $50 node but not be able to transact on it? I think decentralization is a means to an end (electronic P2P cash), not a goal in itself. In other words, blockchains should be decentralized enough that no single entity can take control of the network, but too much decentralization is inefficient, so an equilibrium must be found.

[WanderPanda]

> In other words, blockchains should be decentralized enough that no single entity can take control of the network, but too much decentralization is inefficient, so an equilibrium must be found.

I believe that is the hardest problem that bitcoin didn‘t solve. The hashrate is governed by the price and a arbitrary halving schedule. There is no mechanism to regulate the hashrate to a certain setpoint where attacking the network is not feasible. This issue becomes even more severe when the block reward is dominated by fees in the future. In that scenario the hashrate is not so much determined by the price anymore but the available block space and the utility of on-chain transactions. It is really hard to judge bitcoins security model considering all these variables. But for now the solution seems to be to vastly overcommit hashrate

[shawnz]

It's not becoming more efficient if you are just allowing blocks to be filled with frivolous data that wouldn't have otherwise ever been put on the blockchain.

It's easy to increase the block size, but it's very unlikely it would ever be decreased again, so it makes sense to wait until there is no other option.

[irae]

Bitcoin strength and value is on decentralization. If you increase the block size, it will be seized by governments or large corporations. This has long being debated, and the reason it is like it is today, is that everyone really vested into it agreed (in a distributed way) to keep it as so.

More on that here: https://twitter.com/DocumentingBTC/status/139399717145689293...

And you can even buy books explaining this way better than I (or twitter) can.

[fidelramos]

> If you increase the block size, it will be seized by governments or large corporations.

That doesn't make any sense. Any actor, like for example a government, might seize (control) a blockchain by having overwhelming mining majority (51% attack), but that has little to do with the size of the blockchain itself.

The only reason one might have to think that way is believing the false narrative that a BTC "full node" does anything to secure the network. Only mining nodes secure the network, having a copy of the full blockchain is not enough.

Edit: typo.

[xref]

Just says “tweet unavailable” for me, and I don’t understand how a 2mb block means a government can “seize” Bitcoin where they can’t with a 1mb block

[irae]

today with a raspberry pi and a 1TB hard drive you can have a node and be one of the validators. If hardware is unattainable by the users interested in helping with decentralization (and there are few enough of those) large corporations or governments will be the only validators and defeat the purpose of decentralization

[dathinab]

This is only the case of you would arbitrarily increase the number of potential transactions per block.

But as far as I know the maximal number of transactions is capped in practice.

Furthermore the security of PoW is based on it being far more expensive to mess with it then to mine it. But if you push more mommy through the same number of blocks it's at some point breaking apart.

Lastly no one says it will ever consume all energy. That works be absurd. It's about the required energy (and hardware cost) in relationship to the provided value being unhinged and for security you need steadily increasing energy costs for increased usage.

[fidelramos]

> But as far as I know the maximal number of transactions is capped in practice.

What do you mean? There are no hard technical impediments to Bitcoin being able to scale to worldwide usage with basically the same structure as today. It's a matter of optimizing software and having powerful hardware (that is available today, and will be even cheaper in the future). This article by Johannes Vermorel [1] goes over it in detail.

If you have any evidence that goes counter to this I would love to read more about it.

[1] http://blog.vermorel.com/journal/2017/12/17/terabyte-blocks-...