Umbrella issue for 22.0 testing. As there have been changes to the release process and distribution (thanks to the hard work of @dongcarl and others), I expect some more issues to come up than with the usual major release. Please help testing on a wide variety of supported platforms, as well as interaction with different software.

Let us know which version you tested on which operating system.

If you find an issue, please search Github for known issues first and then open a new Github issue. This meta issue should not be used to report bugs, as a single thread makes it impossible to track more than one topic.

• See Draft Release Notes for a list of changes, and testing reports for earlier releases (v0.19.0), for an idea what to test.

• For suggestion on how and what to test see the 22.0 Release Candidate Testing Guide.

• rc2 announcement: https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2021-August/000100.html

• Release schedule: Release schedule for 22.0 #20851

Note on verifying the binaries

(updated as of rc2)

We are retiring the Bitcoin Core binary release signing key for new major releases. This single key (by @laanwj) was always used to sign SHA256SUMS.asc.

Instead, the idea is to use the attestations of the deterministic builders (GUIX builders) directly. Instead of a single SHA256SUMS.asc there will be two files shipped with the distribution:

• a SHA256SUMS with hashes of the distributed binaries.

db29446e55fd8b05c327ecfe036073fe27fbbd2f8597bf6c5f99aca64a378e7f  aarch64-linux-gnu/bitcoin-22.0rc2-aarch64-linux-gnu-debug.tar.gz
f7158d5a195aa0c59f931e5dbf3ac685e951a51f896abc38a87d04e99c0b8857  aarch64-linux-gnu/bitcoin-22.0rc2-aarch64-linux-gnu.tar.gz
⋮
d7afb5b36d49df0082e0fe68187665efb321bed783e9f79c92dfa3974877b7aa  x86_64-w64-mingw32/bitcoin-22.0rc2-win64-setup-unsigned.exe
078178ef69100e9bee36d4c74bcd3446ff1239b3a20b1efda37b7149b3b4aa70  x86_64-w64-mingw32/bitcoin-22.0rc2-win64.zip

• a SHA256SUMS.asc file with concatenated GPG signatures of the different builders/attesters who attest to the same single output:

-----BEGIN PGP SIGNATURE-----

iQJGBAABCAAwFiEE0dvyxLlvLev0wWZUQQEIES5+qB8FAmEKeVUSHGhlYmFzdG9A
⋮
-----END PGP SIGNATURE-----
-----BEGIN PGP SIGNATURE-----

iQEzBAABCgAdFiEEnerg3HBjJJ+wVHRoHkrtYphs0l0FAmEKg/oACgkQHkrtYphs
⋮
-----END PGP SIGNATURE-----
⋮

To verify, first check the signatures

$ gpg --verify SHA256SUMS.asc SHA256SUMS

This will show an output like:

gpg: Good signature from "Antoine Poinsot <darosior@protonmail.com>" [unknown]
⋮
gpg: Good signature from "Michael Ford (bitcoin-otc) <fanquake@gmail.com>" [unknown]
⋮
gpg: Good signature from "Wladimir J. van der Laan <laanwj@visucore.com>" [unknown]
⋮

Make sure it has good signatures by people you trust to do a Bitcoin Core release.

Then, verify the file hashes:

$ sha256sum -c --ignore-missing < SHA256SUMS
bitcoin-22.0rc3-aarch64-linux-gnu.tar.gz: OK
bitcoin-22.0rc3-arm-linux-gnueabihf.tar.gz: OK
bitcoin-22.0rc3.tar.gz: OK
bitcoin-22.0rc3-powerpc64-linux-gnu.tar.gz: OK
bitcoin-22.0rc3-powerpc64le-linux-gnu.tar.gz: OK
bitcoin-22.0rc3-riscv64-linux-gnu.tar.gz: OK
bitcoin-22.0rc3-osx-signed.dmg: OK
bitcoin-22.0rc3-osx64.tar.gz: OK
bitcoin-22.0rc3-x86_64-linux-gnu.tar.gz: OK
bitcoin-22.0rc3-win64-setup.exe: OK
bitcoin-22.0rc3-win64.zip: OK