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

persist silent payment address mappings for safe rbf of sp-sending transactions

Public commit record

What the developer wrote

Authored by Craig Raw

50/100 · Thin
persist silent payment address mappings for safe rbf of sp-sending transactions
✓ Specific, descriptive subject✓ Names a concrete action or component! No meaningful explanatory body
The short version

What changed, and why it matters

This commit adds a safety feature for a new Bitcoin privacy technology called 'silent payments.' It records the relationship between a regular-looking payment address and its silent-payment counterpart in the wallet's database. The main goal is to prevent users from accidentally breaking silent-payment outputs when they later modify (RBF) a transaction, such as by removing inputs. The commit also blocks one risky UI action with a warning dialog when such a change would be unsafe.

Recommended action

Review the `clearAndAddAll` implementation for transactional safety and ensure the `silentPaymentAddress` table is included in backup/restore logic. Verify that the `isSafeToAddInputsOrOutputs` check covers all RBF/modification paths, not just input exclusion. Confirm the `drongo` submodule change aligns with the new persistence contract and does not introduce serialization incompatibilities.

Security signals we found

01

New database table storing address-to-silent-payment mappings

02

Persistence of silent payment metadata across wallet sessions

03

UI guard added to prevent unsafe input exclusion during RBF of silent-payment transactions

04

PSBT signing/combining/finalization paths now learn and store silent payment addresses

05

Potential data-loss risk if mapping is cleared and re-inserted transactionally (clearAndAddAll pattern)

06

No input validation or sanitization visible for serialized silent payment address bytes before DB insert

Risk score

Why this scored 30/100

Our methodology →
Potential impact 8/30
Exploitability 4/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.