From 1eb7c08b4525861e93d4b9889499d7ab1bca912d Mon Sep 17 00:00:00 2001 From: fanquake Date: Fri, 19 May 2023 12:07:38 +0100 Subject: [PATCH] doc/ci: Use Bitcoin Core 24.1 Leave minimum supported version as 24.0.1. --- .cirrus.yml | 8 ++++---- doc/TRY.md | 12 ++++++------ 2 files changed, 10 insertions(+), 10 deletions(-) diff --git a/.cirrus.yml b/.cirrus.yml index a6d41069..9968dc25 100644 --- a/.cirrus.yml +++ b/.cirrus.yml @@ -43,10 +43,10 @@ task: set -xe # Download the bitcoind binary - curl -O https://bitcoincore.org/bin/bitcoin-core-24.0.1/bitcoin-24.0.1-x86_64-linux-gnu.tar.gz - echo "49df6e444515d457ea0b885d66f521f2a26ca92ccf73d5296082e633544253bf bitcoin-24.0.1-x86_64-linux-gnu.tar.gz" | sha256sum -c - tar -xzf bitcoin-24.0.1-x86_64-linux-gnu.tar.gz - export BITCOIND_PATH=bitcoin-24.0.1/bin/bitcoind + curl -O https://bitcoincore.org/bin/bitcoin-core-24.1/bitcoin-24.1-x86_64-linux-gnu.tar.gz + echo "c112af3d19cca7f5b5f942708ca4d522110d8e1dc1c0f8d3077f531c94e5f00f bitcoin-24.1-x86_64-linux-gnu.tar.gz" | sha256sum -c + tar -xzf bitcoin-24.1-x86_64-linux-gnu.tar.gz + export BITCOIND_PATH=bitcoin-24.1/bin/bitcoind # The misc tests have a backward compat test that need the path to a previous version of Liana. # For now it requires using 0.3. diff --git a/doc/TRY.md b/doc/TRY.md index 9bf3a053..f59d05dd 100644 --- a/doc/TRY.md +++ b/doc/TRY.md @@ -59,10 +59,10 @@ other platforms refer to [https://bitcoincore.org/en/download/#verify-your-download](https://bitcoincore.org/en/download). 1. Download the `bitcoind` binary from [the official website of the Bitcoin Core -project](https://bitcoincore.org/bin/bitcoin-core-24.0.1/) according to your platform (in the context -of this guide, it is most likely `bitcoin-24.0.1-x86_64-linux-gnu.tar.gz`), and associated SHA256SUMS and SHA256SUMS.asc verification files. +project](https://bitcoincore.org/bin/bitcoin-core-24.1/) according to your platform (in the context +of this guide, it is most likely `bitcoin-24.1-x86_64-linux-gnu.tar.gz`), and associated SHA256SUMS and SHA256SUMS.asc verification files. ``` -curl -O https://bitcoincore.org/bin/bitcoin-core-24.0.1/bitcoin-24.0.1-x86_64-linux-gnu.tar.gz -O https://bitcoincore.org/bin/bitcoin-core-24.0.1/SHA256SUMS -O https://bitcoincore.org/bin/bitcoin-core-24.0.1/SHA256SUMS.asc +curl -O https://bitcoincore.org/bin/bitcoin-core-24.1/bitcoin-24.1-x86_64-linux-gnu.tar.gz -O https://bitcoincore.org/bin/bitcoin-core-24.1/SHA256SUMS -O https://bitcoincore.org/bin/bitcoin-core-24.1/SHA256SUMS.asc ``` 2. Verify the hash of the downloaded archive. @@ -80,21 +80,21 @@ gpg --verify SHA256SUMS.asc 4. Finally, uncompress the archive to get access to the `bitcoind` binary. ``` -tar -xzf bitcoin-24.0.1-x86_64-linux-gnu.tar.gz +tar -xzf bitcoin-24.1-x86_64-linux-gnu.tar.gz ``` ### Start `bitcoind` on signet Run `bitcoind` in the background on the public signet network. On Linux: ``` -./bitcoin-24.0.1/bin/bitcoind -signet -daemon +./bitcoin-24.1/bin/bitcoind -signet -daemon ``` If it is the first time you start a signet Bitcoin on this machine it will take a few minutes to synchronize (depends on your connection and hardware of course, but it shouldn't take longer than a handful of minutes). You can track the progress using the `getblockchaininfo` command. On Linux: ``` -./bitcoin-24.0.1/bin/bitcoin-cli -signet getblockchaininfo +./bitcoin-24.1/bin/bitcoin-cli -signet getblockchaininfo ``` **You do not need to wait for full synchronisation before moving on to the next step.**