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

Merge pull request #726 from Foundation-Devices/sft-7086-add-screen-confirming-amount-being-sent-to-op_return

Public commit record

What the developer wrote

Authored by mjg-foundation

73/100 · Adequate
Merge pull request #726 from Foundation-Devices/sft-7086-add-screen-confirming-amount-being-sent-to-op_return

SFT-7086: label OP_RETURN outputs and warn when they carry value
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Provides an explanatory body✓ Links an issue, advisory, or supporting reference
The short version

What changed, and why it matters

This commit adds safety warnings and clearer labels for a special kind of Bitcoin transaction output called OP_RETURN. Any bitcoins sent to an OP_RETURN output are permanently destroyed ('burned'). Previously, the wallet showed the amount and a user message but did not clearly tell the user the money was unspendable. The change also makes sure that if the OP_RETURN message contains unusual characters the device cannot display, it shows the raw bytes in hex instead of silently appearing blank, which could hide a hidden message or trick the user.

Recommended action

Treat as a security-hardening fix. Users should install the firmware update containing this commit, and developers should review whether any other user-controlled fields rendered during transaction signing can spoof labels or hide information.

Security signals we found

01

Adds explicit warning when value is sent to an unspendable OP_RETURN output

02

Prevents invisible or zero-width OP_RETURN messages by falling back to hex when no printable ASCII is present

03

Escapes user-controlled OP_RETURN payload to prevent it from spoofing UI labels such as amount or destination

04

Adds unit tests covering burn warning, multi-output aggregation, page ordering, and message rendering edge cases

Risk score

Why this scored 60/100

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