What the developer wrote
Authored by Mitchell Bagot
crypto: Remove bitcoin-io dependency
With the removal of the io-dependent functions from the key and
signature types, the bitcoin-io dependency can be entirely dropped from
the crypto crate.
Remove bitcoin-io dependency from manifest and update lock files.
Remove io re-export from crate root.
What changed, and why it matters
This commit is a routine cleanup that removes an unused dependency called bitcoin-io from the crypto crate. It only touches package metadata and lock files, not any code that handles keys, signatures, or user data. There is no security issue visible in this change.
No security action needed. Treat as normal dependency cleanup.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The commit drops the bitcoin-io dependency from crypto/Cargo.toml, removes the corresponding feature forwarding in std/alloc, deletes the io re-export in crypto/src/lib.rs, and updates Cargo-minimal.lock and Cargo-recent.lock. The commit message states this is possible because io-dependent functions were already removed from key and signature types in prior work. The diff contains no functional code changes, no input parsing, no cryptographic operations, and no API behavior changes beyond removing a public re-export of a dependency crate.
Changed components
crypto/Cargo.tomlcrypto/src/lib.rsCargo-minimal.lockCargo-recent.lockInspect captured patch +2 / −7
diff --git a/Cargo-minimal.lock b/Cargo-minimal.lock
index 4c642edd..9eba61eb 100644
--- a/Cargo-minimal.lock
+++ b/Cargo-minimal.lock
@@ -95,7 +95,6 @@ dependencies = [
"arbitrary",
"base58ck",
"bitcoin-internals",
- "bitcoin-io",
"bitcoin-network-kind",
"bitcoin_hashes",
"hex-conservative 0.3.2",
diff --git a/Cargo-recent.lock b/Cargo-recent.lock
index 71dd952d..8b9d2212 100644
--- a/Cargo-recent.lock
+++ b/Cargo-recent.lock
@@ -94,7 +94,6 @@ dependencies = [
"arbitrary",
"base58ck",
"bitcoin-internals",
- "bitcoin-io",
"bitcoin-network-kind",
"bitcoin_hashes",
"hex-conservative 0.3.2",
diff --git a/crypto/Cargo.toml b/crypto/Cargo.toml
index c24bf918..dbb97368 100644
--- a/crypto/Cargo.toml
+++ b/crypto/Cargo.toml
@@ -15,9 +15,9 @@ exclude = ["tests", "contrib"]
[features]
default = ["std"]
-std = ["alloc", "base58/std", "hashes/std", "hex-stable/std", "hex-unstable/std", "internals/std", "io/std", "network/std", "secp256k1/std", "serde?/std"]
+std = ["alloc", "base58/std", "hashes/std", "hex-stable/std", "hex-unstable/std", "internals/std", "network/std", "secp256k1/std", "serde?/std"]
rand = ["secp256k1/rand"]
-alloc = ["base58/alloc", "hashes/alloc", "hex-stable/alloc", "hex-unstable/alloc", "internals/alloc", "io/alloc", "network/alloc", "secp256k1/alloc", "serde?/alloc"]
+alloc = ["base58/alloc", "hashes/alloc", "hex-stable/alloc", "hex-unstable/alloc", "internals/alloc", "network/alloc", "secp256k1/alloc", "serde?/alloc"]
serde = ["dep:serde", "hashes/serde", "internals/serde", "secp256k1/serde"]
arbitrary = ["dep:arbitrary", "secp256k1/arbitrary"]
@@ -27,7 +27,6 @@ hashes = { package = "bitcoin_hashes", path = "../hashes", version = "0.20.0", d
hex-unstable = { package = "hex-conservative", version = "0.3.2", default-features = false }
hex-stable = { package = "hex-conservative", version = "1.0.0", default-features = false }
internals = { package = "bitcoin-internals", path = "../internals", version = "0.5.0", features = ["hex"] }
-io = { package = "bitcoin-io", path = "../io", version = "0.5.0", default-features = false, features = ["hashes"] }
network = { package = "bitcoin-network-kind", path = "../network", version = "0.1.0", default-features = false }
secp256k1 = { version = "0.32.0-beta.2", default-features = false }
diff --git a/crypto/src/lib.rs b/crypto/src/lib.rs
index e108ef3e..d20cef08 100644
--- a/crypto/src/lib.rs
+++ b/crypto/src/lib.rs
@@ -21,8 +21,6 @@ pub extern crate base58;
pub extern crate network;
-pub extern crate io;
-
pub extern crate secp256k1;
#[cfg(feature = "alloc")]
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.