<p>Typically, this is caused by a corrupted block chain database - it causes your client to consider the real chain invalid, and try to find another one. Since the real chain remains the longest obviously, it shows this warning, as it notices its opinion differs from the rest of the network.</p>

<p>The solution is deleting blkindex.dat/blk000?.dat and let redownload the chain. In case you're running 0.8 (if not, upgrade), you can just use -reindex to rebuild the database (no downloading necessary in that case).</p>

CC BY-SA 3.0
2013-02-25T10:30:27.143Z
2013-02-25T10:30:27.143Z
Pieter Wuille
<p>While trying to retrieve the private key from satoshi bitcoin client i'm getting this error code:  </p>

<p>Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade. (code -2)</p>

<p>Does anyone know how to fix this?</p>

<p><strong>It is QT VERSION 4.8.2 &amp; v0.7.2-beta in the lower right hand corner it says it is catching up but has not added any blocks for a really, really, really, long time, it sitting on 90.13% . What else do you need to know?</strong></p>

<p><strong>I am Technically inept so I need to be clear so I dont screw up. I NEED THE PRIVATE KEYS for 2 ADDRESSES generated by this bitcoin-qt, when I type in dumpprivkey address I get the above error message. Will upgrading cause a conflict?  What is the proper way to upgrade as I dont see that as an option?</strong> </p>

CC BY-SA 3.0
2013-02-25T10:21:17.740Z
Are you sure this is the *bitcoin* client and not some other coin? What version of the client do you have?
David Schwartz
CC BY-SA 3.0
2013-02-25T15:37:40.387Z
If it is about Freicoin, this message was showing up because there was a malevolent hard fork (didn't followed freicoin rules) that has been actually longer than freicoin's chain for some time. When the client sees a longer chain that doesn't follow the rules it enters in safe mode, disabling some features such as sending coins.

The attack seems to have stopped, but you may need to run the client disabling the auto-safe-mode stuff.

Is it about Freicoin ?
jtimon
CC BY-SA 3.0
2013-02-25T21:31:39.590Z
Before anything: make a backup of wallet.dat, by using the backup function in the menu. Then, just install 0.8 and let it rebuild its database.
Pieter Wuille
<private-key>
How Do I Fix: "Safe mode: Warning: Displayed transactions may not be correct!"
Shon
# How Do I Fix: "Safe mode: Warning: Displayed transactions may not be correct!"

(Asked by: username_0 on 2013-02-25)

While trying to retrieve the private key from satoshi bitcoin client i'm getting this error code:

Safe mode: Warning: Displayed transactions may not be correct! You may need to upgrade, or other nodes may need to upgrade. (code -2)

Does anyone know how to fix this?

**It is QT VERSION 4.8.2 & v0.7.2-beta in the lower right hand corner it says it is catching up but has not added any blocks for a really, really, really, long time, it sitting on 90.13% . What else do you need to know?**

**I am Technically inept so I need to be clear so I dont screw up. I NEED THE PRIVATE KEYS for 2 ADDRESSES generated by this bitcoin-qt, when I type in dumpprivkey address I get the above error message. Will upgrading cause a conflict? What is the proper way to upgrade as I dont see that as an option?**

**Tags:** private-key

> **Comments:**
> **username_1**: Are you sure this is the *bitcoin* client and not some other coin? What version of the client do you have?  
> **username_2**: If it is about Freicoin, this message was showing up because there was a malevolent hard fork (didn't followed freicoin rules) that has been actually longer than freicoin's chain for some time. When the client sees a longer chain that doesn't follow the rules it enters in safe mode, disabling some features such as sending coins.  The attack seems to have stopped, but you may need to run the client disabling the auto-safe-mode stuff.  Is it about Freicoin ?  
> **username_3**: Before anything: make a backup of wallet.dat, by using the backup function in the menu. Then, just install 0.8 and let it rebuild its database.  

---

## 1 answers

### Answer by username_3 on 2013-02-25. Score: 4

Typically, this is caused by a corrupted block chain database - it causes your client to consider the real chain invalid, and try to find another one. Since the real chain remains the longest obviously, it shows this warning, as it notices its opinion differs from the rest of the network.

The solution is deleting blkindex.dat/blk000?.dat and let redownload the chain. In case you're running 0.8 (if not, upgrade), you can just use -reindex to rebuild the database (no downloading necessary in that case).


---

