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

keep stored and followed paynym contacts over directory entries and their names, search the listed contacts, and show the payment code when linking

Public commit record

What the developer wrote

Authored by Craig Raw

50/100 · Thin
keep stored and followed paynym contacts over directory entries and their names, search the listed contacts, and show the payment code when linking
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit fixes a user-interface bug in Sparrow Wallet's PayNym contact handling. Previously, the wallet could mix up contacts that had the same display name but different payment codes, and it could overwrite a user's own stored contact names with names from the public PayNym directory. The change makes the wallet prefer contacts you have already saved or followed, lets you search the contact list, and shows the actual payment code when you link to someone so you can confirm it is the right person. It is a usability and correctness improvement rather than a fix for a remote exploit.

Recommended action

Treat as a normal bug-fix / UX-hardening commit. Reviewers may want to confirm that `followedPayNyms` is cleared appropriately when the wallet is closed or switched, and that the notification-address equality logic handles testnet/mainnet address prefixes correctly. No urgent security deployment is indicated by the diff alone.

Security signals we found

01

BIP47 payment-code / notification-address confusion is reduced by indexing contacts on notification address

02

Name-squatting / collision risk in the PayNym directory is mitigated by preferring stored and followed contacts over directory names

03

Link dialog now shows abbreviated payment code, improving user verification before creating a notification transaction

04

No input validation, cryptography, network, or privilege changes observed

Risk score

Why this scored 20/100

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