<p>This is how I usually do it. Check the wget links in <a href="https://bitcoincore.org/bin" rel="nofollow noreferrer">https://bitcoincore.org/bin</a></p>

<pre><code># Download Bitcoin Core packages for Ubuntu

wget https://bitcoincore.org/bin/bitcoin-core-0.20.0/bitcoin-0.20.0-x86_64-linux-gnu.tar.gz

# check the checksum and fingerprint //optional
wget https://bitcoincore.org/bin/bitcoin-core-0.20.0/SHA256SUMS.asc
wget https://bitcoin.org/laanwj-releases.asc
sha256sum --check SHA256SUMS.asc --ignore-missing
    &gt;expected: xxx.tar.gz: OK
gpg --import ./laanwj-releases.asc
gpg --refresh-keys
gpg --verify SHA256SUMS.asc
    &gt;expected: Good signature from "Wladimir J. van der Laan ..."

# extract, install and check versions of the binaries
tar -xvf bitcoin-0.20.0-x86_64-linux-gnu.tar.gz
sudo install -m 0755 -o root -t /usr/local/bin bitcoin-0.20.0/bin/*
bitcoind --version
    &gt;expected: Bitcoin Core version x0.20.0
</code></pre>

CC BY-SA 4.0
2020-06-06T10:09:29.900Z
When I run `sha256sum --check SHA256SUMS.asc --ignore-missing` I receive `bitcoin-0.20.0-x86_64-linux-gnu.tar.gz: OK` and `sha256sum: WARNING: 20 lines are improperly formatted`
Mohammad Saberi
CC BY-SA 4.0
2020-06-06T14:31:43.880Z
It's fine :) Formatting of 20 lines is improper to do sha256sum, from how I understand it, it's somewhat expected if you don't force the check sha256sum.
Tony Sanak
CC BY-SA 4.0
2020-06-07T17:16:53.583Z
I'm getting different warnings while running your codes... `gpg: WARNING: This key is not certified with a trusted signature! gpg:  There is no indication that the signature belongs to the owner.` , `gpg: no ultimately trusted keys found`
Mohammad Saberi
CC BY-SA 4.0
2020-06-07T17:27:48.940Z
I think it's because it's still a key you've just downloaded from the internet. The warning says it can't confirm that this key is certified (legit). I don't know more secure way of checking validity if you're not into building the package yourself. And the only way for it to be false is if both sources would be spoofed.
Tony Sanak
CC BY-SA 4.0
2020-06-07T17:29:22.510Z
Here is extended explanation: https://bitcoin.stackexchange.com/questions/565/how-can-one-download-the-bitcoin-client-securely
Tony Sanak
CC BY-SA 4.0
2020-06-05T19:26:29.937Z
2020-06-05T19:26:29.937Z
Tony Sanak
<p>I've installed <strong>Bitcoin Core</strong> on <strong>Ubuntu 18.04</strong> (CLI). Now, the version 0.20 of Bitcoin Core is released and I want to upgrade my server to it, but it seems the new version is not included in PPA yet. May you help me to upgrade my Bitcoin Core server to 0.20 in a safe and correct way please?</p>

<bitcoin-core><linux><ubuntu>
How to upgrade Bitcoin Core from 0.18 to 0.20 on Ubuntu 18.04?
Mohammad Saberi
# How to upgrade Bitcoin Core from 0.18 to 0.20 on Ubuntu 18.04?

(Asked by: username_0 on 2020-06-05)

I've installed **Bitcoin Core** on **Ubuntu 18.04** (CLI). Now, the version 0.20 of Bitcoin Core is released and I want to upgrade my server to it, but it seems the new version is not included in PPA yet. May you help me to upgrade my Bitcoin Core server to 0.20 in a safe and correct way please?

**Tags:** bitcoin-core, linux, ubuntu


---

## 1 answers

### Answer by username_1 on 2020-06-05. Score: 2

This is how I usually do it. Check the wget links in https://bitcoincore.org/bin
# Download Bitcoin Core packages for Ubuntu

wget https://bitcoincore.org/bin/bitcoin-core-0.20.0/bitcoin-0.20.0-x86_64-linux-gnu.tar.gz

# check the checksum and fingerprint //optional
wget https://bitcoincore.org/bin/bitcoin-core-0.20.0/SHA256SUMS.asc
wget https://bitcoin.org/laanwj-releases.asc
sha256sum --check SHA256SUMS.asc --ignore-missing
    >expected: xxx.tar.gz: OK
gpg --import ./laanwj-releases.asc
gpg --refresh-keys
gpg --verify SHA256SUMS.asc
    >expected: Good signature from "Wladimir J. van der Laan ..."

# extract, install and check versions of the binaries
tar -xvf bitcoin-0.20.0-x86_64-linux-gnu.tar.gz
sudo install -m 0755 -o root -t /usr/local/bin bitcoin-0.20.0/bin/*
bitcoind --version
    >expected: Bitcoin Core version x0.20.0

> **Comments:**
> **username_0**: When I run `sha256sum --check SHA256SUMS.asc --ignore-missing` I receive `bitcoin-0.20.0-x86_64-linux-gnu.tar.gz: OK` and `sha256sum: WARNING: 20 lines are improperly formatted`  
> **username_1**: It's fine :) Formatting of 20 lines is improper to do sha256sum, from how I understand it, it's somewhat expected if you don't force the check sha256sum.  
> **username_0**: I'm getting different warnings while running your codes... `gpg: WARNING: This key is not certified with a trusted signature! gpg:  There is no indication that the signature belongs to the owner.` , `gpg: no ultimately trusted keys found`  
> **username_1**: I think it's because it's still a key you've just downloaded from the internet. The warning says it can't confirm that this key is certified (legit). I don't know more secure way of checking validity if you're not into building the package yourself. And the only way for it to be false is if both sources would be spoofed.  
> **username_1**: Here is extended explanation: https://bitcoin.stackexchange.com/questions/565/how-can-one-download-the-bitcoin-client-securely  

---

