<p>When Bitcoin-Qt detects that something is seriously wrong with the network, it disables most RPC functionality in order to prevent automated Bitcoin sites from losing a lot of money due to network problems. (The okSafeMode functions are not disabled.) All versions since ~0.3 go into safe mode when the longest chain is invalid (illegal transaction, creating too much money, etc.). Upcoming versions will also go into safe mode when a large fork (valid or invalid) is in danger of overtaking the current chain.</p>

CC BY-SA 4.0
2020-02-05T10:59:22.167Z
I thought that the longest valid fork was in fact the "current chain".
Alessandro Polverini
CC BY-SA 3.0
2013-10-30T00:55:32.440Z
2013-10-30T00:55:32.440Z
theymos
<p>The <a href="https://github.com/bitcoin/bitcoin/blob/master/src/bitcoinrpc.cpp#L223" rel="nofollow">source code here</a> has a list of RPC commands and a "okSafeMode" parameter.</p>

<p>What is the purpose of this SafeMode and how does it affect the usage of the client?</p>

<bitcoin-core><json-rpc><safemode>
What is "safe mode" and how does it affect RPC Commands?
makerofthings7
# What is "safe mode" and how does it affect RPC Commands?

(Asked by: username_0 on 2013-10-29)

The [source code here](https://github.com/bitcoin/bitcoin/blob/master/src/bitcoinrpc.cpp#L223) has a list of RPC commands and a "okSafeMode" parameter.

What is the purpose of this SafeMode and how does it affect the usage of the client?

**Tags:** bitcoin-core, json-rpc, safemode


---

## 1 answers

### Answer by username_1 on 2013-10-30. Score: 1 | Accepted answer

When Bitcoin-Qt detects that something is seriously wrong with the network, it disables most RPC functionality in order to prevent automated Bitcoin sites from losing a lot of money due to network problems. (The okSafeMode functions are not disabled.) All versions since ~0.3 go into safe mode when the longest chain is invalid (illegal transaction, creating too much money, etc.). Upcoming versions will also go into safe mode when a large fork (valid or invalid) is in danger of overtaking the current chain.

> **Comments:**
> **username_2**: I thought that the longest valid fork was in fact the "current chain".  

---

