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

fix(cardano): ask detail level for datum outputs

Public commit record

What the developer wrote

Authored by Jakub Janků

80/100 · Strong
fix(cardano): ask detail level for datum outputs

Simple transactions skip the level of details prompt, which also hid
output datums and reference scripts although they are signed.

- ask for the level of details when the first output carrying Plutus
data is encountered
- add show-details fixtures for such simple transactions

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
(cherry picked from commit 801cf7033f96951eb17ab4c72ebfe94eac8ec6ee)
✓ 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 update fixes a user-interface bug in Trezor's Cardano transaction signing. For simple-looking Cardano transactions, the device was skipping the 'show details' prompt. Because of that, the user never saw important output data—specifically inline datums and reference scripts—even though those data are part of what the device signs. A malicious or buggy wallet app could have hidden those details from the user while still getting the device to sign them. The fix makes the device ask whether to show details as soon as it encounters an output containing Plutus data, so the user can review and decide.

Recommended action

Treat as a security fix and include in release notes. Users should upgrade firmware so that Cardano simple-transaction prompts reveal outputs containing datum/reference-script data before signing. Wallet software does not need changes, but should expect the new prompt.

Security signals we found

01

UI bypass / hidden signed data in simple Cardano transactions

02

Inline datum, reference script, and datum_hash outputs not shown to user before signing

03

New user prompt introduced for outputs containing Plutus data

04

Security changelog entry present: core/.changelog.d/+cardano-datum-prompt.security

05

Test fixtures added for ordinary transactions with datum/reference script

Risk score

Why this scored 60/100

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