From dcb612b7ed2ad678da79cc6c2a28189ac30580a0 Mon Sep 17 00:00:00 2001 From: Ben Westgate Date: Thu, 22 Oct 2026 09:49:55 -0500 Subject: [PATCH] core: Pin fixtures and tutorials to stable v32.0 Replace the 32.0rc2 fixture archive and rc1 tutorial links with stable v32.0. Pin the two previously moving offline-signing links to the same stable tag and remove the obsolete pre-final-release wording. The Linux archive checksum agrees across the valid signed fanquake and achow101 attestations in bitcoin-core/guix.sigs at 5071821e840184a414edb74ae09f130df2d804da. Validation: both stable tutorial files exist, both build signatures verify, and git diff --check passes. The official stable archive endpoint currently returns 404, so fixture execution remains pending publication. Runtime behavior and tests are unchanged. --- .github/workflows/bitcoin-core-fixtures.yml | 8 ++++---- docs/developer/api.md | 8 ++++---- docs/user/guide.md | 6 +++--- 3 files changed, 11 insertions(+), 11 deletions(-) diff --git a/.github/workflows/bitcoin-core-fixtures.yml b/.github/workflows/bitcoin-core-fixtures.yml index 565a47b4..af9f4df1 100644 --- a/.github/workflows/bitcoin-core-fixtures.yml +++ b/.github/workflows/bitcoin-core-fixtures.yml @@ -18,9 +18,9 @@ permissions: contents: read env: - BITCOIN_CORE_ARCHIVE: bitcoin-32.0rc2-x86_64-linux-gnu.tar.gz - BITCOIN_CORE_SHA256: 0255103718033e6aee15fa944717fc277e047b845bff1e7408af0ea732d8d0c1 - BITCOIN_CORE_URL: https://bitcoincore.org/bin/bitcoin-core-32.0/test.rc2 + BITCOIN_CORE_ARCHIVE: bitcoin-32.0-x86_64-linux-gnu.tar.gz + BITCOIN_CORE_SHA256: 512d95d64591ddd1a74390cbfdd41b1c1a4f5494531d78db46ec8fdacafbeb71 + BITCOIN_CORE_URL: https://bitcoincore.org/bin/bitcoin-core-32.0 jobs: verify: @@ -41,7 +41,7 @@ jobs: env: PYTHONPATH: ${{ github.workspace }}/src run: | - core="$RUNNER_TEMP/bitcoin-32.0rc2/bin" + core="$RUNNER_TEMP/bitcoin-32.0/bin" "$core/bitcoind" --version | head -1 python tools/bitcoin_core_regtest.py \ --bitcoind "$core/bitcoind" \ diff --git a/docs/developer/api.md b/docs/developer/api.md index 51c9fb5c..b6f51032 100644 --- a/docs/developer/api.md +++ b/docs/developer/api.md @@ -653,10 +653,10 @@ xprv through `bitcoin-cli -stdin`, asks Core to create account-0 descriptors, and relocks an encrypted destination after success, failure, or interruption. It never handles a passphrase. -For offline signing/watch-only and multisig workflows, use Bitcoin Core v32's -maintained procedures. Until the final v32 release, see the versioned -[offline-signing tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0rc1/doc/offline-signing-tutorial.md) -and [multisig tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0rc1/doc/multisig-tutorial.md). +For offline signing/watch-only and multisig workflows, use Bitcoin Core v32.0's +maintained, versioned procedures: +[offline-signing tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0/doc/offline-signing-tutorial.md) +and [multisig tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0/doc/multisig-tutorial.md). The direct `ms32 xprv` primitive remains top-level and carries an explicit secret-root warning. diff --git a/docs/user/guide.md b/docs/user/guide.md index b875ab04..7c55392a 100644 --- a/docs/user/guide.md +++ b/docs/user/guide.md @@ -207,7 +207,7 @@ keys enabled and run `ms32 wallet`. Keep that computer disconnected from every network while recovery text or signing keys are present. After the signer is restored, follow Bitcoin Core v32's maintained -[offline-signing tutorial](https://github.com/bitcoin/bitcoin/blob/master/doc/offline-signing-tutorial.md). +[offline-signing tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0/doc/offline-signing-tutorial.md). That workflow owns the watch-only export/import and PSBT transport steps. In Bitcoin Core v32, `exportwatchonlywallet` creates the watch-only wallet file and `restorewallet` loads it on the online node. Do not improvise a codex32-specific @@ -245,7 +245,7 @@ its public wallet data with the separate wallet record. account-0 descriptors, scans history, and relocks an encrypted wallet. 6. If you need an online watch-only counterpart, keep the restored signer offline and follow Bitcoin Core v32's - [offline-signing tutorial](https://github.com/bitcoin/bitcoin/blob/master/doc/offline-signing-tutorial.md) + [offline-signing tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0/doc/offline-signing-tutorial.md) to export and restore the watch-only wallet. Let the online node synchronize, then compare the account, policy, addresses, balance, and transaction history with the wallet record. @@ -264,7 +264,7 @@ results disagree, or the wallet is multisig or nonstandard. Restore the cosigner's private Bitcoin Core wallet with `ms32 wallet`, then follow Bitcoin Core v32's maintained -[multisig tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0rc1/doc/multisig-tutorial.md). +[multisig tutorial](https://github.com/bitcoin/bitcoin/blob/v32.0/doc/multisig-tutorial.md). ### Card maintenance and damaged writing