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

XOR doesn’t display invalid mnemonic lengths for user selection (#747)

Public commit record

What the developer wrote

Authored by Tads

81/100 · Strong
XOR doesn’t display invalid mnemonic lengths for user selection (#747)

* XOR doesn’t display invalid mnemonic lengths for user selection

* XOR prompt msg now warns about passphrase

* XOR fix incorrect fingerprint displayed when using passphrase
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit fixes two user-facing bugs in Krux's 'mnemonic XOR' feature. First, when asking the user to pick a mnemonic length, it now only shows the length that matches the currently loaded wallet (12 or 24 words), preventing the user from accidentally selecting an incompatible length. Second, it now warns the user that the wallet passphrase and descriptor will be discarded before starting the XOR operation, and it corrects the fingerprint shown after the XOR so it no longer incorrectly includes the old passphrase. These are usability and correctness fixes rather than remote-exploitable security holes.

Recommended action

Review the change as a normal bug-fix/UX-hardening commit. No urgent security response is indicated, but downstream users should be aware that prior versions could display a misleading fingerprint during XOR when a passphrase was in use, and allowed selecting an incompatible mnemonic length.

Security signals we found

01

UI now restricts mnemonic-length selection to the length of the currently loaded key, reducing risk of user error during XOR

02

Prompt now explicitly warns that passphrase and descriptor will be discarded, improving informed consent

03

Fingerprint display bug fixed: XOR result fingerprint is now computed from the bare mnemonic instead of inheriting the previous wallet's passphrase

04

No evidence of memory corruption, remote code execution, or cryptographic weakness introduced

Risk score

Why this scored 24/100

Our methodology →
Potential impact 4/30
Exploitability 2/25
Stealth signal 3/15
Affected reach 5/15
Confidence 7/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.