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

feat(clear_signing): ERC-7730 constant (const_value) display fields

Public commit record

What the developer wrote

Authored by PrisionMike

85/100 · Strong
feat(clear_signing): ERC-7730 constant (const_value) display fields

- constant path (resolved by offline parser)
- renamed `hint` to `is_mono` in clear signing
[no changelog]

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
✓ Specific, descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context
The short version

What changed, and why it matters

This commit adds a new way for Ethereum transaction definitions to include fixed text labels (called 'constant values') that are shown to the user during signing. It does not change how transaction data is parsed or signed, but it expands what untrusted display-format definitions can put on the device screen. The change is a feature addition, not a fix for a known bug, and there is no vendor statement that it is security-relevant.

Recommended action

Review whether `const_value` strings need length limits, character-set validation, or HTML/Unicode normalization before display, because they are supplied by host-side or downloaded ERC-7730 definitions and shown to the user during signing. Confirm that the UI layer treats them as untrusted display text and does not interpret them as commands or URLs.

Security signals we found

01

New untrusted input surface: `const_value` string in ERC-7730 display-format definitions is rendered to the user without length or content validation visible in the diff.

02

Display-only data path bypasses calldata parsing, so a malicious or compromised host-side definition could show arbitrary constant text alongside real transaction fields.

03

No input sanitization, escaping, or length limits are added for `const_value` in the changed code.

04

Renaming `hint` to `is_mono` is cosmetic and not a security signal.

05

No changelog entry and no vendor security disclosure language present.

Risk score

Why this scored 27/100

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