fix: use correct function name in taproot-psbt error message
What changed, and why it matters
This commit fixes a typo in an example program's error message. The message previously told users to call a non-existent function; now it points to the correct function name. There is no security issue.
No security action needed. Treat as a routine example-code fix.
Security signals we found
No strong security signals were identified.
Evidence from the diff
In bitcoin/examples/taproot-psbt.rs, an error string in BenefactorWallet::create_inheritance_transaction was corrected from ‘refresh_inheritance_timelock’ to ‘refresh_tx’. This is a documentation/string fix within example code and does not alter program logic, cryptography, or network behavior.
Changed components
bitcoin/examples/taproot-psbt.rsInspect captured patch +1 / −1
diff --git a/bitcoin/examples/taproot-psbt.rs b/bitcoin/examples/taproot-psbt.rs
index 1f1f6781..6dc8d980 100644
--- a/bitcoin/examples/taproot-psbt.rs
+++ b/bitcoin/examples/taproot-psbt.rs
@@ -386,7 +386,7 @@ impl BenefactorWallet {
) -> Result<(Transaction, Psbt), Box<dyn std::error::Error>> {
if let ChildNumber::Normal { index } = self.next {
if index > 0 && self.current_spend_info.is_some() {
- return Err("transaction already exists, use refresh_inheritance_timelock to refresh the timelock".into());
+ return Err("transaction already exists, use refresh_tx to refresh the timelock".into());
}
}
// We use some other derivation path in this example for our inheritance protocol. The important thing is to ensure
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.