http://sourceforge.net/mailarchive/message.php?msg_id=30587843 https://bitcointalk.org/index.php?topic=152030.0
-
Rav3nPL commented at 9:13 AM on March 12, 2013: contributor
-
PartTimeLegend commented at 10:13 AM on March 12, 2013: none
This would make no sense. The block size is too small for scaling at 1 mb currently.
There is no point in decreasing size. This would just break more things and would require a hard fork.
-
Rav3nPL commented at 12:50 PM on March 12, 2013: contributor
We have hard fork because all daemons under 0.8 NOT accept 1MB blocks. Force upgrade to 0.8 or it will come back and hit again.
-
gmaxwell commented at 12:54 PM on March 12, 2013: contributor
This issue is confused. The issue is not directly caused by size. And you can't solve one hardfork by adding another, unless you mean the target, in which case it's still is the wrong thing to change to avoid the issue.
- gmaxwell closed this on Mar 12, 2013
-
Rav3nPL commented at 3:31 PM on March 12, 2013: contributor
Ok, how then avoid same situation in future? Majority of users are on old (<0.8) versions that use BDB and WILL have same trouble when some mine will create another huge block... New database system is superior to BDB and we should force users at some point to upgrade to avoid same issue in future or limit new versions to not produce blocks that will not be accepted by older clients. But second option will be step back, when BTC become more and more popular there will be more and more txes and blocks will be larger and larger...
-
jgarzik commented at 3:34 PM on March 12, 2013: contributor
It is being worked on, but outside the scope of this github issue.
- DrahtBot locked this on Sep 8, 2021
Contributors