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

psbt: disallow hybrid pubkeys

Public commit record

What the developer wrote

Authored by Jon Griffiths

50/100 · Thin
psbt: disallow hybrid pubkeys

Modern txs should not be using hybrid pubkeys, so reject them outright.
✓ Descriptive subject✓ Provides an explanatory body
The short version

What changed, and why it matters

This commit tightens public-key validation inside PSBT (Partially Signed Bitcoin Transaction) handling by rejecting 'hybrid' public keys. Hybrid keys are an old, non-standard encoding that sits between compressed and uncompressed formats. The change swaps a lenient verifier for a strict one in four places where PSBT data is parsed, so malformed or non-standard keys are now refused rather than accepted.

Recommended action

Review whether any callers or downstream users intentionally relied on hybrid-key acceptance; update tests to cover compressed, uncompressed, and rejected hybrid encodings; consider documenting the stricter parsing behavior in release notes.

Security signals we found

01

Rejects non-standard hybrid public-key encoding in transaction-related data

02

Narrows public-key acceptance to only compressed/uncompressed standard encodings

03

Applies consistent strict validation across keypath, signature, and blinding pubkey paths

04

Could prevent malleability or parsing confusion caused by hybrid-key representations

Risk score

Why this scored 47/100

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