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

feat(ethereum): clear sign first 4kb

Public commit record

What the developer wrote

Authored by Ioan Bizău

57/100 · Thin
feat(ethereum): clear sign first 4kb

[no changelog]
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope! No meaningful explanatory body
The short version

What changed, and why it matters

This commit changes how Trezor handles Ethereum transaction data (calldata). Previously, clear signing only worked if the entire calldata fit in the first chunk sent by the host. Now the device actively requests and stores up to 4 KB of calldata so it can try clear signing on larger transactions. If clear signing succeeds, the user sees a human-readable confirmation instead of raw hex data. The change refactors the code to collect initial data before deciding whether to clear sign or fall back to blind signing. There is no direct evidence in the commit of a security vulnerability being fixed; it reads as a feature improvement.

Recommended action

Treat as a normal feature/refactor commit. Reviewers should verify that request_initial_data correctly bounds the collected data to MAX_DATA_STORED, that HashWriter state remains consistent across initial and subsequent chunks, and that falling back from clear signing to blind signing cannot be triggered by malformed calldata in a way that bypasses user confirmation. No immediate security response is indicated by the supplied materials.

Security signals we found

01

Behavioral change in transaction confirmation flow: device now requests up to 4 KB of calldata before deciding on clear vs blind signing

02

Clear signing previously limited to data_length <= len(data_initial_chunk); now supports multi-chunk calldata up to 4 KB

03

New exception base class ClearSigningFailed unifies InvalidFunctionCall and InvalidFormatDefinition handling

04

Removal of ParsingContext and its truncated flag; calldata truncation logic moved into request_initial_data

05

No explicit security bug, CVE, or advisory referenced in commit message or diff

Risk score

Why this scored 35/100

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