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

feat(cardano): stop hashing in message signing

Public commit record

What the developer wrote

Authored by Peter Jaško

57/100 · Thin
feat(cardano): stop hashing in message signing
✓ 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 removes the option to sign a hash of a Cardano message instead of the message itself. The device now always signs the actual message payload directly, up to a size limit. This is a feature/API change rather than a fix for an active security flaw, but it does eliminate a mode where users might have signed data they could not fully inspect.

Recommended action

Treat this as a breaking API change. Wallets and integrations using `hash_payload=true` must be updated to send the full payload and remove the field. Users relying on hashed-message signing should verify compatibility before upgrading firmware or client libraries.

Security signals we found

01

Removed hash-then-sign mode for Cardano message signing

02

Firmware now signs raw message payload instead of a hash

03

Payload size capped at MAX_CHUNK_SIZE and only one chunk accepted

04

User confirmation now shows the raw payload rather than a message hash

05

Protobuf field renumbering breaks backward compatibility for the removed option

Risk score

Why this scored 32/100

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