Public commit record
68/100 · Adequate
What the developer wrote
Authored by Liam Aharon
api: Update sha3_256 hashing api
a983c10 introduced changes to the sha3-256 hashing api.
Applies the diff generated by './contrib/check-for-api-changes.sh' to
keep 'api/hashes/..' consistent with the aforementioned code change.
✓ Descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
What changed, and why it matters
This commit only updates generated API snapshot text files to match a recent code change. It renames a function parameter from 'data' to 'inp' and changes a return type description from the full type name to 'Self'. These are documentation-like API snapshots, not actual source code changes, and they have no effect on program behavior or security.
Recommended action
No security action needed. This is a routine API-snapshot synchronization commit.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies three ‘api/hashes/*.txt’ files, which are generated public-API snapshots produced by ‘./contrib/check-for-api-changes.sh’. The changes reflect an upstream source-code refactor (commit a983c10) in the sha3_256 module: HashEngine::default()’s return type is now written as ‘Self’ instead of ‘bitcoin_hashes::sha3_256::HashEngine’, and HashEngine::input()’s parameter is renamed from ‘data’ to ‘inp’. These are purely cosmetic in the API snapshot and do not alter the crate’s compiled behavior, ABI, or any security-relevant logic.
Changed components
api/hashes/all-features.txtapi/hashes/alloc-only.txtapi/hashes/no-features.txtInspect captured patch +6 / −6
diff --git a/api/hashes/all-features.txt b/api/hashes/all-features.txt
index b231619b..f9922581 100644
--- a/api/hashes/all-features.txt
+++ b/api/hashes/all-features.txt
@@ -950,11 +950,11 @@ pub fn bitcoin_hashes::sha3_256::Hash::partial_cmp(&self, other: &bitcoin_hashes
pub fn bitcoin_hashes::sha3_256::Hash::serialize<S: serde::ser::Serializer>(&self, s: S) -> core::result::Result<<S as serde::ser::Serializer>::Ok, <S as serde::ser::Serializer>::Error>
pub fn bitcoin_hashes::sha3_256::Hash::to_byte_array(self) -> Self::Bytes
pub fn bitcoin_hashes::sha3_256::HashEngine::clone(&self) -> bitcoin_hashes::sha3_256::HashEngine
-pub fn bitcoin_hashes::sha3_256::HashEngine::default() -> bitcoin_hashes::sha3_256::HashEngine
+pub fn bitcoin_hashes::sha3_256::HashEngine::default() -> Self
pub fn bitcoin_hashes::sha3_256::HashEngine::finalize(self) -> Self::Hash
pub fn bitcoin_hashes::sha3_256::HashEngine::flush(&mut self) -> std::io::error::Result<()>
pub fn bitcoin_hashes::sha3_256::HashEngine::fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result
-pub fn bitcoin_hashes::sha3_256::HashEngine::input(&mut self, data: &[u8])
+pub fn bitcoin_hashes::sha3_256::HashEngine::input(&mut self, inp: &[u8])
pub fn bitcoin_hashes::sha3_256::HashEngine::n_bytes_hashed(&self) -> u64
pub fn bitcoin_hashes::sha3_256::HashEngine::write(&mut self, buf: &[u8]) -> std::io::error::Result<usize>
pub fn bitcoin_hashes::sha3_256::hash(data: &[u8]) -> bitcoin_hashes::sha3_256::Hash
diff --git a/api/hashes/alloc-only.txt b/api/hashes/alloc-only.txt
index b187154a..b8b70cd5 100644
--- a/api/hashes/alloc-only.txt
+++ b/api/hashes/alloc-only.txt
@@ -801,10 +801,10 @@ pub fn bitcoin_hashes::sha3_256::Hash::hash_byte_chunks<B, I>(byte_slices: I) ->
pub fn bitcoin_hashes::sha3_256::Hash::partial_cmp(&self, other: &bitcoin_hashes::sha3_256::Hash) -> core::option::Option<core::cmp::Ordering>
pub fn bitcoin_hashes::sha3_256::Hash::to_byte_array(self) -> Self::Bytes
pub fn bitcoin_hashes::sha3_256::HashEngine::clone(&self) -> bitcoin_hashes::sha3_256::HashEngine
-pub fn bitcoin_hashes::sha3_256::HashEngine::default() -> bitcoin_hashes::sha3_256::HashEngine
+pub fn bitcoin_hashes::sha3_256::HashEngine::default() -> Self
pub fn bitcoin_hashes::sha3_256::HashEngine::finalize(self) -> Self::Hash
pub fn bitcoin_hashes::sha3_256::HashEngine::fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result
-pub fn bitcoin_hashes::sha3_256::HashEngine::input(&mut self, data: &[u8])
+pub fn bitcoin_hashes::sha3_256::HashEngine::input(&mut self, inp: &[u8])
pub fn bitcoin_hashes::sha3_256::HashEngine::n_bytes_hashed(&self) -> u64
pub fn bitcoin_hashes::sha3_256::hash(data: &[u8]) -> bitcoin_hashes::sha3_256::Hash
pub fn bitcoin_hashes::sha3_256::hash_byte_chunks<B, I>(byte_slices: I) -> bitcoin_hashes::sha3_256::Hash where B: core::convert::AsRef<[u8]>, I: core::iter::traits::collect::IntoIterator<Item = B>
diff --git a/api/hashes/no-features.txt b/api/hashes/no-features.txt
index ad8375ec..a5121b70 100644
--- a/api/hashes/no-features.txt
+++ b/api/hashes/no-features.txt
@@ -800,10 +800,10 @@ pub fn bitcoin_hashes::sha3_256::Hash::hash_byte_chunks<B, I>(byte_slices: I) ->
pub fn bitcoin_hashes::sha3_256::Hash::partial_cmp(&self, other: &bitcoin_hashes::sha3_256::Hash) -> core::option::Option<core::cmp::Ordering>
pub fn bitcoin_hashes::sha3_256::Hash::to_byte_array(self) -> Self::Bytes
pub fn bitcoin_hashes::sha3_256::HashEngine::clone(&self) -> bitcoin_hashes::sha3_256::HashEngine
-pub fn bitcoin_hashes::sha3_256::HashEngine::default() -> bitcoin_hashes::sha3_256::HashEngine
+pub fn bitcoin_hashes::sha3_256::HashEngine::default() -> Self
pub fn bitcoin_hashes::sha3_256::HashEngine::finalize(self) -> Self::Hash
pub fn bitcoin_hashes::sha3_256::HashEngine::fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result
-pub fn bitcoin_hashes::sha3_256::HashEngine::input(&mut self, data: &[u8])
+pub fn bitcoin_hashes::sha3_256::HashEngine::input(&mut self, inp: &[u8])
pub fn bitcoin_hashes::sha3_256::HashEngine::n_bytes_hashed(&self) -> u64
pub fn bitcoin_hashes::sha3_256::hash(data: &[u8]) -> bitcoin_hashes::sha3_256::Hash
pub fn bitcoin_hashes::sha3_256::hash_byte_chunks<B, I>(byte_slices: I) -> bitcoin_hashes::sha3_256::Hash where B: core::convert::AsRef<[u8]>, I: core::iter::traits::collect::IntoIterator<Item = B>
Risk score
Our methodology →Why this scored 15/100
Human-validated context
Community notes
Notes can correct, qualify, or add evidence to the AI analysis. Every note shown here has been validated by a human moderator.
No validated notes yet.
The AI analysis stands alone for now. Submit a note if you can add evidence or important context.