mirror of
https://github.com/seigler/dash-docs
synced 2025-07-27 01:36:13 +00:00
4213d102da
* Adds Makefile test to ensure all subheadings, except those on Choose Your Wallet, have an ID (anchor reference) * Adds an ID to all subheads that didn't have on previously
72 lines
3.1 KiB
HTML
72 lines
3.1 KiB
HTML
---
|
|
title: "15 May 2013 Upgrade Deadline"
|
|
alias: "may15"
|
|
active: false
|
|
banner: ""
|
|
---
|
|
<h2 id="what-is-happening">What is happening</h2>
|
|
<p>
|
|
If you are using an old version of Bitcoin-Qt (or bitcoind, the server bitcoin software),
|
|
you must either upgrade to version 0.8.0 or later before May 15, 2013,
|
|
<a href="#backports">upgrade to an up-to-date "backport" release</a>,
|
|
or <a href="#workaround">modify a file</a> and
|
|
restart bitcoin to work around a bug with the old software.
|
|
</p>
|
|
<p>This bug does not affect any bitcoins you already have, but if you do nothing you will
|
|
be out of sync with the rest of the Bitcoin network and will be unable to receive
|
|
bitcoins (payments sent to you will look like they never get confirmed, or will be confirmed
|
|
very slowly). You also risk being the victim of a "double-spend" attack, where somebody sends
|
|
you bitcoins that the rest of the network would reject as invalid.
|
|
</p>
|
|
<p>
|
|
We recommend that you
|
|
<a href="http://sourceforge.net/projects/bitcoin/files/Bitcoin/bitcoin-0.8.1/">upgrade to version 0.8.1</a>
|
|
before the 15th of May to avoid any issues. If you are a solo miner or mining pool operator,
|
|
please see the the notes at the end of this page for how to upgrade safely.
|
|
</p>
|
|
<h2 id="backports">If you cannot upgrade to version 0.8.1</h2>
|
|
<p>
|
|
If you cannot upgrade to the latest version,
|
|
<a href="https://bitcointalk.org/?topic=199699">backports to older branches are now in final testing</a>.
|
|
These include not only compatibility for the 15 May changes, but also fixes for known vulnerabilities and bugs, which have already been included and tested in the latest release.
|
|
</p>
|
|
<h2 id="workaround">If you cannot upgrade to a backport</h2>
|
|
<p>
|
|
If you cannot upgrade to any of the above, you can still avoid the problem.
|
|
Create a file called DB_CONFIG in the bitcoin data directory, containing this line:
|
|
</p>
|
|
<blockquote>
|
|
<pre>
|
|
set_lk_max_locks 537000
|
|
</pre>
|
|
</blockquote>
|
|
<p>
|
|
<a href="https://en.bitcoin.it/wiki/Data_directory">Look here</a> if you need help
|
|
finding the bitcoin data directory.
|
|
</p>
|
|
<h2 id="miners">Miners/mining pool operators</h2>
|
|
<p>
|
|
If you are creating new blocks (you are a solo miner or mining pool operator), then
|
|
you should be aware that upgrading from 0.7 to 0.8 requires a lengthy
|
|
re-indexing operation; you <b>must</b> wait for the reindex to complete before
|
|
serving work to miners.
|
|
</p>
|
|
<p>
|
|
And if you are creating blocks and cannot upgrade to version 0.8.1 or a
|
|
backport for some
|
|
reason, you should <b>not</b> set_lk_max_locks in a DB_CONFIG file until
|
|
May 15th; if you increase locks before then you run the risk of creating
|
|
or building on blocks incompatible with the rest of the network.
|
|
</p>
|
|
<h2 id="why-necessary">Why this is necessary</h2>
|
|
<p>
|
|
A bug caused a <a href="/chainfork">temporary block chain fork on 11 March, 2013</a>.
|
|
After investigating
|
|
that bug, we determined that the bug can happen even if the entire network was
|
|
still running old versions of Bitcoin-Qt/bitcoind. Therefore, the only option is to
|
|
require everybody to either upgrade or workaround the bug.
|
|
</p>
|
|
|
|
<div style="text-align:right">
|
|
<i>This notice last updated: Fri, 10 May 2013 21:30:00 UTC</i>
|
|
</div>
|