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

SFT-7086: label OP_RETURN outputs and warn when they carry value

Public commit record

What the developer wrote

Authored by Jack

73/100 · Adequate
SFT-7086: label OP_RETURN outputs and warn when they carry value

Transaction review showed an OP_RETURN output as an amount followed by a
message, which reads like an ordinary payment with a note, and nothing
named the output or said the amount can never be spent.

- Review shows "Destination: OP_RETURN" above the message.
- The message is never blank. No payload shows "(empty)", and a payload
with nothing the review font can draw (it only carries printable ASCII)
falls back to its bytes in hex.
- When OP_RETURN outputs carry value, a "Burned Amount" warning reports
the total. Review pages through each warning before signing. This warns
rather than blocks: a valued OP_RETURN is standard and is sometimes
used on purpose.
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit improves the user interface shown when reviewing Bitcoin transactions that include OP_RETURN outputs. OP_RETURN outputs permanently destroy any bitcoins sent to them. Previously, the wallet displayed these outputs like a normal payment with a note, which could mislead a user into thinking the funds were spendable. The change now clearly labels the output as OP_RETURN, never leaves the message field blank, falls back to hex for unprintable characters, and shows a warning when any value is being burned. It is a defensive UX fix rather than a cryptographic vulnerability patch.

Recommended action

Treat as a security-relevant hardening improvement. Users should install the firmware update containing this commit, and developers should verify that the new warning page is shown during all OP_RETURN spend reviews. No immediate incident response is indicated by the commit itself.

Security signals we found

01

UI spoofing / social-engineering risk mitigated: OP_RETURN outputs previously resembled spendable payments with a memo

02

Non-printable OP_RETURN payloads now rendered as hex, preventing invisible or misleading message content

03

Empty OP_RETURN payloads explicitly labeled '(empty)' so the message field is never blank

04

Burned-value warning added for any satoshis sent to OP_RETURN outputs

05

Forged label injection in the message is escaped, preserving single real headings

Risk score

Why this scored 52/100

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