AI-generated analysisPublished automatically and not human-verified. Validated context appears in community notes below.
← Watch feed
Low 46 Bitcoin

support psbt

Public commit record

What the developer wrote

Authored by ww3512687

18/100 · Opaque
support psbt
✓ Subject identifies a change! Too few words to establish purpose! No meaningful explanatory body! Opaque security-relevant change
The short version

What changed, and why it matters

This commit adds support for signing extended PSBTs for several UTXO-based coins (Litecoin, Dogecoin, Dash, Bitcoin Cash) in the Keystone 3 hardware wallet firmware. It also contains several changes that look like temporary debug or development shortcuts rather than production-hardened code: a hardcoded return value that hides the real battery percentage, disabling a boot-version mismatch warning, sending real UART output in production builds, and pointing Rust dependencies to a local path on a developer's Windows machine. These shortcuts reduce the device's defensive posture but are not, by themselves, a remote exploit.

Recommended action

Treat this as a feature commit that needs review before release. Revert or gate the debug-only changes (local Cargo paths, unconditional 100% battery, disabled boot-version check, production UART output, simulator test UR) before any production build. Audit the new CryptoPSBTExtend parsing/signing paths for correct coin-type validation, path validation, and PSBT sanity checks, especially because utxo_check_psbt_extend currently short-circuits validation. Verify that the refactored btc_sign_psbt_dynamic and btc_check_psbt_common do not introduce type-safety or lifetime regressions at the FFI boundary.

Security signals we found

01

New signing path for extended PSBTs with additional UTXO coin support

02

Refactored PSBT signing/checking functions to accept raw byte vectors instead of typed UR objects

03

Added coin_id handling in CryptoPSBTExtend signing flow

04

Hardcoded local filesystem dependency paths in Cargo.toml (supply-chain/build reproducibility concern)

05

Disabled boot version mismatch warning in initialization flow

06

Forced battery percentage display to 100%

07

Enabled real UART output in BUILD_PRODUCTION configuration

08

Simulator hardcoded a test UR string and disabled screen QR capture

09

utxo_check_psbt_extend currently returns an empty TransactionCheckResult before any validation

Risk score

Why this scored 46/100

Our methodology →
Potential impact 12/30
Exploitability 8/25
Stealth signal 7/15
Affected reach 10/15
Confidence 6/10
Evidence quality 3/5
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.