joshua/dash-docs
1
0
Fork 0
mirror of https://github.com/seigler/dash-docs synced 2025-07-27 17:56:16 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions

Merge pull request #179 from luke-jr/073rc3_backports

Browse source 
Update May15 page with backports
This commit is contained in:
saivann 2013-05-10 18:34:38 -07:00
commit 1f70efadcd
1 changed files with 23 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

32
may15.html
View file

@ -6,9 +6,17 @@ layout: base-en
<h1>15 May 2013 Upgrade Deadline</h1> <h1>15 May 2013 Upgrade Deadline</h1>
<h2>What is happening</h2> <h2>What is happening</h2>
<p> <p>
If you are using Bitcoin-Qt/bitcoind version 0.7.2 or earlier, you must take action If you are using an old version of Bitcoin-Qt (or bitcoind, the server bitcoin software),
before 15 May, 2013. If you do nothing, you are likely to be left behind and you must either upgrade to version 0.8.0 or later before May 15, 2013,
will be out of sync with the rest of the Bitcoin network. <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 &quot;double-spend&quot; attack, where somebody sends
you bitcoins that the rest of the network would reject as invalid.
</p> </p>
<p> <p>
We recommend that you We recommend that you
@ -16,16 +24,21 @@ We recommend that you
before the 15th of May to avoid any issues. If you are a solo miner or mining pool operator, 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. please see the the notes at the end of this page for how to upgrade safely.
</p> </p>
<h2>If you cannot upgrade to version 0.8.1</h2> <h2 id="backports">If you cannot upgrade to version 0.8.1</h2>
<p> <p>
If you cannot upgrade to the latest version, you can still avoid the problem. 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 Create a file called DB_CONFIG in the bitcoin data directory, containing
these two lines: these two lines:
</p> </p>
<blockquote> <blockquote>
<pre> <pre>
set_lg_dir database set_lk_max_locks 537000
set_lk_max_locks 120000
</pre> </pre>
</blockquote> </blockquote>
<p> <p>
@ -40,7 +53,8 @@ re-indexing operation; you <b>must</b> wait for the reindex to complete before
serving work to miners. serving work to miners.
</p> </p>
<p> <p>
And if you are creating blocks and cannot upgrade to version 0.8.1 for some 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 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 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. or building on blocks incompatible with the rest of the network.
@ -54,7 +68,7 @@ still running old versions of Bitcoin-Qt/bitcoind. Therefore, the only option is
require everybody to either upgrade or workaround the bug. require everybody to either upgrade or workaround the bug.
</p> </p>
<div style="text-align:right"> <div style="text-align:right">
<i>This notice last updated: 18 March 2013 16:15 UTC</i> <i>This notice last updated: 10 May 2013 21:30 UTC</i>
</div> </div>
</section> </section>
</div> </div>