<p>Seems you answer the first question yourself :-).  Yes, it's a fork as it enforces new rules. But it does allow you to run an older version of <code>bitcoind</code> (not <em>recommended</em> though, but <em>supported</em>) and still be part of the Bitcoin network.</p>
<blockquote>
<p>is there any active &quot;soft&quot; branches in the network that I can transfer on ?</p>
</blockquote>
<p>This would mean there was a network split, what a <strong>soft</strong> fork is trying to avoid.<br />
There are still <a href="https://luke.dashjr.org/programs/bitcoin/files/charts/software.html" rel="nofollow noreferrer">old clients running</a> that for example do not enforce the last soft fork that occured (Segwit), but they are part of the Bitcoin network and not an alternate one because the change was backward-compatible.</p>

CC BY-SA 4.0
2020-07-24T16:16:19.467Z
Thank you a lot for your quick answer :)
ddavi031
CC BY-SA 4.0
2020-07-24T16:05:02.570Z
2020-07-24T16:10:31.983Z
2020-07-24T16:10:31.983Z
Antoine Poinsot
<p>I understand a soft fork occurs when changes in the Bitcoin protocol are backwards compatible, but why is that a fork? Is there really a branch or is that just a formality? Or does this give me a chance to run an older version of Bitcoin (older than the soft fork), and still be part of the system? But, again, why would I do such a thing. For example, is there any active &quot;soft&quot; branches in the network that I can transfer on? <br/>
Thank you guys!</p>

CC BY-SA 4.0
2020-07-24T17:46:36.517Z
Related: https://bitcoin.stackexchange.com/q/30817/5406
Murch
<soft-fork>
What is the point of a soft fork when it's backwards compatible?
ddavi031
# What is the point of a soft fork when it's backwards compatible?

(Asked by: username_0 on 2020-07-24)

I understand a soft fork occurs when changes in the Bitcoin protocol are backwards compatible, but why is that a fork? Is there really a branch or is that just a formality? Or does this give me a chance to run an older version of Bitcoin (older than the soft fork), and still be part of the system? But, again, why would I do such a thing. For example, is there any active "soft" branches in the network that I can transfer on?   
Thank you guys!

**Tags:** soft-fork

> **Comments:**
> **username_1**: Related: https://bitcoin.stackexchange.com/q/30817/5406  

---

## 1 answers

### Answer by username_2 on 2020-07-24. Score: 1 | Accepted answer

Seems you answer the first question yourself :-). Yes, it's a fork as it enforces new rules. But it does allow you to run an older version of `bitcoind` (not *recommended* though, but *supported*) and still be part of the Bitcoin network.

> is there any active "soft" branches in the network that I can transfer on ?

This would mean there was a network split, what a **soft** fork is trying to avoid.  
There are still [old clients running](https://luke.dashjr.org/programs/bitcoin/files/charts/software.html) that for example do not enforce the last soft fork that occured (Segwit), but they are part of the Bitcoin network and not an alternate one because the change was backward-compatible.

> **Comments:**
> **username_0**: Thank you a lot for your quick answer :)  

---

