<p>As of June 24th 2013, There has not actually been a fork after the May 15th changes. That means that 0.6.0.6 should actually still work (though you shouldn't rely on that). This means that the fact that your client doesn't synchronize is caused by another issue, most likely a corrupted block chain database.</p>

<p>In case you didn't do things like copying wallets / using them from different locations (which you shouldn't), there should not really be a problem. Just upgrade, and you should get in sync, and the client will see (or try to get) the transaction confirmed. </p>

<p>Upgrading will take a while to 0.8.x, because of the new database layout, though. As a practical upshot, that also means the corrupted database won't matter. Oh, and make sure you have a wallet backup, and shutdown your client cleanly before upgrading.</p>

CC BY-SA 3.0
2013-06-24T17:49:52.123Z
thanks.  ill give it a try tonight and report back for anyone with similar concerns
syntax
CC BY-SA 3.0
2013-06-24T17:14:32.117Z
2013-06-24T19:43:05.750Z
2013-06-24T19:43:05.750Z
Pieter Wuille
<p>I have bitcoin client 0.6.0.6 (no longer supported!):</p>

<ol>
<li><p>I did not upgrade on May15.</p></li>
<li><p>My current client will not synchronize past 85%.</p>

<p>no luck with, DB_CONFIG set_lk_max_locks 537000 </p></li>
<li><p>I am in the process of trying to send coins, transaction remains unconfirmed</p></li>
</ol>

<p>How should I best proceed?</p>

<p>I am concerned about upgrading to new client without the current being fully synchronized. What are the issues?</p>

<p>Also, I have an unconfirmed transaction looming.  This transaction are coins being sent, not receiving coins.</p>

<p>I am somewhat frustrated; wish I had known about the May15/synch/upgrade issues before send transaction.  Perhaps that is confounding the synch somehow?  Anyhow, what is the best way to proceed?</p>

<p>Best and thanks in advance</p>

CC BY-SA 3.0
2013-06-24T16:34:36.510Z
Tried upgrading to the most recent version?
Nick ODell
CC BY-SA 3.0
2013-06-24T16:59:24.737Z
No, want to check that upgrade is not a problem, given current client is not fully synched and there is an unconfirmed transaction (send coins).  If I upgrade, then the new client should synch and detect my current wallet without any known issues? this is what I am trying to clarify. (sorry if these issues are independent/without effect on an upgrade)
syntax
CC BY-SA 3.0
2015-09-06T18:40:00.837Z
// , This looks sort of like a request for tech. support. Maybe try the forums?
Nathan Basanese
<bitcoin-core>
bitcoin upgrade needed: the current client is not synchronized
syntax
# bitcoin upgrade needed: the current client is not synchronized

(Asked by: username_0 on 2013-06-24)

I have bitcoin client 0.6.0.6 (no longer supported!):

1. I did not upgrade on May15.
2. My current client will not synchronize past 85%.

   no luck with, DB\_CONFIG set\_lk\_max\_locks 537000
3. I am in the process of trying to send coins, transaction remains unconfirmed

How should I best proceed?

I am concerned about upgrading to new client without the current being fully synchronized. What are the issues?

Also, I have an unconfirmed transaction looming. This transaction are coins being sent, not receiving coins.

I am somewhat frustrated; wish I had known about the May15/synch/upgrade issues before send transaction. Perhaps that is confounding the synch somehow? Anyhow, what is the best way to proceed?

Best and thanks in advance

**Tags:** bitcoin-core

> **Comments:**
> **username_1**: Tried upgrading to the most recent version?  
> **username_0**: No, want to check that upgrade is not a problem, given current client is not fully synched and there is an unconfirmed transaction (send coins).  If I upgrade, then the new client should synch and detect my current wallet without any known issues? this is what I am trying to clarify. (sorry if these issues are independent/without effect on an upgrade)  
> **username_2**: // , This looks sort of like a request for tech. support. Maybe try the forums?  

---

## 1 answers

### Answer by username_3 on 2013-06-24. Score: 0

As of June 24th 2013, There has not actually been a fork after the May 15th changes. That means that 0.6.0.6 should actually still work (though you shouldn't rely on that). This means that the fact that your client doesn't synchronize is caused by another issue, most likely a corrupted block chain database.

In case you didn't do things like copying wallets / using them from different locations (which you shouldn't), there should not really be a problem. Just upgrade, and you should get in sync, and the client will see (or try to get) the transaction confirmed.

Upgrading will take a while to 0.8.x, because of the new database layout, though. As a practical upshot, that also means the corrupted database won't matter. Oh, and make sure you have a wallet backup, and shutdown your client cleanly before upgrading.

> **Comments:**
> **username_0**: thanks.  ill give it a try tonight and report back for anyone with similar concerns  

---

