<p>You can build any of the stable releases by checking out a tagged branch. For <code>v24.0.1</code>, this would be something like this:</p>
<pre class="lang-sh prettyprint-override"><code>git checkout v24.0.1
</code></pre>
<p>and then proceed with building, same as before. Regarding downgrading, generally speaking, you should have no issues when upgrading or downgrading between client versions but you should always check the release notes to see if there is a downgrade warning and any additional steps you might need to take.</p>
<p>In your case, there are no release notes yet, so make a backup of your <code>wallet.dat</code> file before downgrading the client. In the very unlikely event that you have issues with your block data or chainstate data after downgrading, you can first try running <code>-reindex-chainstate</code> before resorting to re-doing IBD.</p>
<p>EDIT: as mentioned in the comments, it is usually possible to use an older <code>wallet.dat</code> file with a newer client but not always guaranteed that a newer <code>wallet.dat</code> file can be used with an older client. Make sure you have a backup as you may need to sweep the funds to an intermediary wallet first and then transfer them to a newly created wallet on the downgraded client.</p>

CC BY-SA 4.0
2023-02-15T10:07:16.520Z
To be honest even if Bitcoin Core's master is reasonably stable, downgrading a wallet from a development version to the previous release sounds inadvisable. There could have been any forward incompatible change that were made during the development cycle. I'm not even sure we have any guarantee of forward-compatibility between release generally?
Antoine Poinsot
CC BY-SA 4.0
2023-02-15T10:19:33.090Z
Good point regarding forward compatibility, as we mostly try to guarantee backward compatibility. I'll amend the answer.
josie
CC BY-SA 4.0
2023-02-15T10:03:54.503Z
2023-02-15T10:44:02.770Z
2023-02-15T10:44:02.770Z
josie
<p>If you have downloaded the source from the GitHub repo, you can simply checkout to the proper release branch and re-install the software following the tutorial again. Installing the binaries should not affect the user data.</p>
<p>To checkout to the proper branch just do:</p>
<pre><code>git checkout v24.0.1
</code></pre>
<p>If the <code>v24.0.1</code> tag happens not to be present in your local copy, you can fetch the tags from upstream:</p>
<pre><code>&gt; git checkout v24.0.1
error: pathspec 'v24.0.1' did not match any file(s) known to git
</code></pre>
<pre><code>git fetch origin
git checkout v24.0.1
</code></pre>
<p>If you're concerned about potentially losing your wallet data, I'd recommend you make a backup of the user directory just to be safe. Given you're linking to a macOS installing guide, your user directory should be located at <code>/Users/${USER}/Library/Application Support/Bitcoin/</code>.</p>

CC BY-SA 4.0
2023-02-15T10:05:01.060Z
2023-02-15T10:05:01.060Z
sr_gi
<p>I wanted to build Bitcoin Core myself, so I followed <a href="https://github.com/bitcoin/bitcoin/blob/master/doc/build-osx.md" rel="nofollow noreferrer">this official guide</a>, but in the process I failed to realize that by cloning the git repo I would just get the latest source code, not the latest stable release. I have downloaded the full blockchain, created a wallet, deposited funds, but I am running a pre-release version, 24.99. Is it possible to downgrade to the latest stable release (24.0.1)? What are the consequences, do I need to redownload the blockchain, restore my wallet, etc?</p>

CC BY-SA 4.0
2023-02-15T10:10:06.350Z
I would advise moving your funds to another wallet, and sending them back after you downgraded to `24.0.1` and created a new wallet. I don't expect there'd be any issue in this particular case (i could be very wrong though!), but IMHO you should not expect any forward-compatibility guarantee between a development branch and the latest release.
Antoine Poinsot
<bitcoin-core><blockchain><wallet><synchronization><compiling>
Downgrading Bitcoin Core 24.99 (latest source code) to 24.0.1
Rits
# Downgrading Bitcoin Core 24.99 (latest source code) to 24.0.1

(Asked by: username_0 on 2023-02-15)

I wanted to build Bitcoin Core myself, so I followed [this official guide](https://github.com/bitcoin/bitcoin/blob/master/doc/build-osx.md), but in the process I failed to realize that by cloning the git repo I would just get the latest source code, not the latest stable release. I have downloaded the full blockchain, created a wallet, deposited funds, but I am running a pre-release version, 24.99. Is it possible to downgrade to the latest stable release (24.0.1)? What are the consequences, do I need to redownload the blockchain, restore my wallet, etc?

**Tags:** bitcoin-core, blockchain, wallet, synchronization, compiling

> **Comments:**
> **username_1**: I would advise moving your funds to another wallet, and sending them back after you downgraded to `24.0.1` and created a new wallet. I don't expect there'd be any issue in this particular case (i could be very wrong though!), but IMHO you should not expect any forward-compatibility guarantee between a development branch and the latest release.  

---

## 2 answers

### Answer by username_2 on 2023-02-15. Score: 3

You can build any of the stable releases by checking out a tagged branch. For `v24.0.1`, this would be something like this:

```sh
git checkout v24.0.1

```

and then proceed with building, same as before. Regarding downgrading, generally speaking, you should have no issues when upgrading or downgrading between client versions but you should always check the release notes to see if there is a downgrade warning and any additional steps you might need to take.

In your case, there are no release notes yet, so make a backup of your `wallet.dat` file before downgrading the client. In the very unlikely event that you have issues with your block data or chainstate data after downgrading, you can first try running `-reindex-chainstate` before resorting to re-doing IBD.

EDIT: as mentioned in the comments, it is usually possible to use an older `wallet.dat` file with a newer client but not always guaranteed that a newer `wallet.dat` file can be used with an older client. Make sure you have a backup as you may need to sweep the funds to an intermediary wallet first and then transfer them to a newly created wallet on the downgraded client.

> **Comments:**
> **username_1**: To be honest even if Bitcoin Core's master is reasonably stable, downgrading a wallet from a development version to the previous release sounds inadvisable. There could have been any forward incompatible change that were made during the development cycle. I'm not even sure we have any guarantee of forward-compatibility between release generally?  
> **username_2**: Good point regarding forward compatibility, as we mostly try to guarantee backward compatibility. I'll amend the answer.  

---

### Answer by username_3 on 2023-02-15. Score: 1

If you have downloaded the source from the GitHub repo, you can simply checkout to the proper release branch and re-install the software following the tutorial again. Installing the binaries should not affect the user data.

To checkout to the proper branch just do:

```
git checkout v24.0.1

```

If the `v24.0.1` tag happens not to be present in your local copy, you can fetch the tags from upstream:

```
> git checkout v24.0.1
error: pathspec 'v24.0.1' did not match any file(s) known to git

```

```
git fetch origin
git checkout v24.0.1

```

If you're concerned about potentially losing your wallet data, I'd recommend you make a backup of the user directory just to be safe. Given you're linking to a macOS installing guide, your user directory should be located at `/Users/${USER}/Library/Application Support/Bitcoin/`.


---

