FS#48099 - [bitcoin-qt] Switch to bitcoin-classic?
Attached to Project:
Community Packages
Opened by Melanie (zanny) - Monday, 08 February 2016, 18:10 GMT
Last edited by Timothy Redaelli (tredaelli) - Wednesday, 10 February 2016, 15:27 GMT
Opened by Melanie (zanny) - Monday, 08 February 2016, 18:10 GMT
Last edited by Timothy Redaelli (tredaelli) - Wednesday, 10 February 2016, 15:27 GMT
|
Details
This is like libav vs ffmpeg, except more dramatic and
adoption actually matters in the short term.
https://bitcoinclassic.com/ bitcoin-classic is forking bicoin-core, with the intent to increase block size to 2MB and make no other immediate changes. The upstream bitcoin-core developers have refused to increase the blocksize in the official release (this one) so the community is trying to get consensus in full nodes to force it (ie, Arch users running a full blockchain node with bitcoin-qt). Many Arch bitcoin users may not know this even exists. A tremendous number of participating miners and web services around bitcoin are supporting it, so I think it would be nice if Arch supported classic, either as an update to bitcoin-qt itself or as a separate package (it is already on the AUR). Bitcoin-classic's block size increase won't take effect until 75% of full nodes have consensus on it, so it is relevant to the proposal to get classic made available to users. If it succeeds in gaining adoption and hardforking the protocol, there is a 28 day grace period before the bitcoin-core client will stop working (unless they merge the classic blocksize increase and release a compatible update). Either way, we should have a plan to adopt it if / when it does happen. I hope this isn't inappropriate as a feature request, but I'm not sure of anywhere in the official forum or on the mailing list to bring something like this up. It is kind of absurd and thankfully fairly rare when an upstream software project refuses to adopt changes according to super-majority consensus. |
This task depends upon
Closed by Timothy Redaelli (tredaelli)
Wednesday, 10 February 2016, 15:27 GMT
Reason for closing: Won't implement
Additional comments about closing: bitcoin-classic package on aur is actually broken (wrong depency on qt5), outdated and with only one vote.
If the bitcoin-classic package will receive enough votes (more than 10) and someone else wants to maintain it, it can be ported on community by someone else with bitcoin-core, not as a replacement.
Wednesday, 10 February 2016, 15:27 GMT
Reason for closing: Won't implement
Additional comments about closing: bitcoin-classic package on aur is actually broken (wrong depency on qt5), outdated and with only one vote.
If the bitcoin-classic package will receive enough votes (more than 10) and someone else wants to maintain it, it can be ported on community by someone else with bitcoin-core, not as a replacement.