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

feat: 32 bytes amount in ETH payment requests

Public commit record

What the developer wrote

Authored by Ioan Bizău

57/100 · Thin
feat: 32 bytes amount in ETH payment requests

[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 payment-request amounts are encoded in Trezor firmware. Previously amounts were 8-byte numbers; now they can be 8 or 32 bytes, with 32 bytes used for Ethereum/EVM transactions. The change is a feature update to support larger EVM token amounts, not a clearly disclosed security fix. It does add length checks and an overflow guard, which reduces risk, but the change touches the trusted payment-request verification path, so any bug there could affect what amount the user is asked to approve.

Recommended action

Treat as a protocol-breaking feature change rather than a vulnerability. Review that all host-side libraries (Python, Rust, and third-party clients) are updated to send `bytes` at field 6, because old `uint64` values at field 4 will be ignored by the new firmware. Verify the length check and overflow assert cover all paths, and run the updated device tests for Bitcoin and Ethereum payment requests.

Security signals we found

01

Wire format change for a security-critical field (payment-request amount)

02

New length validation on amount bytes

03

Added overflow guard for MicroPython int.to_bytes() behavior

04

Ethereum payment requests now use 32-byte amounts

05

Field number 4 reserved, which can break older clients still sending uint64 at tag 4

Risk score

Why this scored 36/100

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