Bump old bitcoin version to 0.32.9 in fuzz
What changed, and why it matters
This commit simply updates a dependency version number used only in fuzz testing infrastructure. It changes the pinned version of an older 'bitcoin' crate from 0.32.8 to 0.32.9 in lock files and fuzz configuration files. There is no indication this is a security fix for the main project, nor does the commit itself describe any security relevance.
No security action required. Treat as routine maintenance.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff updates old_bitcoin from version 0.32.8 to 0.32.9 in fuzz/Cargo.toml, fuzz/generate-files.sh, and the generated lock files Cargo-minimal.lock and Cargo-recent.lock. This is a routine dependency bump within the fuzzing harness, which references an older release of the crate for differential fuzzing purposes. No source code changes, no vulnerability fixes, and no security discussion are present in the commit.
Changed components
fuzz/Cargo.tomlfuzz/generate-files.shCargo-minimal.lockCargo-recent.lockInspect captured patch +8 / −8
diff --git a/Cargo-minimal.lock b/Cargo-minimal.lock
index 8de1b7e0..0cbb79ac 100644
--- a/Cargo-minimal.lock
+++ b/Cargo-minimal.lock
@@ -57,9 +57,9 @@ dependencies = [
[[package]]
name = "bitcoin"
-version = "0.32.8"
+version = "0.32.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "1e499f9fc0407f50fe98af744ab44fa67d409f76b6772e1689ec8485eb0c0f66"
+checksum = "9cf93e61f2dbc3e3c41234ca26a65e2c0b0975c52e0f069ab9893ebbede584d3"
dependencies = [
"base58ck 0.1.0",
"bech32",
@@ -136,7 +136,7 @@ name = "bitcoin-fuzz"
version = "0.0.1"
dependencies = [
"arbitrary",
- "bitcoin 0.32.8",
+ "bitcoin 0.32.9",
"bitcoin 0.33.0-beta",
"bitcoin-consensus-encoding",
"bitcoin-p2p-messages",
diff --git a/Cargo-recent.lock b/Cargo-recent.lock
index 977c261c..e33dff60 100644
--- a/Cargo-recent.lock
+++ b/Cargo-recent.lock
@@ -56,9 +56,9 @@ dependencies = [
[[package]]
name = "bitcoin"
-version = "0.32.8"
+version = "0.32.9"
source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "1e499f9fc0407f50fe98af744ab44fa67d409f76b6772e1689ec8485eb0c0f66"
+checksum = "9cf93e61f2dbc3e3c41234ca26a65e2c0b0975c52e0f069ab9893ebbede584d3"
dependencies = [
"base58ck 0.1.0",
"bech32",
@@ -135,7 +135,7 @@ name = "bitcoin-fuzz"
version = "0.0.1"
dependencies = [
"arbitrary",
- "bitcoin 0.32.8",
+ "bitcoin 0.32.9",
"bitcoin 0.33.0-beta",
"bitcoin-consensus-encoding",
"bitcoin-p2p-messages",
diff --git a/fuzz/Cargo.toml b/fuzz/Cargo.toml
index e31805e9..59e41c9f 100644
--- a/fuzz/Cargo.toml
+++ b/fuzz/Cargo.toml
@@ -13,7 +13,7 @@ cargo-fuzz = true
# We shouldn't need an explicit version on the next line, but Andrew's tools
# choke on it otherwise. See https://github.com/nix-community/crate2nix/issues/373
bitcoin = { path = "../bitcoin", version = "0.33.0-beta", features = [ "serde", "arbitrary" ] }
-old_bitcoin = { version = "0.32.8", package = "bitcoin" }
+old_bitcoin = { version = "0.32.9", package = "bitcoin" }
bitcoin_consensus_encoding = { path = "../consensus_encoding", package = "bitcoin-consensus-encoding" }
p2p = { path = "../p2p", package = "bitcoin-p2p-messages", features = ["arbitrary"] }
diff --git a/fuzz/generate-files.sh b/fuzz/generate-files.sh
index 71b49e8f..4a4e2e95 100755
--- a/fuzz/generate-files.sh
+++ b/fuzz/generate-files.sh
@@ -26,7 +26,7 @@ cargo-fuzz = true
# We shouldn't need an explicit version on the next line, but Andrew's tools
# choke on it otherwise. See https://github.com/nix-community/crate2nix/issues/373
bitcoin = { path = "../bitcoin", version = "0.33.0-beta", features = [ "serde", "arbitrary" ] }
-old_bitcoin = { version = "0.32.8", package = "bitcoin" }
+old_bitcoin = { version = "0.32.9", package = "bitcoin" }
bitcoin_consensus_encoding = { path = "../consensus_encoding", package = "bitcoin-consensus-encoding" }
p2p = { path = "../p2p", package = "bitcoin-p2p-messages", features = ["arbitrary"] }
Why this scored 15/100
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.