<p>The builder keys file has moved to a <a href="https://github.com/bitcoin-core/guix.sigs/tree/main/builder-keys" rel="nofollow noreferrer">different repository</a>. The <a href="https://bitcoincore.org/en/download/#verify-your-download" rel="nofollow noreferrer">download verification instructions</a> on the bitcoincore.org website were updated. Follow the steps detailed there to verify your Bitcoin Core download.</p>

CC BY-SA 4.0
2023-03-22T08:47:05.300Z
2023-12-26T18:39:49.957Z
2023-12-26T18:39:49.957Z
Antoine Poinsot
<p>gpg --list-keys</p>
<p>wget <a href="https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/achow101.gpg" rel="nofollow noreferrer">https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/achow101.gpg</a></p>
<p>wget <a href="https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/benthecarman.gpg" rel="nofollow noreferrer">https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/benthecarman.gpg</a></p>
<p>wget <a href="https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/fanquake.gpg" rel="nofollow noreferrer">https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/fanquake.gpg</a></p>
<p>gpg --import achow101.gpg</p>
<p>gpg --import benthecarman.gpg</p>
<p>gpg --import fanquake.gpg</p>
<p>gpg --verify SHA256SUMS.asc</p>

CC BY-SA 4.0
2023-02-19T21:34:56.653Z
2023-02-19T21:36:39.873Z
2023-02-19T21:36:39.873Z
user140327
<p>You'll just have to follow the steps listed at</p>
<p><a href="https://bitcoincore.org/en/download/" rel="nofollow noreferrer">https://bitcoincore.org/en/download/</a></p>
<p>But essentially, you're doing it right, downloading those three files and then running sha256sum returns the following:</p>
<pre><code>$ sha256sum --ignore-missing --check SHA256SUMS
bitcoin-24.0.1-x86_64-linux-gnu.tar.gz: OK
</code></pre>

CC BY-SA 4.0
2023-02-10T00:40:54.930Z
So I don't need to get public keys anymore and verify it? Cause when I follow the instructions the rest doesn't make sense cause of missing pages on GitHub.
DJ_Splash
CC BY-SA 4.0
2023-02-10T10:35:00.747Z
Not really sure what steps are you following. The official documentation is the one I linked to on my original answer.
mrn_gomez
CC BY-SA 4.0
2023-02-11T00:08:27.273Z
This answer seems to be missing most of the point.
Pieter Wuille
CC BY-SA 4.0
2023-02-18T11:22:48.100Z
That's verifying the checksums match, bit is missing the gpg verification of the checksum file's authrnticity
cdecker
CC BY-SA 4.0
2023-02-09T22:42:01.163Z
2023-02-09T22:42:01.163Z
mrn_gomez
<p>I am a newbie when it comes to setting up a bitcoin node but I am trying to gpg verify my bitcoin core download the pub keys to do so are no longer available. I have tried doing my own research but I can't seem to find someone to explain in Layman's terms how to do so now.</p>
<p>I have downloaded all three files needed to do so:</p>
<pre><code>bitcoin-24.0.1-x86_64-linux-gnu.tar.gz
SHA256SUMS 
SHA256SUMS.asc
</code></pre>
<p>I have verified the checksum of the release file</p>
<pre><code>sha256sum --ignore-missing --check SHA256SUMS
</code></pre>
<p>Now I am totally lost on what to do from here because the txt file is not on GitHub anymore. I have been trying to figure this out for a while now but can't seem to do so. Any help is much appreciated.</p>

<bitcoin-core><ubuntu><verification><installation>
How to gpg verify my bitcoin core download step by step on ubuntu server?
DJ_Splash
# How to gpg verify my bitcoin core download step by step on ubuntu server?

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

I am a newbie when it comes to setting up a bitcoin node but I am trying to gpg verify my bitcoin core download the pub keys to do so are no longer available. I have tried doing my own research but I can't seem to find someone to explain in Layman's terms how to do so now.

I have downloaded all three files needed to do so:

```
bitcoin-24.0.1-x86_64-linux-gnu.tar.gz
SHA256SUMS 
SHA256SUMS.asc

```

I have verified the checksum of the release file

```
sha256sum --ignore-missing --check SHA256SUMS

```

Now I am totally lost on what to do from here because the txt file is not on GitHub anymore. I have been trying to figure this out for a while now but can't seem to do so. Any help is much appreciated.

**Tags:** bitcoin-core, ubuntu, verification, installation


---

## 3 answers

### Answer by username_1 on 2023-03-22. Score: 3

The builder keys file has moved to a [different repository](https://github.com/bitcoin-core/guix.sigs/tree/main/builder-keys). The [download verification instructions](https://bitcoincore.org/en/download/#verify-your-download) on the bitcoincore.org website were updated. Follow the steps detailed there to verify your Bitcoin Core download.


---

### Answer by username_2 on 2023-02-19. Score: 2

gpg --list-keys

wget <https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/achow101.gpg>

wget <https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/benthecarman.gpg>

wget <https://raw.githubusercontent.com/bitcoin-core/guix.sigs/main/builder-keys/fanquake.gpg>

gpg --import achow101.gpg

gpg --import benthecarman.gpg

gpg --import fanquake.gpg

gpg --verify SHA256SUMS.asc


---

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

You'll just have to follow the steps listed at

<https://bitcoincore.org/en/download/>

But essentially, you're doing it right, downloading those three files and then running sha256sum returns the following:

```
$ sha256sum --ignore-missing --check SHA256SUMS
bitcoin-24.0.1-x86_64-linux-gnu.tar.gz: OK

```

> **Comments:**
> **username_0**: So I don't need to get public keys anymore and verify it? Cause when I follow the instructions the rest doesn't make sense cause of missing pages on GitHub.  
> **username_3**: Not really sure what steps are you following. The official documentation is the one I linked to on my original answer.  
> **username_4**: This answer seems to be missing most of the point.  
> **username_5**: That's verifying the checksums match, bit is missing the gpg verification of the checksum file's authrnticity  

---

