Tag Archives: bitcoin-qt

Reminder: Hard Fork Coming May 15th, Backports Of v0.8.1 Fix Available

Leave a reply
Reminder: Hard Fork Coming May 15th, Backports Of v0.8.1 Fix Available:

A post on Bitcoin Money (@BitcoinMoney) blog describes the upcoming May 15th 2013 hard fork:

“Released following the Bitcoin blockchain fork on March 11th 2013 was an updated v0.8 client (v0.8.1) that temporarily respects an undocumented limit found in all prior versions of the Bitcoin-Qt/bitcoind clients.”
-
“That temporary grace period ends and on May 15th 2013 (12:00 am UTC) any node that still hasn’t been fixed to remove this limitation will eventually find itself rejecting valid blocks from the Bitcoin blockchain. It is possible that these unfixed nodes will see block confirmations but those blocks will not be part of the longest chain so it is critical that no commerce continue on or after May 15th using a node that hasn’t been upgraded.”
-
“Release v0.8.1 of Bitcoin-Qt/bitcoind has been available since March 18th, 2013 and accommodates the May 15th 2013 hard fork properly. The fix has been backported to v0.7.3, v0.6.5, v0.5.8, and v0.4.9 clients as well.”

 - http://www.bitcoinmoney.com/post/50027334954
 - http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.1
 - http://bitcointalk.org/index.php?topic=199699.0 (Backports)

All News - Daily E-mail Subscription - Twitter: @BitcoinNews

Gavin Andresen – Core Development Update #3

Leave a reply
Gavin Andresen - Core Development Update #3:

Excerpts from the latest update from Bitcoin.org project lead Gavin Andresen (@GavinAndresen):

“If you are using bitcoind or Bitcoin-Qt and you haven’t upgraded yet, you should: the new release [v0.8] is much faster and is more gentle on your disk drives.”
-
“[Foundation member Saivann Carignan is] redesigning the bitcoin.org website. He has also been doing the hard work of getting rough consensus on what the design and content should be,”
-
“This week transaction volume reached the voluntary, easy-to-change, 250,000 bytes-per-block limit — and that caused some pain for people. […] At least a couple of the big pools have decided to increase the size of the blocks they create.”
-
“There is a non-voluntary, hard-to-change, 1,000,000-bytes-of-transactions-per-block limit that needs to be raised. […] I’m confident that raising the 1MB limit will be only slightly painful for most people– you’ll just have to upgrade old Bitcoin software.”

 - https://bitcoinfoundation.org/blog/?p=135
 - http://bitcointalk.org/index.php?topic=149668.0 (Further discussion of the scalability issue)

All News - Daily E-mail Subscription  - Twitter: @BItcoinNews