Re: How a floating blocksize limit inevitably leads towards centralization

The absolute minimum transaction size(1) is for single input single-output transactions. They are 192 bytes each, 182 if transaction combining is aggressively used. 1MiB/10minutes * 182bytes = 9.6tx/s

Ok, let's go with 9.6 tps. That means roughly 25,000,000 transactions per month. If Bitcoin becomes a payment backbone where users transactions are reconciled monthly, the current blocksize limit supports 25 million users. I strongly dislike hard forks, so until we have several million users, the blocksize needs to be left alone.

When the user is in serveral millions, it is even harder for a hard fork. Actually, that is almost an event that may kill bitcoin.

Bullshit. Bitcoin is entirely voluntary and nodes are entirely sovereign. What this means is that if you don't like the rules, you can fork Bitcoin and go your separate way where your bitcoins are incompatible with mine. My Bitcoin doesn't get hurt from that, well only as much as the exchange rate would likely drop due to decreased demand if many users left. And you can have a new Bitcoin out of thin air with new rules and if you can find enough demand for it it can also be valuable and keep a respectable exchange rate.

There is no need for a one size fits all solution with Bitcoin. We can have as many forks as we want. And you can use the one the rules of which you agree with and I'll stick with the one the rules of which I agree with.