6 ms·
An important thing to consider is that, while there probably is an ideal block size for the current set of conditions (risk of centralization, average Bitcoin n
by CydeWeys 11y ago
An important thing to consider is that, while there probably is an ideal block size for the current set of conditions (risk of centralization, average Bitcoin network latency, rate of transactions), there's no a priori reason that it should be 1 MB. It may well be less than 1 MB, or it may well be more. 1 MB is arbitrary. My best guess is that the optimal current block size is somewhat larger than 1 MB.
- wsxcde 11y ago> My best guess is that the optimal current block size is somewhat larger than 1 MB. I disagree. There's good reason to believe the ideal block size is now smaller than 1 MB because large pools have been caught red-handed not validating blocks. (Which is like their ONE job and the the thing they get paid the big bucks for!) Presumably, the only reason they're doing this is because orphan rates are too high, which in turn suggests block sizes are too high.
- paulmd 11y agoClassic tragedy of the commons: for everyone as a whole, it's better to process transactions as fast as possible. But with the way incentives are currently structured, it's better for any individual miner to produce an empty block that propagates faster. Or in other words, to process transactions as slowly as possible. There's two ways you can fix the incentives. One would be to kill the block reward. You don't process transactions, you don't get any fees. This would likely cause a massive increase in transaction fees if the network were to retain its current hashrate (and thus level of security). The other way is to make a law, basically. You'd need a hardfork that refuses to recognize any block that isn't at least 75% full, but you keep the block reward and thus avoid blowing up transaction costs. This has the problem that the network could "stall out" under the right conditions (no incoming transactions, gigabyte blocksize, etc). Or instead of messing with incentives you can change the protocol itself - if everyone works on the same transaction set then all you really need is a fixed-size structure to propagate the winning hash, and there are no empty blocks unless there's no incoming transactions. Again, you're talking a hardfork and this one would involve core changes to the Bitcoin protocol.
- pstrateman 11y ago> Classic tragedy of the commons You're absolutely right on that, but you have the issue backwards. Each individual miner has an incentive to build a block which pays the most in fees. That means that as long as the transaction rate is less than the absolute limit, fees will tend towards zero. (Any fee is marginally better than nothing). The size of the block and propagation time are no longer strongly correlated thanks to the hard work of Matt Corallo on the relay network ( http://bitcoinrelaynetwork.org/ http://bitcoinrelaynetwork.org/ ).
- paulmd 11y agoSeparate of the blocksize issue - fundamentally I don't think the network should run on the back of transaction fees. The benefit of a high hashrate (a secure network) isn't limited only to those actively transferring money. Anyone who holds Bitcoin has a stake in the network. Everyone also benefits from high scalability of transaction processing, so ideally transaction fees should stay low or zero. I don't accept the idea of meta-currency (alt-currencies and sidechains) to rectify this situation - too much risk when you have a known quantity that works pretty OK. It also decreases security by splitting processing power. If the problem is that it doesn't scale well, fix it, don't replace it. Joel on Programming's #1 Thing You Should Never Do: start over from scratch. It's impossible to maintain the massive amount of processing power spent on this solely through transaction fees. Block rewards effectively socialize this collective interest in network security though a very low level of inflation, which hits the right population (Bitcoin holders as a whole). To me transaction fees should be nothing more than spam prevention, to prevent a DOS attack from clogging up the transaction blocks. Really there's no reason you couldn't have an arbitrarily-large transaction block as long as the bandwidth is reasonable. You still have the problem of the chain becoming too great in size, but that's a problem with some pretty obvious answers.
- pstrateman 11y ago> It's impossible to maintain the massive amount of processing power spent on this solely through transaction fees. 0.00625 BTC in fees is enough to match the current block reward. That's to say the current security of the network would continue on if everybody paid $1.63 per transaction in fees. > You still have the problem of the chain becoming too great in size, but that's a problem with some pretty obvious answers. Uh... like what?
- pstrateman 11y ago> My best guess is that the optimal current block size is somewhat larger than 1 MB. The optimal current block size is without a doubt smaller than 1MB. The two most important metrics for block size limit are node count and miner validation. Node count has been continually dropping for years despite heroic efforts to improve performance in bitcoin core. Miners have been found to be blindly mining blocks in an attempt to reduce their orphan rates.
- statoshi 11y agoThe optimal block size is obviously 0, as these blocks will propagate through the network the fastest, thus lowering the orphan rate to nearly 0, and will require the least resource usage (bandwidth, hard disk space, CPU cycles) for full node operators. ... see what I did there?
- pstrateman 11y agoThe blocksize limit is fundamentally a trade off between capacity and usability. Too far in either direction is bad. The evidence strongly supports the argument that the current 1MB limit is too high.
- davidgerard 11y agoDescribing what miners are doing already, with no-transaction blocks and not bothering to verify existing blocks?
- CydeWeys 11y agoDo you really think that the number of full nodes has been dropping because of the 1 MB block limit though? Not for other reasons? Is it really so onerous to run a full node now that the average computer cannot handle it?