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

feat(tron): add TriggerSmartContract support.

Public commit record

What the developer wrote

Authored by PrisionMike

90/100 · Strong
feat(tron): add TriggerSmartContract support.

- Blind signing TRON smart contracts.
- Only contract address shown to user.
- USDT,USDD transfer tested.
- Fee layout imperfect. To be fixed later.

[no changelog]
✓ Descriptive subject✓ Names a concrete action or component✓ Uses a recognizable type or scope✓ Provides detailed explanatory context✓ Mentions testing or verification
The short version

What changed, and why it matters

This commit adds support for signing TRON smart-contract calls (like USDT/USDD transfers) on Trezor hardware wallets. Because the device cannot yet decode the actual token-transfer details, users are shown only the smart-contract address and raw data, meaning they are 'blind signing' the transaction. The commit message explicitly calls this out. There is also a fee-limit check to cap how much TRX can be burned, and a fix changing some timestamp/expiration fields from signed to unsigned integers.

Recommended action

Treat this as a notable security-relevant feature change rather than a vulnerability. Users should be warned that TRON smart-contract signing is currently blind and should only be used with trusted contracts. Developers should prioritize the TODO to parse TRC-20 transfer details (recipient, amount, token identity) so the device can show meaningful confirmation before signing. Review the fee-limit cap and unsigned-int change for correctness against TRON protocol limits.

Security signals we found

01

Blind signing of smart-contract data: only contract address shown, not recipient or amount

02

Fee-limit cap enforced in firmware to limit TRX burn for smart-contract calls

03

Field type change from signed to unsigned int64 for expiration/timestamp/fee_limit

04

New contract type added to allowed message types and raw contract enum

05

TODO comment indicating amount extraction from contract.data is not yet implemented

06

Commit message explicitly states 'Blind signing TRON smart contracts' and 'Only contract address shown to user'

Risk score

Why this scored 51/100

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