What the developer wrote
Authored by Marko Bencun
xpubcache: typo in docstring
What changed, and why it matters
This commit fixes a single typo in a code comment (docstring). The example Bitcoin keypath was missing an apostrophe in one place (m/84/0'/0'/0/0 changed to m/84'/0'/0'/0/0). No actual program code was changed, so there is no functional or security impact.
No action required; this is a non-functional documentation fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
The diff modifies only a documentation comment in src/rust/bitbox02-rust/src/xpubcache.rs. It corrects a BIP32 keypath example from m/84/0’/0’/0/0 to m/84’/0’/0’/0/0 to accurately reflect a standard BIP84 hardened account path. No executable Rust code, logic, or data handling changed.
Changed components
src/rust/bitbox02-rust/src/xpubcache.rs (documentation comment only)Inspect captured patch +1 / −1
diff --git a/src/rust/bitbox02-rust/src/xpubcache.rs b/src/rust/bitbox02-rust/src/xpubcache.rs
index 97cac0f..bac1987 100644
--- a/src/rust/bitbox02-rust/src/xpubcache.rs
+++ b/src/rust/bitbox02-rust/src/xpubcache.rs
@@ -39,7 +39,7 @@ pub trait Xpub: Sized {
///
/// The cache must be configured using `add_keypath()`, otherwise no caching occurs. The reason
/// for this is that automatic caching is harder to get right and reason about, e.g. in a BTC tx, we
-/// shouldn't cache xpubs at the address level (e.g. m/84/0'/0'/0/0), as they don't repeat and there
+/// shouldn't cache xpubs at the address level (e.g. m/84'/0'/0'/0/0), as they don't repeat and there
/// can be many of them.
pub struct XpubCache<X> {
// List of keypaths for which we want to cache xpubs for.
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.