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

keystore: Old_KeyStore: allow odd-length hex seeds

Public commit record

What the developer wrote

Authored by Ferdinando Ametrano

81/100 · Strong
keystore: Old_KeyStore: allow odd-length hex seeds

An old seed decodes to an odd number of hex digits when one of its word
triples is worth 2**32 or more. Since 4.6.1 such seeds fail on import,
and wallets restored from them earlier can no longer sign. Accept them
again. get_seed now raises a clear error for them, as mn_encode cannot
encode them.

fixes https://github.com/spesmilo/electrum/issues/11045
✓ 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 a bug in Electrum where very old wallet seeds containing a rare word combination could no longer be imported or used to sign transactions since version 4.6.1. The fix restores support for these odd-length hex seeds while preventing the wallet from trying to display them as a normal word seed. It is a bug fix for a denial-of-service/access-loss issue, not an exploitable vulnerability that lets an attacker steal funds.

Recommended action

Apply the patch. Users with old Electrum seeds who could not import or sign since 4.6.1 should upgrade. Advise affected users to back up the original seed phrase, because the wallet cannot display these odd-length seeds as words again.

Security signals we found

01

Bug causes loss of access to existing wallets for users with rare old seeds

02

Fix restores signing capability for affected old wallets

03

No new cryptographic primitive or entropy weakness introduced

04

get_seed now explicitly refuses to re-encode unrepresentable seeds, reducing user confusion

05

Change is narrowly scoped to Old_KeyStore legacy seed handling

Risk score

Why this scored 42/100

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